>From: Leo Weppelman <leo@wau.mis.ah.nl>
>
>On Fri 28 Nov 1997, maximum entropy wrote:
>
>> Here's a traceback of the crash from the BOOTX kernel (typed in
>> manually, please pardon any typos):
>> 
>> panic: Bus error
>> Stopped at	_Debugger+0x6: unlk	a6
>> db> trace
>> _Debugger(0,dbdec,87eea,87dd4,0) + 6
>> _panic(87dd4,0,0,dbf68,abd80) + 40
>> _panictrap(0,74d,300022c,dbe44) + aa
>> _trap(0,74d,300022c) + 1e2
>> faultstkadj(a34d4,116000,dc000,3,0) + 0
>> _pmap_steal_memory(8000,0,dfffffc,abd80,dbf6c) + a0
>> _vm_page_bootstrap(dbf68,dbf64,19b22,0,dbfa8) + 54
>> _vm_mem_init(99eac,0,3,fffffffc,1000000) + 12
>> _main(dbfb4) + 2c
>
>Since this happens during the registering of free pages (at least it looks
>this way), the first thing I would try is adding the options '-s -S 4194304'
>to the loadbsd command line. This starts the kernel with 4Mb ST-RAM only.
>
>If this helps, either the detection of the RAM size or the handling of the
>amount is wrong. When it helps, some fiddling with the 's', 'S' and 'T' flags
>might provide some usable info ;-)

I tried "-s -S 4194304" as you suggested, and it still panics in
exactly the same way.  Other things I tried earlier in the weekend
include:

-s
-S 2097152
-S 4194304
-T 4194304

None of these seem to make a difference.  I think the detection is
working OK -- with "-D -w -t" the memory sizes look correct, and cpu
type is 8 which also looks right.

Is there anything else I should try?

Thanks,
entropy

--
entropy -- it's not just a good idea, it's the second law.