Bug 3588 - [Atom-PC]dmesg errors on atom-pc
Summary: [Atom-PC]dmesg errors on atom-pc
Status: RESOLVED INVALID
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-intel (show other bugs)
Version: 1.4
Hardware: Netbook Multiple
: Undecided normal
Target Milestone: ---
Assignee: Darren Hart
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2012-12-13 14:00 UTC by Alexandru Palalau
Modified: 2012-12-14 12:31 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandru Palalau 2012-12-13 14:00:56 UTC 
dmesg | grep -i error provides the following output.
Commit ID: 
ACPI Error: [CAPB] Namespace lookup failure, AE_ALREADY_EXISTS (20110623/dsfield-143)
ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node f64230d8), AE_ALREADY_EXISTS (20110623/psparse-536)
ACPI: Marking method _OSC as Serialized because of AE_ALREADY_EXISTS error
ACPI Error: [CAPB] Namespace lookup failure, AE_ALREADY_EXISTS (20110623/dsfield-143)
ACPI Error: Method parse/execution failed [\_SB_.PCI0._OSC] (Node f64230d8), AE_ALREADY_EXISTS (20110623/psparse-536)

Poky commit ID: 381c4b69c7e8b452f4d3de2f8214e6e5f6a9abe7
Images from http://autobuilder.yoctoproject.org/pub/nightly/20121205-3/
Comment 1 Alexandru Georgescu 2012-12-13 15:58:11 UTC 
This was tested on Lenovo Ideapad S10-3.
It also happens with the ATOM-PC build for denzil-next:

http://autobuilder.pokylinux.org/nightly/20121206-2/machines/atom-pc/core-image-sato-sdk-atom-pc.hddimg


The errors appear on the dmesg ouput after the image boots.
Comment 2 Alexandru Palalau 2012-12-13 21:23:49 UTC 
1.4_M1 branch
Image written on usb-stick with dd.
Comment 3 Ross Burton 2012-12-14 12:31:55 UTC 
So that's the ACPI bug https://www.acpica.org/bugzilla/show_bug.cgi?id=946, closed resolved invalid.

Linux's behaviour is identical to Windows (which is the "real" spec) and conformant to the actual spec (which says that the instructions provided by the BIOS is invalid).