public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomas Ogren <stric@ing.umu.se>
To: linux-kernel@vger.kernel.org
Subject: Fried the onboard Broadcom 4401 network...
Date: Sun, 25 Jan 2004 03:42:38 +0100	[thread overview]
Message-ID: <20040125024238.GA10424@ing.umu.se> (raw)

Hello.

I'm not exactly sure what caused this or if it's reproducable, but
here's my story anyway.

I have an ASUS A7V8X with onboard Broadcom 4401 (Rev 01) 10/100 and I've
been running 2.4.x (2.4.21) for a long time now with Broadcoms bcm4400
driver (v2.0.2) which has worked just fine. Now I decided to try 2.6 and
installed 2.6.2-rc1-bk2 with the b44 driver that comes with the kernel.
While doing some tests I noticed that I got really crappy performance
(3-4MB/s) while sending, but full throughput (~11MB/s) while receiving.

So I figured that it could be the shipped driver.. Downloaded bcm4400
v3.0.7 which has 2.6 support and installed it. Didn't make stuff go
faster. So I thought I'd boot into 2.4.25pre6 and see how it behaves
under a 2.4 kernel with the latest bcm4400 driver. The 2.4.25pre6 I had
compiled includes the b44 driver. I booted it up and then I got a bunch
of the following:
"eth0: b44: BUG!  Timeout waiting for bit 80000000 of register 428 to
clear."
followed by:
"eth0: Link is down."

After that, I have not been able to get link (neither see it through
Linux/WinXP or the physical LED). I have tried multiple cables and my
laptop is perfectly happy with all of them, but the broadcom thingie
seems not. The switch doesn't see link either.

The actual chip seems to be alive, it responds to PCI stuff... it can be
initialized and all but I can't get link.

Not sure what you can do with this information, but I can probably not
do anything more with this NIC at least..

CC me for any replies, please.

/Tomas
-- 
Tomas Ögren, stric@ing.umu.se, http://www.ing.umu.se/~stric/
|- Student at Computing Science, University of Umeå
`- Sysadmin at {cs,ing,acc}.umu.se

             reply	other threads:[~2004-01-25  2:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-25  2:42 Tomas Ogren [this message]
2004-01-25  8:37 ` Fried the onboard Broadcom 4401 network Andrew Walrond
2004-01-25 13:15   ` Tomas Ogren
2004-01-26  9:08 ` Pavel Machek
2004-01-26  9:48   ` Tomas Ogren
2004-01-26  9:56     ` Vojtech Pavlik
2004-01-26 12:30     ` Jamie Lokier
2004-01-26 23:34       ` Andrew Walrond

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=20040125024238.GA10424@ing.umu.se \
    --to=stric@ing.umu.se \
    --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