[Packard Bell BV Vega] suspend/resume failure [non-free: nvidia]

[Adam]

sleep mode doesn't work

ProblemType: KernelOops
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-16-generic 3.8.0-16.26
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
Uname: Linux 3.8.0-16-generic i686
NonfreeKernelModules: nvidia
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.9.2-0ubuntu5
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: moran 1851 F.... pulseaudio
 /dev/snd/controlC1: moran 1851 F.... pulseaudio
 /dev/snd/controlC0: moran 1851 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Fri Apr 5 17:12:18 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=14014583-edb4-455f-819a-a3523a3ba7d3
InstallationDate: Installed on 2013-04-03 (2 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130402.1)
InterpreterPath: /usr/bin/python3.3
IwConfig:
 lo no wireless extensions.

 virbr0 no wireless extensions.

 eth0 no wireless extensions.
MachineType: Packard Bell BV Vega
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-16-generic root=UUID=366911e2-10f6-492d-8c92-1191a20a07a0 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.8.0-16-generic N/A
 linux-backports-modules-3.8.0-16-generic N/A
 linux-firmware 1.104
RfKill:

SourcePackage: linux
Title: [Packard Bell BV Vega] suspend/resume failure [non-free: nvidia]
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 11/18/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS P5NSLI ACPI BIOS Revision 1801
dmi.board.name: P5NSLI
dmi.board.vendor: Packard Bell BV
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Packard Bell BV
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5NSLIACPIBIOSRevision1801:bd11/18/2008:svnPackardBellBV:pnVega:pvr1.XX:rvnPackardBellBV:rnP5NSLI:rvr1.XX:cvnPackardBellBV:ct3:cvrChassisVersion:
dmi.product.name: Vega
dmi.product.version: 1.XX
dmi.sys.vendor: Packard Bell BV

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

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]. You will need to 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-rc5-raring/

[Adam (l2velial)]

i update kernel to v3.9-rc6-raring, but the bug is not fixed

[Vladimir (volnes88)]

I have the same problem on ubuntu 12.04.2

[Brad Figg (brad-figg)]

There have been a number of kernel updates since the one you reported this
bug against. Please test again with the newer kernel and indicate in the
bug if you are still not able to suspend/resume.

You can update to the latest kernel by simply running the following commands in a terminal window:
    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the
bug no longer exists, change the bug status from Incomplete to Fix Released.

Thank you for your help, we really do appreciate it.

[penalvch (penalvch)]

Adam, could you please provide the full computer model as noted on the sticker?

[Adam (l2velial)]

I assembled this computer manually

[penalvch (penalvch)]

Adam, could you please provide the specific motherboard model as noted on the sticker of it?

[Adam (l2velial)]

http://i.imgur.com/nITnc4c.jpg
http://i.imgur.com/ZZtWxNT.jpg

[Adam (l2velial)]

this?

[penalvch (penalvch)]

Adam, thank you for providing the requested information. Did you swap the P5GPL-X motherboard in after you first reported this?

[Adam (l2velial)]

Sorry that's another motherboard. I dont have the box for a new motherboard.
http://i.imgur.com/EY7ikSt.jpg it can help you?

[penalvch (penalvch)]

Adam, so just to clarify, since you first reported this bug, did you swap out any of the hardware?

[Adam (l2velial)]

No

[penalvch (penalvch)]

Adam, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. 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:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc3

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. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

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.

[penalvch (penalvch)]

Adam, with the newest mainline kernel, could you please the information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[penalvch (penalvch)]

Adam, thank you for posting this requested information. Did this problem not occur in a release prior to Raring?

[Adam (l2velial)]

the problem was from ubuntu 12.04 (I really do not remember exactly)

[penalvch (penalvch)]

Adam, so just to clarify, it was reproducible in 12.04 onwards?

[Adam (l2velial)]

I do not remember exactly, but it seems to be yes

[penalvch (penalvch)]

Adam, for regression testing purposes, could you please test for this in Lucid via http://old-releases.ubuntu.com/releases/lucid/ ?

[Adam (l2velial)]

I'm sorry but I can check it after 10 days

[Launchpad Janitor (janitor)]

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