From owner-freebsd-current@FreeBSD.ORG Wed Oct 6 00:07:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD03B16A4CE for ; Wed, 6 Oct 2004 00:07:01 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68C5643D31 for ; Wed, 6 Oct 2004 00:07:01 +0000 (GMT) (envelope-from marchenko@gmail.com) Received: by mproxy.gmail.com with SMTP id 74so365342rnk for ; Tue, 05 Oct 2004 17:07:01 -0700 (PDT) Received: by 10.38.152.63 with SMTP id z63mr25922rnd; Tue, 05 Oct 2004 17:07:01 -0700 (PDT) Received: by 10.38.22.66 with HTTP; Tue, 5 Oct 2004 17:07:01 -0700 (PDT) Message-ID: Date: Tue, 5 Oct 2004 20:07:01 -0400 From: Vlad To: Marc UBM Bocklet In-Reply-To: <20041006015131.10116be7.ubm@u-boot-man.de> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041006015131.10116be7.ubm@u-boot-man.de> cc: current@freebsd.org Subject: Re: [BETA7-panic] sodealloc(): so_count 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Vlad List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Oct 2004 00:07:01 -0000 Welcome to the club, Marc I have the the same problem, here is several observes that I've made: 1) doesn't happen if kernel compiled w/o SMP 2) happen under heavy traffic 3) I had problems with my network configuration (incorrect broadcast assigned to aliased ip on interface) + packets loss issue (switch side). when those two issues has been resolved it seems that it's working more stable now. anything common with the above on your end? On Wed, 6 Oct 2004 01:51:31 +0200, Marc UBM Bocklet wrote: > > Hiho! :-) > > My system panics reliably within two or three days with > > panic: sodealloc(): so_count 1 > cpuid = 1 > > I have reenabled my serial console and will hopefully catch it the next > time it happens and get a backtrace/ddb stuff. > > In the meantime, has anybody got any idea what's going on without > additional info from the debugger? > > Thanks a lot! :-) > > Bye > Marc > -- Vlad