udevd cpu high usage <SOLVED>

[docnascar]

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

Wow, do you live on here? LOL

Yes, to answer the question.

I do have a log of the rebuild, but its on my linux pc that won't boot. Saved it before the reboot... LOL

[docnascar]

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

So, since this originally returned nothing, Maybe that should have been a clue and I should not have rebooted?

[AS]

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

Wow, do you live on here? LOL

Yes, to answer the question.

I do have a log of the rebuild, but its on my linux pc that won't boot. Saved it before the reboot... LOL

I think it's possible to specify the the initrd= parameter on grub parameters line, but need to check about the exact syntax ...
wait a moment ...

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

So, since this originally returned nothing, Maybe that should have been a clue and I should not have rebooted?

need to be investigated ...  a wrong initrd name on the mkinitrd commands will result in the same output ...

[Old-Polack]

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

So, since this originally returned nothing, Maybe that should have been a clue and I should not have rebooted?

Bingo!

[docnascar]

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

So, since this originally returned nothing, Maybe that should have been a clue and I should not have rebooted?

Bingo!

Told you I was learning! 

[Old-Polack]

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

So, since this originally returned nothing, Maybe that should have been a clue and I should not have rebooted?

Bingo!

Told you I was learning! 

Sorry, the devil made me do that! 

Don't worry, it's entirely fixable, from the liveCD.

Rule one... stay focused.

Do you know which partition is the / partition that currently won't boot?

[docnascar]

Code: [Select]

[Linux-bzImage, setup=0x3800, size=0x2358c0]
initrd (hd0,0)/boot/initrd.img
I think its 0,0 according to the error during boot.

I do have two hard drives, the other has my home on it.

I don't have a current LIVECD (honestly, not sure if I have any somewhat current livecd; i'll have to dig around my man-cave). My grub has an older kernel listed. Can I boot to it to at least get to the terminal to fix my booboo? From Grub list;  "Linux with kernel 2.6.33.5-pclos1.bfs"

[AS]

Old-Polack,

adding this option at grub parameters:

Code: [Select]

initrd=initrd-2.6.38.8-pclos3.bfs.img-bak
shouldn't work ?

[Old-Polack]

Old-Polack,

adding this option at grub parameters:

Code: [Select]

initrd=initrd-2.6.38.8-pclos3.bfs.img-bak
shouldn't work ?

If it saved properly, yes it should.

[Old-Polack]

Code: [Select]

[Linux-bzImage, setup=0x3800, size=0x2358c0]
initrd (hd0,0)/boot/initrd.img
I think its 0,0 according to the error during boot.

I do have two hard drives, the other has my home on it.

I don't have a current LIVECD (honestly, not sure if I have any somewhat current livecd; i'll have to dig around my man-cave). My grub has an older kernel listed. Can I boot to it to at least get to the terminal to fix my booboo? From Grub list;  "Linux with kernel 2.6.33.5-pclos1.bfs"

Use it!

[docnascar]

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 initrd.img.old
[docnascar@localhost boot]$




[docnascar]

Interesting data point. There is No loop with the older kernel.

Code: [Select]

[docnascar@localhost boot]$ 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 boot]$ uname -r
2.6.33.5-pclos1.bfs


[AS]

Back in linux using the older kernel (2.6.33.5).

What's next to recover?

[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 initrd.img.old
[docnascar@localhost boot]$

Actually it was my fault, lost the .img suffix 

docnascar,

Code: [Select]

mv /boot/initrd-2.6.38.8-pclos3.bfs  /boot/initrd-2.6.38.8-pclos3.bfs.img
before to reboot, retry:

Code: [Select]

lsinitrd /boot/initrd-2.6.38.8-pclos3.bfs.img  |  grep modprobe

[docnascar]

Ahh good catch!

Code: [Select]

[root@localhost boot]# mv /boot/initrd-2.6.38.8-pclos3.bfs  /boot/initrd-2.6.38.8-pclos3.bfs.img
[root@localhost boot]# lsinitrd /boot/initrd-2.6.38.8-pclos3.bfs.img  |  grep modprobe
-rwxr-xr-x   1 root     root        26832 Jun 13  2011 bin/modprobe
-rwxr-xr-x   1 root     root        24332 Jun 13  2011 lib/libmodprobe.so.0.0.0
lrwxrwxrwx   1 root     root           25 Feb 12 11:19 lib/libmodprobe.so.0 -> /lib/libmodprobe.so.0.0.0
init
modprobe -q pata_amd
modprobe -q sata_nv
modprobe -q ext3
modprobe -q ide-core
modprobe -q ide-disk
modprobe -q ide-gd_mod
modprobe -q scsi_mod
modprobe -q sd_mod
modprobe -q libata
modprobe -q amd74xx
modprobe -q pata_acpi
modprobe -q ide-pci-generic
modprobe -q ata_generic
modprobe -q ide_generic
[root@localhost boot]# ^C
[root@localhost boot]#

Shall I reboot?

[AS]

Yes!