From owner-freebsd-stable@FreeBSD.ORG Fri Oct 22 20:17:55 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 B32C91065674 for ; Fri, 22 Oct 2010 20:17:55 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [147.28.0.36]) by mx1.freebsd.org (Postfix) with ESMTP id 97A0E8FC0C for ; Fri, 22 Oct 2010 20:17:55 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=rmac.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.72 (FreeBSD)) (envelope-from ) id 1P9O3j-000Azv-Ns; Fri, 22 Oct 2010 20:17:52 +0000 Date: Fri, 22 Oct 2010 16:17:47 -0400 Message-ID: From: Randy Bush To: Mike Tancsa In-Reply-To: <201010221848.o9MIm7WF096197@lava.sentex.ca> References: <201010221416.o9MEGSa0094817@lava.sentex.ca> <201010221425.o9MEPcWC094867@lava.sentex.ca> <201010221848.o9MIm7WF096197@lava.sentex.ca> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: Chris Morrow , Joel Jaeggli , 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:17:55 -0000 >>>>> 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