From owner-freebsd-amd64@FreeBSD.ORG Sun Nov 12 17:40:34 2006 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC8FE16A417 for ; Sun, 12 Nov 2006 17:40:34 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2A3B43D7E for ; Sun, 12 Nov 2006 17:40:31 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id kACHeVvq084013 for ; Sun, 12 Nov 2006 17:40:31 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kACHeVow084012; Sun, 12 Nov 2006 17:40:31 GMT (envelope-from gnats) Date: Sun, 12 Nov 2006 17:40:31 GMT Message-Id: <200611121740.kACHeVow084012@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Wojciech Puchar Cc: Subject: Re: amd64/105437: 6.2-BETA3 crashes on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Wojciech Puchar List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Nov 2006 17:40:34 -0000 The following reply was made to PR amd64/105437; it has been noted by GNATS. From: Wojciech Puchar To: Ruslan Ermilov Cc: Wojciech Puchar , bug-followup@FreeBSD.org Subject: Re: amd64/105437: 6.2-BETA3 crashes on amd64 Date: Sun, 12 Nov 2006 18:32:36 +0100 (CET) > > options INVARIANTS # Enable calls of extra sanity checking > options INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS > options WITNESS # Enable checks to detect deadlocks and cycles > options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed > > It will run more slowly, but could allow to catch the bug earlier. > > It could turn out to be a problem with the IPv6 routing code. yes i DO use IPv6 intensively. this machine has native IPv6 connectivity, offers native connectivity and over TUN (ppp) and tunnels over gif. options added kernel compiled machine rebooted. on what messages should i look for? now i know that sometimes 2 machines in my IPv6 network crashes at the same time? special kind of packets? will my firewall config and kernel config help?