Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 2 Oct 2002 14:16:03 -0700 (PDT)
From:      David Wolfskill <david@catwhisker.org>
To:        current@freebsd.org
Subject:   panic (Fatal trap 12: page fault while in kernel mode) today
Message-ID:  <200210022116.g92LG3ec012100@bunrab.catwhisker.org>

next in thread | raw e-mail | index | archive | help
Saw Alfred's commit to un-break -CURRENT, did likewise locally,
built today's -CURRENT, and an attempted multi-user boot panics:

...
Starting nfsd.
Updating motd.
Starting ntpd.
Configuring syscons: blanktime.
Starting sshd.
Expensive timeout(9) function: 0xc02bea10(0xc406a000) 0.006791320
g_dev_clone(tty)
Expensive timeout(9) function: 0xc02bea10(0xc406a000) 0.006783223
Initial i386 initialization:.
Additional ABI support:.
Local package initialization:g_post_event(1, 0, 0, 0xc439a300, 0)
Eg_do_event(0xc43730c0) 1 m:0 g:0 p:0xc439a300 c:0 - 
EV_NEWx_PROVIDER(md10)
aes_taste(AES,md10)
pensive timeout(9) function: 0xc02125a0(0) 0.008110381


Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic.id = 00000000
fault virtual address   = 0x110
fault code              = supervisor read, page not present
instruction pointer     = 0x8:0xc0153d95
stack pointer           = 0x10:0xd6963ba8
frame pointer           = 0x10:0xd6963bc0
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 2 (g_event)
kernel: type 12 trap, code=0
Stopped at      mdopen+0x45:    movl    0x110(%ecx),%eax
db> tr
mdopen(c4393000,3,0,0,0) at mdopen+0x45
g_disk_access(c439a300,1,0,0,0) at g_disk_access+0xf8
g_access_rel(c4367b80,1,0,0,a) at g_access_rel+0x2af
g_aes_taste(c03b1260,c439a300,0,98,0) at g_aes_taste+0xc8
g_do_event(c43730c0,0,c036eba0,f3,66666667) at g_do_event+0x229
one_event(d6963d08,c01a9425,c03b198c,0,4c) at one_event+0x1e6
g_run_events(c03b198c,0,4c,c036f04f,a) at g_run_events+0x15
g_event_procbody(0,d6963d48,c0371bd1,34d,0) at g_event_procbody+0x25
fork_exit(c01a9400,0,d6963d48) at fork_exit+0xa7
fork_trampoline() at fork_trampoline+0x1a
--- trap 0x1, eip = 0, esp = 0xd6963d7c, ebp = 0 ---
db> show pcpu 0 
cpuid        = 0
curthread    = 0xc15838f0: pid 2 "g_event"
curpcb       = 0xd6963da0
fpcurthread  = none
idlethread   = 0xc1582a90: pid 12 "idle: cpu0"
currentldt   = 0x28
spin locks held:
db> show pcpu 1
cpuid        = 1
curthread    = 0xc15829c0: pid 11 "idle: cpu1"
curpcb       = 0xd692dda0
fpcurthread  = none
idlethread   = 0xc15829c0: pid 11 "idle: cpu1"
currentldt   = 0x28
spin locks held:
db> show lockedvnods
Locked vnodes
db> show locks
exclusive sleep mutex Giant r = 0 (0xc03b7520) locked @ /usr/src/sys/vm/vm_fault.c:206
exclusive sx GEOM topology r = 0 (0xc03b17e0) locked @ /usr/src/sys/geom/geom_event.c:224
db> 

Single-user seems to boot OK, but trying to get a dump is less useful:

db> panic
panic: from debugger
cpuid = 0; lapic.id = 00000000
Debugger("panic")


Fatal trap 3: breakpoint instruction fault while in kernel mode
cpuid = 0; lapic.id = 00000000
instruction pointer     = 0x8:0xc032ad85
stack pointer           = 0x10:0xd696391c
frame pointer           = 0x10:0xd6963928
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = IOPL = 0
current process         = 2 (g_event)
Stopped at      mdopen+0x45:    movl    0x110(%ecx),%eax
db> 


This is on my SMP (2x866 PIII) build machine; I added GEOM yesterday
(and built and ran -CURRENT OK then).

I just reset the machine, booted to single-user (same kernel, built with
sources updated via CVSup at 0347 PDT (7 hrs. west of GMT) from
cvsup13), and am doing a "fsck -p" (which just finished as I was typing).

Some of the programs being run in the mutli-user startup were compiled
under -STABLE:  I run both -CURRENT and -STABLE (on diffeent slices) on
the machine, but /usr/local is shared between them, and build all the
ports under -STABLE (except that ebery once in a while, I go ahead and
upgrade X11 under -CURRENT).

Anyway, this appears fairly repeatable, so if someone would like
me to try some thing, I'm willing.

Oh, and booting the previous kernel seems OK:

freebeast(5.0-C)[1] uname -a
FreeBSD freebeast.catwhisker.org 5.0-CURRENT FreeBSD 5.0-CURRENT #9: Tue Oct  1 15:40:23 PDT 2002     root@freebeast.catwhisker.org:/common/S4/obj/usr/src/sys/FREEBEAST  i386
freebeast(5.0-C)[2] tail /var/log/cvsup-history.log
Oct  1 00:00:00 freebeast newsyslog[1077]: logfile turned over
CVSup begin from cvsup14.freebsd.org at Tue Oct  1 03:47:02 PDT 2002
CVSup begin from cvsup13.freebsd.org at Tue Oct  1 03:47:05 PDT 2002
CVSup ended from cvsup13.freebsd.org at Tue Oct  1 03:54:41 PDT 2002
CVSup begin from cvsup14.freebsd.org at Wed Oct  2 03:47:03 PDT 2002
CVSup begin from cvsup13.freebsd.org at Wed Oct  2 03:47:06 PDT 2002
CVSup ended from cvsup13.freebsd.org at Wed Oct  2 04:31:07 PDT 2002
freebeast(5.0-C)[3]

Cheers,
david
-- 
David H. Wolfskill				david@catwhisker.org
To paraphrase David Hilbert, there can be no conflicts between the
discipline of systems administration and Microsoft, since they have
nothing in common.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200210022116.g92LG3ec012100>