Bug 34192 - Invalid UUID reported in ACPI command
Summary: Invalid UUID reported in ACPI command
Alias: None
Product: ACPI
Classification: Unclassified
Component: ACPICA-Core (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: acpi_acpica-core@kernel-bugs.osdl.org
Depends on:
Reported: 2011-05-01 21:25 UTC by Abhishek Udupa
Modified: 2012-05-24 07:58 UTC (History)
2 users (show)

See Also:
Kernel Version:
Tree: Mainline
Regression: No

dmesg output (75.57 KB, text/x-log)
2011-05-01 21:25 UTC, Abhishek Udupa
lscpi -vvv output (35.12 KB, text/x-log)
2011-05-01 21:27 UTC, Abhishek Udupa
dmidecode output (12.64 KB, text/x-log)
2011-05-01 21:28 UTC, Abhishek Udupa

Description Abhishek Udupa 2011-05-01 21:25:38 UTC
Created attachment 56102 [details]
dmesg output

I'm running Ubuntu 11.04 with a stock kernel on a Dell XPS L502X. I see three instances of the following message during bootup:

\_SB_.PCI0:_OSC invalid UUID

which is always followed by something like:

_OSC request data:1 8 1f,

with different numbers each time. The system works fine. The only problem I have is that whenever I change the power state (disconnecting the AC adapter or reconnecting it) when the system is running, the hard disk starts clicking every few minutes and the load cycle count goes up by one each time this happens. The problem goes away if I somehow reset the HDD (e.g. by suspending and resuming) I'm not sure if this is related to the invalid UUID error in the dmesg, but thought I'd mention it if they are indeed related.

I've attached various logs which I think might be useful. I'd be happy to include any other information that might be necessary to help resolve this.
Comment 1 Abhishek Udupa 2011-05-01 21:27:16 UTC
Created attachment 56112 [details]
lscpi -vvv output
Comment 2 Abhishek Udupa 2011-05-01 21:28:00 UTC
Created attachment 56122 [details]
dmidecode output
Comment 3 Zhang Rui 2012-01-18 05:09:08 UTC
please attach the output of acpidump of your laptop.
Comment 4 Zhang Rui 2012-05-24 07:58:01 UTC
bug closed as there is no response from the bug reporter.
please feel free to reopen it if the problem still exists in the latest upstream kernel.

Note You need to log in before you can comment on or make changes to this bug.