public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phil Brutsche <phil@tux.obix.com>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: Problems with 3c59x in 2.6.7-rc1-bk*
Date: Thu, 27 May 2004 20:30:41 -0500	[thread overview]
Message-ID: <40B69641.2080001@tux.obix.com> (raw)

With a 3c905C NIC, I get a kernel panic & hard lock while trying to 
bring up the interface at boot.

After reverting the following patch (introduced in 2.6.6-bk1) there are 
no more kernel panics.  2.6.6 and earlier work fine with this card.

diff -Nru a/drivers/net/3c59x.c b/drivers/net/3c59x.c
--- a/drivers/net/3c59x.c       2004-03-13 22:54:58 -08:00
+++ b/drivers/net/3c59x.c       2004-05-10 04:25:39 -07:00
@@ -520,7 +520,7 @@
         {"3c905B-FX Cyclone 100baseFx",
          PCI_USES_IO|PCI_USES_MASTER, IS_CYCLONE|HAS_HWCKSM, 128, },
         {"3c905C Tornado",
-        PCI_USES_IO|PCI_USES_MASTER, IS_TORNADO|HAS_NWAY|HAS_HWCKSM, 
128, },
+       PCI_USES_IO|PCI_USES_MASTER, 
IS_TORNADO|HAS_NWAY|HAS_HWCKSM|EXTRA_PREAMBLE, 128, },
         {"3c980 Cyclone",
          PCI_USES_IO|PCI_USES_MASTER, IS_CYCLONE|HAS_HWCKSM, 128, },
         {"3c980C Python-T",

The strange part?  The patch description shows that it tries to fix 
100baseTX-FD problems with 3c905C cards... which it precisely what works 
fine here WITHOUT the patch.

Yell if anyone needs the text of the panic.

(Andrew, this is directed at you because the changelog shows the patch 
came to Linus from you via -mm)

-- 

Phil Brutsche
phil@tux.obix.com

                 reply	other threads:[~2004-05-28  1:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=40B69641.2080001@tux.obix.com \
    --to=phil@tux.obix.com \
    --cc=akpm@osdl.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