linux-kernel - FW: ACPI Warning: Invalid length for Pm1aControlBlock: 32, using default 16 (20090903/tbfadt-607)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <88E058D95F1C6047975B85AB9C600B1F6DB20525AF@GVW1342EXA.americas.hpqcorp.net>
Date:	Fri, 14 Jan 2011 18:33:13 +0000
From:	"Berahalli, Sreenivasa Reddy" <sreenivasa-reddy.berahalli@...com>
To:	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: FW: ACPI Warning: Invalid length for Pm1aControlBlock: 32, using
 default 16 (20090903/tbfadt-607)

Resending because delivery failure in first attempt.

Sreenivas

_____________________________________________
From: Berahalli, Sreenivasa Reddy
Sent: Friday, January 14, 2011 11:28 AM
To: 'lenb@...nel.org'; 'ming.m.lin@...el.com'; 'robert.moore@...el.com'; 'linux-acpi@...r.kernel.org'; 'linux-kernel@...r.kernel.org'
Cc: K, Narmadha
Subject: ACPI Warning: Invalid length for Pm1aControlBlock: 32, using default 16 (20090903/tbfadt-607)


Hi,

>From kernel version 2.6.31.13, the "acpi_tb_setup_fadt_registers" function is added to check for any incorrect length.
In ACPI tables, this function checks if the length of register and the default value are the same, and will replace if the values are different.
 acpi_tb_setup_fadt_registers() function in /drivers/acpi/acpica/tbfadt.c verifies the length of Pm1aControlBlock.

"ACPI Warning: Invalid length for Pm1aControlBlock: 32, using default 16 (20090903/tbfadt-607)"

This warning message means the length of register in the ACPI tables and the default values are different.
We see it as  over-aggressive check in Linux, with no issue.

Warning messages in dmesg are alarm to the end users.
This issue can be addressed by moving these messages to debug level instead of throwing it by default to dmesg.

Thanks
Sreenivas


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/