From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org Subject: [Bug 108058] New: After resuming from suspend, discrete GPU is powered on and can't be turned off Date: Tue, 25 Sep 2018 12:15:55 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0216190893==" Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: nouveau-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Sender: "Nouveau" To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org List-Id: nouveau.vger.kernel.org --===============0216190893== Content-Type: multipart/alternative; boundary="15378777551.a1dF63D3.10122" Content-Transfer-Encoding: 7bit --15378777551.a1dF63D3.10122 Date: Tue, 25 Sep 2018 12:15:55 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D108058 Bug ID: 108058 Summary: After resuming from suspend, discrete GPU is powered on and can't be turned off Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Reporter: domenico.iezzi.201-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org Created attachment 141734 --> https://bugs.freedesktop.org/attachment.cgi?id=3D141734&action=3Dedit kernel log Overall, nouveau works without problem in managing discrete GPU PM, and if I check power consumption using powertop on a fresh boot it reports an average battery discharge rate of ~7W like always. After I resume the laptop from suspend, /sys/kernel/debug/vgaswitcheroo/swi= tch reports that the device is dynamically turned off: 0:IGD:+:Pwr:0000:00:02.0 1:DIS: :DynOff:0000:01:00.0 But if I check with powertop, I get a battery discharge rate of ~11W. To be= tter identify the problem, I tried using bumbleebee+bbswitch+nvidia-driver and s= ee what bbswitch module reports. On a fresh boot, it works ok as the nouveau driver, but after resuming from suspend /proc/acpi/bbswitch reports that the card is turned ON, and there is no way= to power it off: [root@example user]# cat /proc/acpi/bbswitch=20 0000:04:00.0 ON [root@example user]# tee /proc/acpi/bbswitch <<
Bug ID 108058
Summary After resuming from suspend, discrete GPU is powered on and c= an't be turned off
Product xorg
Version unspecified
Hardware x86-64 (AMD64)
OS Linux (All)
Status NEW
Severity normal
Priority medium
Component Driver/nouveau
Assignee nouveau@lists.freedesktop.org
Reporter domenico.iezzi.201@gmail.com
QA Contact xorg-team@lists.x.org

Created attachment 141734 [det=
ails]
kernel log

Overall, nouveau works without problem in managing discrete GPU PM, and if I
check power consumption using powertop on a fresh boot it reports an average
battery discharge rate of ~7W like always.
After I resume the laptop from suspend, /sys/kernel/debug/vgaswitcheroo/swi=
tch
reports that the device is
dynamically turned off:

0:IGD:+:Pwr:0000:00:02.0
1:DIS: :DynOff:0000:01:00.0

But if I check with powertop, I get a battery discharge rate of ~11W. To be=
tter
identify the problem, I tried using bumbleebee+bbswitch+nvidia-driver and s=
ee
what bbswitch module reports. On a fresh boot, it works
ok as the nouveau driver, but after resuming from suspend
/proc/acpi/bbswitch reports that the card is turned ON, and there is no way=
 to
power it off:

[root@example user]# cat /proc/acpi/bbswitch=20
0000:04:00.0 ON
[root@example user]# tee /proc/acpi/bbswitch <<<OFF
OFF
[root@example user]# cat /proc/acpi/bbswitch=20
0000:04:00.0 ON

I attached the kernel log using following parameters when using only nouveau
driver (no bumblebee/bbswitch/nvidia): log_buf_len=3D1M nouveau.debug=3Ddeb=
ug.

System specs:
Asus Vivobook S551LN
Intel i7 4500U
NVIDIA 840M
Archlinux 4.18.9-arch1-1-ARCH (but affecting older versions, since early 4.x
version when i started using linux)


You are receiving this mail because:
  • You are the assignee for the bug.
= --15378777551.a1dF63D3.10122-- --===============0216190893== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTm91dmVhdSBt YWlsaW5nIGxpc3QKTm91dmVhdUBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cHM6Ly9saXN0cy5m cmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9ub3V2ZWF1Cg== --===============0216190893==--