[foxboro] FW: FW: AW51D Problem
- From: "Kashif Ijaz" <kashifijaz93@xxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Thu, 12 Jul 2007 16:12:08 +0400
Can it be that 64 MB memory on the box running two display manager sessions
runs out of memory and that makes it crash. If yes, how to verify it.
Regards,
Kashif Ijaz
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Kashif Ijaz
Sent: Thursday, July 12, 2007 4:07 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] FW: AW51D Problem
One more information on this is that Additional display manager is =
running
and remote machine is also accessing this AW51D through Exceed X server.
Regards,
-----Original Message-----
From: Kashif Ijaz [mailto:kashifijaz93@xxxxxxxxxxx]=20
Sent: Thursday, July 12, 2007 3:58 PM
To: foxboro@xxxxxxxxxxxxx
Subject: RE: [foxboro] AW51D Problem
Dear Kevin
The whole string is "panic[cpu0]/thread=3D0x609c65a0:trap" in the
/var/adm/messages file.
The vmstat 10 10 gives me around 88% idle time on nearly all attempts.
When the display freezes, mouse does not move and you can do absolutely =
no
action. Also the last screen with the last values of process parameters =
is
frozen. Only resolution is to the turn the power to the box off and then =
on.
We are using version 4.3 of I/A.
Also there is no weight on the boxes.
Regards,
Kashif Ijaz
Senior Design & Application Engineer
INTECH Process Automation
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] =
On
Behalf Of Kevin Fitzgerrell
Sent: Thursday, July 12, 2007 3:45 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] AW51D Problem
Kashif,
The information after the "Panic" is pretty important for determining
what the problem is.
If this has happened recently, take a look in the output of the dmesg
command or in the /var/adm/messages* files and see what the whole
panic string is. Alternatively, go to /opt/crash/{letterbug} and do
"strings * | grep panic" and see what the panic strings have been.
There were some CPU issues with Ultrasparc-II CPUs - you may be seeing
cache or writeback data parity issues - these are CPU related. Other
panic strings may point to memory problems.
64mb of ram seems small for an AW51D - can you email a copy of the
output of vmstat 10 10
in your reply?
Your problem with the display freezing is likely a different issue.
Many users have had an issue with the alarm manager causing the screen
to stop taking mouse/kbd input. If the mouse moves but can't click
anything, try to log in remotely and kill the alarm manager task. If
the screen un-freezes then you know that's the issue. The alarm
manager will restart the next time the alarm button is selected.
There have been a number of Foxboro Helpful Hints and QFs that reduce
the incidence of this problem but I don't know if it is completely
resolved. What I/A version are you at?
I've seen frequent other problems with the 51D series workstations -
they seem to be significantly less sturdy than the other boxes in the
51A-51E range. I've had significantly more power supply, cpu and card
failures in these boxes.
If the boxes are being used on a desktop, ensure that they are not
supporting a heavy monitor. Enough weight on the top of the case when
used horizontally can cause the box to panic or shut down.
Regards,
Kevin FitzGerrell
=20
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
=20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
- » [foxboro] FW: FW: AW51D Problem
