From: Andi Kleen <andi@firstfloor.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Andi Kleen <andi@firstfloor.org>,
LKML <linux-kernel@vger.kernel.org>, Len Brown <lenb@kernel.org>,
robert.moore@intel.com, Jan Beulich <jbeulich@novell.com>
Subject: Re: Endless ACPI errors on Linus tree (5b664cb235)
Date: Fri, 18 Jul 2008 17:52:44 +0200 [thread overview]
Message-ID: <20080718155244.GE32051@basil.nowhere.org> (raw)
In-Reply-To: <s5hk5fjurag.wl%tiwai@suse.de>
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 <tiwai@suse.de> 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.
-Andi
next prev parent reply other threads:[~2008-07-18 15:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 11:24 Endless ACPI errors on Linus tree (5b664cb235) Takashi Iwai
2008-07-18 11:35 ` Andi Kleen
2008-07-18 13:15 ` Takashi Iwai
2008-07-18 13:34 ` Takashi Iwai
2008-07-18 15:48 ` Takashi Iwai
2008-07-18 15:52 ` Andi Kleen [this message]
2008-07-18 15:56 ` Takashi Iwai
2008-07-18 16:16 ` Jan Beulich
2008-07-18 16:38 ` Takashi Iwai
2008-07-18 16:58 ` Andi Kleen
2008-07-19 9:23 ` Takashi Iwai
2008-07-21 8:11 ` Jan Beulich
2008-07-21 8:43 ` Andi Kleen
2008-07-23 11:27 ` Jan Beulich
2008-07-23 15:43 ` Moore, Robert
2008-07-23 16:14 ` Jan Beulich
2008-09-17 4:56 ` Andrew Paprocki
2008-09-17 6:43 ` Jan Beulich
2008-09-17 15:04 ` Andi Kleen
2008-07-18 15:52 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080718155244.GE32051@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=jbeulich@novell.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.moore@intel.com \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox