From owner-freebsd-bugs@FreeBSD.ORG Tue May 13 13:49:10 2008 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4CF381065681 for ; Tue, 13 May 2008 13:49:10 +0000 (UTC) (envelope-from nsayer@kfu.com) Received: from quack.kfu.com (6to4.kfu.com [IPv6:2002:478d:4001::1]) by mx1.freebsd.org (Postfix) with ESMTP id AF4578FC22 for ; Tue, 13 May 2008 13:49:09 +0000 (UTC) (envelope-from nsayer@kfu.com) Received: from zeus.kfu.com (zeus.kfu.com [IPv6:2002:478d:4002:0:21f:5bff:feed:cccc]) (authenticated bits=0) by quack.kfu.com (8.14.2/8.14.2) with ESMTP id m4DDn5aX029467 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 13 May 2008 06:49:08 -0700 (PDT) (envelope-from nsayer@kfu.com) Message-Id: <5DD1AFF5-B437-4D9C-BFCE-D55CD4BFAB07@kfu.com> From: Nick Sayer To: Pekka Savola In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Tue, 13 May 2008 06:49:05 -0700 References: X-Mailer: Apple Mail (2.919.2) X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (quack.kfu.com [IPv6:2002:478d:4001:0:217:31ff:fee9:bc66]); Tue, 13 May 2008 06:49:08 -0700 (PDT) Cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/122283: [ip6] [panic] Panic in ip_output related to IPv6 routes X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 May 2008 13:49:10 -0000 I too have an SMP machine - a core 2 duo. I rather suspect that the bug is elsewhere - something is pooching the route table, then this code is stumbling over the results. On May 13, 2008, at 3:42 AM, Pekka Savola wrote: > Hi Nick, > > I got hit by this after upgrading a dual-CPU system (6to4 relay) > from 6.3 to 7.0. At the same time I enabled SMP. I'm going to try > to disable SMP but I don't know if it helps. > > The backtrace seems somewhat similar, unfortunately I have less > information than you do: > > Tracing pid 12 tid 100003 td 0xc4d08880 > ip_output(c5434700,0,c5001804,0,0,...) at ip_output+0x15c > stf_output(c4fd3c00,c5430a00,c08166c4,c51ced20,0,...) at stf_output > +0x431 > nd6_output(c4fd3c00,c4fd3c00,c5430a00,c08166c4,c51ced20,...) at > nd6_output+0x70d > ip6_forward(c5430a00,0,10,1,0,...) at ip6_forward+0x88d > ip6_input(c5430a00,c058019e,1,93472,c4d08880,...) at ip6_input+0xd7e > netisr_processqueue(1,e0633985,202,1000000,c4d08880,...) at > netisr_processqueue+0xcd > swi_net(0,0,c0788ef0,46b,0,...) at swi_net+0xbe > ithread_loop(c4cc58f0,e529dd38,0,0,0,...) at ithread_loop+0x1ab > fork_exit(c056d8e0,c4cc58f0,e529dd38) at fork_exit+0x99 > fork_trampoline() at fork_trampoline+0x8 > > -- > Pekka Savola "You each name yourselves king, yet the > Netcore Oy kingdom bleeds." > Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings