linux-kernel - Re: Endless ACPI errors on Linus tree (5b664cb235)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <s5hr69rz57u.wl%tiwai@suse.de>
Date:	Fri, 18 Jul 2008 15:34:13 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	LKML <linux-kernel@...r.kernel.org>, Len Brown <lenb@...nel.org>,
	robert.moore@...el.com
Subject: Re: Endless ACPI errors on Linus tree (5b664cb235)

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@...e.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.


thanks,

Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/