Adding myself to CC

please attach the full dmesg output and the acpidump output of this laptop

Hello Zhang,

You can download and view it from :

dmesg: http://userweb.kernel.org/~jaswinder/acer_netbook/dmesg_2634-rc7.txt

acpidump: http://userweb.kernel.org/~jaswinder/acer_netbook/acpidump_output.txt

.config: http://userweb.kernel.org/~jaswinder/acer_netbook/config_2634-rc7.txt

Thanks.

Created attachment 26349 [details]
dmesg

Created attachment 26350 [details]
.config

Created attachment 26351 [details]
acpidump

            Method (_OSC, 4, NotSerialized)
            {
                Store (Arg2, Local0)
                Multiply (Local0, 0x04, Local1)
                Name (BUF1, Buffer (Local1) {})
                Store (Arg3, BUF1)
                Store (Zero, Local1)
                Store (Zero, Local2)
                While (Local0)
                {
                    Multiply (Local1, 0x04, Local2)
                    CreateDWordField (BUF1, Local2, CAPB)
                    If (Arg1)
                    {
                        If (LEqual (Local1, Zero))
                        {
                            And (CAPB, 0xFFFFFFFC, CAPB)
                        }
                    }
                    Else
                    {
                    }

                    Increment (Local1)
                    Decrement (Local0)
                }

                Return (BUF1)
            }

we can see that CAPB is created in the while loop.
this is a violation of ACPI spec that should be fixed by BIOS.
So I'll close this bug as we can/will do nothing in Linux kernel to fix/workaround this bug.

I think you should raise this issue to Acer, to push them fix it in new BIOS releases. :)

Hello Zhang,

We can handle the bug in Linux kernel as treated like special case OR at least print the message to fix or update BIOS or something like that.

What is your opinion.

Thanks.

N(In reply to comment #8)
> Hello Zhang,
> 
> We can handle the bug in Linux kernel as treated like special case OR

No, this is handled in ACPICA code, and I don't think we can put any workaround/fix for this AML bug.

> at least
> print the message to fix or update BIOS or something like that.
> 
> What is your opinion.
> 
No.
ACPICA has its own code base, and is used by many OS, like Linux, Solaris, etc.
ACPICA is not able to detect this kind of bug.
I talked with an ACPICA expert and he said it's overkill to do so because it needs quite a lot of changes in ACPICA.

As we can rootcause the problem according to the current error messages, I think we should put more effort to push Acer to fix this BIOS bug for us. :)

Hello Zhang,

Thanks for your help.

I do not have access to Acer. If possible, please request them to fix this BUG in upcoming models.

If you want you can close this BUG.

Thanks,
--
Jaswinder Singh.