From: John Stultz <john.stultz@linaro.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: BUG: soft lockup - CPU#1 stuck for 1024s!
Date: Tue, 11 Sep 2012 16:50:32 -0700 [thread overview]
Message-ID: <504FCE48.1050409@linaro.org> (raw)
In-Reply-To: <20120911234130.GA13382@localhost>
On 09/11/2012 04:41 PM, Fengguang Wu wrote:
> On Mon, Sep 10, 2012 at 10:06:33AM -0700, John Stultz wrote:
>> On 09/09/2012 12:59 AM, Fengguang Wu wrote:
>>> Hi John,
>>>
>>> The below lockup warning pops up very occasionally in kvm guest
>>> kernels and it's bisected down to
>>>
>>> commit 2a8c0883c3cfffcc148ea606e2a4e7453cd75e73
>>> Author: John Stultz <john.stultz@linaro.org>
>>> Date: Fri Jul 13 01:21:56 2012 -0400
>>>
>>> time: Move xtime_nsec adjustment underflow handling timekeeping_adjust
>>>
>>> [ 8.340327] Freeing unused kernel memory: 460k freed
>>> [ 1107.515496] [sched_delayed] sched: RT throttling activated
>>> [ 1107.516439] BUG: soft lockup - CPU#1 stuck for 1024s! [swapper/1:0]
>>
>> Thanks so much for sending this. One detail I'm curious about is
>> that these kernels from the Bug messages seem to be v3.6-rc1 or
>> earlier.
>>
>> Ingo had a fix 1d17d17484d40f2d5b35c79518597a2b25296996 ("time: Fix
>> adjustment cleanup bug in timekeeping_adjust") that landed in
>> 3.6-rc2
>>
>> Has this issue actually been seen on a 3.6-rc2+ kernel?
> Nope. I tested -rc5 for 10000+ boots and it's obviously free from the bug.
> Sorry for the noise!
No worries. Thanks so much for following up on this, and your continued
testing!
-john
prev parent reply other threads:[~2012-09-11 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-09 7:59 BUG: soft lockup - CPU#1 stuck for 1024s! Fengguang Wu
2012-09-10 17:06 ` John Stultz
2012-09-11 23:41 ` Fengguang Wu
2012-09-11 23:50 ` John Stultz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=504FCE48.1050409@linaro.org \
--to=john.stultz@linaro.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.