From owner-freebsd-current@FreeBSD.ORG Fri May 7 12:08:51 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 94FCF16A4CE; Fri, 7 May 2004 12:08:51 -0700 (PDT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23D0943D3F; Fri, 7 May 2004 12:08:51 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: from freebsd.org (junior-wifi.samsco.home [192.168.0.11]) by pooker.samsco.org (8.12.10/8.12.10) with ESMTP id i47JCxu6040217; Fri, 7 May 2004 13:12:59 -0600 (MDT) (envelope-from scottl@freebsd.org) Message-ID: <409BDE98.9080200@freebsd.org> Date: Fri, 07 May 2004 13:08:08 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040304 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <409A92FA.6080104@DeepCore.dk> <409AA44B.9010404@freebsd.org> <200405071401.17296.jhb@FreeBSD.org> In-Reply-To: <200405071401.17296.jhb@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-net@freebsd.org cc: freebsd-current@freebsd.org 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 19:08:51 -0000 John Baldwin wrote: > On Thursday 06 May 2004 04:47 pm, Scott Long wrote: > >>Søren Schmidt wrote: >> >>>Petri Helenius wrote: >>> >>>>I´m 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? > The interrupt storm code does indeed get triggered. What info do you need in order to track down the routing? Scott