Date: Mon, 16 Apr 2018 10:27:36 -0700 From: Conrad Meyer <cem@freebsd.org> To: Vitalij Satanivskij <satan@ukr.net> Cc: "freebsd-hackers@freebsd.org" <hackers@freebsd.org>, freebsd-current <freebsd-current@freebsd.org>, Stephen Hurd <shurd@freebsd.org>, Sean Bruno <sbruno@freebsd.org>, Matthew Macy <mmacy@nextbsd.org> Subject: Re: Current panic on boot on H11DSI motherboard with epyc cpu (nexus_add_irq: failed) Message-ID: <CAG6CVpWgMz1Hosb9Q=4ZmVZv4WMCwZq5FGTpNS=m4ShfZcO%2BBg@mail.gmail.com> In-Reply-To: <20180416102710.GA90028@hell.ukr.net> References: <20180416102710.GA90028@hell.ukr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Vitalij, On Mon, Apr 16, 2018 at 3:27 AM, Vitalij Satanivskij <satan@ukr.net> wrote: > DUMP can be found here http://hell.ukr.net/panic/panic.jpg > or even video record from screen http://hell.ukr.net/panic/recorder.webm Looks like the panic message is printed directly after: "igb0: using 2 rx queues 2 tx queues" (iflib_msix_init(), called by iflib_device_register()). And stack is indeed coming from iflib in probe (0:17 in linked video): panic() nexus_add_irq() msix_alloc() pci_alloc_msix_method() iflib_device_register() iflib_device_attach() device_attach() ... Stephen, Matt, or Sean might be able to help diagnose further. Best, Conrad
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG6CVpWgMz1Hosb9Q=4ZmVZv4WMCwZq5FGTpNS=m4ShfZcO%2BBg>