From owner-freebsd-current  Mon Feb 16 14:53:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id OAA25486
          for freebsd-current-outgoing; Mon, 16 Feb 1998 14:53:04 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25404
          for <current@freebsd.org>; Mon, 16 Feb 1998 14:52:42 -0800 (PST)
          (envelope-from hasty@rah.star-gate.com)
Received: from rah (localhost.star-gate.com [127.0.0.1])
          by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id OAA27368;
          Mon, 16 Feb 1998 14:51:37 -0800 (PST)
          (envelope-from hasty@rah.star-gate.com)
Message-Id: <199802162251.OAA27368@rah.star-gate.com>
X-Mailer: exmh version 2.0gamma 1/27/96
To: Julian Elischer <julian@whistle.com>
cc: Ollivier Robert <roberto@keltia.freenix.fr>, current@FreeBSD.ORG
Subject: Re: Working (apparently) soft-update code available. 
In-reply-to: Your message of "Mon, 16 Feb 1998 14:21:41 PST."
             <Pine.BSF.3.95.980216141817.8949N-100000@current1.whistle.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 16 Feb 1998 14:51:37 -0800
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Nope, Kirk's last patch does not fix the problem that some of us are seeing.

If anyone is interested in tracking down the problem, I can give you
an account on my test box , cioloco.star-gate.com , it still has
the last crash stashed away in case that anyone wants to examine
the kernel data structures leading to the panic.

This is my stack trace for my panic:


#13 0xf01d6217 in large_i586_bcopy_loop ()
#14 0xf01a6e57 in softdep_setup_allocindir_page (ip=0xf0eea400, lbn=35, 
    bp=0xf2ee6320, ptrno=23, newblkno=2925336, oldblkno=0, nbp=0xf2ee7d5c)
    at ../../ufs/ffs/ffs_softdep.c:1402
#15 0xf01a447d in ffs_balloc (ap=0xf4e53ea4) at ../../ufs/ffs/ffs_balloc.c:302
#16 0xf01ad98c in ffs_write (ap=0xf4e53ef8) at vnode_if.h:995
#17 0xf013c2a7 in vn_write (fp=0xf0ec05c0, uio=0xf4e53f40, cred=0xf0edea80)
    at vnode_if.h:331
#18 0xf011f7bb in write (p=0xf4da96c0, uap=0xf4e53f94)
    at ../../kern/sys_generic.c:268
#19 0xf01d7e5f in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 331776, 
      tf_esi = 97788, tf_ebp = -272644200, tf_isp = -186302492, 
      tf_ebx = 537460832, tf_edx = 97788, tf_ecx = -272644192, tf_eax = 4, 
      tf_trapno = 12, tf_err = 7, tf_eip = 537405009, tf_cs = 31, 
      tf_eflags = 518, tf_esp = -272644224, tf_ss = 39})
    at ../../i386/i386/trap.c:994


Basically, softdep_setup_allocindir attempted to copy data to block -12 of the
inode.

It appears that the crash always has the same pattern , attempting to copy
to block -12.

(kgdb) print *bp
$1 = {b_hash = {le_next = 0x0, le_prev = 0xf0214c58}, b_vnbufs = {
    le_next = 0x0, le_prev = 0xf2ee7d64}, b_freelist = {tqe_next = 0xf2eeae68, 
    tqe_prev = 0xf2ee37d8}, b_act = {tqe_next = 0x0, tqe_prev = 0xf022992c}, 
  b_proc = 0x0, b_flags = 536870960, b_qindex = 0, b_usecount = 14 '\016', 
  b_error = 0, b_bufsize = 8192, b_bcount = 8192, b_resid = 0, 
  b_dev = 4294967295, b_data = 0xf35e6000 "", b_kvabase = 0xf35e6000 "", 
  b_kvasize = 8192, b_lblkno = -12, b_blkno = -12, b_iodone = 0, 
  b_iodone_chain = 0x0, b_vp = 0xf4dcf820, b_dirtyoff = 0, b_dirtyend = 0, 
  b_generation = 157, b_rcred = 0x0, b_wcred = 0x0, b_validoff = 0, 
  b_validend = 0, b_pblkno = 6312288, b_saveaddr = 0x0, b_savekva = 0x0, 
  b_driver1 = 0x0, b_driver2 = 0x0, b_spc = 0x0, b_cluster = {cluster_head = {
      tqh_first = 0x0, tqh_last = 0xf2eeeb70}, cluster_entry = {
      tqe_next = 0x0, tqe_prev = 0xf2eeeb70}}, b_pages = {0xf0c70404, 
    0xf0c6a938, 0x0 <repeats 30 times>}, b_npages = 2, b_dep = {
    lh_first = 0x0}}

	Cheers,
	Amancio




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