Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Crash of AIX box

232 views
Skip to first unread message

Michael McCrann

unread,
Sep 26, 1997, 3:00:00 AM9/26/97
to

Can anyone help me with an error log report, shown below.

I can't find any information the manuals about SYSVMM errors.

---------------------------------------------------------------------------
ERROR LABEL: DSI_PROC
ERROR ID: 20FAED7F

Date/Time: Wed Sep 24 12:42:55
Sequence Number: 223219
Machine Id: 002073635700
Node Id: maxmlprd
Error Class: S
Error Type: PERM
Resource Name: SYSVMM

Error Description
Data Storage Interrupt, Processor

Probable Causes
SOFTWARE PROGRAM

Failure Causes
SOFTWARE PROGRAM

Recommended Actions
IF PROBLEM PERSISTS THEN DO THE FOLLOWING
CONTACT APPROPRIATE SERVICE REPRESENTATIVE

Detail Data
Data Storage Interrupt Status Register
4000 0000
Data Storage Interrupt Address Register
0000 0000
Segment Register, SEGREG
05D1 5EC0
EXVAL
FFFF FFFA
---------------------------------------------------------------------------

Jim Shaffer

unread,
Sep 26, 1997, 3:00:00 AM9/26/97
to

You had an invalid memory reference with a segment other than the
kernel segment i.e., not seg 0. Did you get a dump?
If present, it's benefitial to look at the SYSDUMP_SYMP error log
entry which contains a stack traceback.

If you got a dump use crash to look at it.

In article <60g8c8$1rs$1...@hardcopy.ny.jpmorgan.com>,

--
Jim Shaffer

Steve Wise

unread,
Sep 26, 1997, 3:00:00 AM9/26/97
to Michael McCrann


Data Storage Interrupt implies that the system tried to store to a bogus
memory location. This can happen due to referencing a bogus pointer,
stepping on someone else's kernel memory, trying to access memory that's
paged out when you have interrupts disabled, etc...


--
------------------------------------------------------
Steve Wise - Senior Project Manager
journyx Consulting - (512)345-8282 - sw...@journyx.com
Get AIX help at http://journyx.com/aixs.html

Kent Squires

unread,
Sep 26, 1997, 3:00:00 AM9/26/97
to

: Probable Causes
: SOFTWARE PROGRAM

: Failure Causes
: SOFTWARE PROGRAM


This happened twice, at 2 separate jobs to me. The first one was due to
outdated microcode on a SCSI adapter. The 2nd was due to a corrupt filesystem.

What you'll need to do is contact ibm, they'll run you through creating
the dump file, and then you send that dump file to ibm for diagnoses.

I think the SYSVMM error is a pretty generic error and can point to
a lot of things.
--
ksqu...@Geeks.ORG
ksqu...@interaccess.com

0 new messages