From owner-freebsd-stable@FreeBSD.ORG Sat Aug 6 10:51:47 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 0C30616A41F for ; Sat, 6 Aug 2005 10:51:47 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id B259F43D45 for ; Sat, 6 Aug 2005 10:51:46 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id 4744246B8F; Sat, 6 Aug 2005 06:51:46 -0400 (EDT) Date: Sat, 6 Aug 2005 11:54:33 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "Alexander S. Usov" In-Reply-To: <20050729125525.D74149@fledge.watson.org> Message-ID: <20050806115232.B46767@fledge.watson.org> 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; format=flowed Cc: freebsd-stable@freebsd.org 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: Sat, 06 Aug 2005 10:51:47 -0000 On Fri, 29 Jul 2005, 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). Two quetions: - Is there substantial IPv6 traffic on this system? I've had at least one report that this panic happens on a system only in the context of IPv6. - Is it possible for you to try running with a latest 5-STABLE kernel? Mohan at Yahoo!, who did the TCP SACK work, has been investigating the problem but has been unable to reproduce it either. Fortunately, it sounds like Geore Neville-Neil is able to reprodeuce it in a test environment, albeit only with IPv6, so we'll see what we can do. Mohan may shortly have a diagnostic patch to run with. Thanks, Robert N M Watson