From owner-freebsd-bugs@FreeBSD.ORG Wed Jun 4 02:40:20 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE5BD37B407 for ; Wed, 4 Jun 2003 02:40:20 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0031F43F85 for ; Wed, 4 Jun 2003 02:40:19 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id h549eIUp060660 for ; Wed, 4 Jun 2003 02:40:18 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id h549eINJ060659; Wed, 4 Jun 2003 02:40:18 -0700 (PDT) Date: Wed, 4 Jun 2003 02:40:18 -0700 (PDT) Message-Id: <200306040940.h549eINJ060659@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Aleksey Ovcharenko Subject: Re: kern/51016: kernel panic: ufsdirhash_lookup: bad offset in hash array X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Aleksey Ovcharenko List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2003 09:40:21 -0000 The following reply was made to PR kern/51016; it has been noted by GNATS. From: Aleksey Ovcharenko To: freebsd-gnats-submit@FreeBSD.org Cc: David Malone Subject: Re: kern/51016: kernel panic: ufsdirhash_lookup: bad offset in hash array Date: Wed, 4 Jun 2003 12:39:55 +0259 On Monday 26 May 2003 14:05, David Malone wrote: > Dear Aleksey, > > The we've suaully found that panics in ufsdirhash_lookup are caused > by bad memory or bad processors. While it is possible there is a > bug in dirhash, it seems more likely that hardware is at fault. The > intermittent nature of your problem would also reenforce this. > > If you can run gdb -k again and get a back trace, by typing "bt" > this might help us see what's going on. I send you this information some days ago, but still no response. Resending it in case it losts. (kgdb) bt #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 #1 0xc014ea58 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:316 #2 0xc014ee8c in poweroff_wait (junk=0xc0259b40, howto=0) at /usr/src/sys/kern/kern_shutdown.c:595 #3 0xc01e8a0f in ufsdirhash_lookup (ip=0xcd473000, name=0xe6b37800 "1051794533.99778.console.ic.kharkov.ua", namelen=38, offp=0xcd473064, bpp=0xe6ec6d5c, prevoffp=0x0) at /usr/src/sys/ufs/ufs/ufs_dirhash.c:361 #4 0xc01e29bb in ufs_lookup (ap=0xe6ec6db8) at /usr/src/sys/ufs/ufs/ufs_lookup.c:212 #5 0xc01e8241 in ufs_vnoperate (ap=0xe6ec6db8) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2422 #6 0xc0178772 in vfs_cache_lookup (ap=0xe6ec6e10) at vnode_if.h:77 #7 0xc01e8241 in ufs_vnoperate (ap=0xe6ec6e10) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2422 #8 0xc017b70d in lookup (ndp=0xe6ec6e8c) at vnode_if.h:52 #9 0xc017b1f8 in namei (ndp=0xe6ec6e8c) at /usr/src/sys/kern/vfs_lookup.c:153 #10 0xc0180fc5 in lstat (p=0xe6e268e0, uap=0xe6ec6f80) at /usr/src/sys/kern/vfs_syscalls.c:1823 #11 0xc022bd21 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 134547712, tf_esi = 134547816, tf_ebp = -1077937680, tf_isp = -420712492, tf_ebx = 672177004, tf_edx = 3, tf_ecx = 134547776, tf_eax = 190, tf_trapno = 12, tf_err = 2, tf_eip = 671854364, tf_cs = 31, tf_eflags = 659, tf_esp = -1077937820, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1175 #12 0xc021ffe5 in Xint0x80_syscall () #13 0x280b756d in ?? () #14 0x280b6dea in ?? () #15 0x8048e62 in ?? () #16 0x80488f1 in ?? () (kgdb) -- Sincerely Yours, Aleksey Ovcharenko