Dell Precision Tower 5820 - FlexBay MiniSAS PCIe NVMe SSD not recognized

[hlalex]

@george1421 No luck on version E. We got the APST feature error, however FOS failed with a kernel panic.

[hlalex]

@george1421 Not a problem! FOG has saved me countless hours of manual configuration over the years, and until this recent batch of hardware I have not come across an issue that wasn’t already answered/fixed in another post. I am happy to help in any way I can, and hopefully save someone else (and possibly my future self) a lot of headache. We got extremely lucky with the unequal exchange approval from Dell, and other techs may not get the same break (It took 2 days and many hours on the phone/sending emails to get the exchange).

[george1421]

@hlalex You didn’t do anything specific with the init.xz did you?

[hlalex]

@george1421 Didn’t touch it at all. I thought about changing it to init_32.xz, but decided to wait for you.

[george1421]

@hlalex No don’t use the 32 bit inits, that will break for sure. I’m building version ‘F’ this time. The APST error is related to APSM kernel feature turned on. I turned it on because it looked like it was part of pcie hot plug. I’ll IM you when the build is done.

If this one doesn’t work (I understand some of the error messages posted in the picture), I’m going to revert back to a stock kernel build and then go in and enable just the PCI hot plug stuff since I may have flipped too many switches trying to make it work. I’m pretty sure I’m in the right neighborhood now.

[hlalex]

@george1421 F produced a similar kernel panic:

[george1421]

@hlalex Ok then rolling back to the stock FOS kernel settings and only turning on hotplug was the right place to start with. The G should be done shortly. I’m going to try to boot the kernel locally first to make sure it gets past the init on my hardware before testing on your kit.

[george1421]

Version G (reset) was sent via IM and on the plus side it did not blow up during my testing.

[hlalex]

@george1421 Sorry, got caught up with some other issues. I tried G, but it hangs at

Configuring (net0 xx:xx:xx:xx:xx:xx)... ok
http://ip.addr/fog/service/ipxe/boot.php... ok
bzImage41713g... ok
init.xz... ok
_

I have double checked and init.xz is still set as default.

Hang on, just found an issue with the BIOS. Testing D - G again to see if it had any effect.

[hlalex]

@george1421 Ok, double checked everything and it appears the bios change didn’t have any effect on the output of any kernels. Same errors and freezes.

[george1421]

@hlalex Ok I’m going to have to take it back into the LAB, because it didn’t do this when I tested. I’ll grab a 7060 (newest bit of hardware I have at the moment) and see why its going sideways.

If this wouldn’t have worked before I would say its the hand-off between iPXE and the uefi firmware. (because with faulty firmware we have seen it hang at this exact spot in the past) But I think you were running in bios mode the last time I look at the logs. I won’t keep pushing tests to you until I’m sure I have it booting correctly on my newest hardware.

[george1421]

Well I’m a bit confused now. The ‘G’ version works correctly on a 3050 as well as a 7060. There is a short delay after bzImage is copied before the kernel starts, like 3-4 seconds where initially I thought that it crashed like on your system.

In your environment, can you roll back to the C-G bzImages and ensure the older ones still boot? For the G build, I went back to FOG defaults and then only enabled hotplug. There might be other things that I turned on that is needed for hotplug. Rolling back to an earlier boot kernel on your end will tell me where to look in the config files.

[hlalex]

@george1421 Same here, The 5820 bios has some different options regarding NVMe drives connected to the FrontFlex Bay. These devices actually show up in bios, while the same drive connected via PCIe adapter does not populate under any bios menu that I have located. This suggest something is very different at the bios level for the two connection methods.

version C

• Boots
• Error parsing PCC subspaces from PCCT
• NVMe not in lsblk

version D

• Boots
• Error parsing PCC subspaces from PCCT
• nvme nvme0: failed to set APST feature (-19)
• NVMe not in lsblk

version E

• Kernel Panic
• Error parsing PCC subspaces from PCCT
• pciehp 0000:b2:02.0:pcie004: Slot(12): Power Fault
• pciehp 0000:b2:03.0:pcie004: Slot(13): Power Fault
• acpiphp_ibm: ibm_acpiphp_init: acpi_walk_namespace failed
• nvme nvme0: failed to set APST feature (-19)
• (/sbin/init & /bin/sh) exists but couldn’t execute it (error -8)

version F

• kernel panic
• Error parsing PCC subspaces from PCCT
• acpiphp_ibm: ibm_acpiphp_init: acpi_walk_namespace failed error
• (/sbin/init & /bin/sh) exists but couldn’t execute it (error -8)

version G

• Boots (No idea what I was doing wrong before…)
• Error parsing PCC subspaces from PCCT
• bzImage41713g.log
• bzImage41713g_lsmod.log

[george1421]

@hlalex Thank you for taking the time to test all of these kernels. I’m glad ‘G’ is working correctly. Let me take a look at the logs you provided so I can keep pushing forward. I understand about ‘F’ crashing, I simply added some settings that sounded good without first researching. That is why I did the reset with ‘G’.

I’ll touch base again when I have a chance to digest your new logs.

[hlalex]

@george1421 If you would like I can upload the bash script I am using to collect the data. Its very basic, but it speeds things up quite a bit (and automatically masks personal info).

[george1421]

@hlalex I’m in the process of rebuilding the kernel for the ( i ) release. One thing I discovered is that I need to have a better change management process in place. I compared your latest syslog with the output from FC27 and I see the error messages I fixed in an earlier release back in the syslog (mainly because I reset the configuration back to a known good setting and did not have good enough documentation on what I changed to get me to that point). Its a bit like starting over, but with the knowledge I fixed the issue once before.

The i build has the pcie hot plug enabled plus MTD support (I think your solution is a combination of drivers that need to be enabled). I’m interested in the results you will generate from this build as compared to the previous one. The level of detail you are providing is excellent.

As for the error “Error parsing PCC subspaces from PCCT” that error is actually present in both FOS and FC27 kernels.

[hlalex]

@george1421 rev I logs:

• bzImage41713i.log
• bzImage41713i_lshw.log

[george1421]

Well, I found out why version E was so close but blew up with the inits. Actually I was chatting with one of the developers and he actually called the problem 2 days ago. He said the inits were mismatched with the kernel architecture (i.e. 64 bit kernel with 32 bit inits). I found it was actually the other way around, the kernel switched to 32 bits and you were trying to boot with the 64 bit inits. I have no idea why the kernel settings switched with the ‘E’ version.

I found this doing a side by side comparison with the kernel build config files. So in the end we were really close, but I shot myself in the foot.

I have a bit more time today so hopefully we can get this knocked out.

[hlalex]

@george1421 No worries! I run into gremlins like that all the time. I’ll keep an eye out for updates.

[hlalex]

@george1421 rev J boots just fine, but I did notice an error message to the effect of “/dev … error creating epoll fd”. It was gone almost before I saw it, but that is what I was able to remember. I vaguely remember seeing this error before, but I do not know if it was with any of the other test kernels or some other project.

Here are the logs:

• bzImage41713j.log
• bzImage41713j_lshw.log