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  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:	Mon, 2 Jan 2012 11:58:56 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 00/16] [GIT PULL] tracing: fixes/cleanups, no
 stop-machine, update stack tracer


* Ingo Molnar <mingo@...e.hu> wrote:

> Hm, i'm seeing spontaneous reboot crashes with these commits 
> applied. The reboots just happen out of the blue during an 
> allyesconfig bootup (config attached), and they happen at 
> random places.

I've done more testing to pin down which commits are to blame.

To complicate matters, re-testing with the NMI bits applied 
produced a spontaneous reboot as well in one case, after 12 
iterations.

Just to give you an impression of how a failure looks like, the 
serial console just stops printing mid-line:

 [   53.212942] calling  vt1211_init+0x0/0x9b @ 1                                                   
 [   53.212971] initcall vt1211_init+0x0/0x9b returned -19 after 23 usecs                           
 [   53.212975] calling  sm_vt8231_init+0x0/0x1b @ 1                                                
   Booting 'Fedora'

and the next message is GRUB's 'Booting ...' line.

I've tested baseline -tip as well:

    db6ffcaa1306: Merge branch 'out-of-tree'

and it seem to be fine: it has survived 70 allyesconfig bootups 
with the config i sent.

So either the NMI bits or the 'fixes' bits are broken - or the 
bug is somehow kernel image dependent and triggered in these two 
trees and somehow left the baseline kernel unaffected ...

Since each test takes half a day to accomplish and i don't have 
the days to spend on this problem alone, one way we could 
proceed from here is if you cherry-picked the '100% safe' 
commits from your tree. I could pull those and make certain that 
they are not crashing things.

Thanks,

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