lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 07 Nov 2009 17:35:54 +0100
From:	Peter Zijlstra <>
To:	Kevin Winchester <>
Cc:	Mike Galbraith <>, Ingo Molnar <>,
	LKML <>,
	"Rafael J. Wysocki" <>,
	Steven Rostedt <>,
	Andrew Morton <>,
	"Paul E. McKenney" <>,
	Yinghai Lu <>
Subject: Re: Intermittent early panic in try_to_wake_up

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.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists