"page fault" panices after upgrading 5.4-RELEASE to 6.0-RELEASE/6.1-PRERELEASE

Pavel Gubin pg at ie.tusur.ru
Thu Mar 9 06:14:36 UTC 2006


On Mon, Mar 06, 2006 at 02:03:19AM -0500, Kris Kennaway wrote:

> Well, that's what you posted, but it was nonsensical.  However, gdb is
> sometimes confused about stack traces, which is why I asked for a
> trace from DDB instead.

  So, I've compiled in DDB and after two days uptime got another panic:

====
panic: vm_fault: fault on nofault entry, addr: cafd2000
KDB: stack backtrace:
kdb_backtrace(100,c1dd4480,0,2,cafd2000) at 0xc05093b5 = kdb_backtrace+0x29
panic(c0660e20,cafd2000,c1dd4480,b,c1d9fa80) at 0xc04f0eb8 = panic+0xa8
vm_fault(c0c43000,cafd2000,2,0,c1dd4480) at 0xc05cd34c = vm_fault+0x16c
trap_pfault(cc7e2af0,0,cafd2041) at 0xc0616856 = trap_pfault+0x182
trap(8,28,28,3c959200,c1ed6838) at 0xc06164c1 = trap+0x2fd
calltrap() at 0xc0605dba = calltrap+0x5

--- trap 0xc, eip = 0xc0525178, esp = 0xcc7e2b30, ebp = 0xcc7e2b3c ---

putc(7d,c1ed6838,0,0,0) at 0xc0525178 = putc+0x164
pppasyncstart(c25cf400,c1e7210c,0,c2590bfa,3c0) at 0xc258d634 = pppasyncstart+0xa8
pppoutput(c1e72000,c35ad700,cc7e2bf0,c2009630,0) at 0xc258bbc8 = pppoutput+0x1e8
ip_output(c35ad700,0,cc7e2bec,1,0,0) at 0xc057b131 = ip_output+0x869
ip_forward(c35ad700,0) at 0xc057a59c = ip_forward+0x284
ip_input(c35ad700) at 0xc057910b = ip_input+0x5bb
netisr_processqueue(c06ab198) at 0xc056007f = netisr_processqueue+0x9f
swi_net(0) at 0xc056027a = swi_net+0xf2
ithread_loop(c1d9a500,cc7e2d38) at 0xc04dbe1d = ithread_loop+0x159
fork_exit(c04dbcc4,c1d9a500,cc7e2d38) at 0xc04db0a4 = fork_exit+0x70
fork_trampoline() at 0xc0605e1c = fork_trampoline+0x8

--- trap 0x1, eip = 0, esp = 0xcc7e2d6c, ebp = 0 ---

KDB: enter: panic
[thread pid 27 tid 100025 ]
Stopped at      0xc0509437 = kdb_enter+0x2b:    nop
db>
===

-- 
Pavel Gubin
TUSC&R / Industrial Electronics dept / System Administrator
2:5005/14 at fidonet / Phone +7-3822-423067 / ICQ 28835566


More information about the freebsd-stable mailing list