The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Pete Clements <clem@clem.clem-digital.net>
To: akpm@osdl.org (Andrew Morton)
Cc: clem@clem.clem-digital.net (Pete Clements),
	klassert@mathematik.tu-chemnitz.de, linux-kernel@vger.kernel.org
Subject: Re: Correction: 2.6.16-git12 killed networking -- 3c900 card
Date: Thu, 30 Mar 2006 08:46:54 -0500 (EST)	[thread overview]
Message-ID: <200603301346.k2UDksdJ001794@clem.clem-digital.net> (raw)
In-Reply-To: <20060329210904.3e1391bb.akpm@osdl.org>

Quoting Andrew Morton
  > Pete Clements <clem@clem.clem-digital.net> wrote:
  > >
  > > Quoting Andrew Morton
  > >   > 
  > >   > Oh damn.  So you're sure that 3c59x.global_enable_wol=0 actually makes the
  > >   > driver behave better?
  > >   > 
  > > Ok, new results.
  > > Built a new virgin 2.6.16.
  > > 1) able to stimulate a tx time out message
  > > 2) rebooted with 3c59x.global_enable_wol=0 on command line,
  > >    able to stimulate a tx time out message
  > > 
  > > Applied the collision statistics fix fix. Changed the extraversion
  > > in the top Makefile to preserve my baseline, also make does more
  > > work than previous. 
  > > 1) Booted and unable to stimulate a tx time out message
  > > 
  > > Rebooted to virgin 2.6.16
  > > 1) able to stimulate a tx time out message
  > > 2) rebooted with 3c59x.global_enable_wol=0 on command line,
  > >    able to stimulate a tx time out message
  > > 
  > > Rebooted to the patched driver kernel (collision statistics fix fix)
  > > 1) unable to stimulate a tx time out message.
  > > 
  > > Rebooted to virgin 2.6.16
  > > 1) able to stimulate a tx time out message
  > > 
  > > Appears that earlier results were tainted.
  > > 
  > 
  > OK, thanks.  So it looks like 3c59x-collision-statistics-fix-fix.patch is
  > the only patch which we need to return your machine to working condition?
  > 

Looks like that is the case until -git12, which Steffen has identified.
Tested on git18 (with git12 fix) and looks good.
-- 
Pete Clements 

  reply	other threads:[~2006-03-30 13:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-27  2:12 Correction: 2.6.16-git12 killed networking -- 3c900 card Pete Clements
2006-03-28 14:14 ` Steffen Klassert
2006-03-28 16:44   ` Pete Clements
2006-03-29 11:47     ` Steffen Klassert
2006-03-29 14:27       ` Pete Clements
2006-03-29  1:12   ` Pete Clements
2006-03-29  2:50   ` Pete Clements
2006-03-29  6:43     ` Andrew Morton
2006-03-29  9:14       ` Steffen Klassert
2006-03-29 14:39       ` Pete Clements
2006-03-29  6:49     ` Andrew Morton
2006-03-29 14:49       ` Pete Clements
2006-03-29 19:29         ` Andrew Morton
2006-03-30  0:53           ` Pete Clements
2006-03-30  1:10             ` Andrew Morton
2006-03-30  1:19               ` Pete Clements
2006-03-30  4:51               ` Pete Clements
2006-03-30  5:09                 ` Andrew Morton
2006-03-30 13:46                   ` Pete Clements [this message]
2006-03-30 14:29                     ` Steffen Klassert
2006-03-30 16:02                       ` Pete Clements
2006-03-29  7:01     ` Andrew Morton
2006-03-29 15:15       ` Pete Clements
2006-03-29  1:07 ` Pete Clements

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=200603301346.k2UDksdJ001794@clem.clem-digital.net \
    --to=clem@clem.clem-digital.net \
    --cc=akpm@osdl.org \
    --cc=klassert@mathematik.tu-chemnitz.de \
    --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