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:	Sun, 8 Nov 2009 18:28:24 +0100
From:	Pavel Machek <>
To:	"Rafael J. Wysocki" <>
Cc:	Peter Zijlstra <>,
	Kevin Winchester <>,
	Mike Galbraith <>, Ingo Molnar <>,
	LKML <>,
	Steven Rostedt <>,
	Andrew Morton <>,
	"Paul E. McKenney" <>,
	Yinghai Lu <>
Subject: Re: Intermittent early panic in try_to_wake_up

> > > 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...

(cesky, pictures)
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