Return-path: <alpha-osf-managers-relay_at_sws1.ctd.ornl.gov>
Received: from sws1.CTD.ORNL.GOV by SLUVCA.SLU.EDU (PMDF V5.0-4 #5070)
id <01HVTSPR2KFK8Y54TN_at_SLUVCA.SLU.EDU> for ALPHAOSF_at_SLUAVA.SLU.EDU; Thu,
28 Sep 1995 23:30:47 -0600 (CST)
Received: (from daemon_at_localhost) by sws1.CTD.ORNL.GOV (8.6.10/8.6.10)
id XAA11511 for aomaa; Thu, 28 Sep 1995 23:14:39 -0400
Received: from oaunx1.ctd.ornl.GOV (oaunx1.ctd.ornl.gov [128.219.128.17])
by sws1.CTD.ORNL.GOV (8.6.10/8.6.10) with ESMTP id XAA11499 for
<alpha-osf-managers_at_sws1.ctd.ornl.gov>; Thu, 28 Sep 1995 23:14:35 -0400
Received: from UMALP3.physics.lsa.umich.edu by oaunx1.ctd.ornl.GOV
(8.6.10/3.0-C) id XAA06192; Thu, 28 Sep 1995 23:14:32 -0400
Received: by umalp1.physics.lsa.umich.edu (MX V4.1 AXP) id 14; Thu,
28 Sep 1995 23:14:15 -0400 (EDT)
Date: Thu, 28 Sep 1995 23:14:14 -0400 (EDT)
From: "Dave Wolinski, University of Michigan"_at_sws1.CTD.ORNL.GOV
Subject: SUMMARY: Session manager dies unexpecedly
Sender: alpha-osf-managers-relay_at_sws1.ctd.ornl.gov
To: alpha-osf-managers_at_ornl.gov
Reply-to: "Dave Wolinski, University of Michigan"
<wolinski_at_umalp1.physics.lsa.umich.edu>
Message-id: <00997180.977E01AD.14_at_umalp1.physics.lsa.umich.edu>
Content-transfer-encoding: 7BIT
Followup-to: poster
I recently requested help for a problem on our Alpha running OSF v3.0.
The symptoms of this weird problem were:
- when logged into the console, your session manager
would die unexpectedly
- when text scrolled by fast, you often saw garbage in that window
- when windows moved/closed, some pixels were left behind until
you did an xrefresh
(all independent of user)
Thanks to those who replied:
granse_at_iws.fhg.de, Peter.Kerschl_at_lfp.blm.tu-muenchen.de, rockwell_at_rch.dec.com,
joe_at_resptk.bhp.com.au, Knut.Hellebo_at_nho.hydro.com
Useful suggestions were:
- verifying the Xwindows subsets
- checking the xdm configuration files and X resource files
- studying the system swap space during the problem
However, none of the above checks uncovered anything that was wrong. Finally,
I halted the machine, cycled power, and while trying to reboot, I received
"system hardware check abort" errors. This was the final tipoff that it was
probably a hardware problem. After swapping out the system board (the larger
"motherboard" in the Dec 3000), the problem went away.
Digital advised me that it is probably a bad graphics adaptor on the system
board.
-Dave Wolinski, University of Michigan
Received on Fri Sep 29 1995 - 05:57:56 NZST