From owner-freebsd-stable@FreeBSD.ORG Fri Oct 22 14:25:47 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 1EE1E106566C for ; Fri, 22 Oct 2010 14:25:47 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2-6.sentex.ca [IPv6:2607:f3e0:80:80::2]) by mx1.freebsd.org (Postfix) with ESMTP id CDF9B8FC13 for ; Fri, 22 Oct 2010 14:25:46 +0000 (UTC) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost2.sentex.ca (8.14.4/8.14.4) with ESMTP id o9MEPcl7092680 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 22 Oct 2010 10:25:38 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.14.4/8.14.4) with ESMTP id o9MEPcWC094867; Fri, 22 Oct 2010 10:25:38 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <201010221425.o9MEPcWC094867@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 22 Oct 2010 10:25:37 -0400 To: Randy Bush From: Mike Tancsa In-Reply-To: References: <201010221416.o9MEGSa0094817@lava.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.67 on 205.211.164.50 Cc: 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 14:25:47 -0000 At 10:18 AM 10/22/2010, 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 ---Mike >randy -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike