From owner-freebsd-current@FreeBSD.ORG Mon Jun 29 14:22:06 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 518281065672 for ; Mon, 29 Jun 2009 14:22:06 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id 2AC128FC1B for ; Mon, 29 Jun 2009 14:22:04 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lstewart-laptop.caia.swin.edu.au (c149.al.cl.cam.ac.uk [128.232.110.149]) (authenticated bits=0) by lauren.room52.net (8.14.3/8.14.3) with ESMTP id n5TELsPu051378 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Jun 2009 00:21:57 +1000 (EST) (envelope-from lstewart@freebsd.org) Message-ID: <4A48CE02.5000200@freebsd.org> Date: Mon, 29 Jun 2009 15:21:54 +0100 From: Lawrence Stewart User-Agent: Thunderbird 2.0.0.22 (X11/20090626) MIME-Version: 1.0 To: Kamigishi Rei References: <4A45ABB1.7040506@haruhiism.net> In-Reply-To: <4A45ABB1.7040506@haruhiism.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,SPF_SOFTFAIL autolearn=disabled version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on lauren.room52.net Cc: freebsd-current@freebsd.org Subject: Re: r194546 amd64: kernel panic in tcp_sack.c X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 14:22:06 -0000 Hi, Kamigishi Rei wrote: > Hello, hope you're having a nice day, > > I've been testing my system mostly to check if ZFS in -current is > stable, however so far I've been getting kernel panics in every other > area except ZFS. This time it's tcp_sack.c according to the panic > message, inside [intr]. lol, handy! > > fujibayashi@ameagari ~ % uname -a > FreeBSD ameagari.fujibayashi.jp 8.0-CURRENT FreeBSD 8.0-CURRENT #1 > r194546: Thu Jun 25 19:44:18 JST 2009 > root@ameagari.fujibayashi.jp:/usr/src/sys/amd64/compile/Ameagari amd64 > > panic: tcp_sack_globalholes >= 0 > cpuid = 0 > KDB: enter: panic > [thread pid 12 tid 100005] > Stopped at kdb_enter+0x3d: movq $0,0x682580(%rip) > db> bt > Tracing pid 12 tid 100005 td 0xffffff0001320000 > kdb_enter() at kdb_enter+0x3d > panic() at panic+0x17b > tcp_sackhole_remove() at tcp_sackhole_remove+0xc7 > tcp_free_sackholes() at tcp_free_sackholes+0x48 > tcp_timer_rexmt() at tcp_timer_rexmt+0xb3 > softclock() at softclock+0x291 > intr_event_execute_handlers() at intr_event_execute_handlers+0x68 > ithread_loop() at ithread_loop+0xb2 > fork_exit() at fork_exit+0x12a > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffff8000026d40, rbp = 0 --- > db > > I'm not intimately familiar with our SACK implementation, and these things are often extremely painful to track down. First step: is the panic reproducible? > No core saved - when I tried to get it to save the core, it just raised > fatal trap 12 (page fault) and got a general protection fault afterwards. > Any ideas? How did you try to get it to save the core? A dump would be very useful to have around. Cheers, Lawrence