bugzilla-daemon at freedesktop.org
2013-Sep-14 06:38 UTC
[Nouveau] [Bug 69345] New: nouveau no longer reports D3cold on linux-next as of at least 20130906
https://bugs.freedesktop.org/show_bug.cgi?id=69345 Priority: medium Bug ID: 69345 Assignee: nouveau at lists.freedesktop.org Summary: nouveau no longer reports D3cold on linux-next as of at least 20130906 Severity: minor Classification: Unclassified OS: Linux (All) Reporter: tod.jackson at gmail.com Hardware: x86-64 (AMD64) Status: NEW Version: git Component: Drivers/DRI/nouveau Product: Mesa Hi there, I saw Rafael made this recent commit: http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8ad928d52e63a9b7d69f0873d7318c4561e2f8cd That may not be the culprit at all, sorry. I noticed that if I'm using, say, the latest drm-intel-next kernel or nouveau kernel ACPI reports nouveau's status properly, e.g. nouveau: power state changed by ACPI to D3cold, however in next I no longer get these messages, although the device seems to be in D3cold (?). At least temperatures are much lower, especially when building software. [23301.994315] ACPI Warning: \_SB_.PCI0.P0P2.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20130725/nsarguments-95) (That's the only indicator of power transitions now - a warning that might go away in the future - p.s., do I need to do some DSDT hacking for that or is it on the Linux-side?) Invoking lm_sensors' sensors command shows N/A for the nouveau device on Optimus laptops, as expected if the device is in D3cold. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20130914/33a2c296/attachment.html>
bugzilla-daemon at freedesktop.org
2013-Sep-14 06:56 UTC
[Nouveau] [Bug 69345] nouveau no longer reports D3cold on linux-next as of at least 20130906
https://bugs.freedesktop.org/show_bug.cgi?id=69345 --- Comment #1 from tod.jackson at gmail.com --- Created attachment 85810 --> https://bugs.freedesktop.org/attachment.cgi?id=85810&action=edit current dmesg -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20130914/4467dc6b/attachment.html>
bugzilla-daemon at freedesktop.org
2013-Sep-16 10:41 UTC
[Nouveau] [Bug 69345] nouveau no longer reports D3cold on linux-next as of at least 20130906
https://bugs.freedesktop.org/show_bug.cgi?id=69345 Peter Wu <lekensteyn at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lekensteyn at gmail.com --- Comment #2 from Peter Wu <lekensteyn at gmail.com> --- 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? -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20130916/31ed57d0/attachment.html>
bugzilla-daemon at freedesktop.org
2013-Sep-16 15:54 UTC
[Nouveau] [Bug 69345] nouveau no longer reports D3cold on linux-next as of at least 20130906
https://bugs.freedesktop.org/show_bug.cgi?id=69345 --- Comment #3 from tod.jackson at gmail.com --- It's quite possibly a non-issue. But it's new behavior, so I just wanted to check it was intentional. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20130916/97337eef/attachment.html>
bugzilla-daemon at freedesktop.org
2013-Oct-11 00:57 UTC
[Nouveau] [Bug 69345] nouveau no longer reports D3cold on linux-next as of at least 20130906
https://bugs.freedesktop.org/show_bug.cgi?id=69345 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |NOTABUG --- Comment #4 from Ilia Mirkin <imirkin at alum.mit.edu> --- 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. -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20131011/a1e13dfd/attachment.html>
Seemingly Similar Threads
- [PATCH] drm/nouveau: suspend to D3hot, not to D3cold
- [PATCH] drm/nouveau/acpi: use DSM if bridge does not support D3cold
- [Bug 69375] New: [NV4E] GPU lockup when using chrome/flash
- [LLVMdev] PR17975 and trunk
- [PATCH v3] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges