Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750770AbYGRP4a (ORCPT ); Fri, 18 Jul 2008 11:56:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757570AbYGRP4P (ORCPT ); Fri, 18 Jul 2008 11:56:15 -0400 Received: from cantor2.suse.de ([195.135.220.15]:39080 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757135AbYGRP4O (ORCPT ); Fri, 18 Jul 2008 11:56:14 -0400 Date: Fri, 18 Jul 2008 17:56:12 +0200 Message-ID: From: Takashi Iwai To: Andi Kleen Cc: LKML , Len Brown , robert.moore@intel.com, Jan Beulich Subject: Re: Endless ACPI errors on Linus tree (5b664cb235) In-Reply-To: <20080718155244.GE32051@basil.nowhere.org> References: <87od4vqvaj.fsf@basil.nowhere.org> <20080718155244.GE32051@basil.nowhere.org> User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/22.2 (x86_64-suse-linux-gnu) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2380 Lines: 70 At Fri, 18 Jul 2008 17:52:44 +0200, Andi Kleen wrote: > > On Fri, Jul 18, 2008 at 05:48:39PM +0200, Takashi Iwai wrote: > > At Fri, 18 Jul 2008 15:34:13 +0200, > > I wrote: > > > > > > At Fri, 18 Jul 2008 15:15:25 +0200, > > > I wrote: > > > > > > > > At Fri, 18 Jul 2008 13:35:48 +0200, > > > > Andi Kleen wrote: > > > > > > > > > > Takashi Iwai writes: > > > > > > > > > > > the boot with the latest Linus git tree fails on x86-64 due to the > > > > > > endless kernel messages like below: > > > > > > > > > > > > ACPI Error (evpge-0710): No handler or method for GPE[10], > > > > > > disabling event[20080609] > > > > > > > > > > > > It happens on today's tree and also on yesterday (33af79d12e). > > > > > > The config is below. > > > > > > > > > > That was after the ACPI merge I assume? > > > > > > > > Yes. > > > > > > > > > Do you have a full boot log? > > > > > > > > Sorry, no. The kernel shows the error message (the number after GPE > > > > constantly changing as 1x) endlessly, and couldn't boot up properly to > > > > get a log. > > > > > > > > > Revert candidates to test would be e38e8a0743b0e996a8a3fbea8908fe75a84f02c7 > > > > > and c91d924e3af08d4f98eab6ebf81f2b8ce132448f (Bob, that were both > > > > > changes from you for evgpe.c). Can you see if reverting > > > > > those helps? If yes which? > > > > > > > > Will give it a spin. > > > > > > I reverting both, but it doesn't fix the problem. > > > > > > Another finding is that the boot reaches to the exec of init, at > > > least. So I could get a sane state with init=/bin/sh. The message > > > appears after the init script running udevd. > > > > > > Also, the machine could boot fine with the recent linux-next kernel, > > > at least, 20080711-0714. (It failed for last couple of days, but it > > > can be irrelevant.) > > > > > > I'll investigate a bit. Any hints are appreciated. > > > > OK, found out the bad commit via bisect. > > Reverting below fixes the boot problem. > > Ah thanks. That one was on the revert list anyways becase > it caused some other problems. OK, good to hear :) thanks, Takashi -- 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/