From owner-freebsd-alpha@FreeBSD.ORG Tue Jun 20 17:31:58 2006 Return-Path: X-Original-To: freebsd-alpha@freebsd.org 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 0188216A47B; Tue, 20 Jun 2006 17:31:58 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB8B143D4C; Tue, 20 Jun 2006 17:31:56 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id k5KHVsan097584; Tue, 20 Jun 2006 19:31:54 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [10.1.1.14]) by cicely5.cicely.de (8.13.4/8.13.4) with ESMTP id k5KHVnDK005544 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 20 Jun 2006 19:31:50 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.13.4/8.13.3) with ESMTP id k5KHVngh015983; Tue, 20 Jun 2006 19:31:49 +0200 (CEST) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id k5KHVmDs015982; Tue, 20 Jun 2006 19:31:48 +0200 (CEST) (envelope-from ticso) Date: Tue, 20 Jun 2006 19:31:48 +0200 From: Bernd Walter To: John Baldwin Message-ID: <20060620173147.GB14871@cicely12.cicely.de> References: <200510231839.j9NIdHnj002910@freefall.freebsd.org> <200606190856.55473.jhb@freebsd.org> <20060620.233256.345485143.furutaka@jb3.so-net.ne.jp> <200606201249.25983.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200606201249.25983.jhb@freebsd.org> X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-4.4 required=5.0 autolearn=ham version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on cicely12.cicely.de Cc: freebsd-alpha@freebsd.org, linimon@freebsd.org Subject: Re: alpha/67626: X crashes an alpha machine, resulting reboot X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jun 2006 17:31:58 -0000 On Tue, Jun 20, 2006 at 12:49:25PM -0400, John Baldwin wrote: > On Tuesday 20 June 2006 10:32, Kazuyoshi Furutaka wrote: > > Dear John, Mark and all others, > > > > From: John Baldwin > > Subject: Re: alpha/67626: X crashes an alpha machine, resulting reboot > > Date: Mon, 19 Jun 2006 08:56:55 -0400 > > > > > We'd really need a stacktrace to help. It would also be useful to know > > > if more recent versions of the OS (such as 6.1) exhibit the same problems. > > > > > > As far as getting serial console working, you don't need to create a > > > /boot.config file (that is i386-specific). However, you need to get SRM > > > to use the serial console and then the loader and kernel will use it. > It's > > > been a while since I set it up, but I would look at your SRM variables and > > > see if there's a CONSOLE variable you can set to SERIAL instead of VIDEO > > > (IIRC). You can then try running 'init' from SRM to restart SRM which > > > should then show up on your serial console. You might be able to find > more > > > definitive instructions on using SRM with a serial console via a web > search. > > > > Well, could you tell me how I can collect more information from > > the current installation, in addition to the attached ? > > > > Later I'll test more recent versions... > > A 0x670 vector machine check indicates a hardware failure specific to the > CPU such as a cache failure. On some machine modells it could also be accessing non exiting memory, which can point to a broken memory mapped videocard driver. If the video card is on a secondary bus it can also be a sparse initialisation problem related to PCI-PCI bridges. Moving slots may help in that case. -- B.Walter http://www.bwct.de http://www.fizon.de bernd@bwct.de info@bwct.de support@fizon.de