From owner-freebsd-current@FreeBSD.ORG Tue Feb 20 15:17:03 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 7A18816D092 for ; Tue, 20 Feb 2007 14:48:57 +0000 (UTC) (envelope-from alex.kovalenko@verizon.net) Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by mx1.freebsd.org (Postfix) with ESMTP id 5A1C113C467 for ; Tue, 20 Feb 2007 14:48:57 +0000 (UTC) (envelope-from alex.kovalenko@verizon.net) Received: from [10.0.3.231] ([70.21.156.216]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JDR003UANTFJH93@vms046.mailsrvcs.net> for current@freebsd.org; Tue, 20 Feb 2007 08:48:53 -0600 (CST) Date: Tue, 20 Feb 2007 09:48:48 -0500 From: "Alexandre \"Sunny\" Kovalenko" In-reply-to: <20070215011400.GA10455@xor.obsecurity.org> To: Kris Kennaway Message-id: <1171982928.751.1.camel@RabbitsDen.RabbitsLawn.verizon.net> MIME-version: 1.0 X-Mailer: Evolution 2.8.1.1 FreeBSD GNOME Team Port Content-type: text/plain Content-transfer-encoding: 7bit References: <1171414959.906.16.camel@RabbitsDen.RabbitsLawn.verizon.net> <20070214011755.GA73381@xor.obsecurity.org> <1171500531.780.6.camel@RabbitsDen.RabbitsLawn.verizon.net> <20070215011400.GA10455@xor.obsecurity.org> Cc: current@freebsd.org 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: Tue, 20 Feb 2007 15:17:03 -0000 On Wed, 2007-02-14 at 20:14 -0500, Kris Kennaway wrote: > 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? How does one check? This system went through cvsup/buildworld/installworld, so I would expect all the bits to match. -- Alexandre "Sunny" Kovalenko