From owner-freebsd-sparc64@FreeBSD.ORG Wed Nov 1 21:30:29 2006 Return-Path: X-Original-To: freebsd-sparc64@hub.freebsd.org Delivered-To: freebsd-sparc64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2DED116A416 for ; Wed, 1 Nov 2006 21:30:29 +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 A82A443D76 for ; Wed, 1 Nov 2006 21:30:28 +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 kA1LUS0g049405 for ; Wed, 1 Nov 2006 21:30:28 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id kA1LUSZW049404; Wed, 1 Nov 2006 21:30:28 GMT (envelope-from gnats) Date: Wed, 1 Nov 2006 21:30:28 GMT Message-Id: <200611012130.kA1LUSZW049404@freefall.freebsd.org> To: freebsd-sparc64@FreeBSD.org From: "=?ISO-8859-1?Q?St=E9phane_Witzmann?=" Cc: Subject: Re: sparc64/105048: trm(4) panics on sparc64 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?ISO-8859-1?Q?St=E9phane_Witzmann?= List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Nov 2006 21:30:29 -0000 The following reply was made to PR sparc64/105048; it has been noted by GNATS. From: "=?ISO-8859-1?Q?St=E9phane_Witzmann?=" To: bug-followup@FreeBSD.org Cc: Subject: Re: sparc64/105048: trm(4) panics on sparc64 Date: Wed, 1 Nov 2006 22:23:56 +0100 I booted a quite recent 7.0 snapshot. Same panic. Details follow: db> bt (...) -- data access error %o7=0xc0b8552c NVRAM_trm_wait_30us() at NVRAM_trm_wait_30us+0x4c trm_attach() at trm_attach+0x548 device_attach() at device_attach+0x0x60 (...) NetBSD 3.0.1/sparc64 successfully attaches the card and its associated CDROM drive, so this is definitely not a hardware problem.