New Proxmox VE kernel branch 2.6.35 - with KSM support
- Thread starter martin
- Start date
Seems a bug in the LPFC driver. Maybe you can report that to the hardware vendor - maybe they have a fix for it? Or report it directly to www.emulex.com - I don't know if they have a support forum.
# modinfo lpfc
filename: /lib/modules/2.6.35-1-pve/kernel/drivers/scsi/lpfc/lpfc.ko
version: 0:8.3.12
author: Emulex Corporation - tech.support@emulex.com
description: Emulex LightPulse Fibre Channel SCSI driver 8.3.12
Last edited:
Ok, I was testing proxmox for a few days. And now want to go for live enviroment. But about kernel choosing, do I have to choose one? I want to get future updates so want to choose one that proxmox will support and improve in future. Will that be 2.6.35 ?
Thanks
L
linuxdatacenter
Guest
Hello,
If you give me the source of the 2.6.35 kernel (I don't know whether it's plain 2.6.35 from ubuntu), I might see what the problem is with Emulex.
If you give me the source of the 2.6.35 kernel (I don't know whether it's plain 2.6.35 from ubuntu), I might see what the problem is with Emulex.
L
linuxdatacenter
Guest
Hi,
Just found a fix for the emulex lpfc driver.
Could you please turn on this parameter in 2.6.35?
-# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set +CONFIG_CC_OPTIMIZE_FOR_SIZE=y
Just found a fix for the emulex lpfc driver.
Could you please turn on this parameter in 2.6.35?
-# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set +CONFIG_CC_OPTIMIZE_FOR_SIZE=y
This morning my server wouldn't boot, it was using kernel pve-kernel-2.6.35-1-pve_2.6.35-3.
I'm not so wise to decipher the syslog myself, so I'm hosting it temporarily here for review in case it can be helpful for the devs.
It was at line 1291 when I attached the local terminal.
The second boot went along without issue, I included the extra lines of the good boot's syslog because the previous failed boot attempt included a 10 minute gap at line 1210 prior to it's halting completely.
In response I've upgraded to pve-kernel-2.6.35-1-pve_2.6.35-5 and will continue to monitor.
Perhaps it's worth noting that after upgrading to this version, I did not have to run
...The network remained functional without doing so.
I'm not so wise to decipher the syslog myself, so I'm hosting it temporarily here for review in case it can be helpful for the devs.
It was at line 1291 when I attached the local terminal.
The second boot went along without issue, I included the extra lines of the good boot's syslog because the previous failed boot attempt included a 10 minute gap at line 1210 prior to it's halting completely.
In response I've upgraded to pve-kernel-2.6.35-1-pve_2.6.35-5 and will continue to monitor.
Perhaps it's worth noting that after upgrading to this version, I did not have to run
Code:
#update-initramfs -uPlease can you test with the latest availavle version: pve-kernel-2.6.35-1-pve_2.6.35-6_amd64.deb
Yes, I fixed the dependency problem.
hpacucli is not compatible with 2.6.32 or later kernel. Last supported kernel is 2.6.24.
Good new but HP say 2.6.24 only.
I tested with hpacucli_8.50-6.0.3-3 and Promox 1.6. The kernel freeze at boot .
Have a look on this topic: http://forum.proxmox.com/threads/4725-1.6-upgrade-failed-gt-PTE-Read-access-is-not-set