From owner-freebsd-stable@FreeBSD.ORG Fri Jun 10 09:37:29 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9D591065675 for ; Fri, 10 Jun 2011 09:37:29 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta11.emeryville.ca.mail.comcast.net (qmta11.emeryville.ca.mail.comcast.net [76.96.27.211]) by mx1.freebsd.org (Postfix) with ESMTP id BD8198FC1A for ; Fri, 10 Jun 2011 09:37:29 +0000 (UTC) Received: from omta22.emeryville.ca.mail.comcast.net ([76.96.30.89]) by qmta11.emeryville.ca.mail.comcast.net with comcast id u9bF1g0011vN32cAB9dUtC; Fri, 10 Jun 2011 09:37:28 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta22.emeryville.ca.mail.comcast.net with comcast id u9dP1g00H1t3BNj8i9dPoF; Fri, 10 Jun 2011 09:37:24 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 35D23102C19; Fri, 10 Jun 2011 02:37:28 -0700 (PDT) Date: Fri, 10 Jun 2011 02:37:28 -0700 From: Jeremy Chadwick To: Bartosz Stec Message-ID: <20110610093728.GA39453@icarus.home.lan> References: <4DC6A277.4030801@it4pro.pl> <4DC6E23B.2040207@it4pro.pl> <4DC81E22.5030806@it4pro.pl> <4DCC3844.6070008@it4pro.pl> <4DCD1672.4020405@FreeBSD.org> <4DF1DC26.5010600@it4pro.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DF1DC26.5010600@it4pro.pl> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Stable , "Vogel, Jack" , Andriy Gapon Subject: Re: Panic during kernel booting on HP Proliant DL180G6 and latest STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 09:37:29 -0000 On Fri, Jun 10, 2011 at 10:56:06AM +0200, Bartosz Stec wrote: > W dniu 2011-05-13 13:30, Andriy Gapon pisze: > >on 12/05/2011 22:43 Bartosz Stec said the following: > >>Allright, if anyone want to follow: http://www.freebsd.org/cgi/query-pr.cgi?pr=156974 > >> > >I suspect that your best course here is to add some diagnostic printfs in > >igb_refresh_mbufs and in m_getzone to see what value is actually passed to > >m_getjcl and why. > > > You're probably right, although I would need some guidance how to do > it. Sorry :( > > Yesterday I rebuilt this machine with fresh sources to upgrade > filesystem to ZFSv28 which was MFC'ed lately. After that server > started to panic regardless of igb loaded as module or integrated > into kernel. > > Finally I found that problem was caused by MSIX somehow. > No more panic after > > hw.pci.enable_msix=0 > > was included in loader.conf. > > There's also no panic with GENERIC kernel. > > Should I really care abou MSIX? Yes, you absolutely should. The performance hit, depending on your interrupt load, can be quite dramatic with this turned off. Remember: what you just turned off was MSI-X for the *entire system*, not just for NICs. Please read about it here: http://en.wikipedia.org/wiki/Message_Signaled_Interrupts CC'ing Jack Vogel here, because your issue pertains to igb(4). Please provide output from "pciconv -lvcb" that pertain to your igb NIC(s), as well as relevant dmesg info that pertains to them (driver, etc.). You can XXX out MAC addresses if you're worried. Jack, original thread starts here: http://lists.freebsd.org/pipermail/freebsd-stable/2011-May/thread.html#62596 -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |