From owner-freebsd-current@freebsd.org  Wed Apr 18 10:56:54 2018
Return-Path: <owner-freebsd-current@freebsd.org>
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 09FB6FA807F;
 Wed, 18 Apr 2018 10:56:54 +0000 (UTC) (envelope-from satan@ukr.net)
Received: from hell.ukr.net (hell.ukr.net [212.42.67.68])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 986B36DD01;
 Wed, 18 Apr 2018 10:56:53 +0000 (UTC) (envelope-from satan@ukr.net)
Received: from satan by hell.ukr.net with local ID 1f8kld-0002jm-NO
 ; Wed, 18 Apr 2018 13:56:49 +0300
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>
References: <20180416102710.GA90028@hell.ukr.net>
 <3723755.0KMZDfyMWu@ralph.baldwin.cx>
 <20180417191553.GA95803@hell.ukr.net>
 <3628282.XVdngBdGlp@ralph.baldwin.cx>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3628282.XVdngBdGlp@ralph.baldwin.cx>
User-Agent: Mutt/1.9.5 (2018-04-13)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Apr 2018 10:56:54 -0000

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);
 }