mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vibol Hou" <vhou@khmer.cc>
To: "Andrew Morton" <andrewm@uow.edu.au>
Cc: "Linux-Kernel" <linux-kernel@vger.kernel.org>
Subject: RE: Sytem slowdown on 2.4.1-ac20 (recurring from 2.4.0)
Date: Mon, 26 Feb 2001 17:03:06 -0800	[thread overview]
Message-ID: <NDBBKKONDOBLNCIOPCGHMEPAEPAA.vhou@khmer.cc> (raw)
In-Reply-To: <3A9AF846.A2A223D@uow.edu.au>

> Are you still getting the "hordes" of Tx timeouts with the
> 3c905B which you reported a week ago?

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.

-


  reply	other threads:[~2001-02-27  1:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27  0:25 Vibol Hou
2001-02-27  0:43 ` Andrew Morton
2001-02-27  1:03   ` Vibol Hou [this message]
2001-02-27  1:18     ` Andrew Morton
2001-03-01  6:15 ` Balbir Singh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=NDBBKKONDOBLNCIOPCGHMEPAEPAA.vhou@khmer.cc \
    --to=vhou@khmer.cc \
    --cc=andrewm@uow.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®