lkml.org 
[lkml]   [2012]   [Mar]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: ntp: BUG: spinlock lockup on CPU#1
    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




    \
     
     \ /
      Last update: 2012-03-15 15:07    [W:0.020 / U:29.808 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site