On Sep 8, 2006, at 6:28 PM, Allen Briggs wrote:

> That sounds like a busted driver or something similar.  What network
> interface are you using?  Can you copy down the registers and the
> instruction that it trapped on?  A backtrace with 't' would also be
> useful to diagnose this.

The following is some of the output I get:

uvm_fault(0x266d60, 0x1ffa0000, 0, 0x1) -> 0xe
    type 8, code [mmu,,ssw]: 401f64d
trap type 8, code = 0x401f64d, v = 0x1ffa0010
kernel program counter = 0x1cea84
kernel: MMU fault trap
pid = 377, lid = 1, pc = 001CEA84, ps = 2100, sfc = 1, dfc = 1

dreg: 00000001 00002104 01010868 01021000 00002200 00000003 01021000  
00002200
areg: 0D132A48 010320D8 01021094 FFFFB87C 00000000 01010868 21040102  
FFFFB87C

Following this is the kernel stack and then:

panic: MMU fault
Stopped in pid 377.1 (ftp) at netbsd:cpu_Debugger+0x6: unlk a6

Then I typed 't' which gives:

cpu_Debugger(4012100,8,1020f68,1020f54,1f25b0) + 6

Was that the info you needed?

Bryan