[Kernel-packages] [Bug 1669620] Re: Reboot when resume from suspend

2017-06-03 Thread Jean-Pierre van Riel
Apologises, I think I'm conflating a resume from hibernate issue vs a resume from suspend issue, so the previous comment is probably not that relevant. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1669620] Re: Reboot when resume from suspend

2017-06-03 Thread Jean-Pierre van Riel
No sure if this will help, but there are plenty of debian bugs related to this to check If you are relying on the `resume=` kernel parameter with /etc/default/grub, that might well be ignored. According to the message below, there are various bugs in upstream debian (and I'm not sure if Ubuntu

[Kernel-packages] [Bug 1669620] Re: Reboot when resume from suspend

2017-03-11 Thread Kai-Heng Feng
Can you make persistent log by $ sudo mkdir -p /var/log/journal $ sudo systemd-tmpfiles --create --prefix /var/log/journal Then reboot the system, and add "drm.debug=0x0e" to kernel parameter? After the resume failed, attach the output of `journalctl -b -1`, thanks! -- You received this bug

[Kernel-packages] [Bug 1669620] Re: Reboot when resume from suspend

2017-03-10 Thread tim474
I tested with another video card (GeForce 8400 GS), and suspend works normally. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1669620 Title: Reboot when resume from suspend Status in

[Kernel-packages] [Bug 1669620] Re: Reboot when resume from suspend

2017-03-10 Thread Kai-Heng Feng
Oops, I misread 9800 as 980. Sorry. So we need to know what's the result of the following... Executes these commands as root: # echo devices > /sys/power/pm_test Then suspend and check if the issue happens. If not # echo platform > /sys/power/pm_test Suspend and check again. If not # echo core

[Kernel-packages] [Bug 1669620] Re: Reboot when resume from suspend

2017-03-10 Thread tim474
I'll try, but on Ubuntu 14.04 suspend works with 340. It's not new card, it's about 10 years old. And there wasn't this problem with this card on previous Ubuntu versions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1669620] Re: Reboot when resume from suspend

2017-03-09 Thread Kai-Heng Feng
I'd say nvidia driver is somewhat necessary for new cards, this can be done by $ sudo apt install nvidia-367 Reboot and test if suspend works. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1669620] Re: Reboot when resume from suspend

2017-03-08 Thread tim474
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1669620 Title: Reboot when resume from suspend Status in linux

[Kernel-packages] [Bug 1669620] Re: Reboot when resume from suspend

2017-03-07 Thread tim474
I tested with 4.10.0, and I have the same problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1669620 Title: Reboot when resume from suspend Status in linux package in Ubuntu:

[Kernel-packages] [Bug 1669620] Re: Reboot when resume from suspend

2017-03-04 Thread tim474
Yes, with kernel 4.10.1-041001-generic there is the same problem. ** Tags added: kernel-bug-exists-upstream ** Description changed: When I resume my computer from suspend2ram, after about 2 seconds it shutdowns and after about 3 seconds swithces on, and system starts to boot from GRUB as

[Kernel-packages] [Bug 1669620] Re: Reboot when resume from suspend

2017-03-03 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 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