[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070329194048.GG4892@waste.org>
Date: Thu, 29 Mar 2007 14:40:49 -0500
From: Matt Mackall <mpm@...enic.com>
To: Mariusz Kozłowski <m.kozlowski@...land.pl>
Cc: Ingo Molnar <mingo@...e.hu>,
Andrew Morton <akpm@...ux-foundation.org>,
Adrian Bunk <bunk@...sta.de>, linux-kernel@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>,
john stultz <johnstul@...ibm.com>
Subject: Re: 2.6.21-rc5-mm1
On Thu, Mar 29, 2007 at 09:02:56PM +0200, Mariusz Kozłowski wrote:
> > > > > This is verified and repeatable _every_ single time I tried.
> > > > > Unfortunately the last thing seen on the screen before system is
> > > > > frozen is 'eth0: link down'. So my guess is that when hunting for
> > > > > hangs I found something else that can hang my laptop (netconsole
> > > > > that is).
> > > >
> > > > fix-sysfs-reclaim-crash.patch is known-bad. Did you try reverting
> > > > that?
> > >
> > > Yes, just tested it. Sorry. It doesn't change anything.
> >
> > could you try a !CONFIG_SMP kernel to make sure it's not some
> > self-locking of netconsole that is interfering? (Is it perhaps the
> > 'eth0: link down' message that is trigger from within netconsole?)
>
> This is from .config:
>
> # CONFIG_SMP is not set
>
> Can this be that 'link down' is emitted by netconsole when the link is
> already down and kernel gets locked? Does it make any sense?
Yes, that's probably exactly the problem. But it probably involves locks.
I think a preemptible kernel can also cause the problem?
--
Mathematics is the supreme nostalgia of our time.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists