From: "Nick Warne" <nick@ukfsn.org>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.3 RT8139too NIC problems [NOT resolved]
Date: Mon, 23 Feb 2004 20:18:25 -0000 [thread overview]
Message-ID: <403A6011.5674.103225D9@localhost> (raw)
> > > > > 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
> >
> > Well, I am at a loss now or any idea what to do next. I have tried
> > everything this morning to build this an eliminate the problem.
> > Whatever I do, kernel builds nice, boots nice and no problems...
> > except for these NIC timeouts - it makes 2.6.3 totally unusable for
> > me.
> >
> > I state again, these _very_same_ cards work perfectly under any other
> > kernel I have ever used over the last 3 years (like I am back on
> > 2.6.2 right now).
>
> "This is usually irq routing related... Try booting with 'noapic' or
> similar. Jeff"
>
> OK, this was the solution. I am right bloody idiot. Good call Jeff.
>
> I believed I had APIC turned off (I didn't). So I then compiled
> kernel with debugging set in 8139too.c, and thought I would be real
> cool and catch the problem and submit a kernel patch (Yea, right!).
> I also looked at what I done.
>
> I was booting with append=noapic... then read a bit... it needed to
> be a string, append="noapic".
>
> It all works great now on 2.6.3.
>
> Sorry to bother you guys when nothing is wrong, and I apologise for
> me being a dipstick twice over :/
I spoke too bloody soon. The problem still exists, but on a lesser
scale:
Feb 23 19:25:39 Linux233 kernel: nfs: server 486Linux not responding,
still trying
Feb 23 19:25:41 Linux233 kernel: NETDEV WATCHDOG: eth0: transmit
timed out
Feb 23 19:25:41 Linux233 kernel: nfs: server 486Linux OK
Feb 23 19:28:27 Linux233 kernel: nfs: server 486Linux not responding,
still trying
Feb 23 19:28:31 Linux233 kernel: NETDEV WATCHDOG: eth1: transmit
timed out
Feb 23 19:28:31 Linux233 kernel: eth1: link up, 10Mbps, half-duplex,
lpa 0x0000
Feb 23 19:28:35 Linux233 kernel: nfs: server 486Linux not responding,
still trying
Feb 23 19:28:35 Linux233 kernel: NETDEV WATCHDOG: eth0: transmit
timed out
Feb 23 19:28:35 Linux233 kernel: nfs: server 486Linux OK
I lose 10 seconds on network when this happens, and eth0 going AWOL
then seems to make eth1 go awol straight after.
The cards all work FINE on 2.6.2/1/0 (2.4.1.->.24)... what has
changed so much to cause this, so at least I can supply some info.
:/
Nick
--
"I am not Spock", said Leonard Nimoy.
"And it is highly illogical of humans to assume so."
next reply other threads:[~2004-02-23 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 20:18 Nick Warne [this message]
2004-02-26 17:53 ` 2.6.3 RT8139too NIC problems [NOT resolved] Stephen Hemminger
2004-02-26 18:07 ` Nick Warne
[not found] <403E34F8.31130.1F29EF00@localhost>
[not found] ` <20040226101330.20190d34@dell_ss3.pdx.osdl.net>
2004-02-26 18:30 ` 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=403A6011.5674.103225D9@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.