[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#638887: marked as done (udev: cdrom_id process can not be killed)

Your message dated Fri, 10 Feb 2012 01:32:26 -0600
with message-id <20120210073226.GA16461@burratino>
and subject line Re: [regression] CD-ROM polling blocks suspend on some machines
has caused the Debian Bug report #628600,
regarding udev: cdrom_id process can not be killed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
628600: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628600
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: udev
Version: 172-1
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Occasionally I find a cdrom_id process stuck in the D
("uninterruptible sleep") state that can not be killed.  I'm not
exactly sure what's causing this (possibly detaching from my dock?)
but this causes multiple problems on my system.  First of all, my
syslog starts filling with the following lines, appearing
approximately once per second:

Aug 22 08:55:26 servo udevd[31950]: timeout: killing 'cdrom_id --lock-media /dev/sr0' [32017]

More frustratingly, my system becomes unable to sleep, because the
cdrom_id process can't be frozen [0].

Restarting udev occasionally works to kill the cdrom_id process, but
sometimes it doesn't, and again I don't know why.

There is a dvd drive in my dock, so I'm assuming it must be somehow
related to that.

Please let me know if I can provide any more useful info.

Thanks so much.

jamie.


[0] syslog clip from an attempt to suspend:
Aug 22 08:55:52 servo kernel: [171579.375884] PM: Preparing system for mem sleep
Aug 22 08:56:13 servo kernel: [171579.712602] Freezing user space processes ... 
Aug 22 08:56:13 servo kernel: [171599.678769] Freezing of tasks failed after 20.01 seconds (1 tasks refusing to freeze, wq_busy=0):
Aug 22 08:56:13 servo kernel: [171599.678800] cdrom_id        D ffff88011fef29b0     0 32017      1 0x00800004
Aug 22 08:56:13 servo kernel: [171599.678809]  ffff88011fef29b0 0000000000000082 ffff88011fef2d68 00ff88023bc92800
Aug 22 08:56:13 servo kernel: [171599.678818]  ffff880232da60c0 0000000000012800 ffff8801ce135fd8 ffff8801ce135fd8
Aug 22 08:56:13 servo kernel: [171599.678826]  0000000000012800 ffff88011fef29b0 0000000000012800 0000000000012800
Aug 22 08:56:13 servo kernel: [171599.678835] Call Trace:
Aug 22 08:56:13 servo kernel: [171599.678850]  [<ffffffff81335939>] ? schedule_timeout+0x2d/0xd7
Aug 22 08:56:13 servo kernel: [171599.678856]  [<ffffffff81038189>] ? test_tsk_need_resched+0xe/0x17
Aug 22 08:56:13 servo kernel: [171599.678860]  [<ffffffff81335713>] ? wait_for_common+0x9d/0x116
Aug 22 08:56:13 servo kernel: [171599.678866]  [<ffffffff8103f0a4>] ? try_to_wake_up+0x199/0x199
Aug 22 08:56:13 servo kernel: [171599.678871]  [<ffffffff8105b266>] ? start_flush_work+0xec/0x103
Aug 22 08:56:13 servo kernel: [171599.678874]  [<ffffffff8105b57c>] ? flush_work+0x24/0x2c
Aug 22 08:56:13 servo kernel: [171599.678878]  [<ffffffff8105ae8f>] ? do_work_for_cpu+0x1b/0x1b
Aug 22 08:56:13 servo kernel: [171599.678883]  [<ffffffff811994be>] ? disk_clear_events+0x86/0xe4
Aug 22 08:56:13 servo kernel: [171599.678890]  [<ffffffff81121c0e>] ? check_disk_change+0x22/0x50
Aug 22 08:56:13 servo kernel: [171599.678896]  [<ffffffffa05b3051>] ? cdrom_open+0x45/0x4aa [cdrom]
Aug 22 08:56:13 servo kernel: [171599.678901]  [<ffffffff811a4c79>] ? kobject_get+0x12/0x17
Aug 22 08:56:13 servo kernel: [171599.678905]  [<ffffffff81198079>] ? get_disk+0x6d/0x8d
Aug 22 08:56:13 servo kernel: [171599.678908]  [<ffffffff8103840a>] ? should_resched+0x5/0x24
Aug 22 08:56:13 servo kernel: [171599.678911]  [<ffffffff8133565f>] ? _cond_resched+0x9/0x20
Aug 22 08:56:13 servo kernel: [171599.678917]  [<ffffffff8124b9df>] ? kobj_lookup+0x13a/0x174
Aug 22 08:56:13 servo kernel: [171599.678920]  [<ffffffff811a4c79>] ? kobject_get+0x12/0x17
Aug 22 08:56:13 servo kernel: [171599.678925]  [<ffffffffa05bf7c3>] ? sr_block_open+0x93/0xbc [sr_mod]
Aug 22 08:56:13 servo kernel: [171599.678928]  [<ffffffff811229b1>] ? __blkdev_get+0xe3/0x380
Aug 22 08:56:13 servo kernel: [171599.678934]  [<ffffffff810cf775>] ? set_pte_at+0x5/0x8
Aug 22 08:56:13 servo kernel: [171599.678937]  [<ffffffff81122ef5>] ? blkdev_get+0x2a7/0x2a7
Aug 22 08:56:13 servo kernel: [171599.678940]  [<ffffffff81122e15>] ? blkdev_get+0x1c7/0x2a7
Aug 22 08:56:13 servo kernel: [171599.678944]  [<ffffffff81122ef5>] ? blkdev_get+0x2a7/0x2a7
Aug 22 08:56:13 servo kernel: [171599.678950]  [<ffffffff810fa32e>] ? __dentry_open+0x182/0x29c
Aug 22 08:56:13 servo kernel: [171599.678954]  [<ffffffff811035df>] ? dget+0x12/0x1e
Aug 22 08:56:13 servo kernel: [171599.678958]  [<ffffffff81105861>] ? do_last+0x46d/0x584
Aug 22 08:56:13 servo kernel: [171599.678961]  [<ffffffff81106bea>] ? path_openat+0xc7/0x349
Aug 22 08:56:13 servo kernel: [171599.678965]  [<ffffffff810d0312>] ? tlb_flush_mmu+0x37/0x50
Aug 22 08:56:13 servo kernel: [171599.678968]  [<ffffffff81106e98>] ? do_filp_open+0x2c/0x72
Aug 22 08:56:13 servo kernel: [171599.678971]  [<ffffffff8133565f>] ? _cond_resched+0x9/0x20
Aug 22 08:56:13 servo kernel: [171599.678976]  [<ffffffff811ac741>] ? __strncpy_from_user+0x19/0x4a
Aug 22 08:56:13 servo kernel: [171599.678981]  [<ffffffff81110208>] ? alloc_fd+0x69/0x110
Aug 22 08:56:13 servo kernel: [171599.678984]  [<ffffffff810fb138>] ? do_sys_open+0x5f/0xe6
Aug 22 08:56:13 servo kernel: [171599.678990]  [<ffffffff8133ba92>] ? system_call_fastpath+0x16/0x1b
Aug 22 08:56:13 servo kernel: [171599.678995] 
Aug 22 08:56:13 servo kernel: [171599.678996] Restarting tasks ... done.


- -- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages udev depends on:
ii  debconf [debconf-2.0]         1.5.40     Debian configuration management sy
ii  libc6                         2.13-10    Embedded GNU C Library: Shared lib
ii  libselinux1                   2.0.98-1.1 SELinux runtime shared libraries
ii  libudev0                      172-1      libudev shared library
ii  lsb-base                      3.2-27     Linux Standard Base 3.2 init scrip
ii  util-linux                    2.19.1-5   Miscellaneous system utilities

Versions of packages udev recommends:
ii  pciutils                      1:3.1.7-12 Linux PCI Utilities
ii  usbutils                      1:001-1    Linux USB utilities

udev suggests no packages.

- -- debconf information:
  udev/new_kernel_needed: false
  udev/title/upgrade:
  udev/reboot_needed:
  udev/sysfs_deprecated_incompatibility:

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQIcBAEBCAAGBQJOUpI2AAoJEO00zqvie6q8aU4P/i+xuoF1c7X+00AO98Fpzic/
vsa95DM/vJFxFgcy0H8izZEwcxLx4ehAxauSHNpFb/nwB65YH1yMAaknn0GzJvXX
I7XkZ+HXdI1yW7RJ1m9fzsqQijaVp5qspEU1b3KhojjOZObUfsJJr0yAs6AZE6GP
+5Q9uyvB1exPVc6JRS3K2IHvJtrxAKI2xKAtS2E2g16maYD5ezvVv1e5RLE4Dx6o
SMffxb2K9rwITeWnP4esZXME5ECk/iB7SXWJmeC38fW1XcRe4ytSWGpNBqwNh7av
GkpBEfbP4/HzDpSvlZZyZ1hYSLxsOFyJV0WTKKNX+vsHXAqSL+V33N2iKW6pJPrN
pV13y7+YjkZToEatD8Z5TZOpbYHQuIHX4LkiMyTm3r0ndTufpqodl8ZY5uGYwgMS
CrjIcQGOts8gYE9usNlnmlsLyHlPLE6vGqcr1w5HnwBdq7VBQiXmPOwqUNxGLHNA
0UdQuQ9xT6zcuEUAwXn6jO3oDP8ALkwywHKR0iEKNdX8PnWZtV+WXcJjz3iT5i/u
bgVRr4f9UbtJMyJm6CGWnIsVpRVE+/5IJu6Zgjj/8Hse68e0iw4gY+yoHAAjhNbl
ufic3wdJFQJzVeP7uC9GU2m0zIgAmoId3+dT+ildlQUIyq1/RiXL26Kaqy2SlHbZ
TI13Vt7/X+r9VzLmgMNz
=UrPO
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
Version: 3.2.4-1

Matthijs Kooijman wrote:
> Hi Jonathan,

>>> The cdrom_id program from the udev package (version 167-3) "refuse to freeze"
>>> with a linux 2.6.39. That prevent the system to suspend.
>>> It works will with a 2.6.38 kernel, then the problem starts with the 2.6.39
>>> kernel.
>>
>> Said to be fixed in 3.2.  Can you confirm?
>
> Seems so: I've been running 3.2 for a few weeks now, the problem has not
> occured so far.

Thanks; closing.

--- End Message ---
Reply to: