Date: Fri, 07 May 2004 13:08:08 -0600 From: Scott Long <scottl@freebsd.org> To: John Baldwin <jhb@freebsd.org> Cc: John Polstra <jdp@polstra.com> Subject: Re: em(4) problems. Message-ID: <409BDE98.9080200@freebsd.org> In-Reply-To: <200405071401.17296.jhb@FreeBSD.org> References: <XFMail.20040505115403.jdp@polstra.com> <409A92FA.6080104@DeepCore.dk> <409AA44B.9010404@freebsd.org> <200405071401.17296.jhb@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
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? Scotthelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?409BDE98.9080200>