Outage registers useful for crash analysis without dump?

Among many other problems with our production SCO OpenServer 5.0.5 system, it kernel traps often. Those who set it up did not allow enough swap/dump space to capture an entire dump - only 16000 pages of 260000. Whenever the machine panics, I take note of all the register values; I've got over a dozen of these lists just since last April. Is there anything I can tell from this data without the dump?

There is some information on this in the OpenServer Handbook re: comparing EIP numbers to determine software/hardware cause, error messages in /usr/adm/messages, etc., but I'm looking for more detailed information.

And yes - on the new 5.0.7 server we're working on, there's more than enough swap/dump space...

I can tell at least one thing: the panics this morning and three days ago were caused by the same condition, I believe: the register values are identical. Don't think I've ever seen that before.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

If EIP is the same it most likely means that you have bad RAM chips in tour system


i.e run memtest86 and other such software

OpenServer does not crash right away.
Kernel panics could cause by hardware, software or combination of both. Life would be
easier it you can get the crash dump image file.

Without a cash dump, you can try to reproduce the same problem by test the same application in an identical machine (with the same OS and application installed) to see
if you get the same problem.

Please have a look at this "Techniques to help identify the failing function of a kernel panic" SCO doc:


and try to write down all the screen error messages when the kernel panic happen again,
to see if you can identify the cause of the problem.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.