Bug 4349

Summary:	acpi disables buttons/hotkeys on R40e
Product:	Drivers	Reporter:	Hari Selvarajan (hari.selvarajan)
Component:	Platform	Assignee:	Luming Yu (luming.yu)
Status:	REJECTED INSUFFICIENT_DATA
Severity:	normal	CC:	acpi-bugzilla
Priority:	P2
Hardware:	i386
OS:	Linux
Kernel Version:	2.6.11	Subsystem:
Regression:	---	Bisected commit-id:
Attachments:	dmesg output DSDT from iasl -d

Description Hari Selvarajan 2005-03-16 13:53:01 UTC

Distribution: Slackware 10.0
Hardware Environment: IBM R40e Model 2864-PA3 (Mobile Celeron 2.2 GHz)
Software Environment: Kernel 2.6.11, ACPI version 20050309
Problem Description:  Enabling ACPI causes volume/mute button and hotkeys to 
stop working

Steps to reproduce:

Boot with acpi=off. Volume control and Mute buttons work, as do Fn+F7 to switch 
from LCD to CRT and Fn+Home and Fn+End to increase/decrease screen brightness. 
tpb -d (http://www.nongnu.org/tpb/) displays a message when a button or hotkey 
is pressed.

Boot again with ACPI enabled. Volume control/Mute buttons do not work any 
longer, and Fn+F7, Fn+Home and Fn+End have no effect. tpb does not print a 
message when a button or hotkey is pressed.

Comment 1 Hari Selvarajan 2005-03-16 14:06:56 UTC

Created attachment 4734 [details]
dmesg output

Output of dmesg

Comment 2 Hari Selvarajan 2005-03-16 14:08:42 UTC

Created attachment 4735 [details]
DSDT from iasl -d

Forgot to mention - this is an IBM Thinkpad R40e; I left out the IBM and
Thinkpad parts

Comment 3 Matthew Garrett 2005-03-17 16:22:19 UTC

The R40e is very different to most Thinkpads. It's entirely possible that the
BIOS disables the hotkeys once an OS switches on ACPI.

Comment 4 Hari Selvarajan 2005-03-17 16:29:14 UTC

I agree that the R40e is very different from most thinkpads - it's more 
a "winpad" than a thinkpad, unfortunately - but looking through the DSDT, it 
does seem that there is a HKEY device and corresponding methods for S3/S4 
sleep, display switching, etc., which are very similar if not identical to 
other thinkpads with better linux support.

I'm not an ACPI expert though (I wish I were) so I'll defer to someone with 
more expertise/experience than me.

Comment 5 Luming Yu 2005-09-06 20:26:10 UTC

It looks like a bug that the HKEY device doesn't work. 
Any differences with more recent kernel?

Comment 6 Luming Yu 2005-10-10 18:40:54 UTC

I found this error in dmesg:

Executing all Device _STA and_INI methods:............................<3>irq 
9: nobody cared!
 [<c012efda>] __report_bad_irq+0x2a/0xa0
 [<c012eac0>] handle_IRQ_event+0x30/0x70
 [<c012f0e0>] note_interrupt+0x70/0xb0
 [<c012ebe0>] __do_IRQ+0xe0/0xf0
 [<c010499e>] do_IRQ+0x3e/0x60
 =======================
 [<c01030a2>] common_interrupt+0x1a/0x20
 [<c01193fe>] __do_softirq+0x2e/0x90
 [<c0104aa1>] do_softirq+0x41/0x50
 =======================
 [<c01049a5>] do_IRQ+0x45/0x60
 [<c01030a2>] common_interrupt+0x1a/0x20
 [<c027d9b6>] acpi_ec_read+0x120/0x14e

Please make sure the recent kernel doesn't have this error.
Please reopen it, if you still have such problem with the latest base kernel.