From owner-freebsd-net@FreeBSD.ORG Mon May 10 12:18:38 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4FB216A4CF for ; Mon, 10 May 2004 12:18:38 -0700 (PDT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FB2643D5A for ; Mon, 10 May 2004 12:18:37 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 19747 invoked from network); 10 May 2004 15:07:55 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 10 May 2004 15:07:55 -0000 Received: from 10.50.40.205 (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i4AF7ilA097722; Mon, 10 May 2004 11:07:44 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Scott Long Date: Mon, 10 May 2004 11:08:09 -0400 User-Agent: KMail/1.6 References: <200405071401.17296.jhb@FreeBSD.org> <409BDE98.9080200@freebsd.org> In-Reply-To: <409BDE98.9080200@freebsd.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200405101108.09701.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: freebsd-net@FreeBSD.org cc: freebsd-current@FreeBSD.org cc: =?iso-8859-1?q?S=F8ren_Schmidt?= cc: John Polstra Subject: Re: em(4) problems. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 May 2004 19:18:38 -0000 On Friday 07 May 2004 03:08 pm, Scott Long wrote: > John Baldwin wrote: > > On Thursday 06 May 2004 04:47 pm, Scott Long wrote: > >>S=F8ren Schmidt wrote: > >>>Petri Helenius wrote: > >>>>I=B4m highly confident that this is a case of integrated "CSA" ethern= et > >>>>with broken BIOS. I suspect you get an message about that when bootin= g. > >>> > >>>Nope. no messages to that effect, oh and it works in windows(tm)... > >>> > >>>The last thing I see if I try to use em0 is: > >>>em0: Link is up 100 Mbps Full Duplex > >>>and then the system locks up hard. > >> > >>I'm looking a t a similar system right now and it definitely looks like > >>an interrupt routing problem, not a driver problem. The interesting > >>thing is that (with 5.2-current as of two days ago) disabling neither > >>ACPI nor APIC helps. I guess that we might want to get John Baldwin > >>involved. > > > > Ugh, does the interrupt storm stuff in -current help at all? > > The interrupt storm code does indeed get triggered. What info do you > need in order to track down the routing? Well, the MADT (if using ACPI) or MPtable (if not using ACPI) as well as th= e=20 IRQ that storms (since that is the IRQ it is supposed to be getting) and th= e=20 IRQ it was assigned. =2D-=20 John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org