[ASUSTeK COMPUTER INC. K55VM] suspend/resume failure

Bug #1228495 reported by Amit Sedai
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Mouse started flickering after reboot and continued to flicker.

ProblemType: KernelOops
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-4-generic 3.8.0-4.8
ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
Uname: Linux 3.8.0-4-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: sankalp 3684 F.... pulseaudio
 /dev/snd/pcmC0D0p: sankalp 3684 F...m pulseaudio
Date: Mon Sep 16 22:53:46 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=7a890c5d-1515-462b-95dc-5d2140b0c509
InstallationDate: Installed on 2013-03-07 (197 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
InterpreterPath: /usr/bin/python3.3
MachineType: ASUSTeK COMPUTER INC. K55VM
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-4-generic root=UUID=7095bd25-6b9e-4a72-abc0-3692cbed727c ro recovery nomodeset
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-4-generic N/A
 linux-backports-modules-3.8.0-4-generic N/A
 linux-firmware 1.100
SourcePackage: linux
Title: [ASUSTeK COMPUTER INC. K55VM] suspend/resume failure
UpgradeStatus: Upgraded to raring on 2013-04-26 (147 days ago)
UserGroups:

dmi.bios.date: 03/13/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K55VM.202
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K55VM
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK55VM.202:bd03/13/2012:svnASUSTeKCOMPUTERINC.:pnK55VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: K55VM
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

Revision history for this message
Amit Sedai (amitsedaiz) 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.12 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/v3.12-rc1-saucy/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Amit Sedai (amitsedaiz) wrote : Re: [Bug 1228495] Re: [ASUSTeK COMPUTER INC. K55VM] suspend/resume failure
Download full text (4.5 KiB)

Hi Joseph,

The mouse flickering is not a consistent issue and after reboot has not
appeared. However, I have just installed the kernel:
linux-image-3.12.0-031200rc1-generic_3.12.0-031200rc1.201309161735_amd64.deb<http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc1-saucy/linux-image-3.12.0-031200rc1-generic_3.12.0-031200rc1.201309161735_amd64.deb>.
I will update if any issue persists after restart in next few days.

I am facing one more issue. Since few months, I have not been receiving any
updates from Ubuntu except for Google chrome for which a separate
repository exists. Is this normal or should I change any configuration.
Thanks.

On Mon, Sep 23, 2013 at 10:30 PM, Joseph Salisbury <
<email address hidden>> 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.12 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/v3.12-rc1-saucy/
>
>
> ** 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/1228495
>
> Title:
> [ASUSTeK COMPUTER INC. K55VM] suspend/resume failure
>
> Status in “linux” package in Ubuntu:
> Incomplete
>
> Bug description:
> Mouse started flickering after reboot and continued to flicker.
>
> ProblemType: KernelOops
> DistroRelease: Ubuntu 13.04
> Package: linux-image-3.8.0-4-generic 3.8.0-4.8
> ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
> Uname: Linux 3.8.0-4-generic x86_64
> Annotation: This occured during a previous suspend and prevented it from
> resuming properly.
> ApportVersion: 2.8-0ubuntu4
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: sankalp 3684 F.... pulseaudio
> /dev/snd/pcmC0D0p: sankalp 3684 F...m pulseaudio
> Date: Mon Sep 16 22:53:46 2013
> ExecutablePath: /usr/share/apport/apportcheckresume
> Failure: suspend/resume
> HibernationDevice: RESUME=UUID=7a890c5d-1515-462b-95dc-5d2140b0c509
> InstallationDate: Installed on 2013-03-07 (197 days ago)
> InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64
> (20121017.5)
> InterpreterPath: /usr/bin/python3.3
> MachineType: ASUSTeK COMPUTER INC. K55VM
> MarkForUpload: True
> ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
> ProcEnviron:
> TERM=linux
> PATH=(custom, no user)
> ProcFB: 0 EFI VGA
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-4-generic
> root=UUID=7095bd25-6b9e-4a72-abc0-3692cbed727c ro recover...

Read more...

Revision history for this message
Amit Sedai (amitsedaiz) wrote :
Download full text (4.9 KiB)

Hi Joseph,

The mouse flicker issue still persists in the new linux image.

On Tue, Sep 24, 2013 at 4:12 PM, Amit Sedai <email address hidden> wrote:

> Hi Joseph,
>
> The mouse flickering is not a consistent issue and after reboot has not
> appeared. However, I have just installed the kernel:
> linux-image-3.12.0-031200rc1-generic_3.12.0-031200rc1.201309161735_amd64.deb<http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc1-saucy/linux-image-3.12.0-031200rc1-generic_3.12.0-031200rc1.201309161735_amd64.deb>.
> I will update if any issue persists after restart in next few days.
>
> I am facing one more issue. Since few months, I have not been receiving
> any updates from Ubuntu except for Google chrome for which a separate
> repository exists. Is this normal or should I change any configuration.
> Thanks.
>
>
> On Mon, Sep 23, 2013 at 10:30 PM, Joseph Salisbury <
> <email address hidden>> 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.12 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/v3.12-rc1-saucy/
>>
>>
>> ** 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/1228495
>>
>> Title:
>> [ASUSTeK COMPUTER INC. K55VM] suspend/resume failure
>>
>> Status in “linux” package in Ubuntu:
>> Incomplete
>>
>> Bug description:
>> Mouse started flickering after reboot and continued to flicker.
>>
>> ProblemType: KernelOops
>> DistroRelease: Ubuntu 13.04
>> Package: linux-image-3.8.0-4-generic 3.8.0-4.8
>> ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
>> Uname: Linux 3.8.0-4-generic x86_64
>> Annotation: This occured during a previous suspend and prevented it
>> from resuming properly.
>> ApportVersion: 2.8-0ubuntu4
>> Architecture: amd64
>> AudioDevicesInUse:
>> USER PID ACCESS COMMAND
>> /dev/snd/controlC0: sankalp 3684 F.... pulseaudio
>> /dev/snd/pcmC0D0p: sankalp 3684 F...m pulseaudio
>> Date: Mon Sep 16 22:53:46 2013
>> ExecutablePath: /usr/share/apport/apportcheckresume
>> Failure: suspend/resume
>> HibernationDevice: RESUME=UUID=7a890c5d-1515-462b-95dc-5d2140b0c509
>> InstallationDate: Installed on 2013-03-07 (197 days ago)
>> InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64
>> (20121017.5)
>> InterpreterPath: /usr/bin/python3.3
>> MachineType: ASUSTeK COMPUTER INC. K55VM
>> MarkForUpload: True
>> ProcCmdline: /usr/bin/python...

Read more...

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.