Re: NIC lockup in 2.4.17 (SMP/APIC/Intel 82557)

Robbert Kouprie (robbert@jvb.tudelft.nl)
Mon, 21 Jan 2002 11:06:55 +0100 (CET)


I know the bad reputation of the BP6, I see APIC errors every day since
the specific printk was added in 2.4.0, but system is fairly stable. Last
time it was unstable the cause was the Intel eepro100, which turned out
to suffer from a chipset bug, which is now corrected for in the
eepro100.c driver.

I ran 2.4 kernels with this NIC and the corrected driver since 2.4.14 or
so and never had problems. 2.4.16 ran for 40 days without trouble.

My BP6 bios is the most recent (RU revision). I can't really say "noapic"
helps as I have no way to reproduce this. It was just a one time message, which was
very similar to the earlier bug report to lkml I mentioned, that's why I
reported it.

If someone has any clues on how to reproduce this I am happy to do some
testing.

Regards,
- Robbert

On Sun, 20 Jan 2002, Mark Hahn wrote:

> > I have an Abit BP6 Dual Celeron 433, 192 Mb RAM, Intel NIC on 100 Mbit,
>
> I assume you know that the BP6 is quite notorious for it's
> rather ignoble irq and apic handling? is it safe to assume
> you have a recent bios installed? does booting "noapic" help?
>
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/