From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Peter Zijlstra <peterz@infradead.org>,
Kevin Winchester <kjwinchester@gmail.com>,
Mike Galbraith <efault@gmx.de>, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>,
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: Sun, 8 Nov 2009 18:28:24 +0100 [thread overview]
Message-ID: <20091108172823.GD1372@ucw.cz> (raw)
In-Reply-To: <200911072001.16223.rjw@sisk.pl>
> > > 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.
>
> FWIW, I see a crash in autoremove_wake_function() during resume from suspend
> to RAM that happens immediately before the thawing of tasks. It always happens
> in the "events" thread. I can trigger it quite reliably, although not 100% of
> the time.
>
> I can only see the bottom half of the call trace, so I can't really say what
> kind of a crash this is.
Our oops printing code sucks. It should mdelay after each screen or
something like that. Call trace should be in reverse order, so the
most useful parts stay on the screen...
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-11-08 17:28 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
2009-11-07 19:01 ` Rafael J. Wysocki
2009-11-08 17:28 ` Pavel Machek [this message]
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=20091108172823.GD1372@ucw.cz \
--to=pavel@ucw.cz \
--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=peterz@infradead.org \
--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