Date: Fri, 31 Aug 2001 12:34:13 -0400 From: Andrew Gallatin <gallatin@cs.duke.edu> To: Peter Wemm <peter@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, freebsd-alpha@FreeBSD.org Subject: Re: cvs commit: src/sys/alpha/alpha pmap.c Message-ID: <20010831123412.A83980@grasshopper.cs.duke.edu> In-Reply-To: <200108310619.f7V6J8i47046@freefall.freebsd.org>; from peter@FreeBSD.org on Thu, Aug 30, 2001 at 11:19:08PM -0700 References: <200108310619.f7V6J8i47046@freefall.freebsd.org>
index | next in thread | previous in thread | raw e-mail
Peter Wemm [peter@FreeBSD.org] wrote:
> peter 2001/08/30 23:19:08 PDT
>
> Modified files:
> sys/alpha/alpha pmap.c
> Log:
> Same treatment as i386/isa/pmap.c - clean up some style to sync towards
> KSE diff.
>
> Revision Changes Path
> 1.64 +35 -40 src/sys/alpha/alpha/pmap.c
Hi Peter,
I hate to be the bearer of bad news, but my UP1000 crashes about 10
minutes into a buildworld with today's top of the tree kernel. After
backing out this pmap change, I'm able to make it further (its still
building).
The crash is:
fatal kernel trap:
trap entry = 0x2 (memory management fault)
faulting va = 0xfffffffe00480ca0
type = access violation
cause = load instructon
pc = 0xfffffc0000582da8
ra = 0xfffffc0000582ee4
sp = 0xfffffe0017bcdd98
usp = 0x11ffb3a8
curproc = 0xfffffe0017b3be40
pid = 29967, comm = as
panic: trap
panic
syncing disks... panic: bwrite: buffer is not busy???
panic
Uptime: 14m44s
dumping to dev ad2b, offset 2888944
<...>
From gdb:
#0 0xfffffc00004426a0 in dumpsys () at
../../../kern/kern_shutdown.c:486
#1 0xfffffc0000442214 in boot (howto=260) at
../../../kern/kern_shutdown.c:330
#2 0xfffffc0000442ab0 in panic (
fmt=0xfffffc00005e0891 "bwrite: buffer is not busy???")
at ../../../kern/kern_shutdown.c:623
#3 0xfffffc00004900cc in bwrite (bp=0xfffffe000b717c20)
at ../../../kern/vfs_bio.c:672
#4 0xfffffc0000490a08 in bawrite (bp=0x0) at
../../../kern/vfs_bio.c:981
#5 0xfffffc000040fa18 in spec_fsync (ap=0xfffffc0000684d98)
at ../../../fs/specfs/spec_vnops.c:405
#6 0xfffffc000040f10c in spec_vnoperate (ap=0x0)
at ../../../fs/specfs/spec_vnops.c:119
#7 0xfffffc0000546ce4 in ffs_sync (mp=0x2, waitfor=2,
cred=0xfffffffe00480000, p=0xfffffc0000684d98) at vnode_if.h:441
#8 0xfffffc00004a4510 in sync (p=0xfffffc0000684d98, uap=0x0)
at ../../../kern/vfs_syscalls.c:622
#9 0xfffffc0000441c1c in boot (howto=256) at
../../../kern/kern_shutdown.c:239
#10 0xfffffc0000442ab0 in panic (fmt=0xfffffc00005eef24 "trap")
at ../../../kern/kern_shutdown.c:623
#11 0xfffffc00005874e4 in trap (a0=18446744065124338848,
a1=18446739675669550072, a2=0, entry=2, framep=0xfffffe0017bcdc70)
at ../../../alpha/alpha/trap.c:630
#12 0xfffffc0000576e5c in XentMM ()
#13 0xfffffc0000582ee4 in pmap_remove_pages (pmap=0xfffffe00152eb4f0,sva=0,
eva=4398046511104) at ../../../alpha/alpha/pmap.c:1649
(kgdb)
At this point, gdb gets confused. I seem to remember from ddb that
an exit syscall was on the stack..
Drew
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010831123412.A83980>