Dear coreboot folks,
in Debian Sid/unstable with Linux 3.2.35 looking at the Linux messages
in the output of `dmesg` I see
ACPI: Invalid PBLK length [0]
which results from
$ more src/mainboard/asrock/e350m1/dsdt.asl
[…]
/*
* Processor Object
*
*/
Scope (\_PR) { /* define processor scope */
Processor(
C000, /* name space name, align with
BLDCFG_PROCESSOR_SCOPE_NAME[01] */
0, /* Unique number for this
processor */
0x810, /* PBLK system I/O address
!hardcoded! */
0x06 /* PBLKLEN for boot processor */
) {
}
Processor(
C001, /* name space name */
1, /* Unique number for this
processor */
0x810, /* PBLK system I/O address
!hardcoded! */
0x00 /* PBLKLEN for boot processor */
) {
}
Processor(
C002, /* name space name */
2, /* Unique number for this
processor */
0x810, /* PBLK system I/O address
!hardcoded! */
0x00 /* PBLKLEN for boot processor */
) {
}
Processor(
C003, /* name space name */
3, /* Unique number for this
processor */
0x810, /* PBLK system I/O address
!hardcoded! */
0x00 /* PBLKLEN for boot processor */
) {
}
} /* End _PR scope */
[…]
Is that an error in the Linux ACPI code? According to Colin King’s
comment (25) to the Launchpad report [1], the ACPI specification allows
it to be set to 0.
»Section 18.5.93 of the ACPI specification states that the
PBlockLength is the length of the processor register block, in
bytes and is either 0 (for no P_BLK) or 6.« [2]
So the DSDT seems to be valid. Before I report that to the Linux ACPI
folks, could you please tell me if I am missing something?
Thanks,
Paul
[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/197267
[2] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/197267/comments/25
signature.asc
Description: This is a digitally signed message part
-- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
