Date: Wed, 18 Apr 2018 13:56:49 +0300 From: Vitalij Satanivskij <satan@ukr.net> To: John Baldwin <jhb@freebsd.org> Cc: Vitalij Satanivskij <satan@ukr.net>, freebsd-current@freebsd.org, cem@freebsd.org, Stephen Hurd <shurd@llnw.com>, Matthew Macy <mmacy@nextbsd.org>, "freebsd-hackers@freebsd.org" <hackers@freebsd.org>, Stephen Hurd <shurd@freebsd.org> Subject: Re: Current panic on boot on H11DSI motherboard with epyc cpu (nexus_add_irq: failed) Message-ID: <20180418105649.GA9989@hell.ukr.net> In-Reply-To: <3628282.XVdngBdGlp@ralph.baldwin.cx> References: <20180416102710.GA90028@hell.ukr.net> <3723755.0KMZDfyMWu@ralph.baldwin.cx> <20180417191553.GA95803@hell.ukr.net> <3628282.XVdngBdGlp@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
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);
}
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180418105649.GA9989>