From owner-freebsd-current@freebsd.org Tue Apr 17 21:21:10 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 7312DF9C2D4; Tue, 17 Apr 2018 21:21:10 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (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 2690F7F6AE; Tue, 17 Apr 2018 21:21:09 +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 4BD8D10AFAD; Tue, 17 Apr 2018 17:21:02 -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: Tue, 17 Apr 2018 13:42:19 -0700 Message-ID: <3628282.XVdngBdGlp@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; ) In-Reply-To: <20180417191553.GA95803@hell.ukr.net> References: <20180416102710.GA90028@hell.ukr.net> <3723755.0KMZDfyMWu@ralph.baldwin.cx> <20180417191553.GA95803@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); Tue, 17 Apr 2018 17:21:02 -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: Tue, 17 Apr 2018 21:21:10 -0000 On Tuesday, April 17, 2018 10:15:53 PM Vitalij Satanivskij wrote: > Dear John > > I'm try patch with no success > > http://hell.ukr.net/panic/recorder_patch165.webm > > Also I'm enable verbose boot and record boot process (hpet was disabled so crash in another driver atach) > http://hell.ukr.net/panic/recorder_patch_verbose.webm > > root@test:/usr/src # svnlite diff > Index: sys/x86/x86/msi.c > =================================================================== > --- sys/x86/x86/msi.c (revision 332650) > +++ sys/x86/x86/msi.c (working copy) > @@ -404,7 +404,7 @@ > /* Do we need to create some new sources? */ > if (cnt < count) { > /* If we would exceed the max, give up. */ > - if (i + (count - cnt) > FIRST_MSI_INT + NUM_MSI_INTS) { > + if (i + (count - cnt) >= FIRST_MSI_INT + NUM_MSI_INTS) { > mtx_unlock(&msi_lock); > free(mirqs, M_MSI); > return (ENXIO); > @@ -645,7 +645,7 @@ > /* Do we need to create a new source? */ > if (msi == NULL) { > /* If we would exceed the max, give up. */ > - if (i + 1 > FIRST_MSI_INT + NUM_MSI_INTS) { > + if (i + 1 >= FIRST_MSI_INT + NUM_MSI_INTS) { > mtx_unlock(&msi_lock); > return (ENXIO); > } > root@test:/usr/src > > If you need any aditional information please tell me about. Can you perhaps turn off the stack trace on boot to not lose the panic messages (remove KDB_TRACE from kernel config) and maybe modify the panic message to include the IRQ number passed to nexus_add_irq? -- John Baldwin