From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754257AbXLDU4X (ORCPT ); Tue, 4 Dec 2007 15:56:23 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751454AbXLDU4O (ORCPT ); Tue, 4 Dec 2007 15:56:14 -0500 Received: from mx2.mail.elte.hu ([157.181.151.9]:40822 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751362AbXLDU4N (ORCPT ); Tue, 4 Dec 2007 15:56:13 -0500 Date: Tue, 4 Dec 2007 21:55:03 +0100 From: Ingo Molnar To: Kamalesh Babulal Cc: Andrew Morton , Kyle McMartin , LKML , linuxppc-dev@ozlabs.org, Andy Whitcroft , Balbir Singh , linux-scsi@vger.kernel.org, "Rafael J. Wysocki" , Matthew Wilcox Subject: Re: [BUG] 2.6.24-rc3-git2 softlockup detected Message-ID: <20071204205503.GD32018@elte.hu> References: <474D15FF.5080508@linux.vnet.ibm.com> <20071127232552.ad16e95c.akpm@linux-foundation.org> <474E5CAC.9000108@linux.vnet.ibm.com> <20071129003533.54b4b20e.akpm@linux-foundation.org> <20071130063929.GD2754@fattire.cabal.ca> <20071129230047.1b482562.akpm@linux-foundation.org> <20071129230204.8698f47e.akpm@linux-foundation.org> <474FBB86.5000004@linux.vnet.ibm.com> <20071204122005.GA27286@elte.hu> <47556AE5.8010708@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47556AE5.8010708@linux.vnet.ibm.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Kamalesh Babulal wrote: > Hi Ingo, > > This softlockup is seen in the 2.6.24-rc4 either and looks like a > message because this is seen while running tbench and machine > continues running other test's after the softlockup messages and some > times seen with the bootup, but the machines reaches the login prompt > and able to continue running tests. do you know whether there's any true delay when this happens, or is it a pure softlockup-detector false positive? Ingo