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
Cc: Andy Whitcroft <apw@shadowen.org>
Subject: Re: 2.6.3 RT8139too NIC problems
Date: Tue, 24 Feb 2004 18:23:06 -0000	[thread overview]
Message-ID: <403B968A.7806.14EEFCEE@localhost> (raw)
In-Reply-To: <14539106.1077630890@42.150.104.212.access.eclipse.net.uk>

 > Ok, the normal step from here is a binary search for the offending patch. 
> You know it works on 2.6.2 and not on 2.6.3.  There should be daily BK 
> snapshots for the period from 2.6.2 to 2.6.3.  See if it broke in the first 
> half/second half and so on.  If you can find the offending patch or day 
> then I am sure someone can find the issue.
>

Hi Andy,

Thanks for reply.

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.

Nick
-- 
"I am not Spock", said Leonard Nimoy.
"And it is highly illogical of humans to assume so."


  parent reply	other threads:[~2004-02-24 18:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-24 20:36 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=403B968A.7806.14EEFCEE@localhost \
    --to=nick@ukfsn.org \
    --cc=apw@shadowen.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