udisks-daemon prevents system from suspending or hibernating

Bug #810686 reported by Kamil Kaczmarczyk
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
udisks (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

If I try to suspend or hibernate my computer I can do it only once before restarting the system. The second time fails, leaving the following message in /var/log/syslog, which makes me blame udisks-daemon:

Jul 14 19:24:02 laptop kernel: [26240.298517] PM: Preparing system for mem sleep
Jul 14 19:24:22 laptop kernel: [26240.552426] Freezing user space processes ...
Jul 14 19:24:22 laptop kernel: [26260.568035] Freezing of tasks failed after 20.01 seconds (1 tasks refusing to freeze, wq_busy=0):
Jul 14 19:24:22 laptop kernel: [26260.568147] udisks-daemon D 810af5cb 0 1299 1295 0x00800004
Jul 14 19:24:22 laptop kernel: [26260.568153] ece97c48 00000086 f7006920 810af5cb 000017d0 0001a829 ece9828c c183a8c0
Jul 14 19:24:22 laptop kernel: [26260.568160] 80fbf20b 000017d0 ece98288 c183a8c0 c183a8c0 f70068c0 ece98000 f3079940
Jul 14 19:24:22 laptop kernel: [26260.568167] 00000001 4cd27560 ece84a00 00000000 ece97c98 c1507bfd 000772d6 f133d2b4
Jul 14 19:24:22 laptop kernel: [26260.568175] Call Trace:
Jul 14 19:24:22 laptop kernel: [26260.568188] [<c1507bfd>] ? schedule+0x3ad/0x740
Jul 14 19:24:22 laptop kernel: [26260.568192] [<c15085cd>] schedule_timeout+0x1ed/0x260
Jul 14 19:24:22 laptop kernel: [26260.568198] [<c10385c2>] ? check_preempt_curr+0x72/0x90
Jul 14 19:24:22 laptop kernel: [26260.568203] [<c1049f53>] ? try_to_wake_up+0x223/0x3c0
Jul 14 19:24:22 laptop kernel: [26260.568207] [<c1508150>] wait_for_common+0xa0/0x130
Jul 14 19:24:22 laptop kernel: [26260.568211] [<c104a124>] ? wake_up_process+0x14/0x20
Jul 14 19:24:22 laptop kernel: [26260.568214] [<c104a0f0>] ? default_wake_function+0x0/0x20
Jul 14 19:24:22 laptop kernel: [26260.568218] [<c15082b7>] wait_for_completion+0x17/0x20
Jul 14 19:24:22 laptop kernel: [26260.568224] [<c1068100>] flush_work+0x30/0x40
Jul 14 19:24:22 laptop kernel: [26260.568228] [<c10666d0>] ? wq_barrier_func+0x0/0x20
Jul 14 19:24:22 laptop kernel: [26260.568231] [<c10697eb>] flush_delayed_work+0x3b/0x40
Jul 14 19:24:22 laptop kernel: [26260.568236] [<c12653a5>] disk_clear_events+0x75/0x120
Jul 14 19:24:22 laptop kernel: [26260.568241] [<c1153b7d>] check_disk_change+0x2d/0x70
Jul 14 19:24:22 laptop kernel: [26260.568246] [<c139cb80>] cdrom_open+0x30/0x1c0
Jul 14 19:24:22 laptop kernel: [26260.568251] [<c1273012>] ? kobject_get+0x12/0x20
Jul 14 19:24:22 laptop kernel: [26260.568255] [<c1263b78>] ? get_disk+0x48/0xa0
Jul 14 19:24:22 laptop kernel: [26260.568259] [<c1273012>] ? kobject_get+0x12/0x20
Jul 14 19:24:22 laptop kernel: [26260.568264] [<c1330c08>] ? get_device+0x18/0x20
Jul 14 19:24:22 laptop kernel: [26260.568269] [<c1351b23>] ? scsi_device_get+0x43/0xa0
Jul 14 19:24:22 laptop kernel: [26260.568274] [<c1367fa7>] sr_block_open+0x67/0xb0
Jul 14 19:24:22 laptop kernel: [26260.568278] [<c1154e3e>] __blkdev_get+0x8e/0x330
Jul 14 19:24:22 laptop kernel: [26260.568281] [<c11551cf>] blkdev_get+0xef/0x230
Jul 14 19:24:22 laptop kernel: [26260.568285] [<c1155368>] blkdev_open+0x58/0x70
Jul 14 19:24:22 laptop kernel: [26260.568289] [<c1125361>] __dentry_open+0xc1/0x280
Jul 14 19:24:22 laptop kernel: [26260.568292] [<c11266ce>] nameidata_to_filp+0x6e/0x80
Jul 14 19:24:22 laptop kernel: [26260.568296] [<c1155310>] ? blkdev_open+0x0/0x70
Jul 14 19:24:22 laptop kernel: [26260.568300] [<c1133b7f>] finish_open+0xaf/0x1a0
Jul 14 19:24:22 laptop kernel: [26260.568303] [<c1133428>] ? do_path_lookup+0x68/0x120
Jul 14 19:24:22 laptop kernel: [26260.568307] [<c11341c7>] do_filp_open+0x207/0x6e0
Jul 14 19:24:22 laptop kernel: [26260.568311] [<c1351ad7>] ? scsi_device_put+0x47/0x50
Jul 14 19:24:22 laptop kernel: [26260.568327] [<c1002a31>] ? do_signal+0x61/0x120
Jul 14 19:24:22 laptop kernel: [26260.568332] [<c113fee9>] ? vfsmount_lock_local_unlock+0x19/0x20
Jul 14 19:24:22 laptop kernel: [26260.568336] [<c1126736>] do_sys_open+0x56/0x120
Jul 14 19:24:22 laptop kernel: [26260.568339] [<c112682e>] sys_open+0x2e/0x40
Jul 14 19:24:22 laptop kernel: [26260.568343] [<c150a194>] syscall_call+0x7/0xb
Jul 14 19:24:22 laptop kernel: [26260.568347] [<c1500000>] ? detect_ht+0x14f/0x16d
Jul 14 19:24:22 laptop kernel: [26260.568425]
Jul 14 19:24:22 laptop rtkit-daemon[1256]: The canary thread is apparently starving. Taking action.
Jul 14 19:24:22 laptop rtkit-daemon[1256]: Demoting known real-time threads.
Jul 14 19:24:22 laptop rtkit-daemon[1256]: Successfully demoted thread 1956 of process 1954 (n/a).
Jul 14 19:24:22 laptop rtkit-daemon[1256]: Successfully demoted thread 1955 of process 1954 (n/a).
Jul 14 19:24:22 laptop rtkit-daemon[1256]: Successfully demoted thread 1954 of process 1954 (n/a).
Jul 14 19:24:22 laptop rtkit-daemon[1256]: Demoted 3 threads.
Jul 14 19:24:22 laptop kernel: [26260.568426] Restarting tasks ... done.
Jul 14 19:24:22 laptop acpid: client 2110[0:0] has disconnected
Jul 14 19:24:22 laptop acpid: client connected from 2110[0:0]
Jul 14 19:24:22 laptop acpid: 1 client rule loaded
Jul 14 19:24:22 laptop kernel: [26260.588395] video LNXVIDEO:00: Restoring backlight state

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: udisks 1.0.2-4ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic i686
Architecture: i386
CustomUdevRuleFiles: 45-libnjb5.rules
Date: Thu Jul 14 20:52:14 2011
MachineType: ASUSTeK Computer Inc. F5SR
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-10-generic root=UUID=69b7086b-bc5c-4c79-8aba-61dde1c4e13a ro quiet splash vt.handoff=7
SourcePackage: udisks
UdevDb: Error: [Errno 2] No such file or directory
UpgradeStatus: Upgraded to natty on 2011-05-01 (74 days ago)
dmi.bios.date: 08/14/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 203
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: F5SR
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr203:bd08/14/2008:svnASUSTeKComputerInc.:pnF5SR:pvr1.0:rvnPEGATRONCORPORATION:rnF5SR:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
dmi.product.name: F5SR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

Revision history for this message
Kamil Kaczmarczyk (kamkacz) wrote :
Revision history for this message
Kamil Kaczmarczyk (kamkacz) wrote :
Download full text (4.2 KiB)

Extra info, because it may be connected - a few minutes after waking the system up from the successful suspension, info "task udisks-daemon:1305 blocked for more than 120 seconds" is logged. The message repeats every few (5, more less) minutes. It does not appear before suspending the system.

An example fragment of /var/log/syslog (the system was resumed from sleep at 15:52:50):

Jul 15 15:56:42 laptop kernel: [ 7320.372044] INFO: task udisks-daemon:1305 blocked for more than 120 seconds.
Jul 15 15:56:42 laptop kernel: [ 7320.372049] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jul 15 15:56:42 laptop kernel: [ 7320.372052] udisks-daemon D 5ce0fba5 0 1305 1304 0x00000000
Jul 15 15:56:42 laptop kernel: [ 7320.372057] eca29c48 00000086 00000672 5ce0fba5 00000672 edbd71d4 eca1ce4c c183a8c0
Jul 15 15:56:42 laptop kernel: [ 7320.372064] 5d145a23 00000672 eca1ce48 c183a8c0 c183a8c0 f70068c0 eca1cbc0 f2ac3280
Jul 15 15:56:42 laptop kernel: [ 7320.372071] eca1cbc0 eca29c24 c1001ed1 00000000 00000000 eca1cebc 00000000 eca29c2c
Jul 15 15:56:42 laptop kernel: [ 7320.372079] Call Trace:
Jul 15 15:56:42 laptop kernel: [ 7320.372090] [<c1001ed1>] ? __switch_to+0xe1/0x190
Jul 15 15:56:42 laptop kernel: [ 7320.372096] [<c103f9f9>] ? finish_task_switch+0x39/0xc0
Jul 15 15:56:42 laptop kernel: [ 7320.372102] [<c1507bfd>] ? schedule+0x3ad/0x740
Jul 15 15:56:42 laptop kernel: [ 7320.372106] [<c1038502>] ? resched_task+0x22/0x70
Jul 15 15:56:42 laptop kernel: [ 7320.372109] [<c15085cd>] schedule_timeout+0x1ed/0x260
Jul 15 15:56:42 laptop kernel: [ 7320.372114] [<c1049f53>] ? try_to_wake_up+0x223/0x3c0
Jul 15 15:56:42 laptop kernel: [ 7320.372117] [<c1508150>] wait_for_common+0xa0/0x130
Jul 15 15:56:42 laptop kernel: [ 7320.372121] [<c104a0f0>] ? default_wake_function+0x0/0x20
Jul 15 15:56:42 laptop kernel: [ 7320.372125] [<c15082b7>] wait_for_completion+0x17/0x20
Jul 15 15:56:42 laptop kernel: [ 7320.372130] [<c1068100>] flush_work+0x30/0x40
Jul 15 15:56:42 laptop kernel: [ 7320.372133] [<c10666d0>] ? wq_barrier_func+0x0/0x20
Jul 15 15:56:42 laptop kernel: [ 7320.372137] [<c10697eb>] flush_delayed_work+0x3b/0x40
Jul 15 15:56:42 laptop kernel: [ 7320.372141] [<c12653a5>] disk_clear_events+0x75/0x120
Jul 15 15:56:42 laptop kernel: [ 7320.372146] [<c1153b7d>] check_disk_change+0x2d/0x70
Jul 15 15:56:42 laptop kernel: [ 7320.372151] [<c139cb80>] cdrom_open+0x30/0x1c0
Jul 15 15:56:42 laptop kernel: [ 7320.372155] [<c1273012>] ? kobject_get+0x12/0x20
Jul 15 15:56:42 laptop kernel: [ 7320.372159] [<c1263b78>] ? get_disk+0x48/0xa0
Jul 15 15:56:42 laptop kernel: [ 7320.372163] [<c1273012>] ? kobject_get+0x12/0x20
Jul 15 15:56:42 laptop kernel: [ 7320.372167] [<c1330c08>] ? get_device+0x18/0x20
Jul 15 15:56:42 laptop kernel: [ 7320.372171] [<c1351b23>] ? scsi_device_get+0x43/0xa0
Jul 15 15:56:42 laptop kernel: [ 7320.372176] [<c1367fa7>] sr_block_open+0x67/0xb0
Jul 15 15:56:42 laptop kernel: [ 7320.372180] [<c1154e3e>] __blkdev_get+0x8e/0x330
Jul 15 15:56:42 laptop kernel: [ 7320.372183] [<c11551cf>] blkdev_get+0xef/0x230
Jul 15 15:56:42 laptop kernel: [ 7320.372186] [<c1155368>] blkdev_open+0x58/0x70
Jul 15...

Read more...

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

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

Changed in udisks (Ubuntu):
status: New → Confirmed
Revision history for this message
Kamil Kaczmarczyk (kamkacz) wrote :

The problem persists on a fresh Ubuntu 11.10 installation.

Revision history for this message
Russ Dill (russ-dill) wrote :

I'm getting this on precise, but the backtrace shows a USB mass storage device, including scsci_set_medium_removal.

Revision history for this message
merlin (merlin-re-cycle) wrote :

I have the same problem
11.10
Not let me suspend by closing lid of Aspire, or by asking it to suspend
When ask it to hybernate, get black screen with white writing, key bit of which seems to be ""task udisks-daemon" which brought me to this page

Also, poss connected:
When leave laptop for a few minutes, screen goes very dark, have to press function screen brighter to see anything again

Please advise :)

Many thanks

Merlin

Revision history for this message
merlin (merlin-re-cycle) wrote :

Ah, and when close lid, later open it and goes to the logon, from boot up, screen - ie crashes
Think this is just from 11.10
Home folder window crashes quite a lot

Revision history for this message
merlin (merlin-re-cycle) wrote :

This fix works

http://thecodecentral.com/2011/01/18/fix-ubuntu-10-10-suspendhibernate-not-working-bug

Did crash the first time i ran it, seems good now

Revision history for this message
merlin (merlin-re-cycle) wrote :

Hmmm, turns out I was a bit hasty...

Sometimes:
- ok
- see screen was on, then black screen with writing, then log on page

Any ideas?

Thanks

Merlin

While I'm here, I set up a charity shipping old bicycles to Africa - www.re-cycle.org

Revision history for this message
merlin (merlin-re-cycle) wrote :

When I open the screen from suspend, get back screen saying

"could not write bytes: broken pipe"
and some other bits

Revision history for this message
Kamil Kaczmarczyk (kamkacz) wrote :

The fault probably lies with the driver of the DVD drive.

In the attachment there's a log made when waking from the first, successful suspension. Apparently at least one device doesn't wake up properly and it is connected by ATA, so it suggests the DVD. Indeed, after the suspension I can't read anything from any disk, even though I could have before. "cat /dev/cdrom/", instead of flooding the terminal, simply hangs up, not reacting even to ctrl-c.

My old friend ksoftirqd/1 also starts eating lots of the CPU power after the wake-up, which, reportedly, is somehow related to the interrupts and device drivers.

Windows Vista running on the same machine doesn't have such problems, so I don't think it's a hardware issue.

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.