Yet another IO-APIC problem (was Re: via-rhine weirdness with via kt8235 Southbridge)

Jeff Garzik
2002-11-15T00:48:53Z

Christian Guggenberger wrote:

> >On Wed, 23 Oct 2002 15:49:31 +0200, Christian Guggenberger wrote:
> >
> >>This concerns both 2.4 and 2.5 kernels (testet with 2.4.20pre*aa
> series,
> >>and with 2.5.43, 2.5.44 and 2.5.44-ac1):
> >>
> >>When I enable APIC in the Bios, the via-rhine module will insert
> >>properly, but I won't get a link... With APIC disabled, link is ok. Ok,
> >>this could be caused by buggy bios, so I'll try again, when a new
> >>biosversion is available.
> >
> >Yeah, it seems there's a problem with IO-APICs. I currently don't have a
> >machine with IO-APIC for testing, though, so...
> >
>
>
> A new Biosversion is installed on my mobo now, but that APIC problem
> is still
> there.
> Are there some dumps I could post to get some light on that topic?
>
> Maybe some outputs of via-diag, mii-diag, lspci, dmesg ...?
> If they could help, what options should I pass to mii-diag and via-diag ?

Yet Another IO-APIC problem. From what I see quoted above, it has
nothing at all to do with the via-rhine, and everything to do with IO-APIC.

Almost universally, in 2.4 and 2.5, running IO-APIC on uniprocessor is
badly broken, and causes all sorts of bogus bug reports for unrelated
subsystems. Sometimes IO-APIC is busted even on SMP.

Workaround solutions: (1) boot with "noapic" on command line, (2)
disable IO-APIC in kernel config (if uniprocessor), and/or (3) make sure
that "MP 1.1" is listed in BIOS setup instead of "MP 1.4".

Man, this must be the fourth or fifth bug report I've gotten in the past
week or so, where the IO-APIC can be blamed. ;-( In all recent cases
it has been uniprocessor IOAPIC, not SMP IOAPIC, that was problematic.
IMO we should just take out UP IOAPIC support in the kernel, or put a
big fat warning in the kernel config _and_ at boot...

Jeff