Lubuntu 13.04 fails to suspend

Bug #1173742 reported by Finog
38
This bug affects 8 people
Affects Status Importance Assigned to Milestone
pm-utils (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I type

    sudo pm-suspend

on the command line.

The screen goes black for about ten or fifteen seconds, the computer does not go into low-power mode, the screen comes back on.

Looking at dmesg shows:

[14196.989910] PM: Syncing filesystems ... done.
[14197.073199] Freezing user space processes ...
[14217.064138] Freezing of tasks failed after 20.01 seconds (1 tasks refusing to freeze, wq_busy=0):
[14217.064165] pci_devices D ffff88023bc53f40 0 1422 1385 0x00000004
[14217.064171] ffff8801570d5dd0 0000000000000086 ffff88022d600000 ffff8801570d5fd8
[14217.064176] ffff8801570d5fd8 ffff8801570d5fd8 ffff8802304d9740 ffff88022d600000
[14217.064181] ffff8802307b10f8 ffff88022d600000 ffff8802307b10fc 00000000ffffffff
[14217.064186] Call Trace:
[14217.064201] [<ffffffff816c9fd9>] schedule+0x29/0x70
[14217.064206] [<ffffffff816ca28e>] schedule_preempt_disabled+0xe/0x10
[14217.064211] [<ffffffff816c8de7>] __mutex_lock_slowpath+0xd7/0x150
[14217.064216] [<ffffffff816c88ba>] mutex_lock+0x2a/0x50
[14217.064225] [<ffffffff8145a893>] control_store+0x53/0xe0
[14217.064230] [<ffffffff81450df8>] dev_attr_store+0x18/0x30
[14217.064238] [<ffffffff812068fc>] sysfs_write_file+0xdc/0x150
[14217.064244] [<ffffffff811940cc>] vfs_write+0xac/0x180
[14217.064248] [<ffffffff81194412>] sys_write+0x52/0xa0
[14217.064255] [<ffffffff816d379d>] system_call_fastpath+0x1a/0x1f
[14217.064280]
[14217.064282] Restarting tasks ... done.
[14217.627873] video LNXVIDEO:00: Restoring backlight state

I am using Lubuntu 13.04 on a fresh install.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in pm-utils (Ubuntu):
status: New → Confirmed
Revision history for this message
Petr Kubánek (petr-kubanek) wrote :

After reboot, I got chmod as the process causing it (its parent was udevd, and there was ~25 udevd, which looks strange).

It works well on 3.5 kernel from 12.10 - this bug is probably kernel related.

Revision history for this message
Finog (finog) wrote :

Petr, how did you find which process was causing it? I'll check to see if its the same process on my machine.

Revision history for this message
Petr Kubánek (petr-kubanek) wrote :

Process is in dmesg (I and you had pci_devices before). It is now working on 3.8 from 13.04 up to suspend, but after resume it does not respond to mouse etc.. and needs to be rebooted. Works fine on 3.5 kernel.

Revision history for this message
Guillaume Millet (guimillet) wrote :

Same problem, same call trace, on Kubuntu 13.04 upgraded today from 12.10, on an Asus UL80VT laptop. It worked well before (on 12.10).

Revision history for this message
Guillaume Millet (guimillet) wrote :

For me, it is a consequence of bug #1169984 related to the HDMI audio driver which prevents pm-powersave to terminate, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1169984. You can check /var/log/pm-powersave.log. Before the workaround, my pm-powersave.log stopped at the nvidia hdmi audio device:

Running hook /usr/lib/pm-utils/power.d/pci_devices false:
Setting Host Bridge 0000:00:00.0 to on
Setting Audio device 0000:00:1b.0 to on
Setting Audio device 0000:01:00.1 to on

From https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1169984/comments/6, the workaround is to install latest upstream drivers according to https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS. It works for me.

Changed in pm-utils (Ubuntu):
status: Confirmed → Invalid
status: Invalid → Confirmed
Revision history for this message
Michał Semeniuk (s3m3n) wrote :

The same problem for me on my HP ProBook 4710s, after upgrading to 13.04.

[12465.397594] PM: Syncing filesystems ... done.
[12465.908373] Freezing user space processes ...
[12485.924249] Freezing of tasks failed after 20.01 seconds (1 tasks refusing to freeze, wq_busy=0):
[12485.924337] pci_devices D ffff88013fc93f40 0 1621 1588 0x00000004
[12485.924341] ffff880133c87dd0 0000000000000086 ffff880134778000 ffff880133c87fd8
[12485.924344] ffff880133c87fd8 ffff880133c87fd8 ffff880137001740 ffff880134778000
[12485.924347] ffff8801396580f8 ffff880134778000 ffff8801396580fc 00000000ffffffff
[12485.924350] Call Trace:
[12485.924359] [<ffffffff816c9fd9>] schedule+0x29/0x70
[12485.924362] [<ffffffff816ca28e>] schedule_preempt_disabled+0xe/0x10
[12485.924365] [<ffffffff816c8de7>] __mutex_lock_slowpath+0xd7/0x150
[12485.924368] [<ffffffff816c88ba>] mutex_lock+0x2a/0x50
[12485.924371] [<ffffffff8145a893>] control_store+0x53/0xe0
[12485.924375] [<ffffffff81450df8>] dev_attr_store+0x18/0x30
[12485.924379] [<ffffffff812068fc>] sysfs_write_file+0xdc/0x150
[12485.924382] [<ffffffff811940cc>] vfs_write+0xac/0x180
[12485.924385] [<ffffffff81194412>] sys_write+0x52/0xa0
[12485.924388] [<ffffffff816d379d>] system_call_fastpath+0x1a/0x1f
[12485.924453]
[12485.924454] Restarting tasks ... done.
[12485.937412] video LNXVIDEO:00: Restoring backlight state

Revision history for this message
Finog (finog) wrote :

I was going to try the workaround posted by Guillaume Millet (guimillet), but my machine successfully went into sleep mode. Therefore, at least for me, the problem is intermittent, which suggests that the particular process involved either does not start with the machine or is not always in a state where it prevents suspension.

Revision history for this message
Michał Semeniuk (s3m3n) wrote :

Solution of Guillaume Millet worked for me.

Revision history for this message
Stephen Langenhoven (stephen-langenhoven) wrote :

Solution also worked on my X220 thinkpad, cheers!

Revision history for this message
dulbirakan (iekanat) wrote :

The workaround did not work for me...

Revision history for this message
dulbirakan (iekanat) wrote :

The workaround may have worked after the restart. I do not have the problem any longer.

Revision history for this message
Guillaume Millet (guimillet) wrote :

Reboot is required because it's a problem with a driver, which fails when loaded and leaves the device in a bugged state, which eventually prevents suspension.

From bug #1169984: === Alternate workaround ===
IF you have no intention to use the HDMI audio, blacklisting the HDMI audio module will probably prevent this issue. The following commands should do it:
echo "blacklist snd-hda-codec-hdmi | sudo tee -a /etc/modprobe.d/blacklisthmdi.conf
sudo depmod -a
(Reboot)

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.