From owner-freebsd-current@freebsd.org Wed Apr 18 18:42:51 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 93608FA1936; Wed, 18 Apr 2018 18:42:51 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 36FE97989A; Wed, 18 Apr 2018 18:42:51 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id 342B310AFAD; Wed, 18 Apr 2018 14:42:50 -0400 (EDT) From: John Baldwin To: Vitalij Satanivskij Cc: freebsd-current@freebsd.org, cem@freebsd.org, Stephen Hurd , Matthew Macy , "freebsd-hackers@freebsd.org" , Stephen Hurd Subject: Re: Current panic on boot on H11DSI motherboard with epyc cpu (nexus_add_irq: failed) Date: Wed, 18 Apr 2018 11:42:41 -0700 Message-ID: <1616582.sIejGazfcv@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; ) In-Reply-To: <20180418105649.GA9989@hell.ukr.net> References: <20180416102710.GA90028@hell.ukr.net> <3628282.XVdngBdGlp@ralph.baldwin.cx> <20180418105649.GA9989@hell.ukr.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Wed, 18 Apr 2018 14:42:50 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Apr 2018 18:42:51 -0000 On Wednesday, April 18, 2018 01:56:49 PM Vitalij Satanivskij wrote: > 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); > } Ohhhh, this is a different issue. Sorry. As a hack, try changing 'FIRST_MSI_INT' to 512 in sys/amd64/include/intr_machdep.h. The issue is that some systems now include more than 256 interrupt pins on I/O APICs, so IRQ 256 is already reserved for use by one of those interrupt pins. The real fix is that I need to make FIRST_MSI_INT dynamic instead of a constant and just define it as the first free IRQ after the I/O APICs have probed. -- John Baldwin