1826797 Members
2624 Online
109703 Solutions
New Discussion

Data Page Fault

 
SOLVED
Go to solution
ramesh_4
Occasional Advisor

Data Page Fault

My Server crashed today and when i checked up the shutdownlog it gave me the the error message "Data page fault". Can anyone pls explain what this error means and is there any fix to rectify it from happening again.
like to find out new things and compare with other flavours of unix
2 REPLIES 2
Steffi Jones_1
Esteemed Contributor
Solution

Re: Data Page Fault

Hello,

just that one line will not get you too far to find the answer.

If the system is configured properly you will find files in /var/adm/crash with the timestamp of the crash.
That actually has all the valid information...
but you need to run a tool called q4 on this crash dump.
Check the ITRC for help on how to use q4 and get it started. But it is probably a good thing to open a call with the HP response center to have them help you.

Some other things you can check are:

- dmesg output
- /var/adm/syslog/OLDsyslog.log
- diagnostics if hw was the reason for the fault

A lot of these crashes can be fixed by installing additional patches

Hope that gave you a start.

Steffi Jones
Printaporn_1
Esteemed Contributor

Re: Data Page Fault

Hi,

Here is the steps to use q4

but log case to Solution Center is recommended

HP-UX 11.0 already have q4 package in /usr/contrib/bin

1. cd /var/adm/crash/crash.0
#/usr/contrib/bin/q4prep
q4 library files being created in /var/adm/crash/crash.0/q4lib

2.cd q4lib
#cp sample.q4rc.pl ~/.q4rc.pl
3. cd ..
#q4 -p
@(#) q4 $Revision: 1.79a $ $Date: 97/09/08 12:00:22 $ 0
Reading kernel symbols ...
Reading kernel data types ...
Initialized PA-RISC 2.0 address translator ...
Initializing stack tracer ...
Get the latest Q4 news by typing "news".

q4> include analyze.pl
loading ./q4lib/analyze.pl ...
loading ./q4lib/uname.pl ...
loading ./q4lib/misc.pl ...
loading ./q4lib/uptime.pl ...
loading ./q4lib/adjust.pl ...
loading ./q4lib/messagebuffer.pl ...
loading ./q4lib/addresses.pl ...
loading ./q4lib/tables.pl ...
loading ./q4lib/processors.pl ...
loading ./q4lib/crashes.pl ...
loading ./q4lib/rpb.pl ...
loading ./q4lib/traces.pl ...
loading ./q4lib/globals.pl ...
loading ./q4lib/processes.pl ...
loading ./q4lib/commands.pl ...
loading ./q4lib/credentials.pl ...
loading ./q4lib/threads.pl ...
loading ./q4lib/user.pl ...
loading ./q4lib/vm.pl ...
loading ./q4lib/vm_vfddbd.pl ...
loading ./q4lib/files.pl ...
loading ./q4lib/vfs.pl ...
loading ./q4lib/inode.pl ...
loading ./q4lib/buf.pl ...
q4>run Analyze UAP > ana.out

-----
then waiting till finish , or in another session
cd /var/adm/crash/crash.0
vi ana.out
search for stack


Stack trace from the first crash event:
stack trace for event 0
crash event was a TOC
FUNC PC SP FMP SSP
idle+0xa78 0.0x135a60 0.0x0'0d20c1f0 0.0x0'0d20c1e0 n/a
swidle_exit+0x0 0.0x1380ac 0.0x0'0d20c050 0.0x0'0d20c040 n/a

enjoy any little thing in my life