Stack Trace: [46586.194135] general protection fault: 0000 [#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 joydev sb_edac edac_core hpilo lpc_ich ioatdma dca shpchp wmi xfs ipmi_si 8250_fintek ipmi_msghandler tpm_infineon acpi_power_meter mac_hid libcrc32c bonding lp parport raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic psmouse raid6_pq sfc raid1 usbhid raid0 mtd hid tg3 pata_acpi i2c_algo_bit multipath ptp mdio hpsa pps_core linear [46586.206368] CPU: 24 PID: 53367 Comm: udevadm Not tainted 4.2.0-30-generic #36~14.04.1-Ubuntu [46586.207925] Hardware name: HP ProLiant DL380p Gen8, BIOS P70 07/01/2015 [46586.208898] task: ffff880386240000 ti: ffff880130fac000 task.ti: ffff880130fac000 [46586.210030] RIP: 0010:[<ffffffffc0030ddc>] [<ffffffffc0030ddc>] host_show_lockup_detected+0x2c/0x50 [hpsa] [46586.213065] RSP: 0018:ffff880130fafd88 EFLAGS: 00010282 [46586.213882] RAX: 2030203020302030 RBX: ffffffffc00422e0 RCX: ffff88274bb66000 [46586.215502] RDX: ffff881fbf980000 RSI: ffffffffc00422e0 RDI: ffff881fb1416968 [46586.216560] RBP: ffff880130fafd88 R08: ffff881fb1416978 R09: 0000000000000000 [46586.217616] R10: 0000000000001000 R11: 0000000000000246 R12: ffffffff818749b0 [46586.218674] R13: 0000000000000001 R14: ffff880130faff20 R15: ffff881fb1d46180 [46586.219969] FS: 00007f060a57d880(0000) GS:ffff881fbf980000(0000) knlGS:0000000000000000 [46586.221181] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [46586.222000] CR2: 0000000001748000 CR3: 0000000a6ad8f000 CR4: 00000000001406e0 [46586.223039] Stack: [46586.223334] ffff880130fafdb8 ffffffff814f0eb0 ffff88274bb66000 ffffffff817ba686 [46586.224518] ffff881fa016aa00 ffff881fb1d46180 ffff880130fafdd8 ffffffff81263bc2 [46586.225716] 0000000000000000 ffff881fa016aa00 ffff880130fafde8 ffffffff81262413 [46586.227165] Call Trace: [46586.227539] [<ffffffff814f0eb0>] dev_attr_show+0x20/0x50 [46586.228313] [<ffffffff817ba686>] ? mutex_lock+0x16/0x37 [46586.229113] [<ffffffff81263bc2>] sysfs_kf_seq_show+0xc2/0x1a0 [46586.229957] [<ffffffff81262413>] kernfs_seq_show+0x23/0x30 [46586.231564] [<ffffffff8120d8a5>] seq_read+0xe5/0x350 [46586.232303] [<ffffffff81262bcd>] kernfs_fop_read+0x10d/0x170 [46586.233180] [<ffffffff811ea708>] __vfs_read+0x18/0x40 [46586.233947] [<ffffffff811eace6>] vfs_read+0x86/0x130 [46586.235451] [<ffffffff811ebb06>] SyS_read+0x46/0xa0 [46586.236180] [<ffffffff817bc332>] entry_SYSCALL_64_fastpath+0x16/0x75 [46586.237160] Code: 1f 44 00 00 55 48 89 d1 48 8b 87 e0 02 00 00 48 89 e5 65 8b 15 a6 93 fd 3f 48 63 d2 48 8b 80 b8 4b 00 00 48 8b 14 d5 80 c1 d2 81 <8b> 14 02 48 c7 c6 5c fb 03 c0 48 89 cf 31 c0 e8 50 0b 38 c1 5d [46586.242101] RIP [<ffffffffc0030ddc>] host_show_lockup_detected+0x2c/0x50 [hpsa] [46586.243446] RSP <ffff880130fafd88>
-- 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: New 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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
