From: Stephen Hemminger <shemminger@vyatta.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Nick Bowler <nbowler@elliptictech.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Sudden kernel panic with skge in 3.3-rc2
Date: Mon, 6 Feb 2012 16:17:57 -0800 [thread overview]
Message-ID: <20120206161757.6eac9277@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <CAP=VYLp6Kh7OtN0nsTBDkvTvNLMV0jymAmbR0tJX4r-yMdTSQA@mail.gmail.com>
On Mon, 6 Feb 2012 19:11:27 -0500
Paul Gortmaker <paul.gortmaker@windriver.com> wrote:
> On Thu, Feb 2, 2012 at 3:45 PM, Stephen Hemminger <shemminger@vyatta.com> wrote:
>
> [...]
>
> >
> > Try reverting this commit, it seems problematic
> > commit d0249e44432aa0ffcf710b64449b8eaa3722547e
> > Author: stephen hemminger <shemminger@vyatta.com>
> > Date: Thu Jan 19 14:37:18 2012 +0000
> >
> > skge: check for PCI dma mapping errors
> >
>
> I'm seeing similar issues, and a revert of the above caused the
> problems to go away. I'm testing on a baseline of net-next
> as of today (3238a9be4d7a) plus some TIPC patches I was
> trying to test (which are 99.9% unrelated to this, I'm sure).
>
> Details captured from serial console are below. 100% reproducible.
>
> I can probably try a test/debug patch for you if need be.
>
> Paul.
There is a simple bug in the cleanup code reordering. And it is
reproducible here. Working on a better solution.
prev parent reply other threads:[~2012-02-07 0:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 19:21 Nick Bowler
2012-02-02 20:45 ` Stephen Hemminger
2012-02-03 19:28 ` Nick Bowler
2012-02-08 16:32 ` Nick Bowler
2012-02-03 22:05 ` Guillaume Chazarain
2012-02-07 0:11 ` Paul Gortmaker
2012-02-07 0:17 ` Stephen Hemminger [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=20120206161757.6eac9277@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nbowler@elliptictech.com \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
/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