black screen after Suspend Mode

[Marcel Beerli]

This is a dell workstation and many times after a suspend mode the monitor stays black.

PS: Choosing a package is very hard here. Either to many matches or no match, I get nothing in between

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-24-generic 4.4.0-24.43
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: rbeerli 3158 F.... pulseaudio
 /dev/snd/controlC0: rbeerli 3158 F.... pulseaudio
CurrentDesktop: Unity
Date: Sat Jun 25 05:18:14 2016
HibernationDevice: RESUME=UUID=db7fb9f9-2ba1-429b-8466-8967a61b8dc7
InstallationDate: Installed on 2014-05-24 (762 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: Dell Inc. Dell DXP051
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic root=UUID=43af0a01-14c0-448b-8fcc-0c23db678b97 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-24-generic N/A
 linux-backports-modules-4.4.0-24-generic N/A
 linux-firmware 1.157
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-06-11 (13 days ago)
dmi.bios.date: 05/30/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0FJ030
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/30/2006:svnDellInc.:pnDellDXP051:pvr:rvnDellInc.:rn0FJ030:rvr:cvnDellInc.:ct7:cvr:
dmi.product.name: Dell DXP051
dmi.sys.vendor: Dell Inc.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[elpd (eyal-lapidot)]

I just tried kernel 4.6.0-040600rc7-generic and it seems to solve the problem for me. Previous kernel was 4.4.0-24.

[penalvch (penalvch)]

Marcel Beerli , thank you for reporting this and helping make Ubuntu better.

Could you please provide the full computer model as noted on the sticker of the computer itself (not from the Bug Description)?

[penalvch (penalvch)]

elpd (eyal-lapidot), it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[Marcel Beerli (493pocbrcycmdw7yksonho9o2qzzq06652mtv6nw76-admin-d18ecat4t1b76tkfi3vttrkfngli4hci2jxl2sxy9j)]

Dell XPS400

[penalvch (penalvch)]

Marcel Beerli, to clarify, did this issue not occur in a release prior to 16.04?

[Marcel Beerli (493pocbrcycmdw7yksonho9o2qzzq06652mtv6nw76-admin-d18ecat4t1b76tkfi3vttrkfngli4hci2jxl2sxy9j)]

This did not happen with 15.10 on the Dell Computer
I upgrade a 2nd computer to 16.04 and there in order to get VMware V11 to open the Image, I had to turn off Secure Boot in the ASUS Bios. (Probably unrelated)
But yes this only happens with 16.04 after Suspend Mode which we use quite often to reduce the boot time on this older computer.

[penalvch (penalvch)]

Marcel Beerli, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.

Thank you for your understanding.

[Marcel Beerli (493pocbrcycmdw7yksonho9o2qzzq06652mtv6nw76-admin-d18ecat4t1b76tkfi3vttrkfngli4hci2jxl2sxy9j)]

kernel-bug-exists-upstream-4.7.04-rc4

this kernel was tested:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc4-yakkety/linux-headers-4.7.0-040700rc4-generic_4.7.0-040700rc4.201606201235_i386.deb

Notes:
I have tested it a few times. It is getting better.
Before 1 out of 15 no black screen
When black screen, also no keyboard lights on caps lock

Now, I only tested it about 5 times and 2 times black screen with no keyboard.

[penalvch (penalvch)]

Marcel Beerli, the next step is to fully commit bisect from kernel 4.2 to 4.4 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of bisecting.

After the offending commit (not kernel version) has been identified, then please mark this report Status Confirmed.

Thank you for your help.

[Marcel Beerli (493pocbrcycmdw7yksonho9o2qzzq06652mtv6nw76-admin-d18ecat4t1b76tkfi3vttrkfngli4hci2jxl2sxy9j)]

This would be very time consuming to do.
What I could do is the following.
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
Which is the first 16.04 one I should try ?

v4.2.4-wily 2015-10-26 11:00 ?
Will the system still work putting an older Kernel on it?

thanks

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]