Aurelien Jarno wrote:
> Brian Szymanski a écrit :
>   
>> Martin Michlmayr wrote:
>>     
>>> * Carlo Segre <[email protected]> [2009-01-19 11:41]:
>>>   
>>>       
>>>> I am wondering if there is any 2.6.26 mipsel kernel suitable for
>>>> running  on an QEMU emulated machine?
>>>>     
>>>>         
>>> Yes, the Malta kernels can be used in QEMU.
>>>
>>> Aurelien: can you update your QEMU mips page
>>> http://www.aurel32.net/info/debian_mips_qemu.php to lenny/2.6.26?
>>>   
>>>       
>> FWIW, using the 2.6.18 kernels specified in the current page, I am
>> getting Error -3 while decompressing the initrd, as well as random
>> instruction bus errors, memory corruption, etc (it differs from boot to
>> boot, sometimes makes it to the installer, sometimes not) - one such
>> attempt (all proceeds normally up to this point):
>>
>> ...
>> RAMDISK: Compressed image found at block 0
>> VFS: Mounted root (cramfs filesystem) readonly.
>> Freeing unused kernel memory: 132k freed
>> Setting up filesystem, please wait ...
>> Error -3 while decompressing!
>> 802bb045(2247)->9fbf0000(4096)
>> Error -3 while decompressing!
>> 802bb90c(1563)->9fbf1000(4096)
>> Error -3 while decompressing!
>> 802bbf27(1913)->9fbf2000(4096)
>> Error -3 while decompressing!
>> 802bc6a0(1590)->9fbf3000(4096)
>> Error -3 while decompressing!
>> 802b9cd6(1894)->9fbf4000(4096)
>> Error -3 while decompressing!
>> 802ba43c(2182)->9fbf5000(4096)
>> Error -3 while decompressing!
>> 802bacc2(1962)->9fbf6000(4096)
>> Error -3 while decompressing!
>> 802bb46c(1848)->9fbf7000(4096)
>> Error -3 while decompressing!
>> 802bbba4(1697)->9fbf8000(4096)
>> Error -3 while decompressing!
>> 802bc245(1761)->9fbf9000(4096)
>> Error -3 while decompressing!
>> 802b5926(1676)->9fbfa000(4096)
>> Error -3 while decompressing!
>> 802b5fb2(1727)->9fbfb000(4096)
>> Error -3 while decompressing!
>> 802b6671(2246)->9fbfc000(4096)
>> Error -3 while decompressing!
>> 802b6f37(1825)->9fbfd000(4096)
>> Starting system log daemon: syslogd, klogd.
>> *** glibc detected *** double free or corruption (!prev): 0x2aec5a18 ***
>> Aborted
>> Segmentation fault
>> Segmentation fault
>> Bus error
>> Segmentation fault
>> Segmentation fault
>> Bus error
>> Segmentation fault
>> Segmentation fault
>> Segmentation fault
>> Segmentation fault
>> Segmentation fault
>> Segmentation fault
>> Segmentation fault
>> Segmentation fault
>> Bus error
>> Segmentation fault
>> Segmentation fault
>> Segmentation fault
>> Segmentation fault
>> Segmentation fault
>> Bus error
>> Bus error
>> Segmentation fault
>> Bus error
>> /build/buildd/cdebconf-0.114etch1/src/debconf.c:135 (main): Cannot
>> initialize debconf template database
>>
>> I am using qemu on ubuntu/amd64 (intrepid and hardy) but I don't think
>> the ubuntu qemu packages are so bad that it would explain this?
>>
>>     
>
> I am not able to reproduce those problems, even with the ubuntu/amd64
> package (installed on a Debian Lenny). Are you using the exact command
> line from this page to launch qemu?
>
>
>   
Sure enough, I wasn't using the exact command on your page. The
offending parameter (at least in terms of the Error -3's, which happen
every time, as opposed to the bus errors, etc. which were intermittent)
seems to be "-m 512" to increase available memory. Looks like the
thresshold for the problem is between "-m 507" and "-m 508". Is this a
known problem?

Thanks!

-- 
Brian Szymanski


Reply via email to