[Dell Inc. Inspiron 1521] suspend/resume failure

Bug #1292627 reported by Yvon TANGUY
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

On resume, the computer shutdown brutally, before displaying something.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-17-generic 3.13.0-17.37
ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
Uname: Linux 3.13.0-17-generic x86_64
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: vono 1891 F.... pulseaudio
Date: Fri Mar 14 18:11:12 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=31d2ebdc-1a41-437f-a0a4-b28873898fc9
InstallationDate: Installed on 2014-02-03 (38 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140203)
InterpreterPath: /usr/bin/python3.4
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: Dell Inc. Inspiron 1521
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=752d0cec-2696-4b2f-8813-b503fa2de9fe ro quiet splash vt.handoff=7
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-17-generic N/A
 linux-backports-modules-3.13.0-17-generic N/A
 linux-firmware 1.126
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Title: [Dell Inc. Inspiron 1521] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 10/30/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0KY766
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA04:bd10/30/2007:svnDellInc.:pnInspiron1521:pvr:rvnDellInc.:rn0KY766:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1521
dmi.sys.vendor: Dell Inc.

Revision history for this message
Yvon TANGUY (vono22) 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.14 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.14-rc6-trusty/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Yvon TANGUY (vono22) wrote :

Hi,

After a few tests with the latest kernel (3.14.0-031400rc6-generic #201403100035 SMP Mon Mar 10 04:36:54 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux) it is far better, but not enough!

Basically, the resume work, but a kernel thread (kworker) is eating 100% of 1 CPU core.
Time to time, it stop working for, something like less than 1s. I was able to launch htop under an X terminal, to see that.
The time this worker thread work, is not constant, something between 10s to 2min. During this time X freeze completely, and all others programs with it. During the clean reboot ('sudo reboot" in my X terminal), it happend too. The events are still monitored during that time. Even if the screen was frozen, I could type on the keybord or move the mouse. Just have to wait the worker thread to let others programs to work a little.

I tried to look at the logs, but I didn't found any evidence which may permit me to better know what was going on.
The only error in /var/log/pm-suspend.log is:

Running hook /usr/lib/pm-utils/sleep.d/60_wpa_supplicant resume suspend:
Failed to connect to non-global ctrl_ifname: (null) error: No such file or directory
/usr/lib/pm-utils/sleep.d/60_wpa_supplicant resume suspend: success.

I don't know if it is related.

You may notice that I have an another bug on this laptop. I can't use the proprietary WiFi driver (which is installed by default). This driver (firmware ? crashed with an "invalid instruction" error. It seems to not be compatible with an "AMD Athlon(tm) 64 X2 Dual-Core Processor TK-55" (on GNU/Linux only, I tried Win8.1 on this laptop, the driver worked fine). That is why, I only use the ethernet connexion,with the FOSS driver. Again, I don't know if this information can help too.

I will retry with the stock kernel, maybe it's the same, I just didn't wait 2min before performing a halt/boot. There is no hardware reset on laptops :-(

Thank you.

Revision history for this message
Yvon TANGUY (vono22) wrote :

With the kernel 3.13, when I press the "power" button after the suspend, the computer simply shutdown.
So the problem is almost fixed upstream, but not completely.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
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[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

Once this bug is reported upstream, please add the tag: 'kernel-bug-reported-upstream'.

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

Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Yvon TANGUY (vono22) wrote :

For some reason, I no longer have this problem with kernel 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Changed in linux (Ubuntu):
status: Triaged → Invalid
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.