From owner-freebsd-alpha@FreeBSD.ORG Mon Nov 8 11:16:10 2004 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3A7C16A4CE for ; Mon, 8 Nov 2004 11:16:10 +0000 (GMT) Received: from bsd.ee (bsd.ee [194.126.101.115]) by mx1.FreeBSD.org (Postfix) with SMTP id 93D1243D2D for ; Mon, 8 Nov 2004 11:16:09 +0000 (GMT) (envelope-from hadara@bsd.ee) Received: (qmail 19795 invoked by uid 1000); 8 Nov 2004 11:16:10 -0000 Date: Mon, 8 Nov 2004 13:16:10 +0200 From: Sven Petai To: freebsd-alpha@freebsd.org Message-ID: <20041108111610.GA19719@bsd.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.25i Subject: 5.3 broken on AlphaPC 164LX X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Nov 2004 11:16:10 -0000 hi Hi I'm having some problems with getting 5.3 to work on a pcalpha (AlphaPC 164LX). This box was running 5.2.1 until now without any problems. Basically it now panics in most cases right after trying to execute init, sometimes it just hangs there forever. boot messages & panic & some ddb output is available @ http://bsd.ee/~hadara/debug/pcalpha/pcalpha_panic_08.11.2004.txt kernel config is available at: http://bsd.ee/~hadara/debug/pcalpha/kernel.txt any debug ideas ? if there aren't any better ones then I will just try to trace down the commit that caused it by cvsuping up/down but that will probably take at least a week... PS how can I tell kernel were it should dump core when it can't reach userland to use dumpdev command ? I tried various ways like setting dumpdev=/dev/ad2b from loader and tried to compile it into kernel, without much luck Sven Petai