Current panic on boot on H11DSI motherboard with epyc cpu (nexus_add_irq: failed)
Vitalij Satanivskij
satan at ukr.net
Wed Apr 18 10:56:54 UTC 2018
JB> > If you need any aditional information please tell me about.
JB>
JB> Can you perhaps turn off the stack trace on boot to not lose the panic messages
JB> (remove KDB_TRACE from kernel config) and maybe modify the panic message to
JB> include the IRQ number passed to nexus_add_irq?
Hm looks like it's always irq with number 256
eg hpet - 256
igb - 256
Chenged made for it was
Index: sys/x86/x86/nexus.c
===================================================================
--- sys/x86/x86/nexus.c (revision 332663)
+++ sys/x86/x86/nexus.c (working copy)
@@ -698,7 +698,7 @@
{
if (rman_manage_region(&irq_rman, irq, irq) != 0)
- panic("%s: failed", __func__);
+ panic("%s: failed irq is: %lu", __func__, irq);
}
More information about the freebsd-hackers
mailing list