From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 9 18:10:11 2011 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8B2DE106567C for ; Fri, 9 Dec 2011 18:10:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7B0998FC14 for ; Fri, 9 Dec 2011 18:10:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id pB9IABCL094454 for ; Fri, 9 Dec 2011 18:10:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id pB9IABim094453; Fri, 9 Dec 2011 18:10:11 GMT (envelope-from gnats) Date: Fri, 9 Dec 2011 18:10:11 GMT Message-Id: <201112091810.pB9IABim094453@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Mark Kamichoff Cc: Subject: Re: amd64/129426: [panic] FreeBSD 7.0 crash after subdiskXX: detached X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mark Kamichoff List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2011 18:10:11 -0000 The following reply was made to PR amd64/129426; it has been noted by GNATS. From: Mark Kamichoff To: jh@FreeBSD.org Cc: freebsd-amd64@FreeBSD.org, bug-followup@FreeBSD.org Subject: Re: amd64/129426: [panic] FreeBSD 7.0 crash after subdiskXX: detached Date: Fri, 9 Dec 2011 13:07:56 -0500 On Fri, Dec 09, 2011 at 05:41:37PM +0000, jh@FreeBSD.org wrote: > Synopsis: [panic] FreeBSD 7.0 crash after subdiskXX: detached > > State-Changed-From-To: open->feedback > State-Changed-By: jh > State-Changed-When: Fri Dec 9 17:41:37 UTC 2011 > State-Changed-Why: > Note that submitter has been asked for feedback. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=129426 I haven't seen this problem since I replaced the original machine with a completely new one that has an entirely different set of hardware. I wouldn't say the issue is resolved, but I'm no longer able to reproduce it, sorry :( - Mark -- Mark Kamichoff prox@prolixium.com http://www.prolixium.com/