Fix ichwd(4) shutdown crash
Intel Xeon E5-2603v4
Asus X99-M WS/SE Intel X99 So.2011-3
32 GB RAM ECC
I am seeing a crash each time I issue a reset or shutdown of my machine. Already did several reinstallations.
Attaching stacktrace and verbose mode boot messages.
#2 Updated by Peter Oruba over 3 years ago
I counterchecked by installing FreeBSD-11.0-RELEASE-amd64 and Ubuntu Server 17.04 and both properly poweroff my machine.
FreeNAS 9.10 leads into a crash, too, when resetting or powering off, but instead of bringing me to the kernel debugger's console it gets stuck in a loop.
#3 Updated by Alexander Motin over 3 years ago
- Status changed from Unscreened to Screened
- Priority changed from No priority to Important
- Target version set to 11.1
This looks like a possible bug in ichwd driver, may be because it calls ichwd_detach() for shutdown event, that, as I suspect, somehow calls it twice. It is surprising that this problem is not reported more widely.
But in your dmesg I also see that you are running debug kernel. Was it enabled intentionally? Does this crash happen for non-debug kernel also?
#8 Updated by Michael de Silva over 3 years ago
Hi all -
Just to give you some context, this is my hardware config
- Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz
- 32GB Crucial RDIMMs ECC RAM (2x16GB)
- Asus X99-E WS/USB3.1
I've setup a new FreeNAS 11 box and during shutdowns I'm also experiencing the panic issue. Output from `devinfo -vr` may be found here: https://gist.github.com/bsodmike/0a97281e359111e6c7ad2e2a47344e41
Here's a snap of the panic: https://photos.app.goo.gl/UpAhKn1METXTIPE52
#9 Updated by Alexander Motin over 3 years ago
- Subject changed from Crash at shutdown / reset to ichwd(4) crash at shutdown / reset
- Status changed from 15 to Fix In Progress
I see the problem now. Unlike all systems I have access to, your system reports ISA bridge in two ways same time: as PCI device, and as ACPI device. The second path is handled first by the OS device scan process, while the second quietly fails. It would be OK if not the terrible horror of ichwd(4) driver resource allocation. It more or less works in case of ISA bridge attached to PCI device, but doesn't in case of ACPI.
I've made a patch to make ichwd(4) driver attach only to ISA attached to PCI bridge, that supposedly should fix the crash.
As alternative workaround I guess setting such loader tunable may help: debug.acpi.disabled="isa". Make sure to create boot environment for recovery before adding this via UI in case I am wrong.