From: "Michael Chan" <mchan@broadcom.com>
To: "Josip Rodin" <joy@entuzijast.net>
Cc: "David Miller" <davem@davemloft.net>,
"billfink@mindspring.com" <billfink@mindspring.com>,
"bhutchings@solarflare.com" <bhutchings@solarflare.com>,
netdev <netdev@vger.kernel.org>,
"mirrors@debian.org" <mirrors@debian.org>
Subject: Re: bnx2_poll panicking kernel
Date: Thu, 10 Jul 2008 15:26:03 -0700 [thread overview]
Message-ID: <1215728763.6901.23.camel@dell> (raw)
In-Reply-To: <20080710220030.GA29558@orion.carnet.hr>
On Thu, 2008-07-10 at 15:00 -0700, Josip Rodin wrote:
> > This is the same crash that you originally reported. The driver was
> > referencing a NULL SKB because the skb_shinfo(skb)->nr_frags was
> > modified on the previous packet in the TX ring.
> >
> > If you had applied my debug patch #1 that I posted several weeks ago, it
> > should have avoided this because we should have saved away the nr_frags
> > for every packet on the TX ring.
>
> It was that same patched kernel that crashed nevertheless.
>
That's strange. You also saw lots of "Corrupted SKB..." dmesg as well,
right? May be the debug patch is not bullet-proof although I cannot see
how we can still get a NULL SKB in the TX completion path.
Anyway, please try today's patch as we need to find the source of the
problem.
Thanks.
next prev parent reply other threads:[~2008-07-10 22:23 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 12:57 bnx2_poll panicking kernel Josip Rodin
2008-06-16 14:04 ` Ben Hutchings
2008-06-16 15:52 ` Michael Chan
2008-06-16 19:13 ` Josip Rodin
2008-06-16 21:38 ` Josip Rodin
2008-06-16 21:48 ` Josip Rodin
2008-06-16 23:45 ` Michael Chan
2008-06-17 22:37 ` Josip Rodin
2008-06-17 22:47 ` Michael Chan
2008-06-21 11:18 ` Josip Rodin
2008-06-21 15:34 ` Bill Fink
2008-06-21 16:11 ` Michael Chan
2008-06-23 18:04 ` Josip Rodin
2008-06-23 21:36 ` Josip Rodin
2008-06-23 22:48 ` Michael Chan
2008-06-24 22:58 ` Michael Chan
2008-06-25 0:04 ` David Miller
2008-06-26 11:01 ` Josip Rodin
2008-06-26 18:04 ` Michael Chan
2008-07-09 16:46 ` Josip Rodin
2008-07-09 16:57 ` Michael Chan
2008-07-09 23:46 ` David Miller
2008-07-10 9:45 ` Aviv Greenberg
2008-07-10 10:09 ` David Miller
2008-07-10 21:00 ` Michael Chan
2008-07-10 21:00 ` David Miller
2008-07-10 21:23 ` Josip Rodin
2008-07-10 21:38 ` Michael Chan
2008-07-10 22:00 ` Josip Rodin
2008-07-10 22:26 ` Michael Chan [this message]
2008-07-10 22:31 ` Josip Rodin
2008-07-10 23:20 ` David Miller
2008-07-11 9:24 ` Josip Rodin
2008-07-11 9:56 ` David Miller
2008-07-11 12:19 ` Patrick McHardy
2008-07-12 9:49 ` Jarek Poplawski
2008-07-12 13:21 ` Jarek Poplawski
2008-07-14 15:27 ` Patrick McHardy
2008-07-14 17:20 ` Jarek Poplawski
2008-07-14 17:25 ` Jarek Poplawski
2008-07-14 20:21 ` Josip Rodin
2008-07-14 21:22 ` Jarek Poplawski
2008-07-14 21:26 ` Josip Rodin
2008-07-14 21:48 ` Jarek Poplawski
2008-07-17 21:30 ` Josip Rodin
2008-07-17 21:44 ` David Miller
2008-07-18 5:12 ` Jarek Poplawski
2008-08-02 12:28 ` bad htb_{en,re}queue return codes causing corrupt data in drivers [was Re: bnx2_poll panicking kernel] Josip Rodin
2008-08-03 7:06 ` bad htb_{en,re}queue return codes causing corrupt data in drivers David Miller
2008-07-14 22:05 ` bnx2_poll panicking kernel Jarek Poplawski
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=1215728763.6901.23.camel@dell \
--to=mchan@broadcom.com \
--cc=bhutchings@solarflare.com \
--cc=billfink@mindspring.com \
--cc=davem@davemloft.net \
--cc=joy@entuzijast.net \
--cc=mirrors@debian.org \
--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 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.