From owner-freebsd-current@FreeBSD.ORG Thu Feb 15 01:14:02 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5549716A406 for ; Thu, 15 Feb 2007 01:14:02 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 4269513C4B8 for ; Thu, 15 Feb 2007 01:14:02 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 1FDB91A3C1A; Wed, 14 Feb 2007 17:14:02 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 02DA05195F; Wed, 14 Feb 2007 20:14:00 -0500 (EST) Date: Wed, 14 Feb 2007 20:14:00 -0500 From: Kris Kennaway To: Alexandre Sunny Kovalenko Message-ID: <20070215011400.GA10455@xor.obsecurity.org> References: <1171414959.906.16.camel@RabbitsDen.RabbitsLawn.verizon.net> <20070214011755.GA73381@xor.obsecurity.org> <1171500531.780.6.camel@RabbitsDen.RabbitsLawn.verizon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1171500531.780.6.camel@RabbitsDen.RabbitsLawn.verizon.net> User-Agent: Mutt/1.4.2.2i Cc: current@freebsd.org, Kris Kennaway Subject: Re: -CURRENT panics on intensive fs operations. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Feb 2007 01:14:02 -0000 On Wed, Feb 14, 2007 at 07:48:51PM -0500, Alexandre Sunny Kovalenko wrote: > On Tue, 2007-02-13 at 20:17 -0500, Kris Kennaway wrote: > > On Tue, Feb 13, 2007 at 08:02:39PM -0500, Alexandre Sunny Kovalenko wrote: > > > I can reliably panic -CURRENT (Feb 11, noon EST) with the something that > > > excersises the file system. I have currently settled on (cd /usr/ports; > > > make clean), but it all started out as doing some "emerges" to test the > > > latest linuxolator. In the case of the "make clean" I have seen it > > > crashing as early as /usr/ports/audio and as late > > > as /usr/ports/textproc. > > > > > > It does not seem to be consistent as to where it crashes (two latest > > > ones are below). This machine is Intel T2400 (1.83GHz 32-bit dual core). > > > I have attached config file to the E-mail. I am going to turn off > > > PREEMPTION for the lack of better ideas, but I will be happy to try any > > > other suggestions. I did run memtest on this machine for about 6 hours > > > without a problem. > > > > How about turning debugging back on to try and catch a more useful > > panic? > I don't know whether it is indeed more useful: > > RabbitsDen# kgdb /usr/obj/usr/src/sys/TPX60/kernel.debug vmcore.0 > kgdb: kvm_read: invalid address (0x16) > [GDB will not be able to debug user-mode > threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 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-marcel-freebsd". > Cannot access memory at address 0x0 > (kgdb) bt > #0 0x00000000 in ?? () > (kgdb) kgdb or libkvm out of date? > Maybe this will help someone: > RabbitsDen# grep savecore /var/log/messages > Feb 14 19:35:35 RabbitsDen savecore: reboot after panic: Bad link elm > 0xc670c3fc prev->next != elm Not really, it's from does it doesn't give any real information. Kris