kerneloops on suspend: failure of previous suspend

Bug #1354410 reported by Rikki on 2014-08-08
This bug affects 6 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

Contents of susres.crash from /var/crash attached.

Cannot manually reproduce this, it occurs seemingly randomly when system suspends.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-32-generic 3.13.0-32.57
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Fri Aug 8 13:04:20 2014
HibernationDevice: RESUME=UUID=a06ceb3d-7b09-41b7-b52d-9f37bd14e5c3
InstallationDate: Installed on 2014-06-07 (61 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
 p2p1 no wireless extensions.

 lo no wireless extensions.
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f3:0110 Elan Microelectronics Corp.
 Bus 001 Device 002: ID 0409:005a NEC Corp. HighSpeed Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MSI MS-7877
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/stripe-root ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw
 linux-restricted-modules-3.13.0-32-generic N/A
 linux-backports-modules-3.13.0-32-generic N/A
 linux-firmware 1.127.5

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install) 03/25/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.2
dmi.board.asset.tag: To be filled by O.E.M. J1900I
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.2:bd03/25/2014:svnMSI:pnMS-7877:pvr1.0:rvnMSI:rnJ1900I:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: MS-7877
dmi.product.version: 1.0
dmi.sys.vendor: MSI

Rikki (rikkicoles) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
tags: added: latest-bios-v1.2

Rikki, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (not the daily folder) following ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:

where VERSION-NUMBER is the version number of the kernel you tested. For example:

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description.

If the mainline kernel does not fix this bug, please add the following tags:

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Rikki (rikkicoles) wrote :

Tried the upstream kernel linux-image-3.16.0-031600rc7-generic_3.16.0-031600rc7.201407271635_amd64 and it seems to work!

Have been running it since Saturday morning with multiple suspend/resume cycles since then, all successful.

tags: added: kernel-fixed-upstream-3.16-rc7
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Rikki (rikkicoles) on 2014-08-11
tags: added: kernel-fixed-upstream
tags: added: needs-reverse-bisect

Rikki, the next step is to fully reverse commit bisect the kernel in order to identify the fix commit. Could you please do this following ?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Rikki (rikkicoles) wrote :


I've managed to pin down the first good and last bad kernel versions as v3.15-rc1-trusty and v3.14.17-utopic respectively.

However, in order to do the reverse commit bisect I need to map these version numbers to the upstream version. I presume that the trusty kernel above maps directly to upstream 3.15-rc1.

I cannot find the utopic kernel number in the mapping table here:

How can I map this kernel to upstream?


Rikki (rikkicoles) on 2014-08-20
Changed in linux (Ubuntu):
status: Incomplete → Confirmed

Rikki, don't let it not showing up on the mapping table be a show stopper. Feel free to test the mainline kernel versions with the same version number, and take it from there.

Rikki (rikkicoles) wrote :

After reverse bisecting the linux-stable branch (git:// as this was the only repo with matching version numbers, I think I have identified the fix commit as:

d586c86d50cefa0897a51a2dbc714060ccedae76: Merge branch 'for-linus' of git://

Please see attached bisection log for more details.

Changed in linux (Ubuntu):
status: Confirmed → Triaged
tags: added: cherry-pick reverse-bisect-done
removed: needs-reverse-bisect
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers