Bug 16328
Summary: | FN+PgUp (thinklight) doesn't generate event (acpi, xev, showkey) | ||
---|---|---|---|
Product: | ACPI | Reporter: | Pavol Klačanský (pavol) |
Component: | Other | Assignee: | Zhang Rui (rui.zhang) |
Status: | REJECTED INSUFFICIENT_DATA | ||
Severity: | normal | CC: | acpi-bugzilla, pavol, rui.zhang |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.32-22-generic | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: |
output after pressing hotkey
output before pressing hotkey acpidump custom _Q14 method dmesg after hotkey pressing dmesg (thinklight on) dmesg (thinklight off) grep acpi output |
Description
Pavol Klačanský
2010-07-03 10:00:21 UTC
Thinkpad T500 please attach the acpidump output. please attach the output of "grep . /sys/firmware/acpi/interrupts/*" both before and after pressing the hotkeys. I hope I do it well Created attachment 27018 [details]
output after pressing hotkey
Created attachment 27019 [details]
output before pressing hotkey
Created attachment 27020 [details]
acpidump
Created attachment 27097 [details]
custom _Q14 method
please
1. build the latest upstream kernel with CONFIG_ACPI_DEBUG=y
2. boot with acpi.debug_level=0x02
3. make sure the debugfs is mounted
4. apply the custom _Q14 method by running "cat _Q14 > /sys/kernel/debug/acpi/custom_method"
5. try to increase the backlight via hotkeys.
6. attach the dmesg output after the test.
Hallo, I am working on this info, I am sorry, I must forgot :/ Please, could you explain, why numbers in /sys/firmware/acpi/interrupts/* are after hotkey press increased by 2? thanks It can be handled by commands sudo sh -c "echo on > /proc/acpi/ibm/light" sudo sh -c "echo off > /proc/acpi/ibm/light" cat /proc/acpi/ibm/light status: off commands: on, off but I need event, at weekend I am going to compile latest kernel with debug flags (I have limited intertned data transfer) please set CONFIG_ACPI_DEBUG, and reboot with acpi.debug_layer=0x04 acpi.debug_level=0x04. please attach the dmesg output after pressing the hotkey. And please do the test in comment #7 Created attachment 32662 [details]
dmesg after hotkey pressing
Created attachment 32672 [details]
dmesg (thinklight on)
Created attachment 32682 [details]
dmesg (thinklight off)
(In reply to comment #11) > Created an attachment (id=32662) [details] > dmesg after hotkey pressing nothing interesting. I'm wondering if CONFIG_ACPI_DEBUG is set or not. :p please attach the output of "grep . /sys/module/acpi/parameters/*" at this time. And could you please do the test in comment #7 in a kernel newer than 2.6.35? follow the steps below. (In reply to comment #7) > Created an attachment (id=27097) [details] > custom _Q14 method > > please > 1. build the latest upstream kernel with CONFIG_ACPI_DEBUG=y > 2. boot with acpi.debug_level=0x02 > 3. make sure the debugfs is mounted > 4. apply the custom _Q14 method by running "cat _Q14 > > /sys/kernel/debug/acpi/custom_method" 5. echo 1 > /sys/module/acpi/aml_debug_output 6. try to increase the backlight via hotkeys. 7. attach the dmesg output after the test. I am idiot, I cannot find it in grep output, but in .config file, there is "CONFIG_ACPI_DEBUG=y" (it has been my first kernel compilation) this is not about thinklight (has two states, on/off) tomorrow, I will compile latest sources, but I really don't know, why it was compiled without ACPI debug Created attachment 32892 [details]
grep acpi output
oh, the grep acpi output shows that CONFIG_ACPI_DEBUG is set but /sys/module/acpi/parameters/debug_layer:debug_layer = 0x00000000 ( * = enabled) can you please echo 4 > /sys/module/acpi/parameters/debug_layer as root user and then 1. dmesg -c 2. press the hotkey for several times 3. attach the dmesg output dmesg output is empty :/ is the custom _Q14.aml applied? yes, is "acpi.debug_level=0x02" required also? (In reply to comment #20) > yes, is "acpi.debug_level=0x02" required also? no if you can make sure /sys/module/acpi/aml_debug_output equals 1. bug closed as there is no response from the bug reporter. please feel free to re-open it if the problem still exists in the latest upstream kernel. |