mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: holt@sgi.com
Cc: mcarlson@broadcom.com, mchan@broadcom.com, benli@broadcom.com,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: Linux 2.6.30-rc1 tg3 endian issues with MAC addresses on BCM5701. Bisected.
Date: Mon, 13 Apr 2009 13:43:45 -0700 (PDT)	[thread overview]
Message-ID: <20090413.134345.160028379.davem@davemloft.net> (raw)
In-Reply-To: <20090413201558.GK10768@sgi.com>

From: Robin Holt <holt@sgi.com>
Date: Mon, 13 Apr 2009 15:15:58 -0500

> On Mon, Apr 13, 2009 at 10:57:24AM -0700, Matt Carlson wrote:
>> Thank you for doing this bisection Robin.  This, and the data you
>> provided in your previous email is really helpful.  Unfortunately, they
>> raise more questions than answers.
>> 
>> I reviewed this patch again, and it still looks correct to me.  It
>> should be one big behavioral no-op.  Obviously something is wrong, but
>> I'm not seeing the root cause at the moment.  I need to think about this
>> some more.
> 
> If you want me to build test kernels with debug printk's, etc.  Let me
> know.  I will be working that issue on the side, so my responses may be
> slightly delayed.  I have access to many tests machines that exhibit
> this problem.
> 
> The problem seems to affect BCM5701 based systems only.  BCM5704 have
> the correct MAC addresses.  Nearly all of our SGI Altix 3700/4700
> machines have the BCM5701 adapters on their base I/O board.

I think it's only going to hit chips that access those particular
NVRAM chip read/write paths.

Matt, realize that on big-endian there are implicit endian
conversions going on.  The read*/write* macros are converting
little-to-big endian on big-endian systems.

Actually, is that the case, that we only see this corrupt MAC
address bug on big-endian systems?  Or are we seeing this on
little-endian too?

  reply	other threads:[~2009-04-13 20:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08  0:20 Linux 2.6.30-rc1 Linus Torvalds
2009-04-08  2:26 ` Kevin Bowling
2009-04-08  5:09   ` Christian Kujau
2009-04-08  4:27 ` Linux 2.6.30-rc1 boot failure on ia64 w/ QLA12160. Bisected Robin Holt
2009-04-08  7:33   ` David Woodhouse
2009-04-08  7:36     ` David Woodhouse
2009-04-08 11:41       ` Robin Holt
2009-04-08  8:31   ` David Woodhouse
2009-04-09 15:43     ` Jaswinder Singh Rajput
2009-04-09 15:59       ` David Woodhouse
2009-04-08  5:37 ` Linux 2.6.30-rc1 Robin Holt
2009-04-08  5:54   ` Michael Chan
2009-04-08  6:25     ` Robin Holt
2009-04-08  7:12       ` Linux 2.6.30-rc1 tg3 endian issues with MAC addresses on BCM5701. Bisected Robin Holt
2009-04-13 17:57         ` Matt Carlson
2009-04-13 20:15           ` Robin Holt
2009-04-13 20:43             ` David Miller [this message]
2009-04-13 20:44           ` David Miller
2009-04-08  6:07 ` Linux 2.6.30-rc1 Michal Simek
2009-04-08  6:41 ` Jike Song
2009-04-08 11:33 ` Morten P.D. Stevens

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=20090413.134345.160028379.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=benli@broadcom.com \
    --cc=holt@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcarlson@broadcom.com \
    --cc=mchan@broadcom.com \
    --cc=torvalds@linux-foundation.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