From: "G. Hugh Song" <ghsong@kjist.ac.kr>
To: ja@ssi.bg, linux-kernel@vger.kernel.org
Subject: NETDEV WATCHDOG (Re: locked 3c905B with 2.4.5pre2)
Date: Fri, 18 May 2001 22:27:11 +0900 [thread overview]
Message-ID: <3B05232F.8C49D2A5@kjist.ac.kr> (raw)
> Re: locked 3c905B with 2.4.5pre2
>
> From: Julian Anastasov (ja@ssi.bg)
> Date: Thu May 17 2001 - 04:22:15 EST
>
> * Next message: Karsten Keil: "Re: patch-2.2.19.gz"
> * Previous message: David Wilson: "RE: FW: I think I've found a serious bug in AMD Athlon page_alloc.c routines, where do I mail the developer(s) ?"
> * In reply to: Andrew Morton: "Re: locked 3c905B with 2.4.5pre2"
> * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
>
> ------------------------------------------------------------------------
>
> Hello,
>
> On Thu, 17 May 2001, Andrew Morton wrote:
>
> > > eth0: Interrupt posted but not delivered -- IRQ blocked by another device?
> >
> > This is a failure of the APIC interrupt controller in
> > the 2.4 kernel. You'll need to boot your kernel with
> > the `noapic' LILO option. Or run -ac kernels, which
> > have a software workaround which fixes the problem.
>
> Yes, it seems noapic solved the problem with the lockup :(
>
> > Rumour has it that the APIC fix will be merged into Linus' tree
> > very soon. It needs to be - one of the more important ethernet
> > drivers is basically unviable on x86 SMP in 2.4.
>
> Agreed :) The performance sucks without apic.
>
> Regards
>
> --
> Julian Anastasov <ja@ssi.bg>
> -
I used to get NETDEV WATCHDOG eth0:timeout error on
Alpha SMP, too, with the tulip card. Definitely, Alpha
has nothing to do with the x86 APIC. Since then, I switched to
3C905B.
I suspect that NETDEV WATCHDOG error covers a broad class of
network errors.
Does anyone know more about this?
Thank you
--
G. Hugh Song
reply other threads:[~2001-05-18 13:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3B05232F.8C49D2A5@kjist.ac.kr \
--to=ghsong@kjist.ac.kr \
--cc=ja@ssi.bg \
--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®