udevd cpu high usage <SOLVED>

[Old-Polack]

Back in linux using the older kernel (2.6.33.5).

What's next to recover?

Code: [Select]

[docnascar@localhost boot]$ ls -l |grep init
-rw------- 1 root root 5873663 Jun  7  2011 initrd-2.6.33.5-pclos1.bfs.img
-rw------- 1 root root 3557337 Feb 12 11:19 initrd-2.6.38.8-pclos3.bfs
-rw------- 1 root root 4955794 Nov  7 20:49 initrd-2.6.38.8-pclos3.bfs.img-bak
lrwxrwxrwx 1 root root      30 Nov  7 20:49 initrd.img -> initrd-2.6.38.8-pclos3.bfs.img
-rw------- 1 root root 9724618 Jun  5  2010 [color=blue][b]initrd.img.old[/b][/color]     [color=green]<-- This is wrong[/color]
[docnascar@localhost boot]$




First, su to root. If you show the prompt;

[root@localhost boot]#

you're good to go to the next command. If you see;

[root@localhost ~]#

you need to cd to /boot before proceeding.

[root@localhost boot]# mkinitrd -v --preload pata_amd --preload sata_nv initrd-2.6.38.8-pclos3.bfs.img  2.6.38.8-pclos3.bfs             <Enter>

[root@localhost boot]# ls -l |grep init                <Enter>

This time the new initrd image should show in the listing, so the initrd.img link actually points to an existing image. Assuming there is one;

[root@localhost boot]# lsinitrd /boot/initrd.img |grep modprobe            <Enter>

You should see the list of modules to be loaded, with the first two being pata_amd and sata_nv.

If you get that, you should be ready to reboot... if not, just post your results.

[Old-Polack]

Yes!  

Smart ass!!! I'm typing all these instructions to gain a missing initrd image, and you tell him to just add .img to the name of the one you botched. No fair... cheat... cheat...  

[AS]

Yes!  

Smart ass!!! I'm typing all these instructions to gain a missing initrd image, and you tell him to just add .img to the name of the one you botched. No fair... cheat... cheat...  

Actually it was my fault, lost the .img suffix 

Where do you were when I was giving him the wrong instructions ? 

docnascar,

reboot 

[docnascar]

Good news and bad news!

Bad news first.
CD Drive Bay won't open.... Hmmm, did I break it? Let me re-check the bios, and maybe boot with the old kernel again.

Good news.
No more loop!

Code: [Select]

[docnascar@localhost ~]$ uname -r
2.6.38.8-pclos3.bfs
[docnascar@localhost ~]$  udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

^C[docnascar@localhost ~]$ ^C
[docnascar@localhost ~]$



[docnascar]

CD rom is not showing up in Dolphin on the LEFT. I see the floppy drive. (who uses those anymore! LOL).

I think it should be there, but don't remember.

Is it mounted? I think it won't open if not, right?

[Old-Polack]

Good news and bad news!

Bad news first.
CD Drive Bay won't open.... Hmmm, did I break it? Let me re-check the bios, and maybe boot with the old kernel again.

Good news.
No more loop!

Code: [Select]

[docnascar@localhost ~]$ uname -r
2.6.38.8-pclos3.bfs
[docnascar@localhost ~]$  udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

^C[docnascar@localhost ~]$ ^C
[docnascar@localhost ~]$



[root@localhost ~]# ls -l /dev |grep cdrom              <Enter>

Post your results.

[AS]

Good news and bad news!

Bad news first.
CD Drive Bay won't open.... Hmmm, did I break it? Let me re-check the bios, and maybe boot with the old kernel again.

.... hmmm ... check cables 

[docnascar]

Code: [Select]

[root@localhost docnascar]# ls -l /dev |grep cdrom
lrwxrwxrwx  1 root      root           3 Feb 12 13:44 cdrom -> sr0
crw-rw----+ 1 root      cdrom    21,   2 Feb 12 13:40 sg2
brw-rw----+ 1 root      cdrom    11,   0 Feb 12 13:44 sr0
[root@localhost docnascar]#


[AS]

Code: [Select]

[root@localhost docnascar]# ls -l /dev |grep cdrom
lrwxrwxrwx  1 root      root           3 Feb 12 13:44 cdrom -> sr0
crw-rw----+ 1 root      cdrom    21,   2 Feb 12 13:40 sg2
brw-rw----+ 1 root      cdrom    11,   0 Feb 12 13:44 sr0
[root@localhost docnascar]#


How/what is listed in dmesg ?

Code: [Select]

dmesg  |  grep ata

[Old-Polack]

Code: [Select]

[root@localhost docnascar]# ls -l /dev |grep cdrom
lrwxrwxrwx  1 root      root           3 Feb 12 13:44 cdrom -> sr0
crw-rw----+ 1 root      cdrom    21,   2 Feb 12 13:40 sg2
brw-rw----+ 1 root      cdrom    11,   0 Feb 12 13:44 sr0
[root@localhost docnascar]#


[root@localhost docnascar]# eject                    <Enter>

[root@localhost docnascar]# eject -t                    <Enter>

[docnascar]

OK...

Drive bay screws were too tight as the door wasn't opening during power. They weren't really that tight but I guess tight enough. Now the door opens.

There is another weird issue.

I can read the cd in dolphin. I can copy a file from a cd track to my desktop and play it. However, I cannot play tracks directly from the cd drive. It tries to read the drive forever. (hence taking so long for me to reply)

I don't know if this related to the changes that we did.

Code: [Select]

[docnascar@localhost ~]$ dmesg  |  grep ata
 BIOS-e820: 000000004fef3000 - 000000004ff00000 (ACPI data)
Memory: 1288444k/1309632k available (3339k kernel code, 20724k reserved, 1645k data, 512k init, 404424k highmem)
      .data : 0xc0442fd5 - 0xc05de780   (1645 kB)
libata version 3.00 loaded.
pata_amd 0000:00:0d.0: version 0.4.1
pata_amd 0000:00:0d.0: setting latency timer to 64
scsi0 : pata_amd
scsi1 : pata_amd
ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf400 irq 14
ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf408 irq 15
ata1.00: ATA-6: Maxtor 51023H2, JAC61HU0, max UDMA/100
ata1.00: 19541088 sectors, multi 16: LBA
ata1.01: ATA-5: WDC WD200BB-75AUA1, 18.20D18, max UDMA/100
ata1.01: 39102336 sectors, multi 16: LBA
ata1: nv_mode_filter: 0x3f39f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1: nv_mode_filter: 0x3f39f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata2.01: ATAPI:         48X12X50 CD-RW    1.04 20021101, 1.04, max UDMA/33
ata2: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (600:60:0x1c)
ata2.01: configured for UDMA/33
sata_nv 0000:00:0e.0: version 3.5
sata_nv 0000:00:0e.0: PCI INT A -> Link[APSI] -> GSI 23 (level, low) -> IRQ 23
sata_nv 0000:00:0e.0: Using SWNCQ mode
sata_nv 0000:00:0e.0: setting latency timer to 64
scsi2 : sata_nv
scsi3 : sata_nv
ata3: SATA max UDMA/133 cmd 0x9f0 ctl 0xbf0 bmdma 0xe000 irq 23
ata4: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xe008 irq 23
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
EXT3-fs (sda1): mounted filesystem with ordered data mode
EXT3-fs (sdb1): mounted filesystem with ordered data mode
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.01: failed command: WRITE DMA
ata1.01: cmd ca/00:00:67:ec:be/00:00:00:00:00/f0 tag 0 dma 131072 out
ata1.01: status: { DRDY }
ata1: soft resetting link
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1.01: device reported invalid CHS sector 0
ata1: EH complete
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.01: failed command: WRITE DMA
ata1.01: cmd ca/00:10:7f:04:b0/00:00:00:00:00/f0 tag 0 dma 8192 out
ata1.01: status: { DRDY }
ata1: link is slow to respond, please be patient (ready=0)
ata1: device not ready (errno=-16), forcing hardreset
ata1: soft resetting link
ata1: link is slow to respond, please be patient (ready=0)
ata1: SRST failed (errno=-16)
ata1: soft resetting link
ata1: link is slow to respond, please be patient (ready=0)
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1.01: device reported invalid CHS sector 0
ata1: EH complete
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.01: failed command: WRITE DMA
ata1.01: cmd ca/00:10:47:f5:b0/00:00:00:00:00/f0 tag 0 dma 8192 out
ata1.01: status: { DRDY }
ata1: link is slow to respond, please be patient (ready=0)
ata1: device not ready (errno=-16), forcing hardreset
ata1: soft resetting link
ata1: link is slow to respond, please be patient (ready=0)
ata1: SRST failed (errno=-16)
ata1: soft resetting link
ata1: link is slow to respond, please be patient (ready=0)
ata1: SRST failed (errno=-16)
ata1: soft resetting link
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1.01: device reported invalid CHS sector 0
ata1: EH complete
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.01: failed command: WRITE DMA
ata1.01: cmd ca/00:00:ff:4f:b3/00:00:00:00:00/f0 tag 0 dma 131072 out
ata1.01: status: { DRDY }
ata1: link is slow to respond, please be patient (ready=0)
ata1: device not ready (errno=-16), forcing hardreset
ata1: soft resetting link
ata1: link is slow to respond, please be patient (ready=0)
ata1: SRST failed (errno=-16)
ata1: soft resetting link
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1.01: device reported invalid CHS sector 0
ata1: EH complete
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.01: failed command: WRITE DMA
ata1.01: cmd ca/00:00:47:7e:b3/00:00:00:00:00/f0 tag 0 dma 131072 out
ata1.01: status: { DRDY }
ata1: link is slow to respond, please be patient (ready=0)
ata1: device not ready (errno=-16), forcing hardreset
ata1: soft resetting link
ata1: link is slow to respond, please be patient (ready=0)
ata1: SRST failed (errno=-16)
ata1: soft resetting link
ata1: link is slow to respond, please be patient (ready=0)
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1.01: device reported invalid CHS sector 0
ata1: EH complete
ata1.01: limiting speed to UDMA/25:PIO4
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.01: failed command: READ DMA
ata1.01: cmd c8/00:08:8f:c5:b0/00:00:00:00:00/f0 tag 0 dma 4096 in
ata1.01: status: { DRDY }
ata1: soft resetting link
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1: nv_mode_filter: 0x339f&0x739f->0x339f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/25
ata1.01: device reported invalid CHS sector 0
ata1: EH complete
[docnascar@localhost ~]$


[docnascar]

I was able to get the cd to work with KsCD. I don't have much experience playing CD's with Linux. Not sure why the cd doesn't auto play when you first put it into the drive and close.

I think as far as this thread is concerned, the udevd issue is fixed. I still have avahi failures when shutting down. I'll start another thread for that.

Thanks AS and O-P!!

[AS]

OK...

Drive bay screws were too tight as the door wasn't opening during power. They weren't really that tight but I guess tight enough. Now the door opens.

There is another weird issue.

I can read the cd in dolphin. I can copy a file from a cd track to my desktop and play it. However, I cannot play tracks directly from the cd drive. It tries to read the drive forever. (hence taking so long for me to reply)

I don't know if this related to the changes that we did.

Code: [Select]

[docnascar@localhost ~]$ dmesg  |  grep ata
 BIOS-e820: 000000004fef3000 - 000000004ff00000 (ACPI data)
Memory: 1288444k/1309632k available (3339k kernel code, 20724k reserved, 1645k data, 512k init, 404424k highmem)
      .data : 0xc0442fd5 - 0xc05de780   (1645 kB)
libata version 3.00 loaded.
pata_amd 0000:00:0d.0: version 0.4.1
pata_amd 0000:00:0d.0: setting latency timer to 64
scsi0 : pata_amd
scsi1 : pata_amd
ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xf400 irq 14
ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xf408 irq 15
ata1.00: ATA-6: Maxtor 51023H2, JAC61HU0, max UDMA/100
ata1.00: 19541088 sectors, multi 16: LBA
ata1.01: ATA-5: WDC WD200BB-75AUA1, 18.20D18, max UDMA/100
ata1.01: 39102336 sectors, multi 16: LBA
ata1: nv_mode_filter: 0x3f39f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1: nv_mode_filter: 0x3f39f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata2.01: ATAPI:         48X12X50 CD-RW    1.04 20021101, 1.04, max UDMA/33
ata2: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (600:60:0x1c)
ata2.01: configured for UDMA/33
sata_nv 0000:00:0e.0: version 3.5
sata_nv 0000:00:0e.0: PCI INT A -> Link[APSI] -> GSI 23 (level, low) -> IRQ 23
sata_nv 0000:00:0e.0: Using SWNCQ mode
sata_nv 0000:00:0e.0: setting latency timer to 64
scsi2 : sata_nv
scsi3 : sata_nv
ata3: SATA max UDMA/133 cmd 0x9f0 ctl 0xbf0 bmdma 0xe000 irq 23
ata4: SATA max UDMA/133 cmd 0x970 ctl 0xb70 bmdma 0xe008 irq 23
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link down (SStatus 0 SControl 300)
EXT3-fs (sda1): mounted filesystem with ordered data mode
EXT3-fs (sdb1): mounted filesystem with ordered data mode
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.01: failed command: WRITE DMA
ata1.01: cmd ca/00:00:67:ec:be/00:00:00:00:00/f0 tag 0 dma 131072 out
ata1.01: status: { DRDY }
ata1: soft resetting link
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1.01: device reported invalid CHS sector 0
ata1: EH complete
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.01: failed command: WRITE DMA
ata1.01: cmd ca/00:10:7f:04:b0/00:00:00:00:00/f0 tag 0 dma 8192 out
ata1.01: status: { DRDY }
ata1: link is slow to respond, please be patient (ready=0)
ata1: device not ready (errno=-16), forcing hardreset
ata1: soft resetting link
ata1: link is slow to respond, please be patient (ready=0)
ata1: SRST failed (errno=-16)
ata1: soft resetting link
ata1: link is slow to respond, please be patient (ready=0)
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1.01: device reported invalid CHS sector 0
ata1: EH complete
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.01: failed command: WRITE DMA
ata1.01: cmd ca/00:10:47:f5:b0/00:00:00:00:00/f0 tag 0 dma 8192 out
ata1.01: status: { DRDY }
ata1: link is slow to respond, please be patient (ready=0)
ata1: device not ready (errno=-16), forcing hardreset
ata1: soft resetting link
ata1: link is slow to respond, please be patient (ready=0)
ata1: SRST failed (errno=-16)
ata1: soft resetting link
ata1: link is slow to respond, please be patient (ready=0)
ata1: SRST failed (errno=-16)
ata1: soft resetting link
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1.01: device reported invalid CHS sector 0
ata1: EH complete
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.01: failed command: WRITE DMA
ata1.01: cmd ca/00:00:ff:4f:b3/00:00:00:00:00/f0 tag 0 dma 131072 out
ata1.01: status: { DRDY }
ata1: link is slow to respond, please be patient (ready=0)
ata1: device not ready (errno=-16), forcing hardreset
ata1: soft resetting link
ata1: link is slow to respond, please be patient (ready=0)
ata1: SRST failed (errno=-16)
ata1: soft resetting link
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1.01: device reported invalid CHS sector 0
ata1: EH complete
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.01: failed command: WRITE DMA
ata1.01: cmd ca/00:00:47:7e:b3/00:00:00:00:00/f0 tag 0 dma 131072 out
ata1.01: status: { DRDY }
ata1: link is slow to respond, please be patient (ready=0)
ata1: device not ready (errno=-16), forcing hardreset
ata1: soft resetting link
ata1: link is slow to respond, please be patient (ready=0)
ata1: SRST failed (errno=-16)
ata1: soft resetting link
ata1: link is slow to respond, please be patient (ready=0)
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/33
ata1.01: device reported invalid CHS sector 0
ata1: EH complete
ata1.01: limiting speed to UDMA/25:PIO4
ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.01: failed command: READ DMA
ata1.01: cmd c8/00:08:8f:c5:b0/00:00:00:00:00/f0 tag 0 dma 4096 in
ata1.01: status: { DRDY }
ata1: soft resetting link
ata1: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1: nv_mode_filter: 0x339f&0x739f->0x339f, BIOS=0x7000 (0xc0c000c0) ACPI=0x701f (60:60:0x1f)
ata1.00: configured for UDMA/33
ata1.01: configured for UDMA/25
ata1.01: device reported invalid CHS sector 0
ata1: EH complete
[docnascar@localhost ~]$


the dmesg output doesn't look very good ... particularly the device ata1.01 ...

ata1.01: ATA-5: WDC WD200BB-75AUA1, 18.20D18, max UDMA/100

[docnascar]

the dmesg output doesn't look very good ... particularly the device ata1.01 ...

I'll keep an eye out for them. These drives are really old.

I'm ready to buy another bare bones pc to upgrade my linux pc, but I just don't have the cash right now.

[AS]

the dmesg output doesn't look very good ... particularly the device ata1.01 ...

I'll keep an eye out for them. These drives are really old.

I'm ready to buy another bare bones pc to upgrade my linux pc, but I just don't have the cash right now.

OK, keep your backups updated ...just in case.
About the ata1.01 (WD 20 GB) ... it could be even a bad ribbon cable ... bad contacts ... bad power cable connection ...

Would you mark this thread as SOLVED ? THX.

AS