kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #179233
[Bug 1581169] Re: kernel panic (General protection fault) on module hpsa (lockup_detected)
Here's a test kernel based on "4.2.0-36.42~14.04.1" including the
upstream commit "fb53c439 - hpsa: move lockup_detected attribute to host
attr".
Please test and provide feedbacks.
Instructions:
# Pre-installation
$ sudo add-apt-repository ppa:slashd/bug1581169
$ sudo apt-get update
# Installation
$ sudo apt-get install linux-image-4.2.0-36-generic=4.2.0-36.42~14.04.1hf98078v20160516b1 -y
$ sudo apt-get install linux-image-extra-4.2.0-36-generic=4.2.0-36.42~14.04.1hf98078v20160516b1 -y
$ sudo apt-get install linux-headers-4.2.0-36-generic=4.2.0-36.42~14.04.1hf98078v20160516b1 -y
# Reboot
$ sudo reboot
Eric
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1581169
Title:
kernel panic (General protection fault) on module hpsa
(lockup_detected)
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Wily:
Triaged
Bug description:
it has been brought to my attention the following:
Kernel version: 4.2.0-30-generic #36~14.04.1-Ubuntu
When running an sosreport on HP DL380 gen8 machines running this
kernel (Ubuntu 14.04.4 using linux-generic-lts-wily), which includes
hpsa 3.4.10-0, hspa causes a kernel panic when sosreport is scanning
block devices. These are machines with an onboard p420i and
daughtercard p420 RAID controller, with each drive in a single raid0
configuration. (unideal, but the machines do not boot when the card is
in HBA mode).
This panic does not happen on kernel 3.13 with hpsa 3.4.1-0 when using
sosreport.
The funny thing is kernel 4.2 / 3.4.10-0 still is a more stable
solution - I have yet to see a prior issue in which the p420 would
lock up on this version. One issue wit h this is HP 99% of the time
will require an sosreport when we raise any hardware issues. I can no
longer produce that on kernel 4.2 machines because they kernel panic.
I can reproduce this consistently with several other machines in our
environment. - please let me know if you would like more info.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581169/+subscriptions
References