Reboot after panic: Data page fault

[Robert Morey]

Hello,

Can anyone tell me how I can find out what might be causing the above scenario on my HP-UX 10.20 system? It doesn't happen all the time and definitely isn't happening in a pattern at least none I can determine. It isn't a critical issue( at least not yet ), but it is becoming annoying.

Thank you,

moreyrd

[John Carr_2]

Hi are you just getting the message or is the server rebooting , if it is rebooting I would be panicking ?

have you checked /var/adm/syslog/syslog.log ?

cheers
John.

[pap]

Hi If this is the first time happened , try to run Q4 analysis on your machine and check the report. Also look at the tumstone log for any hardaware failure caused this reboot. Check the string in /etc/shutdownlog for some more information.

hope this helps.

-pap

[Clemens van Everdingen]

Hi,

I would not run to patches immediately, but have my dump files analyzed with q4.
You can find the dump files in /var/adm/crash.
Also check the /var/tombstones/ts99 file for HPMC error's with might lead to some hardware failure.

C.

[Clemens van Everdingen]

Hi,

Another suggestion might be to log a call at HP response center.

See also this thread where starting with q4 is explained.

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x3b01a22d6d27d5118fef0090279cd0f9,00.html

If you try q4 post the output, so we can try to help you out.

C.

[S.K. Chan]

You won't be able to determine for sure what is causing the data page faults until you examine the stack trace, usually not easy to understand it even if you manage to get a q4 trace on it. In general possible causes are :-
a) Routine/program being called failed to handle it.
b) Bad parameter being passed to caller routine.
c) Data corruption.

Get HP response center to analyse the dump as soon as possible.

[melvyn burnard]

get the dump analysed by your local HP Response Centre. You may not think it critical now, but at some stage, it will become critical, usually when you least expect/need it, and Murphy's Law says it could be when you have no valid backups and the system comes backk up with a file system damaged.