From owner-freebsd-current@FreeBSD.ORG Fri May 7 11:10:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F8E216A4D2 for ; Fri, 7 May 2004 11:10:15 -0700 (PDT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93ECD43D31 for ; Fri, 7 May 2004 11:10:14 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 21613 invoked from network); 7 May 2004 18:10:14 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 7 May 2004 18:10:14 -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 i47IA5q1078812; Fri, 7 May 2004 14:10:11 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Fri, 7 May 2004 14:01:17 -0400 User-Agent: KMail/1.6 References: <409A92FA.6080104@DeepCore.dk> <409AA44B.9010404@freebsd.org> In-Reply-To: <409AA44B.9010404@freebsd.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200405071401.17296.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: freebsd-net@FreeBSD.org cc: Scott Long cc: Petri Helenius cc: =?iso-8859-1?q?S=F8ren_Schmidt?= cc: John Polstra Subject: Re: em(4) problems. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Fri, 07 May 2004 18:10:15 -0000 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" ethernet > >> with broken BIOS. I suspect you get an message about that when booting. > > > > 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? =2D-=20 John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org