Bug 10217
Summary: | Problem with the Fn+F3 key on my laptop | ||
---|---|---|---|
Product: | ACPI | Reporter: | guillaume (giggzounet) |
Component: | Other | Assignee: | ykzhao (yakui.zhao) |
Status: | REJECTED INSUFFICIENT_DATA | ||
Severity: | normal | CC: | acpi-bugzilla, rui.zhang, trenn |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.24.3 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: |
the acpidump output
debug patch dmesg with acpi debug and 2 hit of Fn+F3 acpidump --addr 0x7FF7BE7D --length 0x40 -o mnvs try the custom DSDT try the custom DSDT dmesg with dsdt patched kernel |
Description
guillaume
2008-03-10 11:18:22 UTC
Created attachment 15202 [details]
the acpidump output
Here is the acpidump output
Created attachment 15206 [details]
debug patch
Will you please try the debug patch and boot the system with the option of "acpi.debug_layer=0x08010084 acpi.debug_level=0x1f"? (Of course please set the CONFIG_ACPI_DEBUG in kernel configuration and use the latest kernel 2.6.24.3)
After the system is booted, please press Fn+F3 twice and attach the output of dmesg.
Thanks.
Hi, Guillaume First we should confirm whether Fn+F3 can trigger EC interrupt and produce ACPI event when press hotkey. Please use the debug patch in comment #2 and attach the output of dmesg. Thanks. Created attachment 15218 [details]
dmesg with acpi debug and 2 hit of Fn+F3
I have just compiled the 2.6.24.3 with your patch and booted with correct options. I attach the dmesg output with 2 hits of the Fn+F3 button
Hi, Guillaume
Thanks for the info.
From the log it seems that EC sci interrupt is triggered when pressing hotkey(Fn+F3). But the _Qc AML code can't produce notify event.
> ACPI: EC: Evaluate _Qc
Maybe it is related with the following :
>If (LNotEqual (And (PAR1, 0x40), 0x40))
Will you please attach the output from the following command?
acpidump --addr 0x7FF7BE7D --length 0x40 -o mnvs
Thanks.
Created attachment 15227 [details]
acpidump --addr 0x7FF7BE7D --length 0x40 -o mnvs
Here is the output of ;
acpidump --addr 0x7FF7BE7D --length 0x40 -o mnvs
Created attachment 15366 [details] try the custom DSDT Will you please try the custom DSDT and attach the output of dmesg? The patch and boot option in comment #2 are also required. From the info in comment #7 the initial value of PAR1 is zero. But there is no notify event for the VGA device or the message "SMI route". How to use the custom DSDT can be found http://www.lesswatts.org/projects/acpi/faq.php Thanks. Created attachment 15527 [details] try the custom DSDT Will you please try the custom DSDT and attach the output as required in comment #8? Thanks. Created attachment 15539 [details]
dmesg with dsdt patched kernel
all the things required... :)
Hi, Guillaume Thanks for the info. From the log in comment #11 we can know that the value of PAR1 is 0x60. > [ACPI Debug] String: [0x16] "PAR1 value is 00000060" As the PAR1 is 0x60, it causes that the following AML code can't be executed and no notification event is sent to VGA device. Of course it will fail in video output switching. > If (LNotEqual (And (PAR1, 0x40), 0x40)) { >Notify (\_SB.PCI0.AGP.VGA, 0x80) } It seems that the problem is related with BIOS. Will you please check whether the latest bios is available and see whether the problem still exists? Thanks. It seems that the bug is caused by the broken bios and it is more appropriate to fix it by upgrading BIOS. At the same time since there is no response for more than one month, it will be rejected. |