em(4) problems.

[John Baldwin]

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ø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?

Well, the MADT (if using ACPI) or MPtable (if not using ACPI) as well as the 
IRQ that storms (since that is the IRQ it is supposed to be getting) and the 
IRQ it was assigned.

-- 
John Baldwin <jhb at FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org