linux-kernel - Re: RCU idle CPU detection is broken in linux-next

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5060E863.6020006@gmail.com>
Date:	Tue, 25 Sep 2012 01:10:27 +0200
From:	Sasha Levin <levinsasha928@...il.com>
To:	Frederic Weisbecker <fweisbec@...il.com>
CC:	paulmck@...ux.vnet.ibm.com,
	Michael Wang <wangyun@...ux.vnet.ibm.com>,
	Dave Jones <davej@...hat.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: RCU idle CPU detection is broken in linux-next

On 09/25/2012 01:06 AM, Frederic Weisbecker wrote:
> 2012/9/25 Sasha Levin <levinsasha928@...il.com>:
>> On 09/25/2012 12:47 AM, Sasha Levin wrote:
>>>  - While I no longer see the warnings I've originally noticed, if I run with Paul's last debug patch I see the following warning:
>>
>> Correction: Original warnings are still there, they just got buried in the huge spew that was caused by additional debug warnings
>> so I've missed them initially.
> 
> Are they the same? Could you send me your dmesg?
> 
> Thanks.
> 

Log is attached, you can go directly to 168.703017 when the warnings begin.


Thanks,
Sasha

Download attachment "log.txt.gz" of type "application/gzip" (180589 bytes)