Bug 79781 - ACPI throws warning when executing _DSM
Summary: ACPI throws warning when executing _DSM
Status: RESOLVED WONTFIX
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-07 21:57 UTC by Christian Wehrmeyer
Modified: 2016-07-16 10:32 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
ACPI tables and kern.log (159.88 KB, text/plain)
2014-06-07 21:57 UTC, Christian Wehrmeyer
no flags Details

Description Christian Wehrmeyer 2014-06-07 21:57:38 UTC
Created attachment 100622 [details]
ACPI tables and kern.log

Dunno if I am right here ... Ilja Mirkin from the nouveau mailing list sent me here. Also English is not my native language, so please cut me some slack.

In order to trace a machine hangup I contacted the nouveau guys. Mirkin told me to file a bug here because when the kernel executes _DSM, it throws off two warnings:

Jun  6 21:56:21 asgard kernel: [    1.966614] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140214/nsarguments-95)
Jun  6 21:56:21 asgard kernel: [    1.966657] ACPI Warning: \_SB_.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140214/nsarguments-95)

I am using the 3.15-rc8 kernel and can reproduce the warning with each boot.
Attached is my complete kern.log and my extracted ACPI tables.

I will provide you with additional informations if you need them, just let me know.
Comment 1 Peter Wu 2016-07-16 10:26:35 UTC
The warning can be safely ignored.

Some ACPI firmware expect the non-standard Buffer type and fail if you pass a Package type. Hence nouveau always passes a Buffer which is against the ACPI standard, which triggers this unavoidable warning.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.