suspend fails

Bug #1450756 reported by Jürgen
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

On all kernel suspend is not possible. I ran pm_test and it hangs.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-15-generic 3.19.0-15.15 [modified: boot/vmlinuz-3.19.0-15-generic]
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jott 1557 F.... pulseaudio
CurrentDesktop: KDE
Date: Fri May 1 11:55:32 2015
HibernationDevice: RESUME=UUID=38664fac-0972-4e0f-8425-34b54ed3e248
InstallationDate: Installed on 2015-04-26 (4 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Acer Aspire E3-112
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic root=UUID=10924b10-cb76-4f0b-8275-1a2874fa4b00 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-15-generic N/A
 linux-backports-modules-3.19.0-15-generic N/A
 linux-firmware 1.143
SourcePackage: linux
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/20/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.08
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: R2
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireE3-112:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E3-112
dmi.product.version: V1.08
dmi.sys.vendor: Acer

Revision history for this message
Jürgen (j-w-ott) 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
Changed in linux (Ubuntu):
importance: Undecided → Medium
penalvch (penalvch)
tags: added: bios-outdated-1.10
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jürgen (j-w-ott) wrote : Re: [Bug 1450756] Re: suspend fails

Hello,

I have flashed the latest bios the problem persists

dmidecode says:

V1.10
08/20/2014

Am Samstag, 2. Mai 2015, 11:33:59 schrieben Sie:
> Jürgen, thank you for reporting this and helping make Ubuntu better. As
> per http://us.acer.com/ac/en/US/content/drivers an update to your
> computer's buggy and outdated BIOS is available (1.10). If you update to
> this following https://help.ubuntu.com/community/BIOSUpdate does it
> change anything?
>
> If it doesn't, could you please both specify what happened, and provide the
> output of the following terminal command: sudo dmidecode -s bios-version &&
> sudo dmidecode -s bios-release-date
>
> For more on BIOS updates and linux, please see
> https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
> .
>
> Please note your current BIOS is already in the Bug Description, so
> posting this on the old BIOS would not be helpful. As well, you don't
> have to create a new bug report.
>
> Once the BIOS is updated, and the information above is provided, then
> please mark this report Status Confirmed.
>
> Thank you for your understanding.
>
> ** Tags added: bios-outdated-1.10
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete

Revision history for this message
penalvch (penalvch) wrote :

Jürgen, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test 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 bug 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 XY and Z are numbers corresponding to the kernel version.

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

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

tags: added: latest-bios-1.10
removed: bios-outdated-1.10
description: updated
Jürgen (j-w-ott)
tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.1.0-040100rc2-generic
Revision history for this message
Jürgen (j-w-ott) wrote :

shutdown is not possible too.
when running in recovery mode the last message is "hanging up"
the disk stops spinning, so maybe the problem is at the very end.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Jürgen , did this problem not occur in a release prior to Vivid?

tags: added: kernel-bug-exists-upstream-4.1-rc2
removed: kernel-bug-exists-upstream-4.1.0-040100rc2-generic
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jürgen (j-w-ott) wrote :

This is the last working kernel ( resume to disk is not possible)

(unicorn)
3.16.0-31-generic

Changed in linux (Ubuntu):
status: Incomplete → Opinion
status: Opinion → Incomplete
Revision history for this message
penalvch (penalvch) wrote :

Jürgen, the next step is to fully commit bisect from kernel 3.16 to 3.19 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.

Thank you for your understanding.

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

tags: added: needs-bisect regression-release
Revision history for this message
Jürgen (j-w-ott) wrote :

linux-image-3.16.0-28-generic-3.16.0-28.38 last "good kernel"
linux-image-3.18.0-8-generic 3.18.0-8.9 first "bad one"

It irritates me not to find more users reporting this problem, allthough there are some other asus users reporting similar problems

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jürgen (j-w-ott) wrote :

I tried to bisect the kernel but ended up in a dead end.

http://ubuntuforums.org/archive/index.php/t-2078650.html

describes exactly my problem to help

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
Revision history for this message
penalvch (penalvch) wrote :

Jürgen, as noted in https://wiki.ubuntu.com/Kernel/KernelBisection one would want to switch to bisecting the mainline kernel.

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.