[BusyBox] Re: busybox init memory problems
Erik Andersen
andersen at lineo.com
Fri Jun 2 16:39:28 UTC 2000
On Fri Jun 02, 2000 at 10:40:25PM +1000, bug1 wrote:
> Erik Andersen wrote:
> >
> > On Thu Jun 01, 2000 at 05:30:41AM +1000, bug1 wrote:
> > > When i try and use busybox (0.44pre) init during boot i get a message
> > > "Sorry, your computer does not have enough memory"
> > >
> > > I tried to do a bit of debugging, i put a line in displaying how much
> > > memory it detected just before it goes into the endless loop, it detects
> > > 31 (i assume KB) of memmory, i have 128MB.
> > >
> > > Im trying to use 2.4.0-test1 with it, is this a known problem ?
> >
> > Hmm. That is wierd. I have not yet tried it with 2.4.x yet (I have tried it
> > with the pre series and made a few minor adjustments to accomodate the kernel
> > changes). The mechanism I use to detect memory is sysinfo(2). I wonder if
> > that has broken in the recent kernels? If you comment out the memory check
> > completely, does the boot process complete? What does busybox free show and
> > what does 'cat /proc/meminfo' show after booting?
> >
> > -Erik
> >
> > --
> > Erik B. Andersen email: andersen at lineo.com
> > --This message was written using 73% post-consumer electrons--
>
> I comment out the memmory check part and it continues ok.
>
> busybox free shows only 7 free, /proc/meminfo shows the correct ammount.
>
> I could be doing something wrong, ill download the cvs version of
> busybox and have a go with a clean copy.
Yipe. The fact that there is a discrepancy between the reported value from
free (i.e. the return value of sysinfo(2)) and the contents /proc/meminfo means
there is definately a bug in 2.4.0-test1.
Want to get some glory as a kernel hacker by tracking this one down, or want me
to try?
-Erik
--
Erik B. Andersen email: andersen at lineo.com
--This message was written using 73% post-consumer electrons--
More information about the busybox
mailing list