On Wednesdayen den 16 January 2002 08.57, Borsenkow Andrej wrote: > > Hi list, > > > > I'm running: > > > > mkinitrd -v /boot/initrd-2.4.17-5mdksmp-TEST.img 2.4.17-5mdksmp > > > > And nothing happens for a _very_ long time, it seems mkinitrd is > > comatized... > > > > this: > > > > time -p mkinitrd -v -f /boot/initrd-2.4.17-5mdksmp-TEST.img > > 2.4.17-5mdksmp > > > gives: > > > > real 39.36 > > user 31.78 > > sys 7.26 > > > > (strace log attached.) > > I recall similar problem when program statted fixed built-in device > names that resulted in devfsd attempting to load various modules. What > top says during mkinitrd run? > > BTW if you debug timing problem it is helpful to do strace -r to get > relative timestamps (to know how much which call takes). > > -andrej
I think it's fixed with mkinitrd-3.1.6-18mdk (haven't tried it yet...) -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | Oden Eriksson, Deserve-IT Networks, Jokkmokk, Sweden. | Mandrake Linux release 8.2 (Cooker) for i586 | Current uptime with kernel 2.4.17-5mdksmp: 22 hours 51 minutes | cpu0 @ 799.53 bm, fan 4560 rpm, temp +29°C | cpu1 @ 801.17 bm, fan 4560 rpm, temp +29.5°C
