- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- system crash D390
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-05-2005 07:55 AM
тАО12-05-2005 07:55 AM
system crash D390
Boot IO Dependent Code (IODC) revision 152
HARD Booted.
ISL Revision A.00.43 Apr 12, 2000
ISL booting hpux
Boot
: disc(8/4.10.0;0)/stand/vmunix
9867264 + 1892352 + 1324272 start 0x1f6ae8
j2Dj10L
FLT B800jCj1D
Stored message buffer up to panic:
Variable size pages used to map 1000 graf pages at fffffffff7000000
gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: nfs3_link(): File system was registered at index 3.
NOTICE: autofs_link(): File system was registered at index 6.
NOTICE: cachefs_link(): File system was registered at index 7.
8 ccio
8/0 bc
8/0/0 mux2
8/4 c720
8/4.6 tgt
8/4.6.0 sctl
8/4.8 tgt
8/4.8.0 sdisk
8/4.9 tgt
8/4.9.0 sdisk
8/4.10 tgt
8/4.10.0 sdisk
8/4.11 tgt
8/4.11.0 sdisk
8/16 bus_adapter
8/16/5 c720
8/16/5.6 tgt
8/16/5.6.0 sdisk
8/16/5.7 tgt
8/16/5.7.0 sctl
8/16/6 lan2
8/16/0 CentIf
ps2_readbyte_timeout: no byte after 500 uSec
ps2_readbyte_timeout: no byte after 500 uSec
8/16/7 ps2
8/20 bus_adapter
8/20/2 asio0
10 ccio
g3_init_display: STI init_graph failed (135)
Trap Type 15 (Data page fault):
Instruction Address (pcsq.pcoq) = 0x0.0x32f480
Instruction (iir) = 0x43f30000 (load/store)
Target Address (isr.ior) = 0x0.0x00000000f6000663
Base Register (gr31) = 0x00000000f6000663
Savestate Ptr (ssp) = 0xc048400.0x400003ffffff1ae8
Savestate Return Pointer (ss_rp) = 0x000000000032f458
System Panic:
linkstamp: Mon Dec 5 12:51:02 EST 2005
_release_version: @(#) $Revision: vmunix: vw: -proj selectors: CUPI80_B
L2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL
2000_1108' Wed Nov 8 19:24:56 PST 2000 $
panic: Data page fault
PC-Offset Stack Trace (read across, top of stack is 1st):
0x00209388 0x0025ea2c 0x0015f27c
0x0016159c 0x0032f480 0x00330a98
0x00322fe0 0x00310cec 0x00310638
0x003128b0 0x003028f4 0x0053a758
0x00746a28 0x00478f4c 0x004799f0
0x0038474c 0x00384c70 0x00370fc0
0x003712c4 0x00370f5c 0x003712c4
0x00370f5c 0x003716dc 0x00375050
0x00447ca4 0x0034dbd8 0x0016d544
0x001f70e4
End Of Stack
j2Dj10L
WARN E000jCj1Dj2Dj10L
WARN E000
*** A system crash has occurred. (See the above messages for details.)
*** The system is now preparing to dump physical memory to disk, for use
*** in debugging the crash.
ERROR: Your system crashed before I/O and dump configuration was complete.
A crash dump cannot be taken under these circumstances without
special configuration. Contact your HP support representative.
jCj1Dj2Dj10L
WARN EFFFjCj1D
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-05-2005 08:54 AM
тАО12-05-2005 08:54 AM
Re: system crash D390
Log a call with your local HP Response Centre
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-06-2005 06:26 AM
тАО12-06-2005 06:26 AM
Re: system crash D390
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-06-2005 07:12 AM
тАО12-06-2005 07:12 AM
Re: system crash D390
The best thing is to call in HP and this is a hardware issue ,they would ask you to capture and send these data and they should take care of this.
Rgds
HGN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-09-2006 01:37 AM
тАО02-09-2006 01:37 AM