Summary: | nouveau no longer reports D3cold on linux-next as of at least 20130906 | ||
---|---|---|---|
Product: | Mesa | Reporter: | Tod Jackson <tod.jackson> |
Component: | Drivers/DRI/nouveau | Assignee: | Nouveau Project <nouveau> |
Status: | RESOLVED NOTABUG | QA Contact: | |
Severity: | minor | ||
Priority: | medium | CC: | peter |
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | current dmesg |
Description
Tod Jackson
2013-09-14 06:38:57 UTC
Created attachment 85810 [details]
current dmesg
That DSM argument mismatch warning is caused by the modules (nouveau and bbswitch) and is a workaround for buggy DSDTs. It is possible to make the warning go away, but that will confuse machines with buggy DSDTs. I haven't looked in the code yet, but what is the issue with D3cold not being mentioned in dmesg? It's quite possibly a non-issue. But it's new behavior, so I just wanted to check it was intentional. I believe this is part of the runtime pm support that was added for Optimus setups in 3.12-rc1, which puts the nvidia card into d3cold when it's not being used. You can disable it by adding nouveau.runpm=1. If there are any actual issues with it, feel free to open issues about it. I think that ACPI warning is about buggy AML, perhaps a BIOS update will fix it, or more likely, you'll have to live with it. |
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.