From owner-freebsd-stable@FreeBSD.ORG Sat Oct 23 00:01:25 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 CBE941065693 for ; Sat, 23 Oct 2010 00:01:25 +0000 (UTC) (envelope-from morrowc@ops-netman.net) Received: from neo-u2.ops-netman.net (unknown [IPv6:2001:470:e03a:246:230::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6ED808FC0A for ; Sat, 23 Oct 2010 00:01:25 +0000 (UTC) Received: from [192.168.1.3] (natz.ops-netman.net [71.246.230.122]) (Authenticated sender: morrowc@OPS-NETMAN.NET) by neo-u2.ops-netman.net (Postfix) with ESMTPSA id 9DCC83586F0; Sat, 23 Oct 2010 00:01:24 +0000 (UTC) Message-ID: <4CC225D3.1030502@ops-netman.net> Date: Fri, 22 Oct 2010 20:01:23 -0400 From: Chris Morrow User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.14) Gecko/20101006 Thunderbird/3.0.9 MIME-Version: 1.0 To: Joel Jaeggli References: <201010221416.o9MEGSa0094817@lava.sentex.ca> <201010221425.o9MEPcWC094867@lava.sentex.ca> <201010221848.o9MIm7WF096197@lava.sentex.ca> <4CC1F3B8.3010302@bogus.com> In-Reply-To: <4CC1F3B8.3010302@bogus.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Randy Bush , stable , warren@kumari.net 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: Sat, 23 Oct 2010 00:01:25 -0000 Note, Warren and I attempted to test this this evening on a 10.04 Ubuntu box, no crashy-crashy... -chris On 10/22/10 16:27, Joel Jaeggli wrote: > 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 >>