Date: Fri, 7 May 2004 14:01:17 -0400 From: John Baldwin <jhb@FreeBSD.org> To: freebsd-current@FreeBSD.org Cc: John Polstra <jdp@polstra.com> Subject: Re: em(4) problems. Message-ID: <200405071401.17296.jhb@FreeBSD.org> In-Reply-To: <409AA44B.9010404@freebsd.org> References: <XFMail.20040505115403.jdp@polstra.com> <409A92FA.6080104@DeepCore.dk> <409AA44B.9010404@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200405071401.17296.jhb>