[CLEVO CO. M1100M] suspend/resume failure

Bug #1152620 reported by Fabio Marconi
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Resuming from suspend, pc start, but no video, sysrq key not working, hard reboot needed

The last working kernel is 3.5.7.7-Quantal, while the first not working is 3.6-Quantal.

ProblemType: KernelOops
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-11-generic 3.8.0-11.20
ProcVersionSignature: Ubuntu 3.8.0-11.20-generic 3.8.2
Uname: Linux 3.8.0-11-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: lalla 1349 F.... pulseaudio
CRDA:
 country EC:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 20), (3, 17)
  (5250 - 5330 @ 20), (3, 23), DFS
  (5735 - 5835 @ 20), (3, 30)
Date: Fri Mar 8 14:41:10 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=73bef8af-a5c9-4d96-9540-80e40ed1469d
InstallationDate: Installed on 2013-02-22 (13 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130222)
InterpreterPath: /usr/bin/python3.3
MachineType: CLEVO CO. M1100M
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB:
 0 inteldrmfb
 1 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-11-generic root=UUID=7f39caa1-d198-46fa-b517-20c60de79232 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-11-generic N/A
 linux-backports-modules-3.8.0-11-generic N/A
 linux-firmware 1.103
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Title: [CLEVO CO. M1100M] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 09/08/2010
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: M1100M
dmi.board.vendor: CLEVO CO.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/08/2010:svnCLEVOCO.:pnM1100M:pvrNotApplicable:rvnCLEVOCO.:rnM1100M:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: M1100M
dmi.product.version: Not Applicable
dmi.sys.vendor: CLEVO CO.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

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/v3.9-rc1-raring/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: suspend-watch
tags: added: kernel-bug-exists-upstream
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Hallo Joseph
I've tested many kernels, observing:

the kernel 3.5-Quantal works.

The last working kernel is 3.5.7.7-Quantal ( http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5.7.7-quantal/ )

The first not working is 3.6-Quantal ( http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-quantal/ )

So I think that the bug is introduced starting from 3.6 series.

Thanks
Fabio

tags: added: regression-update
tags: added: needs-bisect
Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
penalvch (penalvch) wrote :

Fabio Marconi, the next step is to fully commit bisect from 3.5.7.7-Quantal to 3.6-Quantal, in order to find the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#Commit_bisecting_upstream_kernel_versions ?

tags: added: kernel-bug-exists-upstream-v3.9-rc1
removed: kernel-bug-exists-upstream
description: updated
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.