mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Pete Clements <clem@clem.clem-digital.net>
Cc: clem@clem.clem-digital.net, klassert@mathematik.tu-chemnitz.de,
	linux-kernel@vger.kernel.org
Subject: Re: Correction: 2.6.16-git12 killed networking -- 3c900 card
Date: Wed, 29 Mar 2006 21:09:04 -0800	[thread overview]
Message-ID: <20060329210904.3e1391bb.akpm@osdl.org> (raw)
In-Reply-To: <200603300451.k2U4pcaK001781@clem.clem-digital.net>

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?


  reply	other threads:[~2006-03-30  5:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-27  2:12 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 [this message]
2006-03-30 13:46                   ` Pete Clements
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=20060329210904.3e1391bb.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=clem@clem.clem-digital.net \
    --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

Powered by JetHome