cdrom causing problems with UDev at boot [SOLVED]

boina · 2012-02-18 17:53:45

Last week I had to take the cdrom reader out of the PC for a few days and when I plugged it back in, the boot process began to take between 1-2 minutes longer that what it used to and with some messages from UDev complying something about the cdrom. After the boot process the cdrom works OK.
When I unplug the cdrom reader the boot process goes smoothly with no complains.
I'm sorry I can't put any more information but I have no idea what is going on here or how to solve it.
Thanks in advanced, José.

Sat Feb 18 14:31:12 2012: :: Adjusting system time and setting kernel timezone    [BUSY]    [DONE] 
Sat Feb 18 14:31:12 2012: :: Starting UDev Daemon    [BUSY]    [DONE] 
Sat Feb 18 14:31:12 2012: :: Triggering UDev uevents    [BUSY]    [DONE] 
Sat Feb 18 14:31:12 2012: :: Loading User-specified Modules    [BUSY]    [DONE] 
Sat Feb 18 14:31:12 2012: :: Waiting for UDev uevents to be processed    [BUSY] udevd[192]: timeout 'cdrom_id --lock-media /dev/sr0'
Sat Feb 18 14:31:12 2012: 
Sat Feb 18 14:31:12 2012: udevd[192]: timeout: killing 'cdrom_id --lock-media /dev/sr0' [245]
Sat Feb 18 14:31:12 2012: 
Sat Feb 18 14:31:12 2012: udevd[187]: worker [192] timeout, kill it
Sat Feb 18 14:31:12 2012: 
Sat Feb 18 14:31:12 2012: udevd[187]: seq 1285 '/devices/pci0000:00/0000:00:06.0/host0/target0:0:0/0:0:0:0/block/sr0' killed
Sat Feb 18 14:31:12 2012: 
Sat Feb 18 14:31:12 2012: udevd[187]: worker [192] terminated by signal 9 (Killed)
Sat Feb 18 14:31:12 2012: 
Sat Feb 18 14:31:12 2012:    [DONE] 
Sat Feb 18 14:31:12 2012: :: Bringing up loopback interface    [BUSY]    [DONE]

Last edited by boina (2014-10-12 15:54:09)

Gcool · 2012-02-19 10:39:58

Have a look in the following threads:

https://bbs.archlinux.org/viewtopic.php?id=135758
https://bbs.archlinux.org/viewtopic.php?pid=895404

boina · 2012-02-28 22:53:15

I'm Sorry for the delay but I've been away for a few days. I have just tried with the solution posted on but it didn't work.
The error.log shows the following when I tried what is posted on those two links:

Feb 28 19:33:14 localhost kernel: [   22.393943] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Feb 28 19:33:14 localhost kernel: [   22.393998] ata1.00: cmd a0/01:00:00:60:00/00:00:00:00:00/a0 tag 0 dma 96 in
Feb 28 19:33:14 localhost kernel: [   22.393999]          res 40/00:02:00:24:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Feb 28 19:33:14 localhost kernel: [   22.394087] ata1.00: status: { DRDY }
Feb 28 19:33:14 localhost kernel: [   53.360075] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Feb 28 19:33:14 localhost kernel: [   53.360140] ata1.00: cmd a0/01:00:00:80:00/00:00:00:00:00/a0 tag 0 dma 16512 in
Feb 28 19:33:14 localhost kernel: [   53.360141]          res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Feb 28 19:33:14 localhost kernel: [   53.360266] ata1.00: status: { DRDY }
Feb 28 19:33:14 localhost kernel: [   56.834721] k10temp 0000:00:18.3: unreliable CPU thermal sensor; monitoring disabled
Feb 28 19:33:14 localhost kernel: [  117.386731] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Feb 28 19:33:14 localhost kernel: [  117.386796] ata1.00: cmd a0/01:00:00:30:01/00:00:00:00:00/a0 tag 0 dma 16688 in
Feb 28 19:33:14 localhost kernel: [  117.386797]          res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Feb 28 19:33:14 localhost kernel: [  117.386923] ata1.00: status: { DRDY }

As it didn't work I reverted the changes I had made and got the following on the error log

Feb 28 19:42:20 localhost kernel: [   22.394006] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Feb 28 19:42:20 localhost kernel: [   22.394061] ata1.00: cmd a0/01:00:00:60:00/00:00:00:00:00/a0 tag 0 dma 96 in
Feb 28 19:42:20 localhost kernel: [   22.394062]          res 40/00:02:00:24:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Feb 28 19:42:20 localhost kernel: [   22.394151] ata1.00: status: { DRDY }
Feb 28 19:42:20 localhost kernel: [   53.360063] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Feb 28 19:42:20 localhost kernel: [   53.360130] ata1.00: cmd a0/01:00:00:80:00/00:00:00:00:00/a0 tag 0 dma 16512 in
Feb 28 19:42:20 localhost kernel: [   53.360131]          res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Feb 28 19:42:20 localhost kernel: [   53.360256] ata1.00: status: { DRDY }
Feb 28 19:42:20 localhost kernel: [   55.762750] k10temp 0000:00:18.3: unreliable CPU thermal sensor; monitoring disabled
Feb 28 19:42:21 localhost /usr/sbin/crond[619]: (CRON) INFO (Syslog will be used instead of sendmail.): No existe el fichero o el directorio
Feb 28 19:42:21 localhost dhcpcd[623]: eth0: sendmsg: Cannot assign requested address
Feb 28 19:42:44 localhost kernel: [  116.426710] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Feb 28 19:42:44 localhost kernel: [  116.426723] ata1.00: cmd a0/01:00:00:30:01/00:00:00:00:00/a0 tag 0 dma 16688 in
Feb 28 19:42:44 localhost kernel: [  116.426724]          res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Feb 28 19:42:44 localhost kernel: [  116.426727] ata1.00: status: { DRDY }
Feb 28 19:42:48 localhost pulseaudio[1609]: [pulseaudio] pid.c: Daemon already running.
Feb 28 19:43:15 localhost udevd[185]: worker [244] timeout, kill it
Feb 28 19:43:15 localhost udevd[185]: seq 1781 '/devices/pci0000:00/0000:00:06.0/host0/target0:0:0/0:0:0:0/block/sr0' killed
Feb 28 19:43:15 localhost udevd[185]: worker [244] terminated by signal 9 (Killed)
Feb 28 19:43:45 localhost kernel: [  177.440069] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Feb 28 19:43:45 localhost kernel: [  177.440083] ata1.00: cmd a0/01:00:00:30:01/00:00:00:00:00/a0 tag 0 dma 16688 in
Feb 28 19:43:45 localhost kernel: [  177.440084]          res 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Feb 28 19:43:45 localhost kernel: [  177.440086] ata1.00: status: { DRDY }

I have no idea what is going here.
Thanks, jose.

boina · 2014-10-12 15:54:45

The CD ROM reader was broken......

Arch Linux

#1 2012-02-18 17:53:45

cdrom causing problems with UDev at boot [SOLVED]

#2 2012-02-19 10:39:58

Re: cdrom causing problems with UDev at boot [SOLVED]

#3 2012-02-28 22:53:15

Re: cdrom causing problems with UDev at boot [SOLVED]

#4 2014-10-12 15:54:45

Re: cdrom causing problems with UDev at boot [SOLVED]

Board footer