From owner-freebsd-alpha Thu May 30 8:45:41 2002 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id E078137B40B for ; Thu, 30 May 2002 08:45:20 -0700 (PDT) Received: from moe.cs.duke.edu (moe.cs.duke.edu [152.3.140.74]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA16540; Thu, 30 May 2002 11:45:20 -0400 (EDT) Received: (gallatin@localhost) by moe.cs.duke.edu (8.8.5/8.6.9) id LAA03800; Thu, 30 May 2002 11:45:19 -0400 (EDT) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15606.18703.321254.508104@moe.cs.duke.edu> Date: Thu, 30 May 2002 11:45:19 -0400 (EDT) To: Allen Thomas Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: XFree86 & Alpha Demi-Sable In-Reply-To: <3CF6455C.AE088A08@attbi.com> References: <3CF3E84A.834835F7@attbi.com> <15603.60089.703466.654500@grasshopper.cs.duke.edu> <3CF3FFCB.C0908ED6@attbi.com> <15604.55234.240322.827898@grasshopper.cs.duke.edu> <3CF6455C.AE088A08@attbi.com> X-Mailer: VM 6.72 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Allen Thomas writes: > > unexpected machine check: > > > > mces = 0x1 > > vector = 0x670 > > param = 0xfffffc0000006000 > > pc = 0x16037e600 > > ra = 0x12006caf0 > > curproc = 0xfffffe00059d04c0 > > pid = 153, comm = XFree86 > > <..> > > unexpected machine check: > > > > mces = 0x1 > > vector = 0x670 > > param = 0xfffffc0000006000 > > pc = 0x16037e600 > > ra = 0x12006caf0 > > curproc = 0xfffffe00059d0a40 > > pid = 203, comm = XFree86 > > <..> > > unexpected machine check: > > > > mces = 0x1 > > vector = 0x670 > > param = 0xfffffc0000006000 > > pc = 0x16037e600 > > ra = 0x12006caf0 > > curproc = 0xfffffe00059d0a40 > > pid = 189, comm = XFree86 > > > > panic: machine check Well, at least it is consistant. The problem is that X is accessing the hardware in ways that the hardware doesn't like. This could be due to bugs in X itself, or in my platform support code for this model of alpha. This sort of problem is _very_ hard to track down. Are you familiar enough with gdb to build X with symbols, and set a breakpoint prior to the instruction which is panic'ing the machine? Another approach would be to try a different kind of graphics boards. Did it crash the same way with the Qvision? Do you have any PCI matrox boards? Drew PS: Wilko, didn't you say you'd run X on some sort of sable? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message