From owner-freebsd-current@FreeBSD.ORG  Wed Jun  8 01:42:41 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
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 9724116A421
	for <current@freebsd.org>; Wed,  8 Jun 2005 01:42:41 +0000 (GMT)
	(envelope-from mohan_srinivasan@yahoo.com)
Received: from web80604.mail.yahoo.com (web80604.mail.yahoo.com [66.218.79.93])
	by mx1.FreeBSD.org (Postfix) with SMTP id 4FC5643D4C
	for <current@freebsd.org>; Wed,  8 Jun 2005 01:42:41 +0000 (GMT)
	(envelope-from mohan_srinivasan@yahoo.com)
Message-ID: <20050608014241.92994.qmail@web80604.mail.yahoo.com>
Received: from [64.172.45.214] by web80604.mail.yahoo.com via HTTP;
	Tue, 07 Jun 2005 18:42:41 PDT
Date: Tue, 7 Jun 2005 18:42:41 -0700 (PDT)
From: Mohan Srinivasan <mohan_srinivasan@yahoo.com>
To: Andrey Chernov <ache@nagual.pp.ru>, current@freebsd.org
In-Reply-To: 6667
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: 
Subject: Re: Still something wrong with tcp_sack_option ()
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jun 2005 01:42:41 -0000

Hi,

I'll take a look at this. In the meantime, you can work around
this by pulling in the following versions in your tree :

tcp_var.h:  1.124
tcp_sack.c: 1.20

thanks

mohan

--- Andrey Chernov <ache@nagual.pp.ru> wrote:
> With very recent kernel I have a panic once per several hours, always in 
> swi1:net, always something called from tcp_sack_option (), see 
> example below:
> 
> Fatal trap 12: page fault while in kernel mode
> fault virtual address   = 0x4
> fault code              = supervisor read, page not present
> instruction pointer     = 0x20:0xc0539f12
> stack pointer           = 0x28:0xcc7e4a8c
> frame pointer           = 0x28:0xcc7e4adc
> code segment            = base 0x0, limit 0xfffff, type 0x1b
>                         = DPL 0, pres 1, def32 1, gran 1
> processor eflags        = interrupt enabled, resume, IOPL = 0
> current process         = 29 (swi1: net)
> trap number             = 12
> panic: page fault
> 
> #5  0xc05ccea0 in trap ()
> #6  0xc05bdf0a in calltrap ()
> #7  0xcc7e0008 in ?? ()
> #8  0x00000028 in ?? ()
> #9  0x00000028 in ?? ()
> #10 0x00000000 in ?? ()
> #11 0xc1a9e1cc in ?? ()
> #12 0xcc7e4adc in ?? ()
> #13 0xcc7e4a78 in ?? ()
> #14 0xcc7e4ab0 in ?? ()
> #15 0xc1129000 in ?? ()
> #16 0x7e56b4a9 in ?? ()
> #17 0xcc7e4ab0 in ?? ()
> #18 0x0000000c in ?? ()
> #19 0x00000000 in ?? ()
> #20 0xc0539f12 in tcp_sack_option ()
> 
> 
> -- 
> http://ache.pp.ru/
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>