From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753895AbYEKJfW (ORCPT ); Sun, 11 May 2008 05:35:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750799AbYEKJfG (ORCPT ); Sun, 11 May 2008 05:35:06 -0400 Received: from mailhost.tue.nl ([131.155.3.8]:56119 "EHLO mailhost.tue.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751163AbYEKJfF (ORCPT ); Sun, 11 May 2008 05:35:05 -0400 From: Henny Wilbrink MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18470.48583.228614.436610@gargle.gargle.HOWL> Date: Sun, 11 May 2008 11:35:03 +0200 To: "Carlos R. Mafra" CC: linux-kernel@vger.kernel.org, venkatesh.pallipadi@intel.com Subject: Re: 2.6.26-rc1 fails to boot In-Reply-To: <20080510222201.GA3754@beyonder.ift.unesp.br> References: <18470.968.939325.722176@gargle.gargle.HOWL> <20080510222201.GA3754@beyonder.ift.unesp.br> X-Mailer: VM 8.0.9 under Emacs 22.1.1 (x86_64-redhat-linux-gnu) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Carlos R. Mafra wrote: > On Sat 10.May'08 at 22:21:28 +0200, Henny Wilbrink wrote: > Content-Description: message body text > > Hello, > > > > Kernel 2.6.26-rc1 completely fails to boot on my laptop. The last line > > appearing on the console is: > > > > ACPI: Processor [CPU1] (supports 8 throttling states) > > Does booting with hpet=disable help? No, 2.6.26-rc1 with hpet=disable now stops at ata_piix 0000:00:1f.2: MAP [ P0 P2 IDE IDE ] However, with idle=mwait as suggested by Venkatesh Pallipadi it did boot in 2 out of 2 attempts. > > > Kernel 2.6.25 fails to boot in an estimated 1 in 2 attempts. The last > > line on the console if this one fails is: > > > > ACPI: LNXTHERM:01 is registered as thermal_zone0 > > > > I did a git bisection with "fails to boot in the first three attempts" > > as the definition of "bad" between 2.6.26-rc1 and 2.6.25-rc3 which I > > believed to be free of this problem. The many reboots in the > > bisection process however showed me that 2.6.25-rc3 also has an > > estimated 1 in 10 chance of failing. Anyway, the bisection ended > > with: > > > > 8a3227268877b81096d7b7a841aaf51099ad2068 is first bad commit > > > > The bisection log and dmesg are attached. > > I have this boot problem since before 2.6.25-rc1 but it is > very difficult to do a bisection. Sometimes the probability > of hanging was 1:30 and what I thought was a good kernel in > fact was bad. > > In fact the commit you got is a "merge commit" which does not > change the source code so it is clearly bogus. > > Mark Lord points out that this bug comes and goes with slight > modifications in the .config, and in fact very recently > the probability of hanging changed dramatically for me. > > I have already booted the kernel afa26be86b65 (six commits > after 2.6.26-rc1) more than 30 times and it did not hang. > > You can also take a look at some discussion here: > http://bugzilla.kernel.org/show_bug.cgi?id=10117 > Yes this definitely looks like the same problem. > And good luck with this! Thanks, Henny