Yes, but they happen a few hours after the system starts up and continue
until the server is restarted. It seems like a separate issue. I haven't
tried taking down the interface and putting it back up since the interface
never dies link others have reported with their NICs. The NIC continues to
work fine, though the logs get flooded with those messages.
> If so, do they only start coming out when the slowdown occurs?
That's a negative.
> You are probably a victim of the APIC bug. A
> workaround for this is present in 2.4.2-ac5. Alternatively,
> boot the kernel with the `noapic' LILO option.
I'll compile 2.4.2-ac5 and we'll see in another 5 days if this happens
again. Till then, any suggestions on what to look for/at and/or what to do
when it happens will help.
Thanks!
-- Vibol Hou KhmerConnection, http://khmer.cc-----Original Message----- From: morton@uow.edu.au [mailto:morton@uow.edu.au]On Behalf Of Andrew Morton Sent: Monday, February 26, 2001 4:44 PM To: Vibol Hou Cc: Linux-Kernel Subject: Re: Sytem slowdown on 2.4.1-ac20 (recurring from 2.4.0)
Vibol Hou wrote: > > I've reported this problem a long while ago, but no one answered my pleas. > To tell you the honest truth, I don't know where to begin looking. It's > difficult to poke around when the serial console is unresponsive :/ >
Sounds like a network driver problem.
Are you still getting the "hordes" of Tx timeouts with the 3c905B which you reported a week ago?
If so, do they only start coming out when the slowdown occurs?
You are probably a victim of the APIC bug. A workaround for this is present in 2.4.2-ac5. Alternatively, boot the kernel with the `noapic' LILO option.
Please let us know the outcome.
-
- 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/