Re: 2.4.0-test4 Out Of Memory ?!

From: Justin C. Ferguson (jferg-linux-kernel@lusArs.net)
Date: Thu Jul 27 2000 - 09:39:44 EST


When last we left our heros, they were speaking of:

         I tried recompiling with the CPU type set to 586 this morning,
and got the same results, as well as when I tried adding mem=224m on the
lilo boot command line. No go. :-< Anyone else have advice? I'm beginning
to wonder if maybe it isn't a processor or MoBo problem, but I don't want to
spend the money for a new one right now, so I'm hoping somebody will have some
other suggestions.

                                                                JF
                                                                
> I had a similar problem.
> I downgraded the CPU type to K5 and things started to work
> I have also heard that
> append="mem=xxxm" also helps to solve this kind of problem.
>
> Please let me know either works.
>
> Regards
> Phil Wilshire
> lineoISG ( formerly Zentropix )
>
> >
> > In part of my mission to figure out where the heck some of the memory
> > problems I've been having are coming from, I compiled a 2.4.0-test4 kernel
> > tonight. (Actually, I've compiled a lot of kernels tonight. But 2.4.0
> > was the only one where I saw this problem.) I did the usual, ran lilo,
> > and rebooted, and got:
> >
> > Uncompressing linux...
> > Booting linux...
> >
> > Out of memory
> >
> > -- System halted.
> >
> > This is all I ever get when I try to boot this kernel. The machine
> > has 224M of memory in it, so somehow I doubt it's out of memory.
> >
> > Machine specs: AMD K6-2/450, Asus P5A Motherboard, 128M memory, sym53c8xx
> > SCSI card, booting off an IDE hard drive, running SuSE 6.2.
> >
> > The memory in the system is brand new, I bought it because I'd been having some
> > weird memory problems under 2.2.x, and I just figured it was bad memory.
> > (Getting bus errors in netscape whenever it's memory spikes, if I try to create
> > a large image in gimp, gimp crashes, SIGILLs and SIGBUSes while compiling
> > large apps.) I'm seeing the exact same behavior with the new memory, however,
> > so I started looking for other causes. Anyone have suggestions? I've also
> > attached my kernel config below.
> >
> >
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/

-- 
    Justin Ferguson - Geek of All Trades - Technical Solutions Consultant
http://www.thedotin.net/jferg   <jferg@lusars.net> <JFerg at The Dot in .Net>
"...By the looks of it, this guy couldn't reproduce himself if he had an 
    installation wizard." -- Andreas Skau in the Scary Devil Monastery

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Mon Jul 31 2000 - 21:00:23 EST