From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761160Ab3BNOyb (ORCPT ); Thu, 14 Feb 2013 09:54:31 -0500 Received: from mail-ea0-f173.google.com ([209.85.215.173]:60287 "EHLO mail-ea0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753680Ab3BNOy2 (ORCPT ); Thu, 14 Feb 2013 09:54:28 -0500 Date: Thu, 14 Feb 2013 15:54:24 +0100 From: Ingo Molnar To: Thomas Gleixner Cc: Linus Torvalds , Linux Kernel Mailing List , Jens Axboe , Alexander Viro , "Theodore Ts'o" , "H. Peter Anvin" Subject: Re: [-rc7 regression] Block IO/VFS/ext3/timer spinlock lockup? Message-ID: <20130214145424.GA26071@gmail.com> References: <20130213111007.GA11367@gmail.com> <20130214144510.GC25282@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130214144510.GC25282@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > CPU0 appears to be idle: > > [ 118.510000] Call Trace: > [ 118.510000] [<7900844b>] cpu_idle+0x86/0xb4 > [ 118.510000] [<792a91df>] rest_init+0x103/0x108 > [ 118.510000] [<794558cc>] start_kernel+0x2c7/0x2cc So, I've done a partial bisection, the breakage appears to have gone upstream between v3.8-rc3 and v3.8-rc4. This roughly coincides with the time frame when I first saw these lockups pop up, so in that sense it's a plausible result - but there weren't all that many commits in -rc4 and none looks really suspicious, so this might be one of those non-bisectable bugs. ( Later today I'll try to finish the bisection just in case it results in something useful. ) Thanks, Ingo