All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pekka Pietikainen <pp@ee.oulu.fi>
To: linux-kernel@vger.kernel.org
Cc: bruceg@em.ca
Subject: Re: Broadcom 4401 problem
Date: Mon, 23 Aug 2004 01:17:34 +0300	[thread overview]
Message-ID: <20040822221734.GA10372@ee.oulu.fi> (raw)
In-Reply-To: <20040822205346.GA17895@em.ca>

On Sun, Aug 22, 2004 at 02:53:46PM -0600, Bruce Guenter wrote:
> Greetings.
> 
> I have a Dell Inspiron 1150 laptop which has a built-in Broadcom 4401
> NIC.  I am using Gentoo's 2.6.8.1 kernel and the built-in b44 driver.
> It compiles, loads, and I can get basic network traffic through it just
> fine.  However, it (the NIC) locks up randomly when I try to do bulk
> data transfers (with rsync for example).  I can get it to reset itself
> 
> Is this likely a hardware problem, or a problem in the driver?
Hiya

Could you try the driver from http://www.ee.oulu.fi/~pp/b44-095-2.tgz ,
which has some fixes that have been submitted but not yet merged. If that
doesn't help, the broadcom driver 
( http://www.broadcom.com/drivers/downloaddrivers.php ) might be
worth a try.

Also if you have more than 1Gb of memory, booting with mem=1024m 
might help (although with standard kernels with a 3:1
memory layout this hardware bug shouldn't get triggered and the typical
symptom is a complete hang). But it's worth a try in any case.
The updated driver mentioned above contains a workaround, so this shouldn't 
be needed anymore in any case.

Anyway, please report whether any of this helped. 
-- 
Pekka Pietikainen

  reply	other threads:[~2004-08-22 22:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-22 20:53 Broadcom 4401 problem Bruce Guenter
2004-08-22 22:17 ` Pekka Pietikainen [this message]
2004-08-23 15:57   ` Bruce Guenter
2004-08-23 19:34     ` Pekka Pietikainen

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=20040822221734.GA10372@ee.oulu.fi \
    --to=pp@ee.oulu.fi \
    --cc=bruceg@em.ca \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.