linux-kernel - Re: Patch needed for ASUS EEEPC 701 2.6.27 (perhaps a regession)

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-next>] [day] [month] [year] [list]

Date:	Sat, 11 Oct 2008 15:50:21 +0100
From:	Alan Jenkins <alan-jenkins@...fmail.co.uk>
To:	Robert Goldner <robert@...79.de>
CC:	linux-kernel <linux-kernel@...r.kernel.org>,
	linux acpi <linux-acpi@...r.kernel.org>,
	linux-stable@...r.kernel.org
Subject: Re: Patch needed for ASUS EEEPC 701 2.6.27 (perhaps a regession)

Robert Goldner wrote:

> Hi,
>
> I am a happy user of an asus eeepc 701 with an self-made kernel 2.6.27.
> Its working quite good, but there is one patch needed to avoid problems
> related to ACPI and Hotkeys.
> After using a few hotkeys there comes a message in syslog like:
> ACPI: EC: GPE storm detected, disabling EC GPE
> and no hotkey event is recognized any more. This is quite bad on a nettop.

Hi, I reported the original bug.  It is a regression, though the issue
has been present for a few kernel versions now.

I recommend that you avoid reproducing the problem.  I now have to add
"noapic" to the boot options on my EeePC, otherwise it randomly hangs /
reboots when I press hotkeys - I think it  damaged the hardware.

BTW you can avoid reproducing the issue on buggy kernels by not pressing
hotkeys quickly - and *never* holding them down; autorepeat is the main
problem.  Wait for the effect of the previous hotkey press to take
effect (e.g. decrementing the screen brightness) before you press a
hotkey again.  But it is safest to just not use them.

> The needed patch and the bug description is available at:
> http://bugzilla.kernel.org/show_bug.cgi?id=10919
> The patch is called 'patch vs 2.6.27-rc7'
>
> The patch fits also to 2.6.27 without any problems and works very fine.
> Thanks to everyone who was involved.
>
> I would suggest to include this patch in the mainline kernel very soon
> (e.g. 2.6.28 or if possible in 2.6.27.1).

The patch is part of Len's ACPI patch queue for the current merge
window, so it should appear in 2.6.28.  However it's not marked "CC:
linux-stable@...r.kernel.org", so it will not be automatically included
in 2.6.27.1.

I think it's up to the ACPI maintainers, if they think there's a risk it
might introduce other regressions.  As you say, it's been tested on a
range of problematic laptops, but OTOH this area has been a minefield. 
Maybe it needs to wait, at least until it's been in an -rc release or two.

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/