linux-kernel - Re: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks on v3.6

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:	Sun, 05 Aug 2012 18:55:41 +0200
From:	Sasha Levin <levinsasha928@...il.com>
To:	Avi Kivity <avi@...hat.com>
CC:	paulmck@...ux.vnet.ibm.com,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	johnstul@...ibm.com, mingo@...nel.org, a.p.zijlstra@...llo.nl,
	prarit@...hat.com, tglx@...utronix.de
Subject: Re: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks on v3.6

On 07/30/2012 03:17 PM, Avi Kivity wrote:
> Possible causes:
>  - the APIC calibration in the guest failed, so it is programming too
> low values into the timer
>  - it actually needs 1 us wakeups and then can't keep up (esp. as kvm
> interrupt injection is slowing it down)
> 
> You can try to find out by changing
> arch/x86/kvm/lapic.c:start_lapic_timer() to impose a minimum wakeup of
> (say) 20 microseconds which will let the guest live long enough for you
> to ftrace it and see what kind of timers it is programming.

I've kept trying to narrow it down, and found out It's triggerable using adjtimex().

At that point I've bisected it, and got the following commit (parties Cc'ed):

commit 5baefd6d84163443215f4a99f6a20f054ef11236
Author: John Stultz <johnstul@...ibm.com>
Date:   Tue Jul 10 18:43:25 2012 -0400

    hrtimer: Update hrtimer base offsets each hrtimer_interrupt


I've also confirmed that reverting the commit above on top of linux-next indeed fixes the issue.
--
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/