lkml.org 
[lkml]   [2008]   [Jul]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Endless ACPI errors on Linus tree (5b664cb235)
    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 <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.

    OK, good to hear :)


    thanks,

    Takashi


    \
     
     \ /
      Last update: 2008-07-18 17:59    [W:0.025 / U:118.016 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site