Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753259AbYCIGP0 (ORCPT ); Sun, 9 Mar 2008 01:15:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751464AbYCIGPS (ORCPT ); Sun, 9 Mar 2008 01:15:18 -0500 Received: from ns2.g-housing.de ([81.169.133.75]:42692 "EHLO mail.g-house.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751428AbYCIGPR (ORCPT ); Sun, 9 Mar 2008 01:15:17 -0500 Date: Sun, 9 Mar 2008 07:15:09 +0100 (CET) From: Christian Kujau X-X-Sender: evil@sheep.housecafe.de To: David Chinner cc: LKML , xfs@oss.sgi.com Subject: 2.6.25-rc hangs (was: INFO: task mount:11202 blocked for more than 120 seconds) In-Reply-To: Message-ID: References: <20080307224040.GV155259@sgi.com> User-Agent: Alpine 1.00 (DEB 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2913 Lines: 65 On Sat, 8 Mar 2008, Christian Kujau wrote: > FWIW, it's 100% reproducible with 2.6.25-rc3 too...sigh :-\ > So, the last working kernel for me is 2.6.24.1 - that's a lot of bisecting > and I fear that compile errors will invalidate the bisecting results again or > make it impossible at all....I'll try anyway....tomorrow... Bisecting failed as expected :-( I tried to follow the git-bisect manpage (and have successfully used bisect in the past a few times), but I think ~5700 revisions between 2.6.24 and 2.6.25 are just too much fuzz. The bisect logs so far, with my comments inbetween: git-bisect start # 2.6.25-rc4, known to be bad: # bad: [84c6f6046c5a2189160a8f0dca8b90427bf690ea] x86_64: make ptrace always sign-extend orig_ax to 64 bits git-bisect bad 84c6f6046c5a2189160a8f0dca8b90427bf690ea # 2.6.24, good: # good: [49914084e797530d9baaf51df9eda77babc98fa8] Linux 2.6.24 git-bisect good 49914084e797530d9baaf51df9eda77babc98fa8 # 2.6.24, hard lockup during boot, bad: # bad: [bd45ac0c5daae35e7c71138172e63df5cf644cf6] Merge branch 'linux-2.6' git-bisect bad bd45ac0c5daae35e7c71138172e63df5cf644cf6 I marked the last one bad, because I could not boot any more. As it's a headless box, I could not get more details. It did not even respond so sysrq-b. After marking this bad, I compiled and booted again - same result, hard lockup. So I tried again: git bisect reset git-bisect start # 2.6.25-rc4, known to be bad: # bad: [84c6f6046c5a2189160a8f0dca8b90427bf690ea] x86_64: make ptrace always sign-extend orig_ax to 64 bits git-bisect bad 84c6f6046c5a2189160a8f0dca8b90427bf690ea # 2.6.24, good: # good: [49914084e797530d9baaf51df9eda77babc98fa8] Linux 2.6.24 git-bisect good 49914084e797530d9baaf51df9eda77babc98fa8 # 2.6.24, hard lockup during boot, marking good anyway: # good: [bd45ac0c5daae35e7c71138172e63df5cf644cf6] Merge branch 'linux-2.6' git-bisect good bd45ac0c5daae35e7c71138172e63df5cf644cf6 # lockup # bad: [f0f1b3364ae7f48084bdf2837fb979ff59622523] Merge branch 'release' of git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6 git-bisect bad f0f1b3364ae7f48084bdf2837fb979ff59622523 Although I could not boot with bd45ac0c5daae35e7c71138172e63df5cf644cf6, I marked it "good", as the lockup is totally unrelated to my problem. However, the box locks up as soon as I'm using the device-mapper. This time it does respond to sysrq-b. But still: I'm unable to diagnose the system hang [0] and I fear that 2.6.25 is released and for the first time since ages I'd have to skip a release... Help! Christian. [0] http://lkml.org/lkml/2008/3/7/308 -- BOFH excuse #288: Hard drive sleeping. Let it wake up on it's own... -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/