From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261996AbUBWSuz (ORCPT ); Mon, 23 Feb 2004 13:50:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261993AbUBWSuz (ORCPT ); Mon, 23 Feb 2004 13:50:55 -0500 Received: from s2.ukfsn.org ([217.158.120.143]:62659 "EHLO mail.ukfsn.org") by vger.kernel.org with ESMTP id S261996AbUBWSux (ORCPT ); Mon, 23 Feb 2004 13:50:53 -0500 From: "Nick Warne" To: linux-kernel@vger.kernel.org Date: Mon, 23 Feb 2004 18:50:51 -0000 MIME-Version: 1.0 Subject: (Fwd) Re: 2.6.3 RT8139too NIC problems [resolved] Message-ID: <403A4B8B.14358.FE1FB73@localhost> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > > > > 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."