Created attachment 97286 [details] dmesg output after resume Lock up after resume on Ubuntu Trusty with the Ubuntu desktop and gnome+compiz desktop interface. No issues with gnome+metacity. Machine locks up completely with the Unity interface, but is responsive enough on gnome+compiz to allow switch to dumb tty to produce dmesg output as attached. Display on tty7 locked up and scrambled though.
Created attachment 97287 [details] output of lspci -vvv
- Bug still exists with Ubuntu's spin of the 3.14 kernel on 31/03/14 Linux usbuntu 3.14.0-031400-generic #201403310035 SMP Mon Mar 31 04:36:23 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux - Bug does not exist when using proprietary nvidia drivers. Note that this report is based on Ubuntu bug 1299821. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1299821 Cheers, Sean
(In reply to comment #2) > - Bug still exists with Ubuntu's spin of the 3.14 kernel on 31/03/14 > Linux usbuntu 3.14.0-031400-generic #201403310035 SMP Mon Mar 31 04:36:23 > UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Can you try the latest mesa? Search for Oliaf's PPA. > - Bug does not exist when using proprietary nvidia drivers. No surprise there :P
(In reply to comment #3) > (In reply to comment #2) > > - Bug still exists with Ubuntu's spin of the 3.14 kernel on 31/03/14 > > Linux usbuntu 3.14.0-031400-generic #201403310035 SMP Mon Mar 31 04:36:23 > > UTC 2014 x86_64 x86_64 x86_64 GNU/Linux > Can you try the latest mesa? Search for Oliaf's PPA. I think you meant 'oibaf'. Not sure what latest mesa would get though...
Installed oibaf ppa and allowed the newer packages in that ppa to update my installation. Still get the same symptoms and the same "Failed to idle channel" messages in dmesg and output to my vtty.
(In reply to comment #4) > I think you meant 'oibaf'. Not sure what latest mesa would get though... Indeed, I'm kind of bad with names. Last time I've checked the packages were from mesa master. (In reply to comment #5) > Installed oibaf ppa and allowed the newer packages in that ppa to update my > installation. Still get the same symptoms and the same "Failed to idle > channel" messages in dmesg and output to my vtty. Can you attach the output of dmesg and glxinfo ? You might want to try the blob's firmware - append nouveau.config=NvGrUseFW=1 to your kernel command line and follow the instructions [1]. Do not forget to add the files to initrd (if you're using one). [1] http://nouveau.freedesktop.org/wiki/VideoAcceleration/#firmware
Created attachment 97340 [details] dmesg_output_after_resume_with_olaif_ppa
glxinfo refused to generate. dmesg is attached. glxinfo -display :0 fails Tried using the binary blob. Will need some help adding to initrd. Without adding to initrd, the system booted but the display was messed up. Was usable enough to work out where the login box was, so I logged in. After suspend/resume there was no display and the laptop started beeping (kernel panic?). So I have no dmesg for you to help debug that one.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1062.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.