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
Forums
Discussions
Discussions
Discussions
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
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
10-12-2003 11:23 PM
10-12-2003 11:23 PM
Boot
I turn off the system at the weekend, and now I srarted it but it always reboot. I connect to GSP and take the note of the system:
real_page_alloc_addr() fails, status = -1
************* SYSTEM ALERT **************
SYSTEM NAME: gsproot
DATE: 10/13/2003 TIME: 02:00:33
ALERT LEVEL: 12 = Software failure
REASON FOR ALERT
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH FLASH FLASH ON ON
LED State: Unexpected Reboot. Running non-OS code. Non-critical error detected.
Check Chassis and Console Logs for error messages.
0xF8E000C01100B800 00000000 0000B800 - type 31 = legacy PA HEX chassis-code
0x58E008C01100B800 00006709 0D020021 - type 11 = Timestamp 10/13/2003 02:00:33
A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry
->Choice:
Stored message buffer up to panic:
System Panic:
linkstamp: Mon Oct 21 12:13:10 TST 2002
_release_version: @(#) $Revision: vmunix: vw: -proj selectors:
CUPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 '
CUPI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
panic: alloc_pdc_pages: real_page_alloc_addr() fails
PC-Offset Stack Trace (read across, top of stack is 1st):
0x001ed1d0 0x0023f4e4 0x003fd274
0x001e0ccc 0x001db234
End Of Stack
*** 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.
[Read only - use ^Ecf for console write access.]
[Read only - use ^Ecf for console write access.]
real_page_alloc_addr() fails, status = -1
************* SYSTEM ALERT **************
SYSTEM NAME: gsproot
DATE: 10/13/2003 TIME: 03:05:37
ALERT LEVEL: 12 = Software failure
REASON FOR ALERT
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH FLASH FLASH ON ON
LED State: Unexpected Reboot. Running non-OS code. Non-critical error detected.
Check Chassis and Console Logs for error messages.
0xF8E000C01100B800 00000000 0000B800 - type 31 = legacy PA HEX chassis-code
0x58E008C01100B800 00006709 0D030525 - type 11 = Timestamp 10/13/2003 03:05:37
Please tell me what matter with my system.
Thank you very much.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-12-2003 11:29 PM
10-12-2003 11:29 PM
Re: Boot
If its the CPU it appears to be the only one you have. You are probably going to have call hardware out for a replacement.
Visually inspect the machine for obvious issues like plugs unplugged by cleaning personnel.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-12-2003 11:39 PM
10-12-2003 11:39 PM
Re: Boot
We are trying to Allocate the PDC (Processor dependent Code) pages and we cannot do so.
You will likely need to open a HW call if you have support on the box.
If you are troubleshooting on your own, check power as well as re-seat the CPU boards .
Next is probably to replace a cpu board.
I will see if I can find out more on this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-12-2003 11:46 PM
10-12-2003 11:46 PM
Re: Boot
The panic under these circumstances is caused because when we go to allocate pdc pages, we want to allocate to a certain set of memory locations .
Because of the defective memory simm, we fail in trying to go out to that memory location .
I would suggest that you involve HP support to help troubleshoot the problem.
Best regards,
Kent Ostby
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-13-2003 12:59 AM
10-13-2003 12:59 AM
Re: Boot
Check out these two patches,
http://www1.itrc.hp.com/service/patch/patchDetail.do?patchid=PHKL_28766&context=hpux:800:11:00
Hope this helps.
Regds