From owner-freebsd-stable@FreeBSD.ORG Wed Aug 3 08:12:01 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 0A9C516A41F for ; Wed, 3 Aug 2005 08:12:01 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71A3243D4C for ; Wed, 3 Aug 2005 08:11:59 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1E0EKn-0005yC-Ey for freebsd-stable@freebsd.org; Wed, 03 Aug 2005 10:10:41 +0200 Received: from gn-hgk-15cd4.adsl.wanadoo.nl ([81.69.122.212]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 03 Aug 2005 10:10:41 +0200 Received: from A.S.Usov by gn-hgk-15cd4.adsl.wanadoo.nl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 03 Aug 2005 10:10:41 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: "Alexander S. Usov" Date: Wed, 03 Aug 2005 10:10:02 +0200 Organization: KVI Lines: 29 Message-ID: References: <6eb82e0507241001615f7490@mail.gmail.com> <20050729002138.X60522@fledge.watson.org> <20050729125525.D74149@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: gn-hgk-15cd4.adsl.wanadoo.nl User-Agent: KNode/0.9.2 Sender: news Subject: Re: panic: sbflush_locked on 5.4-p5/i386 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: Wed, 03 Aug 2005 08:12:01 -0000 Robert Watson wrote: > On Fri, 29 Jul 2005, Alexander S. Usov wrote: > >>>> I got a few similar panics. >>>> It looks that I managet to get rid of them by setting mpsafenet=0, but >>>> I am not sure -- I have to monitor it for a bit longer. >>>> I have managed to get a few dumps, so the traces are: >> >> Unfortunately I don't have these dumps anymore, I will try to switch >> mpsafenet back on and wait for a new ones. They were quite reproducable >> for me. > > Thanks. I will be away this weekend, but hope to have a chance to look > into this early next week. If you could send me the dmesg of the box > also, and the output of "sysctl -a", that would be helpful. Probably out > of band rather than via the list (or if you could put it on a web page I > could reach). Uhm. It's appeared to be not a very good idea to do some cleanup on the notebook before I had enought tee :( Managed to do part of this "cleanup" in the terminal logged in via ssh and to delete this core dump :( However over the night I got one more, and once it will be uploaded to the woking machine I will pust some details. -- Best regards, Alexander.