From: Thomas Gleixner <tglx@linutronix.de>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: John Stultz <john.stultz@linaro.org>,
Dave Jones <davej@redhat.com>,
"linux-kernel@vger.kernel.org List"
<linux-kernel@vger.kernel.org>
Subject: Re: ntp: BUG: spinlock lockup on CPU#1
Date: Thu, 15 Mar 2012 15:04:53 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1203151503530.2466@ionos> (raw)
In-Reply-To: <CA+1xoqdeuorMi+=EZLpyrBN9L+J2o4SF-8meY=5Qypze9XrpiQ@mail.gmail.com>
On Thu, 15 Mar 2012, Sasha Levin wrote:
> On Thu, Mar 15, 2012 at 3:23 PM, Sasha Levin <levinsasha928@gmail.com> wrote:
> > Hi all,
> >
> > I was doing some more fuzzing with trinity in a KVM tools guest, using
> > today's linux-next, when I've experienced a complete system lockup
> > (just in the guest ofcourse). After a bit I got the spew at the bottom
> > of this mail.
> >
> > From what I can tell from the logs, there were several threads waiting
> > on syscall results, and I suspect that the adjtimex() call on CPU3 is
> > somehow responsible for this lockup.
>
> Oh, and I'm not sure if it's related or not, but I've started seeing
> the following spew every time I start fuzzing:
>
> [ 47.105987] ------------[ cut here ]------------
> [ 47.106021] WARNING: at kernel/time/clockevents.c:209
It's unrelated, but I'm mighty curious how you manage that.
Thanks,
tglx
next prev parent reply other threads:[~2012-03-15 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 13:23 ntp: BUG: spinlock lockup on CPU#1 Sasha Levin
2012-03-15 13:28 ` Sasha Levin
2012-03-15 14:04 ` Thomas Gleixner [this message]
2012-03-15 14:52 ` Sasha Levin
2012-03-15 14:03 ` Thomas Gleixner
2012-03-15 14:58 ` Thomas Gleixner
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=alpine.LFD.2.02.1203151503530.2466@ionos \
--to=tglx@linutronix.de \
--cc=davej@redhat.com \
--cc=john.stultz@linaro.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox