[Bug 1803179]
since this bug is fixed in nouveau and the last responses here are all related to the nvidia driver can we close this bug? If people are having issues with the nvidia driver they should contact Nvidia about it. Anyway, removing myself from CC due to the noise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to Ranjith Hegde from comment #172) > New problems in an old thread > > After using @Matthias Fulz's method (bumblebee without bbswitch + pm with > powertop+tlp) its quite simple to run any software requiring nvidia. with > his patch. > > The problem is in preventing any other software from using nvidia when not > run with optirun/primusrun. For example, any software that calls for EGL > automatically turns on nvidia. Mpv is one of those. > > Is there any way to ensure EGL calls intel instead? There is solution in > arch wiki with env-variable > "__EGL_VENDOR_LIBRARY_FILENAMES="/usr/share/glvnd/egl_vendor.d/50_mesa.json" > " > > but it does not work. I have tried adding it in all possible places > (/etc/environment, /etc/profile, bash-profile, zsh-profile-equivalent etc..) Hey, I was also struggling with those problems. What I do is that instead of removing the nvidia-audio from the PCIe Bus, I remove the nvidia card: % cat /usr/local/bin/remove_nvidia #!/usr/bin/bash echo 1 > /sys/bus/pci/devices/:01:00.1/remove echo 1 > /sys/bus/pci/devices/:01:00.0/remove I do this at boot via systemd. There is a post earlier that describes how to do it. You should also make sure that the nvidia modules are not loaded (should be taken care if you use bumblebee). In order to re-enable the nvidia card when you need it, use: % cat /usr/local/bin/add_nvidia #!/usr/bin/env bash echo 1 > /sys/bus/pci/rescan You can modify your bumbleebee/optimus/primus scripts accordingly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to xxxaaa from comment #173) > (In reply to Karol Herbst from comment #169) > > (In reply to xxxaaa from comment #168) > > > (In reply to Karol Herbst from comment #167) > > > > btw, this bug should be fixed with the nouveau river in 5.7 (and > > backports > > > > should follow soon for 5.4, 5.5 and 5.6) > > > > > > I have similar issue https://bugzilla.kernel.org/show_bug.cgi?id=206727 > but > > > I use NVIDIA PRIME driver. Will your bugfix work for that too or does it > > > work only for nouveau drivers? > > > > the fix is for Nouveau only, but I am actually in contact with Nvidia about > > the same issue they have inside their driver as well. > > > > But the bug can be fixed from within the open source files inside the > nvidia > > driver as well I just hope that Nvidia will have a proper solution here as > > the fix in Nouveau is also more of a workaround than a real fix. > > (Sorry for being impatient but this bug has been bugging me a lot.) > Do you know if this has been fixed on Nvidia Drivers yet or not? And if it > has not been fixed then whether it is on their roadmap or not? Afaik they do not and my attempts to get them to even reproduce the issue failed... so I don't see it getting fixed any time soon and honestly, if I have to put more time into it I might even stop caring as the fix we have for Nouveau is good enough and appears to have resolved the issue for good. In case you are still plagued by it I suspect you might want to bring that up to Nvidia directly and see if they get more motivated fixing it if they get more reports. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to Karol Herbst from comment #169) > (In reply to xxxaaa from comment #168) > > (In reply to Karol Herbst from comment #167) > > > btw, this bug should be fixed with the nouveau river in 5.7 (and > backports > > > should follow soon for 5.4, 5.5 and 5.6) > > > > I have similar issue https://bugzilla.kernel.org/show_bug.cgi?id=206727 but > > I use NVIDIA PRIME driver. Will your bugfix work for that too or does it > > work only for nouveau drivers? > > the fix is for Nouveau only, but I am actually in contact with Nvidia about > the same issue they have inside their driver as well. > > But the bug can be fixed from within the open source files inside the nvidia > driver as well I just hope that Nvidia will have a proper solution here as > the fix in Nouveau is also more of a workaround than a real fix. (Sorry for being impatient but this bug has been bugging me a lot.) Do you know if this has been fixed on Nvidia Drivers yet or not? And if it has not been fixed then whether it is on their roadmap or not? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to Karol Herbst from comment #174) > (In reply to xxxaaa from comment #173) > > (In reply to Karol Herbst from comment #169) > > > (In reply to xxxaaa from comment #168) > > > > (In reply to Karol Herbst from comment #167) > > > > > btw, this bug should be fixed with the nouveau river in 5.7 (and > > > backports > > > > > should follow soon for 5.4, 5.5 and 5.6) > > > > > > > > I have similar issue https://bugzilla.kernel.org/show_bug.cgi?id=206727 > > but > > > > I use NVIDIA PRIME driver. Will your bugfix work for that too or does > it > > > > work only for nouveau drivers? > > > > > > the fix is for Nouveau only, but I am actually in contact with Nvidia > about > > > the same issue they have inside their driver as well. > > > > > > But the bug can be fixed from within the open source files inside the > > nvidia > > > driver as well I just hope that Nvidia will have a proper solution here > as > > > the fix in Nouveau is also more of a workaround than a real fix. > > > > (Sorry for being impatient but this bug has been bugging me a lot.) > > Do you know if this has been fixed on Nvidia Drivers yet or not? And if it > > has not been fixed then whether it is on their roadmap or not? > > Afaik they do not and my attempts to get them to even reproduce the issue > failed... > > so I don't see it getting fixed any time soon and honestly, if I have to put > more time into it I might even stop caring as the fix we have for Nouveau is > good enough and appears to have resolved the issue for good. > > In case you are still plagued by it I suspect you might want to bring that > up to Nvidia directly and see if they get more motivated fixing it if they > get more reports. I had asked about it in the nvidia linux forums some time back but nothing came out of it either :( https://forums.developer.nvidia.com/t/bug-cant-change-power-state-from-d3cold-to-d0-config-space-inaccessible-stuck-at-boot/112912 Some time back you had said - > But the bug can be fixed from within the open source files inside the nvidia > driver So, can your nouveau patch be applied to nvidia driver as well? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
New problems in an old thread After using @Matthias Fulz's method (bumblebee without bbswitch + pm with powertop+tlp) its quite simple to run any software requiring nvidia. with his patch. The problem is in preventing any other software from using nvidia when not run with optirun/primusrun. For example, any software that calls for EGL automatically turns on nvidia. Mpv is one of those. Is there any way to ensure EGL calls intel instead? There is solution in arch wiki with env-variable "__EGL_VENDOR_LIBRARY_FILENAMES="/usr/share/glvnd/egl_vendor.d/50_mesa.json" " but it does not work. I have tried adding it in all possible places (/etc/environment, /etc/profile, bash-profile, zsh-profile-equivalent etc..) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
** Bug watch added: Linux Kernel Bug Tracker #206727 https://bugzilla.kernel.org/show_bug.cgi?id=206727 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to xxxaaa from comment #168) > (In reply to Karol Herbst from comment #167) > > btw, this bug should be fixed with the nouveau river in 5.7 (and backports > > should follow soon for 5.4, 5.5 and 5.6) > > I have similar issue https://bugzilla.kernel.org/show_bug.cgi?id=206727 but > I use NVIDIA PRIME driver. Will your bugfix work for that too or does it > work only for nouveau drivers? the fix is for Nouveau only, but I am actually in contact with Nvidia about the same issue they have inside their driver as well. But the bug can be fixed from within the open source files inside the nvidia driver as well I just hope that Nvidia will have a proper solution here as the fix in Nouveau is also more of a workaround than a real fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to Kai-Heng Feng from comment #170) > Karol Herbst, > > Is it fixed by removing the OSI vendor strings? should be, yes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to Karol Herbst from comment #167) > btw, this bug should be fixed with the nouveau river in 5.7 (and backports > should follow soon for 5.4, 5.5 and 5.6) I have similar issue https://bugzilla.kernel.org/show_bug.cgi?id=206727 but I use NVIDIA PRIME driver. Will your bugfix work for that too or does it work only for nouveau drivers? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
Karol Herbst, Is it fixed by removing the OSI vendor strings? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
btw, this bug should be fixed with the nouveau river in 5.7 (and backports should follow soon for 5.4, 5.5 and 5.6) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to Matthias Fulz from comment #165)
> (In reply to Ranjith Hegde from comment #164)
> > (In reply to Matthias Fulz from comment #161)
> >
> > Hello,
> > Thank you for your patch and effort. I tried your primusrun patch. First I
> > get an infinite repetitions of this
> > /bin/bash: warning: shell level (1000) too high, resetting to 1
> >
> Ok this is NOT a patch :)
> It's just a simple script to run optirun / primusrun encapsulated to load
> and unload the nvidia module.
>
> > and when I stop (C-c) I get an infinite loop of this
> >
> > rmmod: ERROR: Module nvidia is not currently loaded
> > finished.
> > unloading nvidia modules ...
> > rmmod: ERROR: Module nvidia is not currently loaded
> > finished.
> >
> > nothing launches..
> > Any ideas?
> >
> Yes: I'm quite sure you've got /usr/local/bin in your PATH and this before
> the /usr/bin entry, where optirun / primusrun should be placed in.
>
> Two possible solutions:
>
> 1.) Change the lines primusrun $@ and optirun $@ to use the full path a.e.
> /usr/bin/primusrun $@ instead of primusrun $@
>
> 2.) Rename the scripts to something like /usr/local/bin/primusrun.sh and
> /usr/local/bin/optirun.sh
>
> Second solution will avoid any naming clushes for sure.
>
> Hope that helps
>
> BR,
> Matthias
Thank you for your reply!
Firstly about the naming hickup. I am from computer music background and
any piece of code is referred to as a patch. I know its quite different
in shell scripting or general programming world. my bad
I tried your second solution of using .sh and running it after I close
all programs running on Nvidia. it works. Thanks
If I were to place your script (!) directly inside usr/bin/primusrun
then where would you suggest I put it. here's how it looks, unedited
#!/bin/bash
# Readback-display synchronization method
# 0: no sync, 1: D lags behind one frame, 2: fully synced
# export PRIMUS_SYNC=${PRIMUS_SYNC:-0}
# Verbosity level
# 0: only errors, 1: warnings (default), 2: profiling
# export PRIMUS_VERBOSE=${PRIMUS_VERBOSE:-1}
# Upload/display method
# 0: autodetect, 1: textures, 2: PBO/glDrawPixels (needs Mesa-10.1+)
# export PRIMUS_UPLOAD=${PRIMUS_UPLOAD:-0}
# Approximate sleep ratio in the readback thread, percent
# export PRIMUS_SLEEP=${PRIMUS_SLEEP:-90}
# Secondary display
# export PRIMUS_DISPLAY=${PRIMUS_DISPLAY:-:8}
# "Accelerating" libGL
# $LIB will be interpreted by the dynamic linker
# export PRIMUS_libGLa=${PRIMUS_libGLa:-'/usr/$LIB/nvidia/libGL.so.1'}
# "Displaying" libGL
# export PRIMUS_libGLd=${PRIMUS_libGLd:-'/usr/$LIB/libGL.so.1'}
# Directory containing primus libGL
PRIMUS_libGL=/usr/\$LIB/primus
# On some distributions, e.g. on Ubuntu, libnvidia-tls.so is not available
# in default search paths. Add its path manually after the primus library
# PRIMUS_libGL=${PRIMUS_libGL}:/usr/lib/nvidia-current:/usr/lib32/nvidia-current
# Mesa drivers need a few symbols to be visible
# export PRIMUS_LOAD_GLOBAL=${PRIMUS_LOAD_GLOBAL:-'libglapi.so.0'}
# Need functions from primus libGL to take precedence
export LD_LIBRARY_PATH=${PRIMUS_libGL}${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}
# And go!
export __GLVND_DISALLOW_PATCHING=1
exec "$@"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803179
Title:
System does not reliably come out of suspend
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to Ranjith Hegde from comment #164) > (In reply to Matthias Fulz from comment #161) > > Hello, > Thank you for your patch and effort. I tried your primusrun patch. First I > get an infinite repetitions of this > /bin/bash: warning: shell level (1000) too high, resetting to 1 > Ok this is NOT a patch :) It's just a simple script to run optirun / primusrun encapsulated to load and unload the nvidia module. > and when I stop (C-c) I get an infinite loop of this > > rmmod: ERROR: Module nvidia is not currently loaded > finished. > unloading nvidia modules ... > rmmod: ERROR: Module nvidia is not currently loaded > finished. > > nothing launches.. > Any ideas? > Yes: I'm quite sure you've got /usr/local/bin in your PATH and this before the /usr/bin entry, where optirun / primusrun should be placed in. Two possible solutions: 1.) Change the lines primusrun $@ and optirun $@ to use the full path a.e. /usr/bin/primusrun $@ instead of primusrun $@ 2.) Rename the scripts to something like /usr/local/bin/primusrun.sh and /usr/local/bin/optirun.sh Second solution will avoid any naming clushes for sure. Hope that helps BR, Matthias -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to Matthias Fulz from comment #161)
> I'm just using bumblebee and do not blacklist nvidia modules.
>
> This is my /etc/bumblebee/xorg.conf.nvidia
>
> Section "ServerLayout"
> Identifier "Layout0"
> Option "AutoAddDevices" "true"
> Option "AutoAddGPU" "false"
> EndSection
>
> Section "Device"
> Identifier "DiscreteNvidia"
> Driver "nvidia"
> VendorName "NVIDIA Corporation"
>
>
> Option "NoLogo" "true"
> Option "UseEDID" "false"
> Option "AllowEmptyInitialConfiguration"
> EndSection
>
> Section "Screen"
> Identifier "Screen0"
> Device "DiscreteNvidia"
> EndSection
>
> And I'm just using an additional systemd service for powertop
> /etc/systemd/system/powertop.service:
>
> [Unit]
> Description=PowerTOP auto tune
>
> [Service]
> Type=idle
> Environment="TERM=dumb"
> ExecStart=/usr/bin/bash -c "sleep 30 && /usr/bin/powertop --auto-tune &&
> sleep 10 && echo 'on' > '/sys/bus/usb/devices/1-1/power/control'"
>
> [Install]
> WantedBy=multi-user.target
>
> Then I've everything ready and can use:
> primusrun
> optirum
>
> for nvidia GPU stuff. For the unloading of the modules after the use I'm
> using the following scripts:
>
> /usr/local/bin/primusrun
>
> #!/bin/bash
>
> trap unload 1 2 3 6
>
> unload() {
> /usr/bin/lsmod | grep nvidia > /dev/null 2>&1
> if [ $? -eq 0 ]
> then
> echo "unloading nvidia modules ..."
> sleep 2
> /usr/bin/lsmod | grep nvidia_modeset > /dev/null 2>&1
> if [ $? -eq 0 ]
> then
> sudo /usr/bin/rmmod nvidia_modeset
> fi
> sudo /usr/bin/rmmod nvidia
> echo "finished."
> fi
> }
>
> primusrun $@
> unload
>
> /usr/local/bin/optirun
>
> #!/bin/bash
>
> trap unload 1 2 3 6
>
> unload() {
> /usr/bin/lsmod | grep nvidia > /dev/null 2>&1
> if [ $? -eq 0 ]
> then
> echo "unloading nvidia modules ..."
> sleep 2
> /usr/bin/lsmod | grep nvidia_modeset > /dev/null 2>&1
> if [ $? -eq 0 ]
> then
> sudo /usr/bin/rmmod nvidia_modeset
> fi
> sudo /usr/bin/rmmod nvidia
> echo "finished."
> fi
> }
>
> optirun $@
> unload
>
> That's it for me.
>
> In addition for powersavings I'm using TLP with quite default settings.
>
> Offloading inside the nvidia drivers is just not really helpful afaik :)
>
> Hope that helps.
Hello,
Thank you for your patch and effort. I tried your primusrun patch. First I get
an infinite repetitions of this
/bin/bash: warning: shell level (1000) too high, resetting to 1
and when I stop (C-c) I get an infinite loop of this
rmmod: ERROR: Module nvidia is not currently loaded
finished.
unloading nvidia modules ...
rmmod: ERROR: Module nvidia is not currently loaded
finished.
nothing launches..
Any ideas?
I am on Arch, optimus laptop with intel coffeelake and RTX 2070
I have bumblebeed enabled with your recommended xorg.nvidia settings, using
powertop pm to turn off Nvidia card which works fine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803179
Title:
System does not reliably come out of suspend
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to Matthias Fulz from comment #161)
> I'm just using bumblebee and do not blacklist nvidia modules.
>
> This is my /etc/bumblebee/xorg.conf.nvidia
>
> Section "ServerLayout"
> Identifier "Layout0"
> Option "AutoAddDevices" "true"
> Option "AutoAddGPU" "false"
> EndSection
>
> Section "Device"
> Identifier "DiscreteNvidia"
> Driver "nvidia"
> VendorName "NVIDIA Corporation"
>
>
> Option "NoLogo" "true"
> Option "UseEDID" "false"
> Option "AllowEmptyInitialConfiguration"
> EndSection
>
> Section "Screen"
> Identifier "Screen0"
> Device "DiscreteNvidia"
> EndSection
>
> And I'm just using an additional systemd service for powertop
> /etc/systemd/system/powertop.service:
>
> [Unit]
> Description=PowerTOP auto tune
>
> [Service]
> Type=idle
> Environment="TERM=dumb"
> ExecStart=/usr/bin/bash -c "sleep 30 && /usr/bin/powertop --auto-tune &&
> sleep 10 && echo 'on' > '/sys/bus/usb/devices/1-1/power/control'"
>
> [Install]
> WantedBy=multi-user.target
>
> Then I've everything ready and can use:
> primusrun
> optirum
>
> for nvidia GPU stuff. For the unloading of the modules after the use I'm
> using the following scripts:
>
> /usr/local/bin/primusrun
>
> #!/bin/bash
>
> trap unload 1 2 3 6
>
> unload() {
> /usr/bin/lsmod | grep nvidia > /dev/null 2>&1
> if [ $? -eq 0 ]
> then
> echo "unloading nvidia modules ..."
> sleep 2
> /usr/bin/lsmod | grep nvidia_modeset > /dev/null 2>&1
> if [ $? -eq 0 ]
> then
> sudo /usr/bin/rmmod nvidia_modeset
> fi
> sudo /usr/bin/rmmod nvidia
> echo "finished."
> fi
> }
>
> primusrun $@
> unload
>
> /usr/local/bin/optirun
>
> #!/bin/bash
>
> trap unload 1 2 3 6
>
> unload() {
> /usr/bin/lsmod | grep nvidia > /dev/null 2>&1
> if [ $? -eq 0 ]
> then
> echo "unloading nvidia modules ..."
> sleep 2
> /usr/bin/lsmod | grep nvidia_modeset > /dev/null 2>&1
> if [ $? -eq 0 ]
> then
> sudo /usr/bin/rmmod nvidia_modeset
> fi
> sudo /usr/bin/rmmod nvidia
> echo "finished."
> fi
> }
>
> optirun $@
> unload
>
> That's it for me.
>
> In addition for powersavings I'm using TLP with quite default settings.
>
> Offloading inside the nvidia drivers is just not really helpful afaik :)
>
> Hope that helps.
Cheers! I'll see what I can do there :) Thank you so much for all the
help
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803179
Title:
System does not reliably come out of suspend
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
Additional information: The on is for my logitech receiver as it is annoying like hell when powersavings are enabled for it. Will need to move the mouse for 2s before it*s working again. And the sleep is needed to be able to have all the hardware available before powertop will change the modes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
I'm just using bumblebee and do not blacklist nvidia modules.
This is my /etc/bumblebee/xorg.conf.nvidia
Section "ServerLayout"
Identifier "Layout0"
Option "AutoAddDevices" "true"
Option "AutoAddGPU" "false"
EndSection
Section "Device"
Identifier "DiscreteNvidia"
Driver "nvidia"
VendorName "NVIDIA Corporation"
Option "NoLogo" "true"
Option "UseEDID" "false"
Option "AllowEmptyInitialConfiguration"
EndSection
Section "Screen"
Identifier "Screen0"
Device "DiscreteNvidia"
EndSection
And I'm just using an additional systemd service for powertop
/etc/systemd/system/powertop.service:
[Unit]
Description=PowerTOP auto tune
[Service]
Type=idle
Environment="TERM=dumb"
ExecStart=/usr/bin/bash -c "sleep 30 && /usr/bin/powertop --auto-tune && sleep
10 && echo 'on' > '/sys/bus/usb/devices/1-1/power/control'"
[Install]
WantedBy=multi-user.target
Then I've everything ready and can use:
primusrun
optirum
for nvidia GPU stuff. For the unloading of the modules after the use I'm
using the following scripts:
/usr/local/bin/primusrun
#!/bin/bash
trap unload 1 2 3 6
unload() {
/usr/bin/lsmod | grep nvidia > /dev/null 2>&1
if [ $? -eq 0 ]
then
echo "unloading nvidia modules ..."
sleep 2
/usr/bin/lsmod | grep nvidia_modeset > /dev/null 2>&1
if [ $? -eq 0 ]
then
sudo /usr/bin/rmmod nvidia_modeset
fi
sudo /usr/bin/rmmod nvidia
echo "finished."
fi
}
primusrun $@
unload
/usr/local/bin/optirun
#!/bin/bash
trap unload 1 2 3 6
unload() {
/usr/bin/lsmod | grep nvidia > /dev/null 2>&1
if [ $? -eq 0 ]
then
echo "unloading nvidia modules ..."
sleep 2
/usr/bin/lsmod | grep nvidia_modeset > /dev/null 2>&1
if [ $? -eq 0 ]
then
sudo /usr/bin/rmmod nvidia_modeset
fi
sudo /usr/bin/rmmod nvidia
echo "finished."
fi
}
optirun $@
unload
That's it for me.
In addition for powersavings I'm using TLP with quite default settings.
Offloading inside the nvidia drivers is just not really helpful afaik :)
Hope that helps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803179
Title:
System does not reliably come out of suspend
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to Matthias Fulz from comment #159) > Yep the problem is bbswitch. Just deinstall it, make sure the power mode for > nvidia gpu and hdmi sound are set to auto and unload the nvidia & > nvidia_modeset modules. > > bbswitch will still lead to the lockups, if used. Awesome! Blacklisting the modules, then setting runtime power management to auto for everything in powertop put the power usage down to about 8W. Loading the modules back up again manually puts the power usage back up, and unloading them back down, without having to use bbswitch at all. Do you know if it's possible to, with an X session that started up without the nvidia modules loaded, then turn those modules on and use that GPU with "__NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=NVIDIA_only __GLX_VENDOR_LIBRARY_NAME=nvidia "$@"" (the PRIME render offload in the recent drivers). I've so far not had any success :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
Yep the problem is bbswitch. Just deinstall it, make sure the power mode for nvidia gpu and hdmi sound are set to auto and unload the nvidia & nvidia_modeset modules. bbswitch will still lead to the lockups, if used. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to Matthias Fulz from comment #157) > Yep the actual arch kernel is working fine here, including these patches: > Linux omega 5.5.2-arch1-1 #1 SMP PREEMPT Tue, 04 Feb 2020 18:56:18 + > x86_64 GNU/Linux > > Best Powerconsumption so far 6-7W normal working (wlan, 25% display, > browsing, etc.) > > No lockups anymore, using bumblebee (primusrun, optirun) just need to > manually unload the nvidia modules afterwards, which I've included in simple > scripts. > > Thanks at all for this :) I'm currently using the vanilla kernel and still run into the lockups I mentioned above. Do I need to apply patches myself? Or is it just the stuff I'm using (eg I only use bbswitch, on top of optimus-manager)? Sorry if this is a little asking the obvious, just had this problem for a while now and not sure how to deal with it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
Yep the actual arch kernel is working fine here, including these patches: Linux omega 5.5.2-arch1-1 #1 SMP PREEMPT Tue, 04 Feb 2020 18:56:18 + x86_64 GNU/Linux Best Powerconsumption so far 6-7W normal working (wlan, 25% display, browsing, etc.) No lockups anymore, using bumblebee (primusrun, optirun) just need to manually unload the nvidia modules afterwards, which I've included in simple scripts. Thanks at all for this :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
Are these patches included in kernel 5.5.2? I blacklist nvidia modules on boot, and "echo 'OFF' | sudo tee /proc/acpi/bbswitch" (which succeeds) followed by lspci also produces a freeze on my machine. Without the call to bbswitch, the freeze does not happen, but my idle power usage is at 25-30W, instead of the ~11 that occurs if I do invoke bbswitch. I'm running Arch, with the 5.5.2 kernel. Hardware is an Intel i7-8750H and NVidia GTX 1070M, and my kernel parameters are "root=/dev/nvme0n1p5 rw add_efi_memmap initrd=intel-ucode.img initrd=initramfs-%v.img nopti intel_iommu=on iommu=on sysrq_always_enabled=1". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
ok I've found out that this difference seems to be gone when using tlp instead of laptop-mode-tools. Kernel 5.5-rc3 (including these patches) + Bumblebee and tlp provides me the full optimus usage + 8/9W power consumption on intel GPU. For me everything is working absolutely perfect now !!! :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
Ok after I removed the patches and the normal Kernel-Update to 5.3.11 happend, I'm experiencing the same higher power consumption that happend during the test before. It could be related to something else not the patches. But I'm unable to find out atm. where it comes from :( The pc is not going below 10W with 5.3.11 on 5.3.8 it drops to 7-8W. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
Of course I've set the power to auto for everything -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
I've tryed the patches and can confirm that the issues with lockups are gone with just using bumblebee (unloading nvidia module). But still the problems are the same: 1.) Just unloading the nvidia modules keeps the power consumption up to 13/14W which is 5-6W more (almoest double) in compare to intel only ~8W 2.) Using acpi call to poweroff the nvidia card completely which drops the power consumption to 8W the lockups are back. So for me the patches are not working :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
More infos: powertop shows this when using intel gpu only (my workarounds from post https://bugzilla.kernel.org/show_bug.cgi?id=156341#c139) 0.0%PCI Device: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) 0.0%PCI Device: Intel Corporation Cannon Lake PCH HECI Controller 0.0%PCI Device: NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] 0.0%PCI Device: Intel Corporation Cannon Lake PCH SPI Controller 0.0%PCI Device: Intel Corporation Cannon Lake PCH cAVS 0.0%PCI Device: NVIDIA Corporation GP107GL High Definition Audio Controller 0.0%PCI Device: Intel Corporation Cannon Lake PCH Shared SRAM 0.0%PCI Device: Intel Corporation Cannon Lake PCH SMBus Controller 0.0%PCI Device: Intel Corporation Cannon Lake PCH PCI Express Root Port #14 when using the patches with nvidia modules unloaded and power set to auto its still saying 100% -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
on Which kernel (of the mainline) the patches are applied. Is it coming soon or I have to apply the patches myself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to Kai-Heng Feng from comment #145) > Laptops with Skylake SoC and later shouldn't need bbswitch. PCIe port PM > will disable the power of the card. > After nvidia.ko gets unloaded, make sure "power/control" is "auto" for its > video (e.g. 01:00.0) and audio (e.g. 01:00.1) functions and its upstream > bridge (use lspci -t to check). > > In addition to that, these two commits are also required for mainline kernel > users: > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/ > ?id=52525b7a3cf82adec5c6cf0ecbd23ff228badc94 > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/ > ?id=bacd861452d2be86a4df341b12e32db7dac8021e I have an i7 8750H with a GTX 1050 Mobile. I applied these two patches on top of Linus' tree. After I switched all "power/control" to "auto", everything works now. Card powers down, suspend/resume works. Thank you for figuring this out. Before this I was getting lockups with bbswitch/acpi_call during boot. I had to do crazy workarounds to get away with this during early boot and suspend/resume. Those days are gone now! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
I have hp-spectre x360 i7-9750h, nvidia gtx 1650 I have the same issue. This is the first laptop that I have, which is not suitable for linux because of this issue. Any ideas when this issue will be fix for any kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to Kai-Heng Feng from comment #145) > Laptops with Skylake SoC and later shouldn't need bbswitch. PCIe port PM > will disable the power of the card. > After nvidia.ko gets unloaded, make sure "power/control" is "auto" for its > video (e.g. 01:00.0) and audio (e.g. 01:00.1) functions and its upstream > bridge (use lspci -t to check). > > In addition to that, these two commits are also required for mainline kernel > users: > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/ > ?id=52525b7a3cf82adec5c6cf0ecbd23ff228badc94 > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/ > ?id=bacd861452d2be86a4df341b12e32db7dac8021e Ok I've a coffee lake and will go to try these two commits and report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to Matthias Fulz from comment #144) > Ok here are more tests: > > Disabling the audio part with your suggestion ist working. > No NVIDIA audio in powertop nor in lspci. > > Your solution is basically loading / unloading the nvidia modul now, which > indeed is working, but not the optimus part I think? Optimus IS working here, no problem at all. [snip] > For some users it might be fully ok to just use load / unload nvidia as it > make a difference for the power consumption. > > But for me it's around 1/3 missing runtime, which relly hurts me :) > > But perhaps you could try my workaround with two boot entries and check the > power consumption on your side, when running intel only? I will try this maybe tonight when I will have more time to spare. I too would be interested in gaining 20-30% battery life! But, then again, I wouldn't want to have to reboot to be able to use the dGPU (I use it for blender3d). > for me it's around 7-8W intel only and around 11W when using your workaround. > But again your solution is just not really disabling the nvidia card, > instead it's more like just not using it and let it stay in idle mode with > limited PM. Yes, and no... as far as I can see from my tests, it is not staying in idle mode, it is being fully powered down by the kernel when not in use, and fully powered up again when I use optirun. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to Kai-Heng Feng from comment #145) Thank you very much for this optimistic-sounding info, Kai-Heng Feng. > Laptops with Skylake SoC and later shouldn't need bbswitch. PCIe port PM > will disable the power of the card. How do I check if I have Skylake SoC? I am actually currently using a modified bbswitch where I have disabled the acpi calls. The point of this is to force bumblebee to automatically load and unload the nvidia modules before and after using optirun. I suspect there is an easier way but for now this works for me. > After nvidia.ko gets unloaded, make sure "power/control" is "auto" for its > video (e.g. 01:00.0) and audio (e.g. 01:00.1) functions and its upstream > bridge (use lspci -t to check). I initially tried what you describe here but the audio part was preventing power management from happening because it was permanently flagged in use by the snd_hda_audio module. Hence my work-around. > In addition to that, these two commits are also required for mainline kernel > users: > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/ > ?id=52525b7a3cf82adec5c6cf0ecbd23ff228badc94 > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/ > ?id=bacd861452d2be86a4df341b12e32db7dac8021e I am not interested in attempting to compile the kernel so will wait for these two commits to make it into the stable release. Reading their descriptions, especially the second one, sounds like it is the perfect fix for what I am experiencing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to Matthias Fulz from comment #143) > (In reply to arpie from comment #142) > > (In reply to Matthias Fulz from comment #141) > > > (In reply to arpie from comment #140) > > [snip] > > Ah I see. > Then I think this is basically somehow similar to my workaround using the > snd_hda_intel modul parameter. > The nvidia card will just be completely "powered off" by not using it in any > way (no module loaded) Yes, now I've read your workaround more closely, I think you're right it is basically achieving the same thing. > > I am sure that there must be a 'proper' solution where the correct ACPI > > commands are used to power off/on both the nvidia video and audio at the > > same time but finding such a solution is far beyond me... > > I think some ACPI / PM guys should definitly check the audio part of the GPU > as there could be some issues related to this bug. Judging by comment 145, they are already way ahead of us! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
Laptops with Skylake SoC and later shouldn't need bbswitch. PCIe port PM will disable the power of the card. After nvidia.ko gets unloaded, make sure "power/control" is "auto" for its video (e.g. 01:00.0) and audio (e.g. 01:00.1) functions and its upstream bridge (use lspci -t to check). In addition to that, these two commits are also required for mainline kernel users: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=52525b7a3cf82adec5c6cf0ecbd23ff228badc94 https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=bacd861452d2be86a4df341b12e32db7dac8021e -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
Ok here are more tests: Disabling the audio part with your suggestion ist working. No NVIDIA audio in powertop nor in lspci. Your solution is basically loading / unloading the nvidia modul now, which indeed is working, but not the optimus part I think? As soon as I try acpi the freeze is happening again after one or two times running lspci. And here the real problem starts: Just loading and afterwards unloading the nvidia module wakes up the card from the real disabled state. Even powertop telling 0% usage of the nvidia card my power consumption is not going below 11W again. So the issue here is: You're way is not triggering the real shutdown for the nvidia card as you're just unloading the module. The difference in using bbswitch (which leads to freezes for you as well) is that this will do the acpi calls and really powering down the card, which leads to the freezes... For some users it might be fully ok to just use load / unload nvidia as it make a difference for the power consumption. But for me it's around 1/3 missing runtime, which relly hurts me :) But perhaps you could try my workaround with two boot entries and check the power consumption on your side, when running intel only? for me it's around 7-8W intel only and around 11W when using your workaround. But again your solution is just not really disabling the nvidia card, instead it's more like just not using it and let it stay in idle mode with limited PM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to arpie from comment #142) > (In reply to Matthias Fulz from comment #141) > > (In reply to arpie from comment #140) > [snip] > > > If I completely disable the audio card using : > > > echo 1 | sudo tee /sys/bus/pci/devices/:01:00.1/remove > > > > > > Then the system hangs are completely cured > > > > Not working for me. Still freezing with this. > > Any chance of more details? When and how is it freezing? Is it any > different from before? What are your machine/card details (looks like you > haven't posted these anywhere above)? > I've got a HP OMEN 15 with a nvidia GTX 1050 running archlinux > Also, are you absolutely sure you've disabled the audio card during boot > *before the kernel notices it is there*? The only reliable way I've found > to check if this is the case, is to run powertop, and look in the 'Device > Status' tab for listings of 'Audio codec hwX: nvidia'. If that is > showing up, then the nvidia sound card is still active and will cause hangs. > My solution only works if the audio card is removed/disabled before the > audio system initialises during boot (hence the WantedBy=sysinit.target in > my service file). > I've used your service file together with bumblebee and bbswitch. > I think I should have also mentioned that in order for the kernel to do the > PM, you need to do something like : > > echo auto | sudo tee /sys/bus/pci/devices/:01:00.0/power/control > > I have TLP installed, which does this for me. > Ok this step was missing. > Now a few days have passed, I admit I have had a few freezes when using > bbswitch. But if I disable bbswitch and just use bumblebee with no power > management, all is well (so far). If I want to power down the nvidia GFX > card I just manually modprobe -r nvidia and the kernel does the rest. > Using this solution, I see a drop from about 20W to 10W when the card powers > off, with no ACPI calls at all (or, rather, none that I am aware of - I have > no idea what the kernel is actually doing behind the scenes). > Ah I see. Then I think this is basically somehow similar to my workaround using the snd_hda_intel modul parameter. The nvidia card will just be completely "powered off" by not using it in any way (no module loaded) > I am sure that there must be a 'proper' solution where the correct ACPI > commands are used to power off/on both the nvidia video and audio at the > same time but finding such a solution is far beyond me... I think some ACPI / PM guys should definitly check the audio part of the GPU as there could be some issues related to this bug. I will try it perhaps once again and give feedback here. But honestly these tests are really harmful for me because it happens very often that some files are truncated to zero during this crash randomly and I've to restore backups then... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to Matthias Fulz from comment #141) > (In reply to arpie from comment #140) [snip] > > If I completely disable the audio card using : > > echo 1 | sudo tee /sys/bus/pci/devices/:01:00.1/remove > > > > Then the system hangs are completely cured > > Not working for me. Still freezing with this. Any chance of more details? When and how is it freezing? Is it any different from before? What are your machine/card details (looks like you haven't posted these anywhere above)? Also, are you absolutely sure you've disabled the audio card during boot *before the kernel notices it is there*? The only reliable way I've found to check if this is the case, is to run powertop, and look in the 'Device Status' tab for listings of 'Audio codec hwX: nvidia'. If that is showing up, then the nvidia sound card is still active and will cause hangs. My solution only works if the audio card is removed/disabled before the audio system initialises during boot (hence the WantedBy=sysinit.target in my service file). I think I should have also mentioned that in order for the kernel to do the PM, you need to do something like : echo auto | sudo tee /sys/bus/pci/devices/:01:00.0/power/control I have TLP installed, which does this for me. Now a few days have passed, I admit I have had a few freezes when using bbswitch. But if I disable bbswitch and just use bumblebee with no power management, all is well (so far). If I want to power down the nvidia GFX card I just manually modprobe -r nvidia and the kernel does the rest. Using this solution, I see a drop from about 20W to 10W when the card powers off, with no ACPI calls at all (or, rather, none that I am aware of - I have no idea what the kernel is actually doing behind the scenes). I am sure that there must be a 'proper' solution where the correct ACPI commands are used to power off/on both the nvidia video and audio at the same time but finding such a solution is far beyond me... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to arpie from comment #140) > After hours of experimenting on this laptop : > > Computer : PC Specialist OptimusIX 15 (aka Clevo N8xxEP6) > BIOS : American Megatrends 1.07.13 > OS : Arch Linux > GPU : NVIDIA GTX 1060 Mobile > > Until recently, any attempt to use bumblebee or acpi commands to power down > the GPU have resulted in a system freeze with lspci, suspend, power cable > plug in, etc. No kernel line parameters seem to have any effect. > > I have discovered that the system freeze is closely linked to the > interaction between the nvidia graphics card on pci address :01:00.0 and > its associated sound card at pci address :01:00.1 (I don't actually > know what that sound card is doing - I presume it's for the HDMI port?) > > If I completely disable the audio card using : > echo 1 | sudo tee /sys/bus/pci/devices/:01:00.1/remove > > Then the system hangs are completely cured - I can acpi _OFF or _ON or _PS3 > or _PS0 to my hearts content and the gfx card will power up and down > perfectly, lspci behaves perfectly normally (without any lag), and > suspend/resume and power cable plug/unplug all works. Even better, kernel > power management on the PCI bus seems to work perfectly too, but only kicks > in when I rmmod nvidia. So far, bumblebee and bbswitch also seem to be > totally happy. > > Can anybody else confirm similar findings? > > Bear in mind that the audio card needs to be removed BEFORE the kernel loads > any audio modules. I do it like this : > > [Unit] > Description=Nvidia Audio Card OnBoot Disabler > Before=bumblebeed.service > > [Service] > Type=oneshot > RemainAfterExit=yes > ExecStart=/usr/bin/sh -c "echo 1 > /sys/bus/pci/devices/:01:00.1/remove" > ExecStop=/usr/bin/sh -c "echo 1 > /sys/bus/pci/rescan" > > [Install] > WantedBy=sysinit.target Not working for me. Still freezing with this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
After hours of experimenting on this laptop : Computer : PC Specialist OptimusIX 15 (aka Clevo N8xxEP6) BIOS : American Megatrends 1.07.13 OS : Arch Linux GPU : NVIDIA GTX 1060 Mobile Until recently, any attempt to use bumblebee or acpi commands to power down the GPU have resulted in a system freeze with lspci, suspend, power cable plug in, etc. No kernel line parameters seem to have any effect. I have discovered that the system freeze is closely linked to the interaction between the nvidia graphics card on pci address :01:00.0 and its associated sound card at pci address :01:00.1 (I don't actually know what that sound card is doing - I presume it's for the HDMI port?) If I completely disable the audio card using : echo 1 | sudo tee /sys/bus/pci/devices/:01:00.1/remove Then the system hangs are completely cured - I can acpi _OFF or _ON or _PS3 or _PS0 to my hearts content and the gfx card will power up and down perfectly, lspci behaves perfectly normally (without any lag), and suspend/resume and power cable plug/unplug all works. Even better, kernel power management on the PCI bus seems to work perfectly too, but only kicks in when I rmmod nvidia. So far, bumblebee and bbswitch also seem to be totally happy. Can anybody else confirm similar findings? Bear in mind that the audio card needs to be removed BEFORE the kernel loads any audio modules. I do it like this : [Unit] Description=Nvidia Audio Card OnBoot Disabler Before=bumblebeed.service [Service] Type=oneshot RemainAfterExit=yes ExecStart=/usr/bin/sh -c "echo 1 > /sys/bus/pci/devices/:01:00.1/remove" ExecStop=/usr/bin/sh -c "echo 1 > /sys/bus/pci/rescan" [Install] WantedBy=sysinit.target -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
If someone is interested in a workaround for using either nvidia or the intel card, I've worked out the following setup: One grub entry for intel only: modprobe.blacklist=nvidia_drm modprobe.blacklist=nvidia_modeset modprobe.blacklist=nvidia snd_hda_intel.enable=1,0,0 Adding the above parameters to grub and using just the intel GPU I'm able to run my omen laptop with 8-9W (25% Display brightness) which gives me around 7-8h :) Every other setup just goes with around 15W Second grub for using the nvidia together with the binary blob: I'm using the following grub parameter to tell that I want to use the discrete card: discretevga=y Therefore I've a shell script that checks for this cmdline param and activate the needed xorg conf: #!/bin/bash if [ -f /etc/X11/xorg.conf.d/20-nvidia.conf ] then rm /etc/X11/xorg.conf.d/20-nvidia.conf fi cat /proc/cmdline | grep 'discretevga' > /dev/null 2>&1 if [ $? -eq 0 ] then ln -s /usr/local/etc/x11-nvidia.conf /etc/X11/xorg.conf.d/20-nvidia.conf else rmmod nvidia_drm rmmod nvidia_modeset rmmod nvidia fi exit 0 here is the x11-nvidia.conf that I'm using: Section "Module" Load "modesetting" EndSection Section "Device" Identifier "Nvidia Card" Driver "nvidia" BusID "1:0:0" Option "AllowEmptyInitialConfiguration" EndSection Drawback is obviously the needed reboot, that is needed to switch between the cards, but at least I'm able to use really both on their own without any issue. And for me 90% of the time I'm just using the intel card, so most important is low power consumption. Hopefully this helps some of you guys ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
I can describe that on latest Ubutnu 18.04.3 LTS (Linux local 5.0.0-29-generic #31~18.04.1-Ubuntu SMP Thu Sep 12 18:29:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux) that there is following behavior for suspend (on HP Spectre x360 15"). - For Nvidia GPU Prime profile, the reliability of wake-up from suspend seems to be improved with recent updates, however there is issue with power draining and heating of the laptop. - When using the integrated Intel graphic by selecting it in PRIME profiles, the computer come out from suspend reliable, however there is the same issue, that the battery is draining and laptop temperature is becoming high while the laptop is suspended. The issue is present also with no peripherals connected, and during suspend the laptop fans are off, so the temperature of laptop is becoming quite high. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
What's the current status on this bug, any reply/update on those patches? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
** Tags added: cscc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
I was posting some patches on the Nouveau mailing list in order to fix this issue. I also wanted some PCI folks to look at it, but nobody replied yet... I am sure that this is in no way a driver issue, but an issue within the PCI subsystem or the PCIe controller, so we are kind of reluctant to push such a "workaround" into a driver as other devices might run into such issues as well? Or maybe it's some Nvidia hardware screwup? Anyways, I have not enough knowledge about how all that PCI stuff works, so I can't come to a final conclusion here. mailing list thread: https://lists.freedesktop.org/archives/nouveau/2019-May/032353.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
HDMI issue on optimus laptops (e.g. HP Spectre x360 - 15) can be fixed by disabling modesetting in the following file: sudo vi /lib/modprobe.d/nvidia-kms.conf # This file was generated by nvidia-prime # Set value to 0 to disable modesetting options nvidia-drm modeset=0 After this prime switching works correctly and HDMI works for NVIDIA card. Tested nvidia-driver-430 but the system still does not come reliable from suspend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
** Description changed: Dell XPS 15 (9750); it might eventually manage to suspend when the lid is closed, but more often than not will not wake up again when the lid is opened. Waking up using the power button often results in a system that is apparently frozen (graphics displayed are the last on screen before suspend, clock seconds do not change) System is unresponsive to the keyboard at that time (can't switch to a VT or otherwise interact with the system other than holding the power button for a few seconds to shut it down). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: mtrudel2516 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: mtrudel2516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 10:42:08 2018 InstallationDate: Installed on 2018-11-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=UUID=14900847-323c-4427-b59e-89210ec1c8ec ro quiet splash vt.handoff=1 RelatedPackageVersions: - linux-restricted-modules-4.18.0-10-generic N/A - linux-backports-modules-4.18.0-10-generic N/A - linux-firmware 1.175 + linux-restricted-modules-4.18.0-10-generic N/A + linux-backports-modules-4.18.0-10-generic N/A + linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
Just to update on this. The same seems for HP Spectre x360 - 15, with nvidia-driver-418 running on Ubuntu 18.04: - HDMI does not work with Intel card selected using prime select. But suspend, restore seems working with acpi_osi=`Windows 2009` in grub. - HDMI does not work also with NVIDIA drivers. And the suspend will freeze laptop. I tested also Fedora 29 and the behavior is the following: - HDMI does not work with Intel card. In suspend the battery seems to be drained. - With nvidia-driver-418 (xorg-x11-drv-nvidia) the HDMI works. But the suspend will freeze laptop. - There is not an easy way as prime select in Ubuntu to switch between Intel and NVIDIA card Also please let me know if there is something how to resolve this. I guess this is affecting many new laptops with Nvidia card. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
This bug also affects the dell precision 5530, unsurprising perhaps given the similarity with the xps 15 9570. Running with boot options `acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep` is a better option so far, compared to acpi_osi=`Windows 2009`, as that broke touchscreen and brightness keys (not important), and also seemed to make battery life much worse (very important). Please let me know if there's any testing that would be helpful on this machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
Additionally it seems for HP Spectre x360 - 15 (with nvidia-driver-415) that also the battery is drained and the laptop is getting warm in the sleep mode. By switching to Intel card (PRIME profile Intel) the sleep mode seems to work well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
Affects also laptop HP Spectre x360 - 15-df0008nc with nvidia-driver-415. The only workaround which seems to work is to use kernel parameters acpi_osi=! acpi_osi=\"Windows 2009\", but that disables the touchpad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
(In reply to Antoine Audras from comment #134) > So what do lspci, lshw and X do that can be "reset" by launching optirun? They wake up the card, but currently nouveau/bbswitch don’t do that properly. I guess that loading the proprietary driver then restores a correct card state maybe? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
Hi,
I am running Arch on an Aero 15x v8 with proprietary nvidia drivers and
bumblebee and I have noted something when using X that I don't see in
the thread (well it echoes the 2 consecutive lspci launch crashing the
system). I dont know if it'll be of any use to you though.
When starting X using just X command without root privilege, X complains
because he wasn't launched with root privilege (can't open /dev/tty0)
And when doing that a second time it just freezes the system right after
printing the initialization messages out ("Using system config [...]")
Once again I launched X unprivileged both times
But launching any application with optirun between the 2 X calls
prevents the second launch from crashing the system.
So I guess optirun must "reset" dôme value somewhere that has been set
by an unprivileged operation.
It can be reproduced lauching lspci or lspci, lshw or X (ex : lspci, X
-> crash, lspci, sudo optirun cat /etc/fstab, X -> no crash)
So what do lspci, lshw and X do that can be "reset" by launching
optirun?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1803179
Title:
System does not reliably come out of suspend
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
Mathieu, does this still happen to XPS 9570? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-410 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
Back with some more info -- although I start to feel that this is getting a bit futile. Hibernation appears to be working again if GuC loading is disabled in i915, so that was probably a separate issue for me. Currently, it seems the machine is fairly stable when running applications with DRI_PRIME=1 or plugging in an external monitor, and power cycling the card with `DRI_PRIME=1 glxinfo` can put it back to state 1 after sleep or hibernation. However, resuming after sleep with an external display connected (i.e., the card is powered on before and after suspend) leads to a non- responsive X server and display manager. I can still switch to another terminal and observe DRI notifier timeout errors from nouveau in dmesg if that rings a bell for someone. Restarting X fixes the problem somewhat, but connecting a display after that freezes the computer for good, during which the monitor complains about unsupported input. At any rate, plugging out the external display to let the card power down before sleep looks like a workaround (this is, of course, after applying the kernel patches in this thread). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
Played around even more. If I set "su -c 'env DISPLAY=:0 DRI_PRIME=1 glxinfo' my_username >/dev/null" as a post-suspend hook in systemd, my GPU returns to state 1 after resume. It would be better to set this hook in KDE, so I don't have to jump through hooks to run in on the X server / with the correct authentication cookie, but I couldn't find a way to do that. I guess this could much rather be done from the kernel, but I am not familiar with nouveau source code at all to write a patch. Resuming from hibernation, on the other hand, is completely broken and leads to a lockup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
Created attachment 279803 DMESG|grep ACPI kernel boot log My ACPI kernel log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
** Bug watch added: github.com/Bumblebee-Project/Bumblebee/issues #1007 https://github.com/Bumblebee-Project/Bumblebee/issues/1007 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
Played around a little bit more with suspend-resume cycles and HDMI connection. It seems that after a suspend-resume-glxgears cycle, I can connect and disconnect by external monitor reliably (no "Unsupported output format" message), so that behavior seems to trigger either only after boot, or randomly (and I didn't manage to trigger it again while playing around). Moreover, after powering on my card by plugging in the monitor, power usage settles around 37W as opposed to 43W, so I might have been too hasty when comparing the power draw of my card in various states. As the discrepancy is quite a bit smaller than I have thought (37W when powered up vs 28W when DynOff with a patched SSDT9), it might be explained by the fact that in "state 2", the card is indeed fully powered, but nouveau thinks it is off, so utilization is 0%. Whereas the card in "state 1" is indeed off, hence the issue when trying to power it up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
I am having similar issues on an ASUS GL504GM (Intel i7 8570H, Nvidia GTX1060) on Linux 4.19.5. My system is stable with the nouveau driver if I use acpi_osi=! acpi_osi="Windows 2009", or if I patch SSDT9 (it appears to handle the dGPU power management) by removing any code conditional on OSI > 2009. However, in that case, the power draw of the laptop is around 28W when the Nvidia GPU is powered off (state DynPwr according to vga_switcheroo), which is lower than the 43W drawn when the Nvidia GPU is powered on, but higher than the 16W drawn with an unpatched SSDT9 and no acpi_osi setting. The latter configuration locks up on lspci or when initiating suspend or poweroff. So the GPU seems to have 3 distinct power states (of course, the proprietary nvidia driver can set lots of different clock speeds that nouveau cannot, but they only come into play when the dGPU is turned on): 1. Fully powered off via ACPI. 2. Partially powered off by vga_switcheroo. 3. Fully powered on. In states 1 and 2, vga_switcheroo reports DynOff, while in state 3 it reports DynPwr. In contrast, bbswitch reports OFF only in state 1, and reports ON in states 2 and 3. It is possible to reach state 1 using bbswitch, but it leads to an unstable system even with the patched SSDT9. After applying patches https://bugzilla.kernel.org/attachment.cgi?id=278269 and https://bugzilla.kernel.org/attachment.cgi?id=278773, my system is stable after booting up and the card is actually in state 1 (I can check the state by looking at the power draw). After a suspend-resume cycle, the card is in state 2. It is possible to return to state 1 by "power cycling" the card: I run DRI_PRIME=1 glxgears to power the card on for PRIME offload and then exit glxgears to power it down. The suspend- resume-offload-exit cycle can be repeated without locking up the system, and lspci also works. The situation is less rosy if I try to connect an external monitor. If I plug in my monitor to the HDMI port, which is wired to the Nvidia GPU, when the card is in state 1, the system locks up. I can avoid the lockup and use the external monitor if I run DRI_PRIME=1 glxgears to put the card into state 3 while plugging in the HDMI cable. After that, gxgears may be exited and the HDMI output continues to function. However, after removing the external monitor this dance cannot be repeated: my monitor just displays "Unsupported output format", as if the card's internal state were corrupted and it sent garbage to the HDMI port. Although some parts of the card must be working correctly because even in this state I can run DRI_PRIME=1 glxgears without problems and see the gears spinning on the internal display of the laptop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
Just wanted to add that I have the same problem with a CLEVO 955ER model. Laptop freezes using lspci/lshw/... with bumblebee switch=OFF on the discrete GPU. Specs: CLEVO 955ER laptop NVIDIA Corporation GP104M [GeForce GTX 1070 Mobile] Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz CPU Distro Archlinux / Kernel 4.14.84-1-lts #1 SMP More infos here: https://github.com/Bumblebee- Project/Bumblebee/issues/1007 Crossing fingers for a fix to be backported to the LTS branch for christmas :] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
The difference between state 1 and 2 is likely the PCIe port (to which the card is attached) being turned off or not from what I understood of all this. And yes, the issue is about powering on the card again, nouveau has issues setting the card configuration correctly at this stage. Going off is working, but on not, resulting in lockup (at worse) or (partially) unusable card. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179]
Same issue. I had to add acpi_osi=! acpi_osi="Windows 2009" as a workaround to boot option. But that caused another issue. My touchpad doesn't work anymore. Model: ASUS FX553VD GTX 1050 + Intel HD Dmesg output have these: [0.00] ACPI: Core revision 20170831 [0.00] ACPI Error: [PRT0] Namespace lookup failure, AE_ALREADY_EXISTS (20170831/dswload-378) [0.00] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20170831/psobject-252) [0.00] ACPI Exception: AE_ALREADY_EXISTS, (SSDT:SataTabl) while loading table (20170831/tbxfload-228) [0.00] ACPI Error: 1 table load failures, 10 successful (20170831/tbxfload-246) [9.722102] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed4-0xfed4087f flags 0x200] vs fed40080 f80 [9.722107] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed4-0xfed4087f flags 0x200] vs fed40080 f80 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
Launchpad has imported 126 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=156341.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2016-09-08T10:25:10+00:00 peter wrote:
Created attachment 232611
dmesg for v4.7-rc5 (triggered runtime-resume via writing "on" to (nvidia
device)/power/control)
See also https://www.spinics.net/lists/linux-pci/msg53694.html ("Kernel
Freeze with American Megatrends BIOS") for more details (acpidump,
lspci, some analysis, etc.).
Steps to reproduce on the affected machines:
1. Load nouveau.
2. Wait for it to runtime suspend.
2. Invoke 'lspci', this resumes the Nvidia PCI device via nouveau.
(alternatively: write "on" to /sys/bus/pci/devices/:01:00.0/power/control)
3. lspci never returns, few moments later an AML_INFINITE_LOOP is reported.
Affected machines from
https://github.com/Bumblebee-Project/Bumblebee/issues/764#issuecomment-234494238
- Clevo P651RA (and other Clevo P6xxRx models).
- MSI GE62 Apache Pro
- Gigabyte P35V5
- Razer Blade 14" (2016)
- Dell Inspiron 7559
These *new* laptops all have an Skylake CPU (i7-6500HQ) and a Nvidia GTX
9xxM GPU. Originally it was only observed for laptops with AMI BIOSes,
but later we found a Dell laptop as well. The workaround
acpi_osi="!Windows 2015" prevents Linux from reporting Windows 10
compatibility and helps *in some cases* because the ACPI code falls back
to a different approach to power on the device (or PCIe link?).
Attached is one of the more interesting dmesg dumps which could be
obtained that shows how the system breaks down over time. (This was
v4.7-rc5 with PCI/PM D3cold + nouveau power resource/PM refcount leaks
patches, but the problem was also visible on unpatches 4.4.0 for
example.)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803179/comments/0
On 2016-09-12T10:51:42+00:00 rui.zhang wrote:
let's focus on one platform first.
For people who encounters this problem and can give quick response, please
attach the acpidump of the platform.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803179/comments/1
On 2016-09-12T10:54:29+00:00 rui.zhang wrote:
Okay, let's focus on Clevo_P651RA first.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803179/comments/2
On 2016-09-12T10:55:33+00:00 rui.zhang wrote:
I don't see how to download the acpidump file at
https://github.com/Lekensteyn/acpi-stuff/blob/master/dsl/Clevo_P651RA/acpidump.txt
can you please attach it here?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803179/comments/3
On 2016-09-12T12:07:08+00:00 peter wrote:
Created attachment 233091
acpidump for Clevo P651RA (BIOS 1.05.07)
You can download the file via the "Raw" link on Github. I have attached
a copy of the acpidump.
Of interest is the \_SB.PCI0.PGON method. See also this extract:
https://github.com/Lekensteyn/acpi-stuff/blob/master/Clevo-P651RA/notes.txt#L94
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803179/comments/4
On 2016-09-19T23:49:11+00:00 lenb wrote:
Does this still fail if you use the proprietary nvidia driver?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803179/comments/5
On 2016-09-20T02:36:24+00:00 lv.zheng wrote:
Peter:
Should you first try this: attachment 239241
Rui:
Do you have PCI contact? Can we have them to look at the issue first?
>From this link:
https://www.spinics.net/lists/linux-pci/msg53694.html
Looks like a PCI power management gap if the attachment 239241 doesn't help.
Thanks
Lv
Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803179/comments/6
On 2016-09-20T08:31:09+00:00 peter wrote:
(In reply to Len Brown from comment #5)
> Does this still fail if you use the proprietary nvidia driver?
I have not tried the proprietary driver, but AFAIK the blob does no
attempts to put the device in D3 state.
(In reply to Lv Zheng from comment #6)
> Peter:
> Should you first try this: attachment 239241 [details]
I can try, but would it really help? Not all firmware have this loop and
they will just assume that the link state is correct. This is the
affected loop:
While ((\_SB.PC
[Bug 1803179] Re: System does not reliably come out of suspend
** Bug watch added: Linux Kernel Bug Tracker #156341 https://bugzilla.kernel.org/show_bug.cgi?id=156341 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=156341 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
A workaround is adding the following boot patameters: `acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep` (Thanks to the input of nvidia forum and github.com/JackHack96/dell- xps-9570-ubuntu-respin ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
Opened a forum thread on the Nvidia dev forum regarding this issue" https://devtalk.nvidia.com/default/topic/1044633/linux/driver-does-not-wake-gpu-properly-after-suspend-ubuntu-18-10-with-branch-390-410-and-415-/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
** Also affects: linux Importance: Undecided Status: New ** No longer affects: linux ** Also affects: nvidia-graphics-drivers-410 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
Some added info. This bug is present in: driver : nvidia-driver-415 - third-party free recommended driver : nvidia-driver-410 - third-party free driver : nvidia-driver-390 - distro non-free GPU info: == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd1C8Csv1028sd087Cbc03sc02i00 vendor : NVIDIA Corporation model: GP107M [GeForce GTX 1050 Ti Mobile] When in the faulty state `nvidia-smi` displays a 100% GPU Utilization. Using `prime-select intel` to switch GPU and killing X gives back your display environment using onboard GPU. ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
Seems like this is caused by nvidia drivers not liking s2idle or forcing the use of 'deep' leads to reliable suspend/resume cycles. Properly removing nvidia drivers leads to a working system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Re: System does not reliably come out of suspend
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.20 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20-rc2 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803179] [NEW] System does not reliably come out of suspend
Public bug reported: Dell XPS 15 (9750); it might eventually manage to suspend when the lid is closed, but more often than not will not wake up again when the lid is opened. Waking up using the power button often results in a system that is apparently frozen (graphics displayed are the last on screen before suspend, clock seconds do not change) System is unresponsive to the keyboard at that time (can't switch to a VT or otherwise interact with the system other than holding the power button for a few seconds to shut it down). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mtrudel2516 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Nov 13 10:42:08 2018 InstallationDate: Installed on 2018-11-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. XPS 15 9570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=UUID=14900847-323c-4427-b59e-89210ec1c8ec ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd09/03/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803179 Title: System does not reliably come out of suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
