lists.openwall.net   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] [day] [month] [year] [list]
Date:	Sun, 8 Nov 2009 19:44:02 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Pavel Machek <pavel@....cz>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	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 Sunday 08 November 2009, Pavel Machek wrote:
> 
> > > > 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...

In this particular case it should fit into the screen, but it happens during
a VT switch or something like this.

Unfortunately, this issue turns out to be quite difficult to nail down and only
triggers in specific configurations.

Thanks,
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