[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200911072001.16223.rjw@sisk.pl>
Date: Sat, 7 Nov 2009 20:01:16 +0100
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Kevin Winchester <kjwinchester@...il.com>,
Mike Galbraith <efault@....de>, Ingo Molnar <mingo@...e.hu>,
LKML <linux-kernel@...r.kernel.org>,
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
On Saturday 07 November 2009, Peter Zijlstra wrote:
> 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.
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.
Also, for quite some time I've been observing a resume-from-hibernation crash
during the final switch from a VT to X that could also be explained by a
problem with "events".
Best,
Rafael
--
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