public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nick Warne" <nick@ukfsn.org>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.3 RT8139too NIC problems
Date: Tue, 24 Feb 2004 20:36:53 -0000	[thread overview]
Message-ID: <403BB5E5.17054.156978FE@localhost> (raw)

 > Funnily enough, I looked at this at work today and decided to check 
> against 8139too.c from 2.6.2 and 2.6.3 trees.  There was a lot of 
> changes, but it appeared only to that file (i.e. nothing referencing 
> it) - so I have just built 2.6.3 with the 8139too.c source from 2.6.2 
> just to make sure it isn't code elsewhere (i.e. pci stuff?) that is 
> causing it.
> 
> So far it is running perfectly.  I will wait a while to test, and if 
> it doesn't show any problems, we can presume it is the changes that 
> caused this problem for me on my system.
> 
> Enquiries to the HantsLUG seem to be that no-one else gets this 
> problem.

This has solved the problem for me.  Please can anyone tell me what 
details are required to provide a bug report on this strange one off 
issue, as I wouldn't know where to start.

To recap:

rtl8139too cards worked on all kernels up until 2.6.3 (like 3 years).

The timeout issues started with 2.6.3 (using make oldconfig)... new 
settings applied.

Tried lilo 'append="noapic"  -> problem still persisted.

After reading I changed: 2.6.2 source-> 8139too.c to replace new 
2.6.3 source-> 8139too.c -> rebuilt with same .config.  No timeouts - 
all hunky dory.

Thanks,

Nick

[root@Linux233 log]# lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT82C585VP [Apollo 
VP1/VPX] (rev 23)
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C586/A/B PCI-to-ISA 
[Apollo VP] (rev 27)
00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06)
00:07.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 02)
00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 
(rev 10)
00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 
(rev 10)


-- 
"When you're chewing on life's gristle,
Don't grumble,
Give a whistle
And this'll help things turn out for the best."


             reply	other threads:[~2004-02-24 20:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-24 20:36 Nick Warne [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-21 14:59 2.6.3 RT8139too NIC problems Nick Warne
     [not found] ` <14539106.1077630890@42.150.104.212.access.eclipse.net.uk>
2004-02-24 18:23   ` Nick Warne
2004-02-19 20:04 Nick Warne
2004-02-19 16:47 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

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=403BB5E5.17054.156978FE@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