From owner-freebsd-bugs@FreeBSD.ORG Mon Nov 13 11:50:12 2006 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 22E3F16A40F for ; Mon, 13 Nov 2006 11:50:12 +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 3A71D43D79 for ; Mon, 13 Nov 2006 11:50:11 +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 kADBoARl099540 for ; Mon, 13 Nov 2006 11:50:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kADBoA86099539; Mon, 13 Nov 2006 11:50:10 GMT (envelope-from gnats) Date: Mon, 13 Nov 2006 11:50:10 GMT Message-Id: <200611131150.kADBoA86099539@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Kai Gallasch Cc: Subject: Re: kern/104765: [hp] kernel panic 6.2 prerelease-20061017 amd64 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kai Gallasch List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 11:50:12 -0000 The following reply was made to PR kern/104765; it has been noted by GNATS. From: Kai Gallasch To: bug-followup@FreeBSD.org, gallasch@free.de Cc: Subject: Re: kern/104765: [hp] kernel panic 6.2 prerelease-20061017 amd64 Date: Mon, 13 Nov 2006 12:49:12 +0100 Server now runs stable for about 10 days (no crash) with FreeBSD 6.2-BETA3 (cvs checkout 2006/11/01) and GENERIC SMP Kernel. debug.mpsafenet=0 We set /boot/loader.conf debug.mpsafenet=0 - seems to help here.. Subject of PR 104765 has been changed from "kern/104765: kernel panic 6.2 prerelease-20061017 amd64" to "kern/104765: [hp] kernel panic 6.2 prerelease-20061017 amd64" Does this mean the bug is HP hardware related? No feedback in the PR?