From: Peter Zijlstra <peterz@infradead.org>
To: Kevin Winchester <kjwinchester@gmail.com>
Cc: Mike Galbraith <efault@gmx.de>, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Steven Rostedt <rostedt@goodmis.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Yinghai Lu <yinghai@kernel.org>
Subject: Re: Intermittent early panic in try_to_wake_up
Date: Sat, 07 Nov 2009 17:35:54 +0100 [thread overview]
Message-ID: <1257611754.4108.12.camel@laptop> (raw)
In-Reply-To: <4AF59F24.4010501@gmail.com>
On Sat, 2009-11-07 at 12:24 -0400, Kevin Winchester wrote:
> 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.
Use vga=ask boot_delay=100 select the highest res possible.
Possibly you could use a digital (video) camera to record the output.
next prev parent reply other threads:[~2009-11-07 16:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 23:33 Intermittent early panic in try_to_wake_up Kevin Winchester
2009-10-23 9:23 ` Mike Galbraith
2009-11-05 23:44 ` Kevin Winchester
2009-11-06 5:34 ` Mike Galbraith
2009-11-06 23:49 ` Kevin Winchester
2009-11-07 4:45 ` Mike Galbraith
2009-11-07 16:24 ` Kevin Winchester
2009-11-07 16:35 ` Peter Zijlstra [this message]
2009-11-07 19:01 ` Rafael J. Wysocki
2009-11-08 17:28 ` Pavel Machek
2009-11-08 18:44 ` Rafael J. Wysocki
2009-11-08 8:29 ` Con Kolivas
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=1257611754.4108.12.camel@laptop \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=efault@gmx.de \
--cc=kjwinchester@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rjw@sisk.pl \
--cc=rostedt@goodmis.org \
--cc=yinghai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox