From owner-freebsd-stable@FreeBSD.ORG Thu Jul 21 18:18:44 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 7BC2516A420 for ; Thu, 21 Jul 2005 18:18:44 +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 12A6843D45 for ; Thu, 21 Jul 2005 18:18:43 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Dvfbi-0007g9-2n for freebsd-stable@freebsd.org; Thu, 21 Jul 2005 20:17:18 +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 ; Thu, 21 Jul 2005 20:17:18 +0200 Received: from A.S.Usov by gn-hgk-15cd4.adsl.wanadoo.nl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 21 Jul 2005 20:17:18 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: "Alexander S. Usov" Date: Thu, 21 Jul 2005 20:17:09 +0200 Organization: KVI Lines: 19 Message-ID: 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.1 Sender: news Subject: Strange panic 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, 21 Jul 2005 18:18:44 -0000 Hi! I have got a pair of very strange panics today. I didn't saw the exact panic message for the firs one, as the X was running at the time it has halted, and all I can say about it is that it was unable to reboot and there are no coredump. For the second one I saw a message (approximate -- I type it in from paper) "panic: sbflush_locked: cc 0 || mb 0xc1bfa600 || mbcnt 0", and it looks like that as soon as it has tried to dump core it has got a second panic and went to reboot. I am unsure if the machine was able to reboot automatically, as I pressed a key to write down panic message. As in the previous case there is no core, so I can't get any backtrace from it. It all has happeden on 5.4-RELEASE-p3. -- Best regards, Alexander.