From: "Nick Warne" <nick@ukfsn.org>
To: linux-kernel@vger.kernel.org
Subject: (Fwd) Re: 2.6.3 RT8139too NIC problems [resolved]
Date: Mon, 23 Feb 2004 18:50:51 -0000 [thread overview]
Message-ID: <403A4B8B.14358.FE1FB73@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 :/
Regards,
Nick
--
"I am not Spock", said Leonard Nimoy.
"And it is highly illogical of humans to assume so."--
"I am not Spock", said Leonard Nimoy.
"And it is highly illogical of humans to assume so."
next reply other threads:[~2004-02-23 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 18:50 Nick Warne [this message]
2004-02-23 19:46 ` (Fwd) Re: 2.6.3 RT8139too NIC problems [resolved] Frédéric L. W. Meunier
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=403A4B8B.14358.FE1FB73@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox