It is code in the kernel bootloader, which is a patch, and which just uses standard valloc calls or some such, it is more likely to be an issue with a memory hole or mismatch between what the kernel detects and what is really there in the low memory areas or something like that, if it even is a memory problem, which maybe it isn't. It is just as likely I guess that the kernel is freezing up reading the media as it is that it is failing to allocate memory. -Tom
On Sat, 5 Jul 2003, Oliver Martin wrote: > Date: Sat, 05 Jul 2003 23:38:50 +0200 > From: Oliver Martin <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Followup-To: [EMAIL PROTECTED] > Subject: Re: [tomsrtbt] System freeze at boot > > Tom suggested using "bz2bzImage mem=16M" at the lilo prompt. Thanks for > the tip, but it didn't make any difference. Anyways, I found out about > PAUD and it seems to be perfectly suited for what I want to do, so from > the practical point of view, a solution isn't required any more. Yet > from the technical aspect, I'm still interested in the topic. Which part > of the system actually does the bzip2 decompression? Is it some part of > the lilo boot code? If yes, does the stock lilo do that or is it somehow > patched? On which factors does it depend that can make it fail? I > haven't extensively tested the RAM yet, I'll do that tomorrow. But I > haven't experienced strange behavior other than that, so I doubt it's > bad RAM. > -- > Oliver >
