From: "Nick Warne" <nick@ukfsn.org>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.3 RT8139too NIC problems
Date: Fri, 20 Feb 2004 16:42:11 -0000 [thread overview]
Message-ID: <403638E3.7864.9E7B698@localhost> (raw)
In-Reply-To: <40353D2C.2050406@pobox.com>
> > Linux233 kernel: NETDEV WATCHDOG: eth1: transmit timed out
> > Linux233 kernel: eth1: link up, 10Mbps, half-duplex, lpa 0x0000
> > Linux233 kernel: nfs: server 486Linux not responding, still trying
> > Linux233 kernel: nfs: server 486Linux not responding, still trying
> > Linux233 kernel: NETDEV WATCHDOG: eth0: transmit timed out
> > Linux233 kernel: nfs: server 486Linux OK
> > Linux233 kernel: nfs: server 486Linux OK
> > Linux233 kernel: nfs: server 486Linux not responding, still trying
> > Linux233 kernel: NETDEV WATCHDOG: eth0: transmit timed out
> > Linux233 kernel: nfs: server 486Linux OK
>
>
> This is usually irq routing related... Try booting with 'noapic' or
> similar.
I don't have apic built in the kernel. This has only started to
happen on 2.6.3. As I said, on all other kernels, 2.4.x, 2.6.0,
2.6.1, 2.6.2 these NIC are OK.
With 2.6.3 my logs are now riddled with these messages (and the
period is totally random - sometimes 10 times in an hour), and I lose
connectivity during these periods.
I will be booting back into 2.6.2 tonight until I can resolve this.
Nick
--
"I am not Spock", said Leonard Nimoy.
"And it is highly illogical of humans to assume so."
next prev parent reply other threads:[~2004-02-20 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 16:47 2.6.3 RT8139too NIC problems Nick Warne
2004-02-19 17:11 ` Paul Mundt
2004-02-19 17:17 ` Nick Warne
2004-02-19 22:48 ` Jeff Garzik
2004-02-20 16:42 ` Nick Warne [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-19 20:04 Nick Warne
2004-02-21 14:59 Nick Warne
[not found] ` <14539106.1077630890@42.150.104.212.access.eclipse.net.uk>
2004-02-24 18:23 ` Nick Warne
2004-02-24 20:36 Nick Warne
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=403638E3.7864.9E7B698@localhost \
--to=nick@ukfsn.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.