** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Summary changed:
- kernel panic (General protection fault) on module hpsa (lockup_detected)
+ General protection fault panic on module hpsa with lockup_detected attribute
--
You received this bug notification because
** Tags removed: verification-needed-wily
** Tags added: verification-done-wily
--
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
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
wily' to 'verification-done-wily'.
If verification is not done by 5 working days from
** Changed in: linux (Ubuntu Wily)
Status: In Progress => Fix Committed
--
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
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Wily)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
An email has been sent to "kernel-t...@lists.ubuntu.com" for an SRU on
Wily.
--
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
Here's what has been brought to my attention :
I've now got everything installed and confirm the kernel build
(42~14.04.1hf98078v20160516b1-Ubuntu) with sosreport and udevadm probe
succeeds on 4 affected machines.
It looks like this solves the issue.
** Changed in: linux (Ubuntu)
Assignee:
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
#
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Tags added: kernel-da-key wily
** Also affects: linux (Ubuntu Wily)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Wily)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Wily)
Hi Brad,
I do have a vmcore + dmesg, but this is very large (total: ~16GB).
I will provide the test kernel based on Ubuntu-lts-4.2.0-36.41_14.04.1
including commit "fb53c43" and ask my contact to test it and confirm if
it mitigate the issue on their affected systems where they can reproduce
the
According to the vmcore[1], the crash seems to occur while performing
the "udevadm"[2] command which is part of the sosreport under the block
plugin.
[1] - vmcore
KERNEL: /usr/lib/debug/boot/vmlinux-4.2.0-30-generic
DUMPFILE: dump.201605101421 [PARTIAL DUMP]
CPUS: 40
DATE: Wed Dec 31 19:00:00
Possible commit to fix the issue, found upstream:
I'll create a testfix and will make it public shortly.
$ git show fb53c43
commit fb53c439d84387621c53808a3957ffd9876e5094
Author: Tomas Henzl
Date: Fri Nov 6 16:24:09 2015 +0100
hpsa: move lockup_detected attribute to host
The problem is reproducible on demand :
root@dob2-bfs-r5n09:~# udevadm --debug info -ap /sys/block/sdf
calling: info
device 0x154a300 has devpath
'/devices/pci:00/:00:02.2/:02:00.0/host2/target2:0:0/2:0:0:5/block/sdf'
Udevadm info starts with the device specified by the devpath and
Stack Trace:
[46586.194135] general protection fault: [#1] SMP
[46586.194933] Modules linked in: ipmi_ssif x86_pkg_temp_thermal
intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul
aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw
input_leds
According to the vmcore[1], the crash seems to occur while performing
the "udevadm"[2] command which is part of the sosreport under the block
plugin.
[1] - vmcore
KERNEL: /usr/lib/debug/boot/vmlinux-4.2.0-30-generic
DUMPFILE: dump.201605101421 [PARTIAL DUMP]
CPUS: 40
DATE: Wed Dec 31 19:00:00
We can confirm this is the last line we see regardless of the disk:
ATTRS{ioerr_cnt}=="0x2"
On a working disk the next line is :
"ATTRS{lockup_detected}"
It seems to stuck at the lockup_detected attribute.
--
You received this bug notification because you are a member of Kernel
Packages,
16 matches
Mail list logo