From owner-freebsd-hackers@FreeBSD.ORG Sun May 28 21:27:40 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 026BB16D10D for ; Sun, 28 May 2006 21:15:21 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 244EE43D6E for ; Sun, 28 May 2006 21:15:14 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost [127.0.0.1]) by mp2.macomnet.net (8.13.4/8.13.3) with ESMTP id k4SLF8hj033309; Mon, 29 May 2006 01:15:09 +0400 (MSD) (envelope-from maxim@macomnet.ru) Date: Mon, 29 May 2006 01:15:08 +0400 (MSD) From: Maxim Konovalov To: Avleen Vig In-Reply-To: <20060528203015.GA8791@silverwraith.com> Message-ID: <20060529011110.G33226@mp2.macomnet.net> References: <20060512220019.GA1911@silverwraith.com> <20060512223919.GA21382@fonon.realnet> <20060513014020.GE1911@silverwraith.com> <20060513074033.GA1236@fonon.realnet> <20060515175802.GA727@silverwraith.com> <20060528203015.GA8791@silverwraith.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-hackers@freebsd.org Subject: Re: 6.1 crash data (was: Re: no core file handler recognizes format) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 May 2006 21:27:42 -0000 On Sun, 28 May 2006, 13:30-0700, Avleen Vig wrote: > On Mon, May 15, 2006 at 10:58:02AM -0700, Avleen Vig wrote: > > On Sat, May 13, 2006 at 11:40:33AM +0400, Stanislav Sedov wrote: > > > Rebuild your kernel with INVARIANTS enabled and debug info. It will > > > provide more information in case the crash happens again. > > Ok, I finally got a core file with the crash :-) > Where's what some of kgdb tells me. > All I can tell, is that the bug happened somewhere around trying to set > a TOS value for an outbound network packet? > Help please? [...] As I already said the issue is known. Please send the backtrace as a followup to kern/97095. -- Maxim Konovalov