Regression: 3.2.x-kernels make my system resume immediately on suspend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Since I bought my computer [HP/Compaq Mini 311 netbook, nvidia Chipset and Intel Atom Processor] and with all 3.0- and 3.1- kernels ubuntu (always at the newest alpha, if available) delivered me my computer suspended as soon as I closed the lid or pressed the suspend button - and resumed on keypress.
The first update to a 3.2.x kernel broke suspend: The computer now turns off all lights at the end of the suspend process as always, then flashes them as if it is resuming and actually resumes.
Did try suspending with the -pae and the normal linux version with and without wireless drivers loaded and with both nvidia and noveau video driver. All combinations seem to be broken. But reverting to any 3.0- or 3.1- kernel still installed on my system allows me to suspend and resume normally again.
In very old bug reports it seems like the USB chipset could cause these problems years ago.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-
ProcVersionSign
Uname: Linux 3.2.0-4-generic-pae i686
NonfreeKernelMo
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.90-0ubuntu1
Architecture: i386
ArecordDevices:
Home directory /home/gunter not ours.
**** List of CAPTURE Hardware Devices ****
card 0: NVidia [HDA NVidia], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
Card hw:0 'NVidia'/'HDA NVidia at 0xd3100000 irq 20'
Mixer name : 'Nvidia MCP79/7A HDMI'
Components : 'HDA:111d7605,
Controls : 18
Simple ctrls : 10
Date: Mon Dec 12 21:56:42 2011
EcryptfsInUse: Yes
HibernationDevice: RESUME=
MachineType: Hewlett-Packard Compaq Mini 311-1000
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
LC_TIME=
ProcKernelCmdLine: BOOT_IMAGE=
PulseSinks:
Error: command ['pacmd', 'list-sinks'] failed with exit code 1: Home directory /home/gunter not ours.
No PulseAudio daemon running, or not running as session daemon.
PulseSources:
Error: command ['pacmd', 'list-sources'] failed with exit code 1: Home directory /home/gunter not ours.
No PulseAudio daemon running, or not running as session daemon.
RelatedPackageV
linux-
linux-
linux-firmware 1.62
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/26/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.16
dmi.board.
dmi.board.name: 3651
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 49.19
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: Compaq Mini 311-1000
dmi.product.
dmi.sys.vendor: Hewlett-Packard
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Changed in linux (Ubuntu): | |
status: | Confirmed → Triaged |
tags: | added: regression-release |
Changed in linux (Ubuntu): | |
status: | Incomplete → Fix Released |
Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . If possible, please test the latest v3.2-rcN kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs- upstream- testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs- upstream- testing' text.
If this bug is fixed by the mainline kernel, please add the following tag 'kernel- fixed-upstream- KERNEL- VERSION' . For example, if kernel version 3.2-rc1 fixed and issue, the tag would be: 'kernel- fixed-upstream- v3.2-rc1' .
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' . If you believe this bug does not require upstream testing, please add the tag: 'kernel- upstream- testing- not-needed' .
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".
Thanks in advance.