I see the same thing on a 3/110 with the miniroot and the install kernels.  If I put in the Generic kernel the problems goes away, but the machine is unusably slow (only 4 MB - anyone have a memory expansion that will work in a 3/110?).  I am working on trying to compile a custom kernel, but am having disk error problems as well as lack of time problems...

James L. Wiley
Mgr. Client/Server Computing
Information Resources
Tarleton State University

Every imaginable disclaimer applies.


-----Original Message-----
From: port-sun3-owner@netbsd.org [mailto:port-sun3-owner@netbsd.org]On
Behalf Of Adam Kropelin
Sent: Monday, November 18, 2002 8:15 PM
To: port-sun3@netbsd.org
Subject: 1.6 vm_fault on ie packet rx


Trying to install 1.6 on my 3/280 I get the below vm_fault soon after I
ifconfig ie0 (onboard). It appears to happen on packet rx. The quoted fault
is from the netbsd.RAMDISK kernel (netbooted) but it happens with the
miniroot as well. 1.5.3 is happy so this seems to be a new issue with 1.6.

I apologize for being something of a NetBSD newbie...in the Linux world we
have a tool to 'symbolize' dumps like this. If I need to do that to make it
useful for you, hit me with a clue-stick and I'll get to it...

--Adam

vm_fault(0xe0c9598, 0x0, 0x2, 0) -> 0xd
trap type=0x8, code=0x105, v=0x0
pid = -1, pc = 0E0A4166, ps = 2300, sfc = 1, dfc = 1
Registers:
             0        1        2        3        4        5        6
7
dreg: 0FA5BE74 0000FFFF 0000F9C0 00000001 00000000 000000F9 000000F9
000000F9
areg: 0FA5BE74 0FA5BE82 0E176434 0E176000 0E0EB620 00000000 0FA5BE84
0DFFFFFC

Kernel stack (0FA5BD4C):
A5BD4C: 0E094A8C 0FA5BD9C 00000080 0000F9C0 00000001 00000000 000000F9
000000F9
A5BD6C: 000000F9 0E176434 0E176000 0E0EB620 00000000 00000000 00000000
0FA5BE84
A5BD8C: 0E0040EC 00000008 00000105 00000000 0FA5BE74 0000FFFF 0000F9C0
00000001
A5BDAC: 00000000 000000F9 000000F9 000000F9 0FA5BE74 0FA5BE82 0E176434
0E176000
A5BDCC: 0E0EB620 00000000 0FA5BE84 0DFFFFFC 00000000 23000E0A 4166B008
3EEC0105
A5BDEC: 24000C81 00000000 00000000 00000000 263C0000 0E0A416E 0E0A416C
0E0A416A
A5BE0C: 0E0A415C 0000FF0B 000F1755 00002400 0FA5BE50 00000000 00000000
80200000
A5BE2C: 00000000 00000000 0000000E 0FA5BE2C 00000001 00000003 00000000
00000000
A5BE4C: 0E0EFF60 FFFF0002 0FFC7FE8 0E176000 0E0EB620 0E0A63EE 0FA5BE8C
0E176734
A5BE6C: 0E176434 00000001 FFFFFFFF FFFF00A0 C91E87EB 08004628 0FA5BEA8
0E0A3DA0
A5BE8C: 0E176000 00000000 00001050 00000003 00000000 0E176000 00000040
0FA5BEC0
A5BEAC: 0E0A3C52 0E176000 00000000 0E15FED0 0F23A740 0FA5BED8 0E0941A2
0E176000
A5BECC: 00000000 00000000 0E0E1470 0FA5BF24 0E00448E 00000000 FFFFFFFC
0FA58000
A5BEEC: 0FA5BF1C 20000E00 460A006C 0E03FB26 0F23A740 0F232004 00000000
00000064
A5BF0C: 0F23A740 00000000 0E039FAE 0E0E1570 3DD81457 000F1B32 0FA5BF44
0E03F6AC
A5BF2C: 0F23A740 0F232000 3DD81457 0000001E 00000000 0E15DB10 0FA5BFA0
0E06354E
panic: MMU fault
syncing disks...
vm_fault(0xe0c9598, 0x0, 0x1, 0) -> 0xd
trap type=0x8, code=0x145, v=0x108
panic: trap during panic!