From owner-freebsd-stable@FreeBSD.ORG Fri Oct 22 20:27:37 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 78E7F106564A for ; Fri, 22 Oct 2010 20:27:37 +0000 (UTC) (envelope-from joelja@bogus.com) Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by mx1.freebsd.org (Postfix) with ESMTP id 54D138FC1D for ; Fri, 22 Oct 2010 20:27:37 +0000 (UTC) Received: from dhcp-176.nokia.net (dhcp-176.nokia.net [192.103.16.176] (may be forged)) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id o9MKRZCC010582 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 22 Oct 2010 20:27:36 GMT (envelope-from joelja@bogus.com) Message-ID: <4CC1F3B8.3010302@bogus.com> Date: Fri, 22 Oct 2010 13:27:36 -0700 From: Joel Jaeggli User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4 MIME-Version: 1.0 To: Randy Bush References: <201010221416.o9MEGSa0094817@lava.sentex.ca> <201010221425.o9MEPcWC094867@lava.sentex.ca> <201010221848.o9MIm7WF096197@lava.sentex.ca> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Fri, 22 Oct 2010 20:27:36 +0000 (UTC) Cc: Chris Morrow , stable Subject: Re: repeating crashes with 8.1 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Oct 2010 20:27:37 -0000 Ok I'll try testing that on some box I can reach with both hands. fyi nagasaki is: [root@nagasaki ~]# uname -a FreeBSD nagasaki.bogus.com 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #13: Sun May 30 22:19:23 UTC 2010 root@nagasaki.bogus.com:/usr/obj/usr/src/sys/GENERIC i386 [root@nagasaki ~]# On 10/22/10 1:17 PM, Randy Bush wrote: >>>>>> Do you know how this panic is triggered ? Are you able to >>>>>> create it on demand ? >>>>> >>>>> no i do not. bring server up and it'll happen in half an hour. >>>>> and the server was happy for two months. so i am thinking hardware. >>>> >>>> Perhaps. The reason I ask is that I had a box go down last night with >>>> the same set of errors. The box has a number of ipv6 routes, but its >>>> next hop was down and the problems started soon after. So I wonder if >>>> it has something to do with that. Do you have ipv6 on this box and >>>> are all the next hop addresses correct / reachable ? >>>> >>>> Oct 22 02:06:02 i4 kernel: em1: discard frame w/o packet header >>>> Oct 22 02:06:10 i4 kernel: em2: discard frame w/o packet header >>>> Oct 22 02:06:21 i4 kernel: em1: discard frame w/o packet header >>> >>> it was co-incident with a border router being taken down for new router >>> install. that router was the v6 exit the servers was using. i have now >>> pointed default6 to a different exit. the server seems happy. >> >> >> Are you servers still up ? I guess the question now is how to >> trigger this problem on demand. Perhaps lots of inbound ipv6 traffic >> with a bad next hop out ? How recent are you sources ? The kernel >> said Oct 21st. Were the sources from then too ? > > yes, kernel and world from 21 oct > > chris had an idea on retrigger, install a static for a small dest that > points to a hole. send a packet to the small dest. > > randy >