[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AF59F24.4010501@gmail.com>
Date: Sat, 07 Nov 2009 12:24:04 -0400
From: Kevin Winchester <kjwinchester@...il.com>
To: Mike Galbraith <efault@....de>
CC: Ingo Molnar <mingo@...e.hu>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
LKML <linux-kernel@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...k.pl>,
Steven Rostedt <rostedt@...dmis.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Yinghai Lu <yinghai@...nel.org>
Subject: Re: Intermittent early panic in try_to_wake_up
Mike Galbraith wrote:
> On Fri, 2009-11-06 at 19:49 -0400, Kevin Winchester wrote:
>
>> The patch below does not apply to mainline, unless I'm doing something wrong.
>> It's against -tip, I assume? Is it just as applicable to mainline?
>
> It was mainline, but I had the scheduler pull request and another in for
> testing as well. Linus has pulled, so it'll apply now, with offsets.
>
It did end up applying, but did not have any effect. Looking at the patch
again, I see that it appears to only affect CONFIG_SMP, which I am not
running (and in fact it adds a build warning for the !SMP case). So there
was not much chance of it fixing anything, I suppose.
Any other ideas? I don't have a serial console, and the trace scrolls off
my console, so I don't know if any debug printks would help. Would it help
if I copied the entire panic message entirely, including the Code section?
I can try that the next time it happens.
--
Kevin
--
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