Summary: | sys-power/acpid-1.0.6-r1 / sys-kernel/gentoo-sources-2.6.28 - ACPI Exception,ACPI Error on ASUS F80S Fn+F8 hotkey | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sr. Cv. <srcv> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | mobile+disabled |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
dmesg output
messages.log after pressing Fn+F8 twice |
Description
Sr. Cv.
2009-01-05 14:32:08 UTC
I just check it again, and have the same problem on: sys-kernel/gentoo-sources-2.6.26-r4 sys-kernel/gentoo-sources-2.6.27-r6 sys-kernel/gentoo-sources-2.6.27-r7 Sorry for wrong info before... (In reply to comment #0) > When using gentoo-sources-2.6.28 with asus-laptop after pressing Fn+F8 hotkey What is Fn+F8 supposed to do on that system? > acpi logs: Which version of sys-power/acpid is that? (Please add that to the Summary.) (In reply to comment #2) > (In reply to comment #0) > > When using gentoo-sources-2.6.28 with asus-laptop after pressing Fn+F8 hotkey > > What is Fn+F8 supposed to do on that system? It is supposed to switch between internal and external monitors. However asus-laptop driver simply causes an acpi exception on hotkeys allowing to serve the event by userspace application. And that's in fact the supposed effect here. Maybe also X driver trying to serve the event is involved here. If that's important I use x11-drivers/xf86-video-radeonhd-1.2.4 > > acpi logs: > > Which version of sys-power/acpid is that? (Please add that to the Summary.) Added. However I'm not convinced that its sys-power/acpi bug because after the bug emerges acpi stops working until reboot. Restart of acpid does not help. However I suppose you know better ;-) New thing I just noticed is that the acpi stops working (events are not registered) after I pressed Fn+F8 for the SECOND time. The first time caused error message in logs, then the other hotkeys caused acpi events and when I pressed again Fn+F8 nothing happened, and no more events were registered. I might not have noticed this before, because I was trying to hit the Fn+F8 more then once every time. And more news: after the bug when I try to remove asus-laptop kernel module rmmod process hangs in D state. Which is the last known working kernel? (In reply to comment #5) > Which is the last known working kernel? > I don't know if there is any. Its new laptop and I just didn't get this hotkey working. Tested on kernels listed previously, if you need I can test on another, but which? Does this also occur when you use the acpi_asus module instead of asus_laptop? Yes(In reply to comment #7) > Does this also occur when you use the acpi_asus module instead of asus_laptop? > You mean asus-acpi? Yes it does. The log is: ACPI Exception (exoparg2-0444): AE_AML_PACKAGE_LIMIT, Index (00000000F) is beyond end of object [20080609] ACPI Error (psparse-0530): Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_._Q11] (Node f781be58), AE_AML_PACKAGE_LIMIT And when I press Fn+F8 second time acpi stops working. Thereafter when I try to remove asus_acpi rmmod says it is un use, when I do rmmod -f the process hangs in D state. I also tried to remove the asus_acpi module after I pressed Fn+F8 for the first time, the error was reported in log, but acpi events still worked. The module was removed properly, but when I loaded it again acpi hanged after the FIRST press of Fn+F8, as I had newer removed the asus_acpi! Could you post your /var/log/messages and dmesg? Please try the following : tail -f /var/log/messages > messages_log press Fn+F8 2 times then ctrl+c tail -f and post messages_log and dmesg output here. Thanks. Created attachment 178592 [details]
dmesg output
This is dmesg output. Only last two lines are relevant I think.
Created attachment 178596 [details]
messages.log after pressing Fn+F8 twice
Can you test with the latest development kernel, git-sources-2.6.29_rc3-r7 as of this this. Please feel free to reopen after you've had a chance to provide the info from comment #12 |