linux-kernel - Re: Asus Eee 901Go ACPI errors on 2.6.30-rc4-git4

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: <9b2b86520905080646r85f30bcp6f50d7388d8289f5@mail.gmail.com>
Date:	Fri, 8 May 2009 14:46:05 +0100
From:	Alan Jenkins <sourcejedi.lkml@...glemail.com>
To:	Mario Lang <mlang@...raz.at>
Cc:	linux-kernel@...r.kernel.org,
	ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
	Alexey Starikovskiy <astarikovskiy@...e.de>
Subject: Re: Asus Eee 901Go ACPI errors on 2.6.30-rc4-git4

On 5/8/09, Mario Lang <mlang@...raz.at> wrote:
> Hi.
>
> Booting 2.6.30-rc4-git4 on an Asus Eee 901Go I get the following in dmesg:
>
> [   27.005071] ACPI: EC: missing confirmations, switch off interrupt mode.
> [   27.548097] ACPI Exception (evregion-0422): AE_TIME, Returned by Handler
> for [EmbeddedControl] [20090320]
> [   27.548139] ACPI Error (psparse-0537): Method parse/execution failed
> [\_SB_.PCI0.SBRG.EC0_.BST1] (Node f7033d4c), AE_TIME
> [   27.548280] ACPI Error (psparse-0537): Method parse/execution failed
> [\_SB_.PCI0.CBST] (Node f70366f8), AE_TIME
> [   27.548393] ACPI Error (psparse-0537): Method parse/execution failed
> [\_SB_.PCI0.BAT0._BST] (Node f7034c48), AE_TIME
> [   27.548521] ACPI Exception (battery-0385): AE_TIME, Evaluating _BST
> [20090320]

Odd.  Did this happen in 2.6.29?

If so - I think there's only one significant EC change since 2.6.29,
you could try reverting that.

34ff4dbccccce54c83b1234d39b7ad9e548a75dd "ACPI: EC: Separate delays
for MSI hardware"

Alan
--
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/