Proxmox 3.4, kernel 2.6.32-48-pve, aacraid - kernel panic

dar_ek

Renowned Member
Feb 6, 2013
4
0
66
Dear All,

I have a problem with new kernels 2.6 patched to CVE-2016-5195 (Dirty COW).

I'd got Kernel Panic at boot on module aacraid.

aacraidkernelpanic.jpg


Kernels with kernel panic:
  • pve-kernel-2.6.32-47-pve (2.6.32-180)
  • pve-kernel-2.6.32-48-pve (2.6.32-182)
Old kernel without problem: pve-kernel-2.6.32-39-pve (2.6.32-157)

Controller Model: Adaptec 5805

On second machine with other adaptec controller - give me same - Kernel Panic (with similar, but not identical mainboard).

Adding some kernel options not resolve problem eg.: noapic scsi_scan=sync pci=nomsi,nommconf pci=nocrs

please help me, thank you...
 
  • Like
Reactions: Ramil and dar_ek
perhaps related to what we also just found out:
=> update aacraid sources to aacraid-linux-src-1.2.1-50667.tgz
you find out that the whole line of 5xxx-controllers is not supported by this release any more...

Thank you for reply.

well, do You have an idea how to solve this? downgrade module?


ps. I will test Proxmox 4 today. But I'm not ready to migration yet..
 
Thank you for reply.

well, do You have an idea how to solve this? downgrade module?
not yet - as i said, we just discovered this issue...
for now, we'll point grub to 2.6.32-46 kernel. perhaps dkms is an option...

ps. I will test Proxmox 4 today. But I'm not ready to migration yet..

interestingly, PVE4 still uses the older, working aacraid driver...
 
Just got same on two production servers with adaptec raid cards 3405 and 2405
Revert back to 2.6.32-46 kernel.
 
Just got same on two production servers with adaptec raid cards 3405 and 2405
Revert back to 2.6.32-46 kernel.

Try add aacrid via DKMS to 2.6.32.48.

Eg. my install downloaded driver aacraid-1.1.7.29100-dkms.noarch.rpm

Code:
# unpack driver
rpm2cpio aacraid-1.1.7.29100-dkms.noarch.rpm | cpio -i --make-directories
# copy to /usr/src/aacraid-1.1.7.29100
cp -a usr/src/aacraid-1.1.7.29100 /usr/src/

# install kernel headers
apt-get install pve-headers-2.6.32-48-pve

dkms add -m aacraid -v 1.1.7.29100
dkms build -m aacraid -v 1.1.7.29100 -k 2.6.32-48-pve
dkms install --force --verbose -m aacraid -v 1.1.7.29100 -k 2.6.32-48-pve
 
Dear All,

I have a problem with new kernels 2.6 patched to CVE-2016-5195 (Dirty COW).

I'd got Kernel Panic at boot on module aacraid.


Kernels with kernel panic:
  • pve-kernel-2.6.32-47-pve (2.6.32-180)
  • pve-kernel-2.6.32-48-pve (2.6.32-182)
Old kernel without problem: pve-kernel-2.6.32-39-pve (2.6.32-157)

Controller Model: Adaptec 5805

.

Hi, i've the some problem on two Supermicro server....
see my post: https://forum.proxmox.com/threads/u...4-upgrade-to-latest-kernel.29699/#post-149924
 
I confirm that.

Controller Model: Adaptec 5405Z

Kernels 2.6.32-{47,48}-pve with new aacraid module are affected.

Temporary fix is to boot into older kernel - 2.6.32-46-pve.

Maybe there is way to put old AND new aacraid modules?
Use some udev rules to load proper module?
 
Last edited:
Same problem here with Adaptec 5405 after upgrade to Kernels 2.6.32-{47,48}-pve.

Servers with Adaptec 6405 works fine.
 
I also stayed with pve-kernel-2.6.32-46-pve. Adaptec 5405z.
I didn't have similar controller to test with new Proxmox 4.4.

Did anyone successful upgrade from Proxmox 3.4 with 2.6.32-46-pve to Proxmox 4.0 and then to newer version?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!