From owner-freebsd-alpha Thu Jul 18 8:59:20 2002 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 B88AD37B47F for ; Thu, 18 Jul 2002 08:59:10 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0618343E6E for ; Thu, 18 Jul 2002 08:59:06 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id LAA26985 for ; Thu, 18 Jul 2002 11:59:05 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g6IFwZW55071; Thu, 18 Jul 2002 11:58:35 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15670.58795.132997.660711@grasshopper.cs.duke.edu> Date: Thu, 18 Jul 2002 11:58:35 -0400 (EDT) To: freebsd-alpha@freebsd.org Subject: OT: Gravity kills XP1000? X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" 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 This is going to sound bizzare. This morning my XP1000 crashed with a machine check (machine was mostly idle). When I attempted to reboot it (power-cycle), I now see: OpenVMS PALcode V1.88-27, Digital UNIX PALcode V1.83-22 FF.FE.FD.FC.FB.FA.F9.F8.F7.F6.F5.F3.F2.F1.F0. EF.EE.EC.*** unable to assign PCI base address *** bus 0, slot 7, function 0, size c0000000 (sparse) *** unable to assign PCI base address *** bus 0, slot 7, function 0, size c0000000 (sparse) *** unable to assign PCI base address *** bus 0, slot 7, function 0, size c0000000 (sparse) EB.no external handler error detected by Pchip 0 Perror = 0020000003fc0040 target abort EA.E9.F4.ED.no external handler error detected by Pchip 0 Perror = 0020000000700080 PCI read data parity error no external handler <... errors continue forever > Then I flip the machine on its side and woila! The errors stop! *** No keyboard plugged in *** E8.E7. ewa0: link up : Negotiated 100BaseTX: full duplex E6.E5.E4. COMPAQ Professional Workstation XP1000 Console V5.9-1 Dec 14 2000 16:19:05 >>> >>>show dev dka0.0.0.6.1 DKA0 RZ2CD-KS 0306 dka100.1.0.6.1 DKA100 SEAGATE ST39140W 1498 dka200.2.0.6.1 DKA200 RZ2DD-KS 0306 dva0.0.0.0.0 DVA0 ewa0.0.0.3.1 EWA0 00-00-F8-71-AE-00 pka0.7.0.6.1 PKA0 SCSI Bus ID 7 5.57 >>>init OpenVMS PALcode V1.88-27, Digital UNIX PALcode V1.83-22 FF.FE.FD.FC.FB.FA.F9.F8.F7.F6.F5.F3.F2.F1.F0. EF.EE.EC.EB.EA.E9.F4.ED.*** No keyboard plugged in *** E8.E7. ewa0: link up : Negotiated 100BaseTX: full duplex E6.E5.E4. COMPAQ Professional Workstation XP1000 Console V5.9-1 Dec 14 2000 16:19:05 >>>sho dev dka0.0.0.6.1 DKA0 RZ2CD-KS 0306 dka100.1.0.6.1 DKA100 SEAGATE ST39140W 1498 dka200.2.0.6.1 DKA200 RZ2DD-KS 0306 dqa0.0.0.107.0 DQA0 TOSHIBA CD-ROM XM-6302B 1017 dqa1.1.0.107.0 DQA1 QUANTUM FIREBALL CX10.2A A3F.0B00 dva0.0.0.0.0 DVA0 ewa0.0.0.3.1 EWA0 00-00-F8-71-AE-00 pka0.7.0.6.1 PKA0 SCSI Bus ID 7 5.57 Is this bizzare or what? I've tried reseating PCI cards, and reseating the CPU daughterboard. The only thing which seems to matter is if the machine is vertical, or flipped over on its side. (The latter seems to make it work just fine!). Do I need a new motherboard or CPU daughterboard? Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message