Regression: 3.2.x-kernels make my system resume immediately on suspend

Bug #903399 reported by PeterPall
30
This bug affects 5 people
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-generic-pae 3.2.0.4.4
ProcVersionSignature: Ubuntu 3.2.0-4.10-generic-pae 3.2.0-rc5
Uname: Linux 3.2.0-4-generic-pae i686
NonfreeKernelModules: wl
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/controlC0: gunter 3159 F.... pulseaudio
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,103c3651,00100402 HDA:10de0007,10de0101,00100100'
   Controls : 18
   Simple ctrls : 10
Date: Mon Dec 12 21:56:42 2011
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=4e9ffcc5-917f-4d76-8fb2-3cd55b1e7186
MachineType: Hewlett-Packard Compaq Mini 311-1000
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LC_TIME=de_DE.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-generic-pae root=UUID=0fe5168a-a771-4519-989f-ef7913db3e38 ro quiet splash noatime resume=/dev/sda2 nouveau.perflvl_wr=7777 i8042.noloop=1 security=selinux selinux=1
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.
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-4-generic-pae N/A
 linux-backports-modules-3.2.0-4-generic-pae N/A
 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.asset.tag: Base Board Asset Tag
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.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.16:bd11/26/2010:svnHewlett-Packard:pnCompaqMini311-1000:pvr0395100000001C00000300000:rvnHewlett-Packard:rn3651:rvr49.19:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.name: Compaq Mini 311-1000
dmi.product.version: 0395100000001C00000300000
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
PeterPall (peterpall) wrote :
Revision history for this message
PeterPall (peterpall) wrote :
Revision history for this message
PeterPall (peterpall) wrote :
description: updated
Brad Figg (brad-figg)
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? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . 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.

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing
tags: added: kernel-da-key
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
PeterPall (peterpall) wrote :

Did test the upstream rc kernel. The Bug does still exist there.

tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
status: Confirmed → Triaged
tags: added: regression-release
Revision history for this message
e X t 7 3 (ext73) wrote :

You can find this bug still in linux-3.2.1 ... I have made a test on MSI X370 (mine kernel build). On this machine kernels from 3.0.x and 3.1.x to 3.1.10 work without this problem.

Revision history for this message
PeterPall (peterpall) wrote :

Tested linux-image-3.3.0-030300rc1-generic-pae and linux-image-3.2.0-11-generic-pae. The problem is still there.

Revision history for this message
Brad Figg (brad-figg) wrote :

@PeterPall,

Have you tried a recent kernel to see if this issue still exists? If it does, please return the status of this bug to "Triaged".

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Sam Van den Eynde (samvde) wrote :

Same problem using the same hp 311 model netbook with kernel 3.2.0-24-generic-pae. No experience in using experimental kernels.

Revision history for this message
Sam Van den Eynde (samvde) wrote :

I can confirm the problem is triggered by the bluetooth/wireless combo card in my system. When I disable the card using a hardware switch prior to suspend, it works fine.

Details:

03:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
 Subsystem: Hewlett-Packard Company Device 365e
 Flags: bus master, fast devsel, latency 0, IRQ 16
 Memory at 93000000 (64-bit, non-prefetchable) [size=16K]
 Capabilities: <access denied>
 Kernel driver in use: wl
 Kernel modules: wl, ssb

Best regards

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Chris Elsworth (chris-shagged) wrote :

Would like to add that I see this issue and it's also down to my USB bluetooth dongle.

With the dongle plugged in, it immediately resumes. With it unplugged, it works fine. I alternated several times and observed consistent behaviour.

Model is:
Bus 004 Device 003: ID 050d:0081 Belkin Components F8T001v2 Bluetooth

If a lsusb -v or other info would help I'll happily provide it.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
truant (launchpad-ninj4) wrote :

OK, I think I have this bug although there are several similar bug reports here and there, also I'm on an AMD64 kernel. Turning on/off bluetooth has no effect for me. Toshiba Satellite L830-114.

Latest mainline kernel build - 3.5.rc7-quantal - does not resolve it, but the daily build (as of 28 july) does. I can suspend/resume on demand. Yay!

uname -a
Linux izumi 3.5.0-999-generic #201207280406 SMP Sat Jul 28 08:07:29 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Because of arch difference I'm not updating tags/status of this bug, but leave this comment in case it's of use to anyone.

Revision history for this message
penalvch (penalvch) wrote :

PeterPall, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

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

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

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.

tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
PeterPall (peterpall) wrote : Re: [Bug 903399] Re: Regression: 3.2.x-kernels make my system resume immediately on suspend

Hello, Christopher,

Did completely forget about this bug report.

Kind regards,

   Gunter.

"Christopher M. Penalver" <email address hidden> schrieb:
>PeterPall, this bug was reported a while ago and there hasn't been any
>activity in it recently. We were wondering if this is still an issue?
>If
>so, could you please test for this with the latest development release
>of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
>/daily-live/current/ .
>
>If it remains an issue, could you please run the following command in
>the development release from a Terminal
>(Applications->Accessories->Terminal), as it will automatically gather
>and attach updated debug information to this report:
>
>apport-collect -p linux <replace-with-bug-number>
>
>Also, could you please test the latest upstream kernel available (not
>the daily folder, but the one all the way at the bottom) following
>https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional
>upstream developers to examine 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:
>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.12
>
>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
>
>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.
>
>
>** Tags added: needs-upstream-testing
>
>** Changed in: linux (Ubuntu)
> Status: Triaged => Incomplete
>
>--
>You received this bug notification because you are subscribed to the
>bug
>report.
>https://bugs.launchpad.net/bugs/903399
>
>Title:
> Regression: 3.2.x-kernels make my system resume immediately on suspend
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/ubuntu/+source/linux/+bug/903399/+subscriptions

--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

PeterPall (peterpall)
Changed in linux (Ubuntu):
status: Incomplete → Fix Released
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.