From: "Ed L. Cashin" <ecashin@coraid.com>
To: Michael Chan <mchan@broadcom.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@redhat.com>
Subject: Re: 2.6.16.11 BUG at tg3.c:2917
Date: Thu, 27 Apr 2006 17:04:54 -0400 [thread overview]
Message-ID: <20060427210454.GF29045@coraid.com> (raw)
In-Reply-To: <1146152724.11406.3.camel@rh4>
On Thu, Apr 27, 2006 at 08:45:24AM -0700, Michael Chan wrote:
> On Thu, 2006-04-27 at 12:52 -0400, Ed L. Cashin wrote:
> > -- [please bite here ] ---------
> > Kernel BUG at drivers/net/tg3.c:2917
> > invalid opcode: 0000 [1] SMP
> > CPU 0
>
> Most likely caused by IO re-ordering. Try the test patch in this
> discussion:
>
> http://marc.theaimsgroup.com/?l=linux-netdev&m=113890239404768&w=2
I'm afraid I might be generating noise here. After my initial post I
found that I cannot trigger a panic without the latest changes to the
aoe driver in place. I haven't been able to trigger a panic using the
aoe driver inside 2.6.16.11.
I think we've identified the problem in the aoe driver, but if I'm
wrong, I will certainly try the TG3_FLAG_MBOX_WRITE_REORDER patch you
mention.
--
Ed L Cashin <ecashin@coraid.com>
prev parent reply other threads:[~2006-04-27 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 16:52 2.6.16.11 BUG at tg3.c:2917 Ed L. Cashin
2006-04-27 15:45 ` Michael Chan
2006-04-27 21:04 ` Ed L. Cashin [this message]
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=20060427210454.GF29045@coraid.com \
--to=ecashin@coraid.com \
--cc=davem@redhat.com \
--cc=mchan@broadcom.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).