Most recent kernel where this bug did not occur:2.6.21 Distribution:Debian ETCH Hardware Environment:P4 805 Dual Core Software Environment:Debian etch Problem Description: I got this error since kernel-2.6.21 in dmesg : input: Power Button (FF) as /class/input/input0 ACPI: Power Button (FF) [PWRF] input: Power Button (CM) as /class/input/input1 ACPI: Power Button (CM) [PWRB] ACPI Warning (tbutils-0158): Incorrect checksum in table [ ^Eð] - 00, should be 4B [20070126] ACPI Error (tbinstal-0134): Table has invalid signature [ ^Eð], must be SSDT or PSDT [20070126] ACPI Error (psparse-0537): Method parse/execution failed [\_PR_.CPU1._PDC] (Node c213c89c), AE_BAD_SIGNATURE ACPI: Processor [CPU1] (supports 8 throttling states) ACPI Warning (tbutils-0158): Incorrect checksum in table [ ^Eð] - 00, should be 4B [20070126] ACPI Error (tbinstal-0134): Table has invalid signature [ ^Eð], must be SSDT or PSDT [20070126] ACPI Error (psparse-0537): Method parse/execution failed [\_PR_.CPU2._PDC] (Node c213c7fc), AE_BAD_SIGNATURE ACPI: Processor [CPU2] (supports 8 throttling states) Real Time Clock Driver v1.12ac The complete dmesg is here : http://webpmenier.dynalias.net/docext/noyau/26215/dmesg Steps to reproduce: it just appears at boot.
Created attachment 11765 [details] config used to compil kernel
Created attachment 11766 [details] result of cat /proc/acpi/dsdt > dsdt && iasl -d dsdt
Created attachment 11767 [details] complete dmesg
Hmmm, there are dynamic tables with invalid signature. It should be a BIOS bug. Please check if there is any BIOS update first.
Please attach the acpidump output. :)
Created attachment 11963 [details] Acpidump Here is the file made by acpidump > acpidump. When i launch the acpidump command, it replies : Wrong checksum for generic table!
Linux version 2.6.21.5-vs2.2.0-rc1 (root@srvweb)... ... ACPI: DSDT 7FFD0440, 4978 (r1 1AAAA 1AAAA000 0 INTL 2002026) ... ACPI: Table DSDT replaced by host OS ACPI: DSDT 00000000, 46CA (r1 1AAAA 1AAAA000 0 INTL 20060912) please re-open this bug if you still have the problem when you run the firmware that came with the machine.