Hang and kernel panic on wake up from suspend.

[zeimusu]

I get frequent, but not always reproducible "hang" after waking from suspend

The hang often occurs before any login or password screen appears. and cannot be broken by ctrl-alt-del or ctrl-alt-1 or any other key combination.

Sometimes the gdm login screen is shown, but the mouse freezes, the keyboard gets no response. The power key also has no effect. I have to disconnect from power to reboot.

The last time I got an error message, which read:
...
Kernel panic - not syncing: Fatal exception in interrupt.
Kernel offset 0x0 from 0xffffffff81000000 (reallocation range 0xffffffff80000000-0xffffffffbfffffff)
drm_kms_helper: panic occured, switching back to text console

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-14-generic 3.19.0-14.14
ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
Uname: Linux 3.19.0-14-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.17.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: jk 1534 F.... pulseaudio
 /dev/snd/controlC0: jk 1534 F.... pulseaudio
CurrentDesktop: GNOME
Date: Fri Apr 17 15:46:06 2015
HibernationDevice: RESUME=UUID=63979b73-ae6b-4ea0-863f-c63d8c7e8aa4
InstallationDate: Installed on 2015-04-06 (10 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Beta amd64 (20150402)
MachineType: SAMSUNG ELECTRONICS CO., LTD. RF510/RF410/RF710
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-14-generic root=UUID=5eb5ba6c-2032-4b8f-bc4c-401b1320b167 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-14-generic N/A
 linux-backports-modules-3.19.0-14-generic N/A
 linux-firmware 1.143
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 02GB.M025.20101027.hkk
dmi.board.asset.tag: Tag 12345
dmi.board.name: RF510/RF410/RF710
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr02GB.M025.20101027.hkk:bd10/27/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnRF510/RF410/RF710:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRF510/RF410/RF710:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: RF510/RF410/RF710
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

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.0 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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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.0-vivid/

[zeimusu (james-kilfiger)]

This bug seems to have begun with about 3.19.0-4

It does not seem to be present in 3.16 (But in 3.16 the screen shows in low resolution)

It appears to be related to the nouveau graphics driver, as installing proprietary nvida seems to clear it.

Tested with mainline 4.0 The bug does not seem to be present, (made two attempts, in both cases the computer awoke normally) marking as "kernel-fixed-upstream"
(But as I have no wifi with the 4.0 kernel, I'll be returning to 3.19 for everyday use. is this a bug or expected?)

Marking confirmed as requested.

[penalvch (penalvch)]

zeimusu, the next step is to fully reverse commit bisect from kernel 3.19 to 4.0 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

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

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Joseph Salisbury (jsalisbury)]

Could you also test the latest upstream 3.19 kernel? It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19.4-vivid/

[Launchpad Janitor (janitor)]

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