From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Frank de Lange <frank@unternet.org>
Cc: Andrew Morton <andrewm@uow.edu.au>, linux-kernel@vger.kernel.org
Subject: Re: QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware related?
Date: Thu, 11 Jan 2001 16:47:00 -0500 [thread overview]
Message-ID: <3A5E29D4.1AA38368@mandrakesoft.com> (raw)
In-Reply-To: <20010110223015.B18085@unternet.org> <3A5D9D87.8A868F6A@uow.edu.au> <20010111220943.F3269@unternet.org>
Frank de Lange wrote:
>
> OK, just one last addition to what has nearly become my own thread...
>
> I now am fairly certain that the problem (network stalls on multiprocessor systems) is not BP6 or NE2K-PCI specific. I found several postings which relate to similar problems on dissimilar hardware. Another interesting one is:
> I have reported it some time ago, and now all I get with
> 2.4.0-test11-pre4 and I think a additional patch is NETDEV WATCHDOG:
> eth0: transmit timed out, and something in the console about lost irq?
Are you judging based on the error message? The 'netdev watchdog ...'
message is a generic error message that could have any number of
causes. It's just saying, well, what it says :) The kernel was unable
to transmit a packet in a certain amount of time. You might get these
messages if you unplug a cable suddenly, or if your hardware isn't
delivering interrupts, or many other things...
Jeff
--
Jeff Garzik | "You see, in this world there's two kinds of
Building 1024 | people, my friend: Those with loaded guns
MandrakeSoft | and those who dig. You dig." --Blondie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-11 21:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 21:30 QUESTION: Network hangs with BP6 and 2.4.x kernels, hardware related? Frank de Lange
2001-01-10 22:21 ` Manfred Spraul
2001-01-10 22:29 ` Frank de Lange
2001-01-10 22:40 ` Frank de Lange
2001-01-11 11:48 ` Andrew Morton
2001-01-11 15:22 ` Frank de Lange
2001-01-11 16:55 ` Frank de Lange
2001-01-11 19:18 ` Frank de Lange
[not found] ` <3A5E0849.EB428D70@mandrakesoft.com>
2001-01-12 0:28 ` Frank de Lange
2001-01-12 11:40 ` Andrew Morton
2001-01-12 15:06 ` Frank de Lange
2001-01-12 15:36 ` Frank de Lange
2001-01-11 19:38 ` Frank de Lange
2001-01-11 19:49 ` Frank de Lange
2001-01-11 21:09 ` Frank de Lange
2001-01-11 21:47 ` Jeff Garzik [this message]
2001-01-11 21:53 ` Frank de Lange
2001-01-12 14:35 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2001-01-12 16:53 Manfred Spraul
2001-01-12 17:02 ` David Woodhouse
2001-01-12 17:16 Manfred Spraul
2001-01-12 17:33 ` Frank de Lange
2001-01-12 17:51 ` Manfred Spraul
2001-01-12 18:25 ` Frank de Lange
2001-01-12 19:04 ` Manfred Spraul
2001-01-12 19:07 ` Frank de Lange
2001-01-12 19:21 ` Frank de Lange
2001-01-12 19:33 ` Manfred Spraul
2001-01-12 19:52 ` Frank de Lange
2001-01-12 19:59 ` Linus Torvalds
2001-01-12 20:03 ` Ingo Molnar
2001-01-14 0:13 ` Roeland Th. Jansen
2001-01-14 0:23 ` Frank de Lange
2001-01-12 20:05 ` Frank de Lange
2001-01-12 21:21 ` Frank de Lange
[not found] <20010112165104.A22465@unternet.org>
2001-01-16 19:23 ` Maciej W. Rozycki
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=3A5E29D4.1AA38368@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=andrewm@uow.edu.au \
--cc=frank@unternet.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.