[Voyage-linux] Slow startup of voayge 0.5.2

Beat Meier (spam-protected)
Wed Jul 16 06:10:02 HKT 2008


Hello

I've notice that starting voyage-0.5.2 on warp needs 120sec. where old 
system (0.2.pre) ok
very old system :-) needed 45sec.
What I have noticed is that for example disks are scanned very long 
about 20sec. and waited for irq timeout
or something similar. Messages like:

hda: CF 1GB, ATA DISK drive
hda: sc1200_set_xfer_mode(MW DMA 2)
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: IRQ probe failed (0xffffbffa)
hdc: IRQ probe failed (0xffffbffa)
hdc: no response (status = 0x0a), resetting drive
hdc: IRQ probe failed (0xffffbffa)
hdc: no response (status = 0x0a)
hdd: IRQ probe failed (0xffffbffa)
hdd: IRQ probe failed (0xffffbffa)
hdd: no response (status = 0x0a), resetting drive
hdd: IRQ probe failed (0xffffbffa)
hdd: no response (status = 0x0a)
hdc: IRQ probe failed (0xffffbffa)
hdc: IRQ probe failed (0xffffbffa)
hdc: no response (status = 0x0a), resetting drive
hdc: IRQ probe failed (0xffffbffa)
hdc: no response (status = 0x0a)
hda: max request size: 128KiB
hda: 1981728 sectors (1014 MB) w/1KiB Cache, CHS=1966/16/63, DMA
 hda: hda1 hda2 hda3 
hda4                                                                                                                                    


Is this because usage of udev??
Without udev the /dev/hda ... /dev/hdc were in /dev and there was no 
long timeout.
My question now:
How can I disable udev and have the same behaviour as the old one?
What is the advantge of using udev?
Ok in a pc environment could be, but on embededd systems I don't know if 
this make sense.

What are the meanings?

BTW: I really have no idea of udev and I will now search the net :-)
but thought to put a message here to see if other people have the same 
"problem".


Greetings

Beat




More information about the Voyage-linux mailing list