From owner-freebsd-sparc64@FreeBSD.ORG Sun Jan 15 22:30:15 2012 Return-Path: Delivered-To: freebsd-sparc64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 428661065679 for ; Sun, 15 Jan 2012 22:30:15 +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 2CB048FC1A for ; Sun, 15 Jan 2012 22:30:15 +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 q0FMUFXl020237 for ; Sun, 15 Jan 2012 22:30:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q0FMUFbY020232; Sun, 15 Jan 2012 22:30:15 GMT (envelope-from gnats) Date: Sun, 15 Jan 2012 22:30:15 GMT Message-Id: <201201152230.q0FMUFbY020232@freefall.freebsd.org> To: freebsd-sparc64@FreeBSD.org From: Marius Strobl Cc: Subject: Re: sparc64/164123: Kernel fails to boot on Sun Ultra 5 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marius Strobl List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jan 2012 22:30:15 -0000 The following reply was made to PR sparc64/164123; it has been noted by GNATS. From: Marius Strobl To: Guy M Broome/FS/VCU Cc: bug-followup@FreeBSD.org Subject: Re: sparc64/164123: Kernel fails to boot on Sun Ultra 5 Date: Sun, 15 Jan 2012 23:23:52 +0100 On Sun, Jan 15, 2012 at 09:42:05AM -0500, Guy M Broome/FS/VCU wrote: > Marius, > > Nevermind tomorrow- I had a chance to get the debugging output immediately. > > After attempting to boot the debug kernel you provided, > > The result of "ctrace" is: > --------------------------------------------- > > PC: c07dc388 > Last leaf: XXXXXXX???? from c07dc350 > ?????? 0 w?? %o0-%o5?? (c0b93888 4b0 8 1 0 4 ) > > --------------------------------------------- > Thanks, I now understand what's going on. Basically this is the same issue as described in the commit log of r227537, I'm not yet sure how to solve this for uart(4) though. Marius