Hi,

  Environment:

   FreeBSD xphome.home.ady.ro 5.0-CURRENT FreeBSD 5.0-CURRENT #0:
   Sun Apr 21 10:39:36 EEST 2002 i386

   XFree86-4.2.0_1,1 (3dfx Velocity 100 graphics card)
   gnome-1.4.1b2_2 + sawfish-gnome-1.0.1
   linux_base-6.1_1
   linux-netscape-communicator-4.79

  Panicstring: bremfree: bp 0xc77fb678 not locked

  How-to-repeat: launch linux-netscape while in X11

 I've attached the stack trace from gdb'ing on the debug kernel file.
I'll keep the core (256Mb) around for a few hours, tell me if you need
further info.

  Side note: are those "lock order reversal" meesages something to worry
about ?

 Happy panicing,
 Ady (@freebsd.ady.ro)
_______________________________________________________________________
| Programming in BASIC causes brain damage.                           |
|   (Edsger Wybe Dijkstra)                                            |
Script started on Sun Apr 21 15:13:31 2002
GNU gdb 4.18

Copyright 1998 Free Software Foundation, Inc.

GDB is free software, covered by the GNU General Public License, and you are

welcome to change it and/or distribute copies of it under certain conditions.

Type "show copying" to see the conditions.

There is absolutely no warranty for GDB.  Type "show warranty" for details.

This GDB was configured as "i386-unknown-freebsd"...

IdlePTD at phsyical address 0x00434000

initial pcb at physical address 0x0031f3a0

panicstr: bremfree: bp 0xc77fb678 not locked

panic messages:

---

panic: recurse



syncing disks... panic: bremfree: bp 0xc77fb678 not locked

Uptime: 4m30s

Dumping 255 MB

ata0: resetting devices .. done

 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240

---

#0  doadump () at /usr/src/sys/kern/kern_shutdown.c:213

213             dumping++;

(kgdb) bt

#0  doadump () at /usr/src/sys/kern/kern_shutdown.c:213

#1  0xc019ce78 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:346

#2  0xc019d021 in panic (fmt=0xc02bdf5d "bremfree: bp %p not locked")

    at /usr/src/sys/kern/kern_shutdown.c:490

#3  0xc01cdd0d in bremfree (bp=0xc77fb678) at /usr/src/sys/kern/vfs_bio.c:619

#4  0xc01cf403 in vfs_bio_awrite (bp=0xc77fb678)

    at /usr/src/sys/kern/vfs_bio.c:1593

#5  0xc0178204 in spec_fsync (ap=0xcecfd95c)

    at /usr/src/sys/fs/specfs/spec_vnops.c:403

#6  0xc0177df1 in spec_vnoperate (ap=0xcecfd95c)

    at /usr/src/sys/fs/specfs/spec_vnops.c:121

#7  0xc024d105 in ffs_sync (mp=0xcdf41200, waitfor=2, cred=0xc7765980, 

    td=0xc02eb300) at vnode_if.h:441

#8  0xc01dbfb7 in sync (td=0xc02eb300, uap=0x0)

    at /usr/src/sys/kern/vfs_syscalls.c:1224

#9  0xc019caba in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:254

#10 0xc019d021 in panic (fmt=0xc02ba6c8 "recurse")

    at /usr/src/sys/kern/kern_shutdown.c:490

#11 0xc01b47a8 in witness_lock (lock=0xced36834, flags=8, 

    file=0xc02b3c40 "/usr/src/sys/kern/kern_descrip.c", line=1114)

    at /usr/src/sys/kern/subr_witness.c:533

#12 0xc0195766 in _mtx_lock_flags (m=0xced36834, opts=0, 

    file=0xc02b3c40 "/usr/src/sys/kern/kern_descrip.c", line=1114)

    at /usr/src/sys/kern/kern_mutex.c:314

---Type <return> to continue, or q <return> to quit---

#13 0xc0187203 in falloc (td=0xcec6ea3c, resultfp=0xcecfdaa0, 

    resultfd=0xcecfdaa8) at /usr/src/sys/kern/kern_descrip.c:1114

#14 0xc0187e3f in fdcheckstd (td=0xcec6ea3c)

    at /usr/src/sys/kern/kern_descrip.c:1532

#15 0xc018b306 in execve (td=0xcec6ea3c, uap=0xcecfdcdc)

    at /usr/src/sys/kern/kern_exec.c:372

#16 0xcea21aff in ?? ()

#17 0xc028e69b in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, 

      tf_edi = -1077950728, tf_esi = 145923594, tf_ebp = -1077950768, 

      tf_isp = -825238156, tf_ebx = -1077950728, tf_edx = 151214976, 

      tf_ecx = -1077950612, tf_eax = 11, tf_trapno = 12, tf_err = 2, 

      tf_eip = 685394187, tf_cs = 31, tf_eflags = 582, tf_esp = -1077950784, 

      tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1022

#18 0xc0281a0d in syscall_with_err_pushed ()

Cannot access memory at address 0xbfbfc6d0.

(kgdb) q


Script done on Sun Apr 21 15:13:38 2002

Reply via email to