[BusyBox 0001381]: While Busybox 1.3.1 booted, 1.4.2 does not

[bugs at busybox.net]

A NOTE has been added to this issue. 
====================================================================== 
http://busybox.net/bugs/view.php?id=1381 
====================================================================== 
Reported By:                laxy
Assigned To:                BusyBox
====================================================================== 
Project:                    BusyBox
Issue ID:                   1381
Category:                   Other
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             06-05-2007 10:04 PDT
Last Modified:              06-08-2007 00:37 PDT
====================================================================== 
Summary:                    While Busybox 1.3.1 booted, 1.4.2 does not
Description: 
I've made a two-floppy linux system. First it had Busybox 1.3.1, then I
upgraded to 1.4.2 and used the exact same config (builtin shell
ash+utils).
It still boots on newer comps, but on my old laptop it won't anymore.

Here I point that it booted fine with 1.3.1.

I'm sure it's busybox, 'cause that's the only thing that changed. After
kernel boot it is supposed to start the init script but now it just hangs
after "released 128k of kernel memory".

Init script:

#/bin/sh
echo -n "."
/bin/mount -o remount,rw /
/bin/mount -a
export PATH=/bin;/sbin;/usr/bin
openvt 2 /bin/sh
openvt 3 /bin/sh
exec /bin/sh </dev/tty1 >/dev/tty1

For debugging I added that echo dot. The lappy does not get there. No
errors, just hangs.
====================================================================== 

---------------------------------------------------------------------- 
 vda - 06-08-07 00:37  
---------------------------------------------------------------------- 
Not enough info. What is your /bin/sh? (We have four shells). What is the
kernel command line? Does booting with init=/bin/ash work? etc... 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-05-07 10:04  laxy           New Issue                                    
06-05-07 10:04  laxy           Status                   new => assigned     
06-05-07 10:04  laxy           Assigned To               => BusyBox         
06-08-07 00:37  vda            Note Added: 0002465                          
======================================================================