udevd cpu high usage <SOLVED>

[AS]

No vendor yet just:

Code:

Probing IDE interface ide1...
hdd: 48X12X50 CD-RW 1.04 20021101, ATAPI CD/DVD-ROM drive
hdd: host max PIO5 wanted PIO255(auto-tune) selected PIO4
hdd: UDMA/33 mode selected
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15

All those logs say pretty much the same thing.
hdd: 48X12X50 CD-RW 1.04 20021101, ATAPI CD/DVD-ROM drive

Should be "Aopen 48X12X50", you can find the related firmware  here:
http://www.cdrom-drivers.com/companies/90.htm

the first listed should be that one actually installed on your drive, apparently the latest ...

Did you tried to disable/detach that unit ?

[docnascar]

I tried disabling through the bios but its not so straight forward. I can't tell the bios there is no dvd drive. I can mess up the "IDE Channel 1 Slave" setting and set it from Auto to NONE. Maybe this will disable it.

If not I'll rip my pc apart tomorrow and try. And I'll confirm the drives vendor, but I think you got it.

Thanks for helping out.

[AS]

I tried disabling through the bios but its not so straight forward. I can't tell the bios there is no dvd drive. I can mess up the "IDE Channel 1 Slave" setting and set it from Auto to NONE. Maybe this will disable it.

NONE ... should do.

If not I'll rip my pc apart tomorrow and try. And I'll confirm the drives vendor, but I think you got it.

Thanks for helping out.

Let us know how it will follow up 

[docnascar]

This problem is definitely related to my cd rom drive. I tried disabling the drive via the BIOS (as previously described) but the cpu was still overloaded.

I physically disconnected the cd rom drive and everything is acting normal.

My drive has the following info on it.
P/N: 91.3AD37.025
MODEL NO: 48x12x50 CD-RW
MANUFACTURED: DEC 2002 J

There is no info on the actual manufacturer's name. Searching Google, there are a few vendors that share the same part number. 

I'm pondering, can this be fixed, is it a bug, is my drive bad?

[AS]

This problem is definitely related to my cd rom drive. I tried disabling the drive via the BIOS (as previously described) but the cpu was still overloaded.

I physically disconnected the cd rom drive and everything is acting normal.

My drive has the following info on it.
P/N: 91.3AD37.025
MODEL NO: 48x12x50 CD-RW
MANUFACTURED: DEC 2002 J

There is no info on the actual manufacturer's name. Searching Google, there are a few vendors that share the same part number. 

I'm pondering, can this be fixed, is it a bug, is my drive bad?

Probably not ... I'm on a couple of similar threads:
http://www.pclinuxos.com/forum/index.php/topic,100800.0.html
http://www.pclinuxos.com/forum/index.php/topic,102486.0.html

including yours, all three threads show the use of /dev/hdX instead of /dev/sdX ...

Please add the output of:

Code:

lspci | grep -i ide

and

Code:

ls -l /dev/sr*

AS

[docnascar]

Hi AS!

Please add the output of:

Code:

lspci | grep -i ide

and

Code:

ls -l /dev/sr*

AS

Note: the drive is not connected
Did you want it connected?

Code:

[root@localhost docnascar]# lspci | grep -i ide
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1)
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
[root@localhost docnascar]# ls -l /dev/sr*
ls: cannot access /dev/sr*: No such file or directory
[root@localhost docnascar]#

[AS]

[root@localhost docnascar]# lspci | grep -i ide
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1)
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)

Nice ... this is the same IDE of the other two threads 

Note: the drive is not connected
Did you want it connected?

Code:

[root@localhost docnascar]# ls -l /dev/sr*
ls: cannot access /dev/sr*: No such file or directory
[root@localhost docnascar]#

Yes, I think to know the answer ... you will not find /dev/sr0 or /dev/sr1 ... but your confirmation is necessary   

[docnascar]

Note: CD Drive is connected.

udevadm monitor scrolls frantically again.

Code:

[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

KERNEL[1329017245.880577] change   /devices/pci0000:00/0000:00:0d.0/ide1/1.1/block/hdd (block)
UDEV  [1329017245.889606] change   /devices/pci0000:00/0000:00:0d.0/ide1/1.1/block/hdd (block)
KERNEL[1329017245.895533] change   /devices/pci0000:00/0000:00:0d.0/ide1/1.1/block/hdd (block)
KERNEL[1329017245.907201] change   /devices/pci0000:00/0000:00:0d.0/ide1/1.1/block/hdd (block)
UDEV  [1329017245.916720] change   /devices/pci0000:00/0000:00:0d.0/ide1/1.1/block/hdd (block)

Code:

[docnascar@localhost ~]$ lspci | grep -i ide
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1)
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
[docnascar@localhost ~]$ ls -l /dev/sr*
ls: cannot access /dev/sr*: No such file or directory
[docnascar@localhost ~]$ ls /dev
adsp             fd0u1920    loop2               ptmx        sg0       tty22  tty46  ttyS3
audio            fd0u360     loop3               pts/        sg1       tty23  tty47  urandom
block/           fd0u720     loop4               ram@        shm/      tty24  tty48  vcs
bus/             fd0u800     loop5               ram0        snapshot  tty25  tty49  vcs1
cdrom@           fd0u820     loop6               ram1        snd/      tty26  tty5   vcs12
char/            fd0u830     loop7               ram10       st0       tty27  tty50  vcs2
console          fd1         lp0                 ram11       st1       tty28  tty51  vcs3
core@            full        lp1                 ram12       stderr@   tty29  tty52  vcs4
cpu/             fuse        lp2                 ram13       stdin@    tty3   tty53  vcs5
cpu_dma_latency  hda         lp3                 ram14       stdout@   tty30  tty54  vcs6
disk/            hda1        mapper/             ram15       tty       tty31  tty55  vcs7
dsp              hda2        mcelog              ram2        tty0      tty32  tty56  vcs8
dvd@             hda5        mem                 ram3        tty1      tty33  tty57  vcsa
fb@              hdb         mice                ram4        tty10     tty34  tty58  vcsa1
fb0              hdb1        mixer               ram5        tty11     tty35  tty59  vcsa12
fd@              hdd         net/                ram6        tty12     tty36  tty6   vcsa2
fd0              hidraw0     network_latency     ram7        tty13     tty37  tty60  vcsa3
fd0u1040         hpet        network_throughput  ram8        tty14     tty38  tty61  vcsa4
fd0u1120         hugepages/  null                ram9        tty15     tty39  tty62  vcsa5
fd0u1440         initctl|    nvidia0             random      tty16     tty4   tty63  vcsa6
fd0u1600         input/      nvidiactl           rawctl      tty17     tty40  tty7   vcsa7
fd0u1680         kmem        oldmem              root        tty18     tty41  tty8   vcsa8
fd0u1722         kmsg        parport0            rtc@        tty19     tty42  tty9   vga_arbiter
fd0u1743         log=        port                rtc0        tty2      tty43  ttyS0  watchdog
fd0u1760         loop0       ppp                 sequencer   tty20     tty44  ttyS1  zero
fd0u1840         loop1       psaux               sequencer2  tty21     tty45  ttyS2
[docnascar@localhost ~]$

[AS]

OK, may be can try to rebuild the initrd image, as suggested in a bug thread elsewhere, another few info are needed:

Code:

uname -r

and

Code:

grep ata /etc/modp*

and

Code:

lsinitrd | grep ata

[docnascar]

OK, may be can try to rebuild the initrd image, as suggested in a bug thread elsewhere, another few info are needed:

Code:

uname -r

and

Code:

grep ata /etc/modp*

and

Code:

lsinitrd | grep ata

No problem.

Code:

[docnascar@localhost ~]$ uname -r
2.6.38.8-pclos3.bfs
[docnascar@localhost ~]$ grep ata /etc/modp*
/etc/modprobe.conf:install scsi_hostadapter /sbin/modprobe sata_nv; /sbin/modprobe pata_amd; /bin/true
[docnascar@localhost ~]$ lsinitrd | grep ata
[docnascar@localhost ~]$

[AS]

OK, may be can try to rebuild the initrd image, as suggested in a bug thread elsewhere, another few info are needed:

Code:

uname -r

and

Code:

grep ata /etc/modp*

and

Code:

lsinitrd | grep ata

No problem.

Code:

[docnascar@localhost ~]$ uname -r
2.6.38.8-pclos3.bfs
[docnascar@localhost ~]$ grep ata /etc/modp*
/etc/modprobe.conf:install scsi_hostadapter /sbin/modprobe sata_nv; /sbin/modprobe pata_amd; /bin/true
[docnascar@localhost ~]$ lsinitrd | grep ata
[docnascar@localhost ~]$

The proper command to recreate the initrd should be (from a root terminal):

Code:

mkinitrd -v -f --preload=pata_amd  /boot/initrd-2.6.38.8-pclos3.bfs   2.6.38.8-pclos3.bfs

when completed, turn off your system, reconnect the CD/DVD unit, and reboot

but wait a moment for Old-Polack confirmation    Four eyes see can much better than two, may be I'm missing something ...

[Old-Polack]

I did it a little different here.

http://www.pclinuxos.com/forum/index.php/topic,102486.msg874580.html#msg874580

Same basic idea, but saved the old initrd image instead of overwriting it, and preloaded both the pata_amd and the sata_nv modules. Waiting for results.

[AS]

I did it a little different here.

http://www.pclinuxos.com/forum/index.php/topic,102486.msg874580.html#msg874580

Same basic idea, but saved the old initrd image instead of overwriting it, and preloaded both the pata_amd and the sata_nv modules. Waiting for results.

OK, a backup never hurt! 

docnascar:

Code:

mv initrd-2.6.38.8-pclos3.bfs.img initrd-2.6.38.8-pclos3.bfs.img-bak
mkinitrd -v -f --preload=pata_amd  --preload=sata_nv  /boot/initrd-2.6.38.8-pclos3.bfs   2.6.38.8-pclos3.bfs

turn of your system, reconnect the drive, reboot and you should be fine. 

BTW, success already reported here: http://www.pclinuxos.com/forum/index.php/topic,102486.msg874584.html#msg874584

[docnascar]

OK, a backup never hurt! 

Good thing.... Oops I did something wrong.

I had to do a cd /boot

And then I should have left well enough alone, but I was trying to understand OP's other commands and ran the last one which was suppose to return something but returned nothing.

[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>

You should see a whole bunch of rolling text as the process progresses. When you are returned to the prompt, the build should be complete.

Again, try the command;

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

Then I rebooted. After grub, Linux won't load and I get a black screen that says:

Code:

[Linux-bzImage, setup=0x3800, size=0x2358c0]
initrd (hd0,0)/boot/initrd.img

What did this do?

lsinitrd /boot/initrd.img |grep modprobe  

I didn't think an ls command would mess up something.


I'm guessing I should revert back to the backup and just use the two commands only you first posted. How do I do this?

My bad for trying to learn....  

[AS]

OK, a backup never hurt! 

Good thing.... Oops I did something wrong.

I had to do a cd /boot

It is correct. 

And then I should have left well enough alone, but I was trying to understand OP's other commands and ran the last one which was suppose to return something but returned nothing.

[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>

You should see a whole bunch of rolling text as the process progresses. When you are returned to the prompt, the build should be complete.

Again, try the command;

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

Then I rebooted. After grub, Linux won't load and I get a black screen that says:

Code:

[Linux-bzImage, setup=0x3800, size=0x2358c0]
initrd (hd0,0)/boot/initrd.img

Are you saying your system doesn't boot anymore ?

What did this do?

lsinitrd /boot/initrd.img |grep modprobe  

I didn't think an ls command would mess up something.

Only a listing of the initrd content, the "grep" filter out only the lines containing "modprobe"

I'm guessing I should revert back to the backup and just use the two commands only you first posted. How do I do this?

My bad for trying to learn....  

There is nothing bad in trying to learn.

So, are you unable to boot using the newly created initrd ?