Date: Mon, 10 May 2004 11:08:09 -0400 From: John Baldwin <jhb@FreeBSD.org> To: Scott Long <scottl@FreeBSD.org> Cc: John Polstra <jdp@polstra.com> Subject: Re: em(4) problems. Message-ID: <200405101108.09701.jhb@FreeBSD.org> In-Reply-To: <409BDE98.9080200@freebsd.org> References: <XFMail.20040505115403.jdp@polstra.com> <200405071401.17296.jhb@FreeBSD.org> <409BDE98.9080200@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <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?200405101108.09701.jhb>