All of lore.kernel.org
 help / color / mirror / Atom feed
From: walt <wa1ter@myrealbox.com>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org, jgarzik@pobox.com
Subject: Re: Broadcom gigabit solution for Jeff.
Date: Wed, 17 Mar 2004 07:46:41 -0800	[thread overview]
Message-ID: <405872E1.8020109@myrealbox.com> (raw)
In-Reply-To: <20040316174511.3003f880.davem@redhat.com>

David S. Miller wrote:
> On Tue, 16 Mar 2004 15:21:40 -0800
> walt <wa1ter@myrealbox.com> wrote:
> 
> 
>>...this is the first time I've tried the driver from Broadcom, so I can't
>> tell you when it was fixed...
> 
> 
> The current driver in the current 2.4.x and 2.6.x pre-release trees should
> have this bug fixed in the tg3 driver.

I admit I seem to be the only one still complaining, so I suspect I must have
a mobo with a rare chip type.  The bug is definitely *not* fixed for me, as of
today's latests changesets from Linus.

The problem lies in the way the chip is initialized on bootup, clearly, because
doing ifconfig down/up changes a few bytes of memory and starts things working
until the next reboot.

Here is a before/after diff of lspci -xxx.  You can see that byte 0x94 has been
reset by the ifconfig down/up:

#diff before after
83,89c83,89
< 90: 09 02 00 01 01 00 00 00 00 00 00 00 c8 00 00 00
< a0: 00 00 00 00 00 00 00 00 00 00 00 00 03 00 00 00
< b0: 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00
< c0: 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00
< d0: 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00
< e0: 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00
< f0: 00 00 00 00 01 00 00 00 00 00 00 00 01 00 00 00
---
 > 90: 09 02 00 01 00 00 00 00 00 00 00 00 c8 00 00 00
 > a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 > b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 > c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 > d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 > e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 > f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

I wish I had the expertise to figure out what code is responsible
for resetting that bit, but alas I don't.

If you could give me even a hint of what sections of the tg3 code
to look at I might be able to pick it up from there -- e.g. what
part of the driver code would be exercised by 'ifconfig down' that
isn't done by the 'ifconfig up' at bootup.

  parent reply	other threads:[~2004-03-17 15:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-16 23:21 Broadcom gigabit solution for Jeff walt
     [not found] ` <20040316174511.3003f880.davem@redhat.com>
2004-03-17 15:46   ` walt [this message]
2004-03-17 18:24     ` David S. Miller
2004-03-17 23:14       ` walt
2004-03-31 22:32         ` David Lang

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=405872E1.8020109@myrealbox.com \
    --to=wa1ter@myrealbox.com \
    --cc=davem@redhat.com \
    --cc=jgarzik@pobox.com \
    --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.