[System manufacturer System Product Name] hibernate/resume failure

[don lesniakowski]

Last activity was hibernate. Upon wake-up (touch spacebar), problems. The system did start without me having to cycle power, etc. and I ended up here.

I'm a linux user, not a programmer. If you want more info, you will have to ask and work with me.

Thanks!

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-53-generic 3.13.0-53.89
ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
Uname: Linux 3.13.0-53-generic x86_64
Annotation: This occured during a previous hibernate and prevented it from resuming properly.
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: don 1948 F.... pulseaudio
 /dev/snd/controlC0: don 1948 F.... pulseaudio
CurrentDmesg: [ 31.115976] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Date: Mon Jun 8 20:44:19 2015
DuplicateSignature: hibernate/resume:System manufacturer System Product Name:0401
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: hibernate/resume
HibernationDevice: RESUME=UUID=ffd2b5a3-0e8e-4f9b-9288-cff133a90145
InstallationDate: Installed on 2011-12-18 (1268 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterpreterPath: /usr/bin/python3.4
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: System manufacturer System Product Name
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=9f13b409-27bd-4e42-99c0-59fccdb87241 ro quiet splash
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.13.0-53-generic N/A
 linux-backports-modules-3.13.0-53-generic N/A
 linux-firmware 1.127.12
RfKill:

SourcePackage: linux
Title: [System manufacturer System Product Name] hibernate/resume failure
UpgradeStatus: Upgraded to trusty on 2014-08-18 (295 days ago)
UserGroups:

dmi.bios.date: 07/15/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0401
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z68-V LX
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0401:bd07/15/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[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.1 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.1-rc7-unstable/

[don lesniakowski (donles)]

Hi,

>Did this issue start happening after an update/upgrade? Was there a
>prior kernel version where you were not having this particular problem?

   To be honest, I don't know what is happening. I've had this version of
Ubuntu for some time and it seems there is usually a weekly update that I
go ahead and install.
   Do you think this is related? I rarely shutdown and boot cold unless
I'm going away and someone might visit the house to help with the dog or if
an update wants a reboot, I'll do it. Usually, I hibernate from one
session to the next. About 6 to 8 weeks ago, I must have rebooted and I
came to what I think is the grub bootloader page. I was asked if I wanted
to run Ubuntu or some other option. I could not select an option or
continue because keyboard input did not work. I blew out the machine with
compressed air. I tried to boot and it worked using my same keyboard.
This has happened once or twice since but a power-down holding the power
button down for >4 seconds and subsequent power-up has been successful.
   When this issue that was reported occured, I thought that I might have
the same experience (boot choice) but did not. I really cannot tell you
what happened because I've seen it only once and it seemed to repair itself.

> Would it be possible for you to test the latest upstream kernel? Refer
>to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
>v4.1 kernel[0].

   I'll check it out and try. As I said in the bug report, I'm comfortable
as a user but am not a programmer.
I am willing to make an effort and help.

Thanks,
Don Lesniakowski

On Tue, Jun 9, 2015 at 12:34 PM, Joseph Salisbury <
<email address hidden>> wrote:

> 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.1 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.1-rc7-unstable/
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1463222
>
> Title:
> [System manufacturer System Product Name] hibernate/resume failure
>
> Status in linux package in Ubuntu:
> Incomplete
>
> Bug description:
> Last activity was hibernate. Upon wake-up (touch spacebar), problems.
> The system did start without me having to cycle power, etc. and I
> ended up here.
>
> I'm a linux user, not a programmer. If y...

[don lesniakowski (donles)]

    Since the incident that triggered the bug report, I have had no
reoccurences. I've woken successfully from hibernation and just a few
minutes ago, installed the latest Ubuntu updates and restarted the pc. Nor
have I experienced the boot choices screen with a seemingly non-working
keyboard.

On Thu, Jun 11, 2015 at 4:26 PM, Don Lesniakowski <email address hidden> wrote:

> Hi,
>
> >Did this issue start happening after an update/upgrade? Was there a
> >prior kernel version where you were not having this particular problem?
>
> To be honest, I don't know what is happening. I've had this version of
> Ubuntu for some time and it seems there is usually a weekly update that I
> go ahead and install.
> Do you think this is related? I rarely shutdown and boot cold unless
> I'm going away and someone might visit the house to help with the dog or if
> an update wants a reboot, I'll do it. Usually, I hibernate from one
> session to the next. About 6 to 8 weeks ago, I must have rebooted and I
> came to what I think is the grub bootloader page. I was asked if I wanted
> to run Ubuntu or some other option. I could not select an option or
> continue because keyboard input did not work. I blew out the machine with
> compressed air. I tried to boot and it worked using my same keyboard.
> This has happened once or twice since but a power-down holding the power
> button down for >4 seconds and subsequent power-up has been successful.
> When this issue that was reported occured, I thought that I might have
> the same experience (boot choice) but did not. I really cannot tell you
> what happened because I've seen it only once and it seemed to repair itself.
>
> > Would it be possible for you to test the latest upstream kernel? Refer
> >to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> >v4.1 kernel[0].
>
> I'll check it out and try. As I said in the bug report, I'm
> comfortable as a user but am not a programmer.
> I am willing to make an effort and help.
>
> Thanks,
> Don Lesniakowski
>
> On Tue, Jun 9, 2015 at 12:34 PM, Joseph Salisbury <
> <email address hidden>> wrote:
>
>> 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.1 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.1-rc7-unstable/
>>
>> ** Changed in: linux (Ubuntu)
>> Importance: Undecided => Medium
>>
>> ** Changed in: linux (Ubuntu)
>> Status: Confirmed => Incomplete
>>
>> --
>> You received this bug ...

[Launchpad Janitor (janitor)]

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