From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760722Ab2COOE4 (ORCPT ); Thu, 15 Mar 2012 10:04:56 -0400 Received: from www.linutronix.de ([62.245.132.108]:40392 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755674Ab2COOEz (ORCPT ); Thu, 15 Mar 2012 10:04:55 -0400 Date: Thu, 15 Mar 2012 15:04:53 +0100 (CET) From: Thomas Gleixner To: Sasha Levin cc: John Stultz , Dave Jones , "linux-kernel@vger.kernel.org List" Subject: Re: ntp: BUG: spinlock lockup on CPU#1 In-Reply-To: Message-ID: References: User-Agent: Alpine 2.02 (LFD 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 15 Mar 2012, Sasha Levin wrote: > On Thu, Mar 15, 2012 at 3:23 PM, Sasha Levin 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