Bug 201199 - hpsa blocking boot on HP smart Array P410
Summary: hpsa blocking boot on HP smart Array P410
Status: NEW
Alias: None
Product: IO/Storage
Classification: Unclassified
Component: SCSI (show other bugs)
Hardware: Intel Linux
: P1 normal
Assignee: linux-scsi@vger.kernel.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-22 00:23 UTC by Seb Lu
Modified: 2018-10-26 14:11 UTC (History)
0 users

See Also:
Kernel Version: 4.18.3
Subsystem:
Regression: No
Bisected commit-id:


Attachments
boot failure message (148.19 KB, image/png)
2018-09-22 00:24 UTC, Seb Lu
Details
boot udevd traceback (150.97 KB, image/png)
2018-09-22 00:24 UTC, Seb Lu
Details
config for 4.19-rc4 (160.68 KB, text/plain)
2018-09-22 00:25 UTC, Seb Lu
Details
config for 4.15.0-22 (working ubuntu) (211.73 KB, text/x-mpsub)
2018-09-22 00:25 UTC, Seb Lu
Details
bios version (141.69 KB, image/png)
2018-09-22 00:26 UTC, Seb Lu
Details
controller version (41.92 KB, image/png)
2018-09-22 00:26 UTC, Seb Lu
Details
lspci (4.96 KB, text/plain)
2018-09-22 00:26 UTC, Seb Lu
Details

Description Seb Lu 2018-09-22 00:23:56 UTC
Hello,

I lease an HP Proliant server, with an Intel Xeon E31220 @3.10Ghz, 16GHz RAM and  a Hewlett-Packard Smart Array P410. The operating system is an (up to date) Arch Linux. The Smart Array P410 firmware version is 6.64 (the last one, from 2015), the BIOS was updated to the last version (from 2018).

I have an issue I cannot understand an my investigations are currently stalled.
I cannot boot any Arch or vanilla kernels newer than 4.9.x. The last and currently booted is a 4.9.128 (config will be attached). Any higher version I tested, up to 4.19-rc4, are stalled because disks are not detected.

As a side note, the issue looks like bug #199703, but the solution was to upgrade the controller firmware to the last version, which is my case, didn't fix the issue.

I will attach the error screenshots from the console, but basically, looks like the hpsa didn't detect the hard drives and systemd-udevd is stalled.
Not sure it's important, but it's not possible to rmmod hpsa module with the initramfs fallback shell.

I tried to play with hpsa_allow_any=1, scsi_mod.scan=sync, iommu=off but nothing helped.

Then, I tried to boot with a live cd of ubuntu 18.04 (kernel 4.15.0-22), and it worked. So, I used the config file from this kernel and built a vanilla kernel (ubuntu 4.15.0-22 is based on a vanilla 4.15.17) to boot on. Unfortunately it didn't worked, still stalled at boot.

So, I took the ubuntu bionic 4.15.0-22 kernel sources and I built a kernel to boot my Arch Linux with. It didn't work neither.

So, I took the already compiled Ubuntu kernel and initramfs from the livecd to boot with. And it booted! There were expected issues with missing modules but the hpsa worked and the drives was detected.

That's weird, because there is a difference between my built from bionic sources and the one ubunbu did I cannot explain. I don't think the toolchain version, like GCC recent version require a patch to built objtool, should be a reason of booting or not.

So, I'm stuck with no idea to where I should dig. I need some help, do you have suggestions?
Comment 1 Seb Lu 2018-09-22 00:24:17 UTC
Created attachment 278699 [details]
boot failure message
Comment 2 Seb Lu 2018-09-22 00:24:43 UTC
Created attachment 278701 [details]
boot udevd traceback
Comment 3 Seb Lu 2018-09-22 00:25:22 UTC
Created attachment 278703 [details]
config for 4.19-rc4
Comment 4 Seb Lu 2018-09-22 00:25:50 UTC
Created attachment 278705 [details]
config for 4.15.0-22 (working ubuntu)
Comment 5 Seb Lu 2018-09-22 00:26:11 UTC
Created attachment 278707 [details]
bios version
Comment 6 Seb Lu 2018-09-22 00:26:23 UTC
Created attachment 278709 [details]
controller version
Comment 7 Seb Lu 2018-09-22 00:26:47 UTC
Created attachment 278711 [details]
lspci
Comment 8 Seb Lu 2018-10-26 14:11:34 UTC
Hello,

Any idea? Any test I can do to find what's wrong?

Note You need to log in before you can comment on or make changes to this bug.