Re: [Cooker] mkinitrd-3.1.6-17mdk is comatized...
Hi ! On Thu, Jan 17, 2002 at 12:19:00PM +0100, Guillaume Cottenceau wrote: > Oden Eriksson <[EMAIL PROTECTED]> writes: > > > 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... > > Anyone else experiencing this problem ? Yes, already told that this is happening to me, but failed to notice that with the latest version it seems to be getting worse and that the load also is much higher than with 16mdk (I skipped/missed 17mdk). > Can you also check if stating of filesystems is reasonably quick > (do "df" and check if speed is normal). df is as fast as usual on both my desktop and laptop system. Regards, Reinhard -- Software-Engineer, Developer for Embedded Devices Project: HyperPen Tablet USB Driver for Linux GnuPG Public Key available on request msg51401/pgp0.pgp Description: PGP signature
Re: [Cooker] mkinitrd-3.1.6-17mdk is comatized...
Oden Eriksson <[EMAIL PROTECTED]> writes: > 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... Anyone else experiencing this problem ? Can you also check if stating of filesystems is reasonably quick (do "df" and check if speed is normal). -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
Re: [Cooker] mkinitrd-3.1.6-17mdk is comatized...
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
Re: [Cooker] mkinitrd-3.1.6-17mdk is comatized...
- Original Message - From: "Chmouel Boudjnah" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 16, 2002 10:38 AM Subject: Re: [Cooker] mkinitrd-3.1.6-17mdk is comatized... > Oden Eriksson <[EMAIL PROTECTED]> writes: > > > 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 > > sh -x mkinitrd -v -f /boot/initrd-2.4.17-5mdksmp-TEST.img 2.4.17-5mdksmp > > give ? Output of this is to huge for this list, I sent it directly to Chmouel.
Re: [Cooker] mkinitrd-3.1.6-17mdk is comatized...
Oden Eriksson <[EMAIL PROTECTED]> writes: > 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 sh -x mkinitrd -v -f /boot/initrd-2.4.17-5mdksmp-TEST.img 2.4.17-5mdksmp give ? -- http://www.linux-mandrake.com/en/club/
RE: [Cooker] mkinitrd-3.1.6-17mdk is comatized...
> > 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
