* (Fwd) Re: 2.6.3 RT8139too NIC problems [resolved]
@ 2004-02-23 18:50 Nick Warne
2004-02-23 19:46 ` Frédéric L. W. Meunier
0 siblings, 1 reply; 2+ messages in thread
From: Nick Warne @ 2004-02-23 18:50 UTC (permalink / raw)
To: linux-kernel
> > > > 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."
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: (Fwd) Re: 2.6.3 RT8139too NIC problems [resolved]
2004-02-23 18:50 (Fwd) Re: 2.6.3 RT8139too NIC problems [resolved] Nick Warne
@ 2004-02-23 19:46 ` Frédéric L. W. Meunier
0 siblings, 0 replies; 2+ messages in thread
From: Frédéric L. W. Meunier @ 2004-02-23 19:46 UTC (permalink / raw)
To: Nick Warne; +Cc: linux-kernel
On Mon, 23 Feb 2004, Nick Warne wrote:
> "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.
>
> Sorry to bother you guys when nothing is wrong, and I apologise for
> me being a dipstick twice over :/
Sure something is. APIC is broken for you, right ? As it's for
me - see
http://marc.theaimsgroup.com/?l=linux-kernel&m=107721911802649&w=2
Yes, it'd be nice to get it working without ACPI, but it's an
improvement that ACPI now works (also in 2.4.25).
But you wrote "This happens about once every 3 hours.", so it
doesn't seem to be completely broken as it's for me.
--
http://www.pervalidus.net/contact.html
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2004-02-23 19:46 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-02-23 18:50 (Fwd) Re: 2.6.3 RT8139too NIC problems [resolved] Nick Warne
2004-02-23 19:46 ` Frédéric L. W. Meunier
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.