Re: ntp: BUG: spinlock lockup on CPU#1

[Thomas Gleixner]

On Thu, 15 Mar 2012, Sasha Levin wrote:

> On Thu, Mar 15, 2012 at 3:23 PM, Sasha Levin <levinsasha928@xxxxxxxxx> 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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/