At 9:00 PM -0500 11/9/98, Armen Babikyan wrote:
>At 5:10 PM -0800 11/9/98, Colin Wood wrote:
>>Richard Massey wrote:
>>> This is the 2nd (or 3rd) time CURRENT has crashed in the same place on
>>> startup (multiuser).
>>>
>>> Machine Q650 with 32MB
>>> Drive Quantum 230MB formatted as 210MB Root&User 20MBSwap. No MacOS
>>>partition.
>>> NetBSD 1.3H (GENERIC #87).
>>>
>>> Boot messages
>>> network initialisation immediatly followed by ...
>>> uvm_fault(0x153204, 0xffff0000, 0, 0x3) -> 0x1
>>> 	type 8, code [mmu,,ssw]:485
>>> Trap type 8, code = 0x485, v = 0xffff0004
>>> kernel program counter = 0xf7e2c
>>> kernel: mmu fault trap
>>> pid = 42, pc = 000F7E2C, ps = 2200, sfc = 1, dfc = 1
>>>
>>> Registers ...
>>>
>>> Kernel stack ...
>>>
>>> panic: MMU fault
>>> stopped in sh at _Debugger+0x6: unlk ab
>>>
>>> a reboot generates an automatic fsck and clean boot.
>>
>>what does a 'trace' at the debugger prompt show?
>>
>
>I seem to be getting the same thing (or something similar) on my quadra700
>under some circumstances using the 1.3.2 snapshot (including 1.3.2 kernel).
>
>i'm testing it out some more...i'll include a trace in another email later
>today (hopefully)
>

I just clean-installed a base 1.3.2 system using the non-SBC GENERIC kernel
that comes with 1.3.2, and it crashed when i attempted to mount -uw / so
that i could edit /etc/rc.conf

I'm not sure if this is my fault, but i got a panic: vm_page_alloc
and trace listed these:
_Debugger(
_panic(
_vm_page_alloc(
_vm_fault(
_trap(
faultstkadj(
_syscall(
_trap0(

what could be causing this panic?

thanks,

  - a