[Kernel-packages] [Bug 1494484] Re: Black screen on resume after suspend

2015-11-14 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1494484] Re: Black screen on resume after suspend

2015-09-15 Thread bp0
Not sure if I understand how to test the results - don't I need the custom kernel that Maxim Kizub compiled? I can confirm that his workaround is effective in v4.2.0-040200-generic #201508301530. -- You received this bug notification because you are a member of Kernel Packages, which is

[Kernel-packages] [Bug 1494484] Re: Black screen on resume after suspend

2015-09-14 Thread Christopher M. Penalver
bp0, did you test the results to confirm that commit is the regression? If not, instructions are available at https://wiki.ubuntu.com/Kernel/KernelBisection . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1494484] Re: Black screen on resume after suspend

2015-09-13 Thread bp0
It appears that a very nice person did a kernel bisect and found the bug I have: https://bugs.launchpad.net/ubuntu/+source/linux-lts- utopic/+bug/1483467 His workaround also works for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to

[Kernel-packages] [Bug 1494484] Re: Black screen on resume after suspend

2015-09-10 Thread Christopher M. Penalver
bp0, before reporting upstream, could you please provide the missing information following https://wiki.ubuntu.com/DebuggingKernelSuspend ? ** Tags added: latest-bios-2.30 ** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.2 ** Changed in: linux (Ubuntu) Status:

[Kernel-packages] [Bug 1494484] Re: Black screen on resume after suspend

2015-09-10 Thread Joseph Salisbury
This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug. Please follow the instructions on