From owner-freebsd-stable@FreeBSD.ORG Sun Jul 31 20:06:59 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 C91CE16A41F for ; Sun, 31 Jul 2005 20:06:59 +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 97AC243D6E for ; Sun, 31 Jul 2005 20:06:45 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1DzK4h-0008Ty-BW for freebsd-stable@freebsd.org; Sun, 31 Jul 2005 22:06:19 +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 ; Sun, 31 Jul 2005 22:06:19 +0200 Received: from A.S.Usov by gn-hgk-15cd4.adsl.wanadoo.nl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 31 Jul 2005 22:06:19 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: "Alexander S. Usov" Date: Sun, 31 Jul 2005 22:06:12 +0200 Organization: KVI Lines: 52 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.1 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: Sun, 31 Jul 2005 20:06:59 -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). In just 2 days of waiting I got it, however it looks that it has fired in a bit different place. (kgdb) bt #0 doadump () at pcpu.h:159 #1 0xc0513899 in boot (howto=260) at ../../../kern/kern_shutdown.c:410 #2 0xc0513ede in panic (fmt=0xc06ac87f "sbdrop") at ../../../kern/kern_shutdown.c:566 #3 0xc05556f4 in sbdrop_locked (sb=0xc2285ad8, len=112) at ../../../kern/uipc_socket2.c:1149 #4 0xc05b27f2 in tcp_input (m=0xc1e31800, off0=152) at ../../../netinet/tcp_input.c:2209 #5 0xc05a9b13 in ip_input (m=0xc1e31800) at ../../../netinet/ip_input.c:776 #6 0xc059215e in netisr_processqueue (ni=0xc070b0f8) at ../../../net/netisr.c:233 #7 0xc059241d in swi_net (dummy=0x0) at ../../../net/netisr.c:346 #8 0xc04fb9a1 in ithread_loop (arg=0xc1979500) at ../../../kern/kern_intr.c:547 #9 0xc04fa9dc in fork_exit (callout=0xc04fb8ea , arg=0x0, frame=0x0) at ../../../kern/kern_fork.c:791 #10 0xc0656a8c in fork_trampoline () at ../../../i386/i386/exception.s:209 I am going to keep it around for some time, so I can easisy do a full bt or variables. Corresponding dmesg & sysctl output can be found at https://kvip88.kvi.nl/~usov -- Best regards, Alexander.