[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120206161757.6eac9277@nehalam.linuxnetplumber.net>
Date: Mon, 6 Feb 2012 16:17:57 -0800
From: Stephen Hemminger <shemminger@...tta.com>
To: Paul Gortmaker <paul.gortmaker@...driver.com>
Cc: Nick Bowler <nbowler@...iptictech.com>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: Sudden kernel panic with skge in 3.3-rc2
On Mon, 6 Feb 2012 19:11:27 -0500
Paul Gortmaker <paul.gortmaker@...driver.com> wrote:
> On Thu, Feb 2, 2012 at 3:45 PM, Stephen Hemminger <shemminger@...tta.com> wrote:
>
> [...]
>
> >
> > Try reverting this commit, it seems problematic
> > commit d0249e44432aa0ffcf710b64449b8eaa3722547e
> > Author: stephen hemminger <shemminger@...tta.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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists