>> I'm having trouble getting this through to the list (bounces with 
>> "no route to host netbsd.org" so I'll try sending to you instead. ;)
>Weird.... I have it cc'd now, let's see.

Well your CC worked, mine evidently didn't. ;)

>> Panic: MMU Fault
>> 
>> _Debugger(8,1dcfda8,7fb9c,7fa07,6) + 6
>> _panic(7fa07,0,8,1878c,585800) + 40
>> _panictrap(8.402a64d,2,1dcfe00) + b0
>> _trap(8,402a6fd,2) + 422
>> _addrerr(?)
>> _vm_page_copy(145530,144770,a000,88,3) + 120
>> _vm_fault(584500,a000,3,0) + 4a0
>> _trap(8,4020709,b054) + 384
>> _addrerr() + 120
>Is there anything below this?

No, that was the whole trace. Sometimes it doesn't even give that much,
just the first 4 lines.

>For the Falcon, I somehow suspect the DMA controller. Did you try running
>NetBSD from the IDE drive? I don't know if this is an option for you. If

Not really - me IDE is only 65Mb and is full of the TOS stuff since my
SCSI drive got cleard for NetBSD. ;) At most I could move my swap
partition to the IDE drive (would it work from there?)

>this helps, it makes sense to go diff-ing the SCSI-driver. I can also try
>building a 1.2E kernel with an 1.1 SCSI-driver.

I'm tempted to suspect that too, since most times it happens there
is intense disk activity going on - e.g. compiling something, or
very annoyingly while fsck is fixing the filesystem after the last crash.

Using the 1.1 SCSI-driver sounds attractive to me since I never
had problems with that one. If it didn't take 16 hours (assuming no
crashes) to build my own kernels I'd experiment a lot more myself.

>> (BTW, would it be possible for someone to update the current.tar.gz in
>I'll do so ASAP. My Hades is currently building a snapshot - I'm having
>trouble with ps too ;-) When this is up and running, I'll regenerate the
>current.tar.gz file.

Great! :)

Dan