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  linux-cve-announce  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, 11 Jul 2011 13:15:08 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Cc:	xen-devel@...ts.xensource.com,
	julie Sullivan <kernelmail.jms@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: 3.0-rc kernels unbootable since -rc3

On Mon, Jul 11, 2011 at 03:30:22PM -0400, Konrad Rzeszutek Wilk wrote:
> > 
> > Hmmm...  Does the stall repeat about every 3.5 minutes after the first stall?
> 
> Starting Configure read-only root support...
> [   81.335070] INFO: rcu_sched_state detected stalls on CPUs/tasks: { 0} (detected by 3, t=60002 jiffies)
> [   81.335091] sending NMI to all CPUs:
> [  261.367071] INFO: rcu_sched_state detected stalls on CPUs/tasks: { 0} (detected by 3, t=240034 jiffies)
> [  261.367092] sending NMI to all CPUs:
> [  441.399066] INFO: rcu_sched_state detected stalls on CPUs/tasks: { 0} (detected by 3, t=420066 jiffies)
> [  441.399089] sending NMI to all CPUs:

OK, then the likely cause is something hanging onto the CPU.  Do the later
stalls also show stack traces?  If so, what shows up?

(Documentation/RCU/stallwarn.txt for more info on this.)

> > 
> > One thing to try would be to disable CONFIG_RCU_FAST_NO_HZ.  I wouldn't
> > expect this to have any effect, but might be worth a try.  It is really
> 
> Did not help.

Well, I guess it met my expectations.  Thank you for trying it!

							Thanx, Paul

> > intended for small battery-powered systems.
> > 
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ