linux-kernel - Re: [2.6.30-rc1] RCU detected CPU 1 stall

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]

Message-Id: <200904140631.BCI82883.LFOHOFJtFMOSVQ@I-love.SAKURA.ne.jp>
Date:	Tue, 14 Apr 2009 06:31:05 +0900
From:	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To:	paulmck@...ux.vnet.ibm.com
Cc:	viro@...IV.linux.org.uk, linux-kernel@...r.kernel.org,
	hugh@...itas.com, jmorris@...ei.org, akpm@...ux-foundation.org
Subject: Re: [2.6.30-rc1] RCU detected CPU 1 stall

Paul E. McKenney wrote:
> > Hello.
> > 
> > Paul E. McKenney wrote:
> > > Is this reproducible?
> > Not always, but it is reproducible.
> 
> Does it reproduce well enough to bisect?
> 
Not impossible, but difficult. This happens less than once on 10 trials.

> > Al Viro wrote:
> > > I'd really love to see results of repeated alt-sysrq-p/alt-sysrq-l, just
> > > to see where was it actually spinning.
> > Below is sysrq message.
> > Maybe something related to khelper's current->mm == NULL warning problem.
> > Full log is at http://I-love.SAKURA.ne.jp/tmp/dmesg-2.6.30-rc1-200904130930.txt .
> 
> I have to defer to the mm guys on this one.

Latest info on khelper's current->mm == NULL warning problem is at
http://lkml.org/lkml/2009/4/13/85 .

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