BusyBox Bug and Patch Tracking
BusyBox
  

Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0001381 [BusyBox] Other crash always 06-05-07 10:04 06-16-07 16:23
Reporter laxy View Status public  
Assigned To BusyBox
Priority normal Resolution unable to reproduce  
Status closed   Product Version 1.4.x
Summary 0001381: 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.
Additional Information It still boots file Zool 1 for example..
Attached Files

- Relationships

- Notes
(0002465)
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...
 
(0002466)
laxy
06-08-07 04:27

what does (builtin shell ash) say about which shell I use?

Anyway sorry about this, I found it's a kernel bug, not busybox.
Sent a bug report to the kernel mailing list, if you're interested it's here:
http://lkml.org/lkml/2007/6/7/245 [^]

That post should answer your new questions too..
 

- 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
06-08-07 04:27 laxy Note Added: 0002466
06-16-07 16:23 vda Status assigned => closed
06-16-07 16:23 vda Resolution open => unable to reproduce


Copyright © 2000 - 2006 Mantis Group
Powered by Mantis Bugtracker