From owner-freebsd-net@FreeBSD.ORG Thu Feb 21 22:20:01 2013 Return-Path: Delivered-To: freebsd-net@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 714EB166 for ; Thu, 21 Feb 2013 22:20:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 60C027D for ; Thu, 21 Feb 2013 22:20:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r1LMK1G6043510 for ; Thu, 21 Feb 2013 22:20:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r1LMK1hS043509; Thu, 21 Feb 2013 22:20:01 GMT (envelope-from gnats) Date: Thu, 21 Feb 2013 22:20:01 GMT Message-Id: <201302212220.r1LMK1hS043509@freefall.freebsd.org> To: freebsd-net@FreeBSD.org Cc: From: John Baldwin Subject: Re: kern/172113: [panic] [e1000] [patch] 9.1-RC1/amd64 panices in igb(4): m_getjcl: invalid cluster type X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: John Baldwin List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Feb 2013 22:20:01 -0000 The following reply was made to PR kern/172113; it has been noted by GNATS. From: John Baldwin To: bug-followup@freebsd.org, egrosbein@rdtc.ru Cc: Subject: Re: kern/172113: [panic] [e1000] [patch] 9.1-RC1/amd64 panices in igb(4): m_getjcl: invalid cluster type Date: Thu, 21 Feb 2013 17:12:55 -0500 An update on this. I think we should just use a workaround as this seems to be specific to a certain set of motherboards. This is the fix I'm using locally: Index: if_igb.c =================================================================== --- if_igb.c (revision 243732) +++ if_igb.c (working copy) @@ -1522,6 +1522,15 @@ u32 newitr = 0; bool more_rx; + /* + * The onboard adapters on certain SuperMicro X8* boards + * trigger a spurious interrupt during boot. Since it + * occurs before the interface is fully configured it + * triggers a panic. Ignore the interrupt instead. + */ + if (!(adapter->ifp->if_drv_flags & IFF_DRV_RUNNING)) + return; + E1000_WRITE_REG(&adapter->hw, E1000_EIMC, que->eims); ++que->irqs; -- John Baldwin