Freezing of tasks failed while trying to suspend

Bug #1400587 reported by Dima Ryazanov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I closed my laptop's lid and unplugged some USB devices while it was suspending. Apparently, Linux failed to suspend - possibly because of USB:

Dec 8 20:24:45 dima-xps kernel: [21918.824398] hub 3-1:1.0: cannot disable port 1 (err = -110)
Dec 8 20:24:46 dima-xps kernel: [21919.168721] PM: Syncing filesystems ... done.
Dec 8 20:24:46 dima-xps kernel: [21919.198809] PM: Preparing system for mem sleep
Dec 8 20:25:06 dima-xps kernel: [21919.823745] hub 3-1:1.0: cannot reset port 1 (err = -110)
Dec 8 20:25:06 dima-xps kernel: [21920.823115] hub 3-1:1.0: cannot reset port 1 (err = -110)
Dec 8 20:25:06 dima-xps kernel: [21921.822391] hub 3-1:1.0: cannot reset port 1 (err = -110)
Dec 8 20:25:06 dima-xps kernel: [21922.821851] hub 3-1:1.0: cannot reset port 1 (err = -110)
Dec 8 20:25:06 dima-xps kernel: [21923.821087] hub 3-1:1.0: cannot reset port 1 (err = -110)
Dec 8 20:25:06 dima-xps kernel: [21923.821092] hub 3-1:1.0: Cannot enable port 1. Maybe the USB cable is bad?
Dec 8 20:25:06 dima-xps kernel: [21924.820392] hub 3-1:1.0: cannot disable port 1 (err = -110)
Dec 8 20:25:06 dima-xps kernel: [21925.819663] hub 3-1:1.0: cannot reset port 1 (err = -110)
Dec 8 20:25:06 dima-xps kernel: [21926.818820] hub 3-1:1.0: cannot reset port 1 (err = -110)
Dec 8 20:25:06 dima-xps kernel: [21927.818350] hub 3-1:1.0: cannot reset port 1 (err = -110)
Dec 8 20:25:06 dima-xps kernel: [21928.817637] hub 3-1:1.0: cannot reset port 1 (err = -110)
Dec 8 20:25:06 dima-xps kernel: [21929.816868] hub 3-1:1.0: cannot reset port 1 (err = -110)
Dec 8 20:25:06 dima-xps kernel: [21929.816873] hub 3-1:1.0: Cannot enable port 1. Maybe the USB cable is bad?
Dec 8 20:25:06 dima-xps kernel: [21930.816139] hub 3-1:1.0: cannot disable port 1 (err = -110)
Dec 8 20:25:06 dima-xps kernel: [21931.815469] hub 3-1:1.0: cannot reset port 1 (err = -110)
Dec 8 20:25:06 dima-xps kernel: [21932.814873] hub 3-1:1.0: cannot reset port 1 (err = -110)
Dec 8 20:25:06 dima-xps kernel: [21933.813968] hub 3-1:1.0: cannot reset port 1 (err = -110)
Dec 8 20:25:06 dima-xps kernel: [21934.813304] hub 3-1:1.0: cannot reset port 1 (err = -110)
Dec 8 20:25:06 dima-xps kernel: [21935.812587] hub 3-1:1.0: cannot reset port 1 (err = -110)
Dec 8 20:25:06 dima-xps kernel: [21935.812592] hub 3-1:1.0: Cannot enable port 1. Maybe the USB cable is bad?
Dec 8 20:25:06 dima-xps kernel: [21936.811935] hub 3-1:1.0: cannot disable port 1 (err = -110)
Dec 8 20:25:06 dima-xps kernel: [21936.811975] hub 3-1:1.0: unable to enumerate USB device on port 1
Dec 8 20:25:06 dima-xps kernel: [21937.811067] hub 3-1:1.0: cannot disable port 1 (err = -110)
Dec 8 20:25:06 dima-xps kernel: [21919.211316] Freezing user space processes ...
Dec 8 20:25:06 dima-xps kernel: [21939.203207] Freezing of tasks failed after 20.006 seconds (2 tasks refusing to freeze, wq_busy=0):
Dec 8 20:25:06 dima-xps kernel: [21939.203298] adb D ffff88011fa14440 0 6143 2249 0x00000004
Dec 8 20:25:06 dima-xps kernel: [21939.203303] ffff88008724dba0 0000000000000002 ffff88011536c7d0 ffff88008724dfd8
Dec 8 20:25:06 dima-xps kernel: [21939.203307] 0000000000014440 0000000000014440 ffff88011536c7d0 ffff8800a28100e8
Dec 8 20:25:06 dima-xps kernel: [21939.203310] ffff8800a28100ec ffff88011536c7d0 00000000ffffffff ffff8800a28100f0
Dec 8 20:25:06 dima-xps kernel: [21939.203313] Call Trace:
Dec 8 20:25:06 dima-xps kernel: [21939.203322] [<ffffffff8171ec69>] schedule_preempt_disabled+0x29/0x70
Dec 8 20:25:06 dima-xps kernel: [21939.203326] [<ffffffff81720ad5>] __mutex_lock_slowpath+0x135/0x1b0
Dec 8 20:25:06 dima-xps kernel: [21939.203331] [<ffffffff817082a8>] ? klist_iter_exit+0x18/0x30
Dec 8 20:25:06 dima-xps kernel: [21939.203335] [<ffffffff81720b6f>] mutex_lock+0x1f/0x2f
Dec 8 20:25:06 dima-xps kernel: [21939.203339] [<ffffffff8154a5a0>] usbdev_open+0xd0/0x230
Dec 8 20:25:06 dima-xps kernel: [21939.203343] [<ffffffff811c11ff>] chrdev_open+0x9f/0x1d0
Dec 8 20:25:06 dima-xps kernel: [21939.203346] [<ffffffff811b9d43>] do_dentry_open+0x233/0x2e0
Dec 8 20:25:06 dima-xps kernel: [21939.203349] [<ffffffff811c1160>] ? cdev_put+0x30/0x30
Dec 8 20:25:06 dima-xps kernel: [21939.203351] [<ffffffff811ba079>] vfs_open+0x49/0x50
Dec 8 20:25:06 dima-xps kernel: [21939.203355] [<ffffffff811c9fa1>] do_last+0x561/0x1200
Dec 8 20:25:06 dima-xps kernel: [21939.203361] [<ffffffff8131175b>] ? apparmor_file_alloc_security+0x5b/0x180
Dec 8 20:25:06 dima-xps kernel: [21939.203365] [<ffffffff811cc0bb>] path_openat+0xbb/0x620
Dec 8 20:25:06 dima-xps kernel: [21939.203369] [<ffffffff8149de68>] ? rpm_suspend+0x1a8/0x6e0
Dec 8 20:25:06 dima-xps kernel: [21939.203372] [<ffffffff811cd47a>] do_filp_open+0x3a/0x90
Dec 8 20:25:06 dima-xps kernel: [21939.203376] [<ffffffff811da237>] ? __alloc_fd+0xa7/0x130
Dec 8 20:25:06 dima-xps kernel: [21939.203379] [<ffffffff811bbb99>] do_sys_open+0x129/0x280
Dec 8 20:25:06 dima-xps kernel: [21939.203384] [<ffffffff81020d45>] ? syscall_trace_enter+0x145/0x250
Dec 8 20:25:06 dima-xps kernel: [21939.203387] [<ffffffff811bbd0e>] SyS_open+0x1e/0x20
Dec 8 20:25:06 dima-xps kernel: [21939.203392] [<ffffffff8172aeff>] tracesys+0xe1/0xe6
Dec 8 20:25:06 dima-xps kernel: [21939.203412] colord-sane D ffff88011fad4440 0 8586 2574 0x00000004
Dec 8 20:25:06 dima-xps kernel: [21939.203415] ffff8800a6febdd0 0000000000000002 ffff88000e4eafe0 ffff8800a6febfd8
Dec 8 20:25:06 dima-xps kernel: [21939.203418] 0000000000014440 0000000000014440 ffff88000e4eafe0 ffff8800a28100e8
Dec 8 20:25:06 dima-xps kernel: [21939.203421] ffff8800a28100ec ffff88000e4eafe0 00000000ffffffff ffff8800a28100f0
Dec 8 20:25:06 dima-xps kernel: [21939.203424] Call Trace:
Dec 8 20:25:06 dima-xps kernel: [21939.203428] [<ffffffff8171ec69>] schedule_preempt_disabled+0x29/0x70
Dec 8 20:25:06 dima-xps kernel: [21939.203431] [<ffffffff81720ad5>] __mutex_lock_slowpath+0x135/0x1b0
Dec 8 20:25:06 dima-xps kernel: [21939.203434] [<ffffffff81720b6f>] mutex_lock+0x1f/0x2f
Dec 8 20:25:06 dima-xps kernel: [21939.203437] [<ffffffff815494c9>] read_descriptors+0x39/0x110
Dec 8 20:25:06 dima-xps kernel: [21939.203440] [<ffffffff812325fb>] ? sysfs_bin_read+0x8b/0x1d0
Dec 8 20:25:06 dima-xps kernel: [21939.203443] [<ffffffff8123264e>] sysfs_bin_read+0xde/0x1d0
Dec 8 20:25:06 dima-xps kernel: [21939.203446] [<ffffffff811bc6f5>] vfs_read+0x95/0x160
Dec 8 20:25:06 dima-xps kernel: [21939.203449] [<ffffffff811bd209>] SyS_read+0x49/0xa0
Dec 8 20:25:06 dima-xps kernel: [21939.203452] [<ffffffff8172aeff>] tracesys+0xe1/0xe6

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-generic (not installed)
ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: dima 2714 F.... pulseaudio
CurrentDesktop: KDE
Date: Mon Dec 8 21:23:08 2014
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=4e604b81-620a-41a0-bf0d-3e9678f1f5fc
InstallationDate: Installed on 2013-04-05 (613 days ago)
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
MachineType: Dell Inc. Dell System XPS L321X
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=bac9562b-214b-4ea6-b574-43052611d85c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-30-generic N/A
 linux-backports-modules-3.13.0-30-generic N/A
 linux-firmware 1.138
SourcePackage: linux
UpgradeStatus: Upgraded to utopic on 2014-09-29 (71 days ago)
dmi.bios.date: 01/22/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: 085X6F
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/22/2013:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System XPS L321X
dmi.sys.vendor: Dell Inc.

Revision history for this message
Dima Ryazanov (dima-gmail) 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
penalvch (penalvch) wrote :

Dima Ryazanov, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to 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 exactly shown as:
kernel-fixed-upstream-3.18

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.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

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: latest-bios-a08
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

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