From owner-freebsd-stable@FreeBSD.ORG Thu Jun 2 06:10:38 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D35DE16A41C for ; Thu, 2 Jun 2005 06:10:38 +0000 (GMT) (envelope-from takeda@takeda.tk) Received: from chinatsu.takeda.tk (node-402413e2.sna.onnet.us.uu.net [64.36.19.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E06543D48 for ; Thu, 2 Jun 2005 06:10:36 +0000 (GMT) (envelope-from takeda@takeda.tk) Received: from takeda.lan (takeda.lan [10.0.0.3]) (authenticated bits=0) by chinatsu.takeda.tk (8.13.3/8.13.1) with ESMTP id j526ASGR002436 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 1 Jun 2005 23:10:28 -0700 (PDT) (envelope-from takeda@takeda.tk) Date: Wed, 1 Jun 2005 23:09:49 -0700 From: =?ISO-8859-2?Q?Derek_Kuli=F1ski?= X-Priority: 3 (Normal) Message-ID: <1886169080.20050601230949@takeda.tk> To: Sven Willenberger In-Reply-To: <1117574977.19736.75.camel@lanshark.dmv.com> References: <8910581751.20050529112956@takeda.tk> <1117574977.19736.75.camel@lanshark.dmv.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV 0.85.1/906/Wed Jun 1 14:38:56 2005 on chinatsu.takeda.tk X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org Subject: Re: stack backtrace X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2005 06:10:38 -0000 Hello Sven, Tuesday, May 31, 2005, 2:29:36 PM, you wrote: > Apparently this is still somewhat of a mystery, but you are not the > first person to witness this: > http://lists.freebsd.org/pipermail/freebsd-stable/2005-April/013679.html > http://lists.freebsd.org/pipermail/freebsd-current/2004-July/031576.html > I don't know if anyone is actually looking into this (behind the scenes > maybe) or whether we just need to accumulate a critical mass of similar > notices to raise an eyebrow. If your system does not lock up as a result > (the way it used to in the earlier 5.x series) then perhaps it is > harmless .. Well, since system don't crash it appear to be harmless (unless some data is damaged in the process). I'm mostly interested what that message means, something apparently is wrong. I'm not expert but it looks to me from the functions that is something related to writing/reading data to/from disk I really hope it doesn't affect the data. -- Best regards, Derek mailto:takeda@takeda.tk CCNA, SCSA, SCNA, LPIC, MCP certified http://www.takeda.tk Logic is a system whereby one may go wrong with confidence. -- Charles Kettering