HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- System rebooting
Operating System - HP-UX
1835201
Members
2543
Online
110077
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
06-16-2004 01:49 AM
06-16-2004 01:49 AM
System rebooting
the error I got in the shutdownlog is
Reboot after panic: TOC, pcsq.pcoq = 0.6a744, isr.ior = 0.6a740
08:26 Tue Jun 15 2004. Reboot after panic: TOC, pcsq.pcoq = 0.6a748, isr.ior = 0.6f04c8
09:00 Tue Jun 15 2004. Reboot after panic: TOC, pcsq.pcoq = 0.6a748, isr.ior = 0.6f04c8
Can any tell what this means or what I need to do?
thank you
Reboot after panic: TOC, pcsq.pcoq = 0.6a744, isr.ior = 0.6a740
08:26 Tue Jun 15 2004. Reboot after panic: TOC, pcsq.pcoq = 0.6a748, isr.ior = 0.6f04c8
09:00 Tue Jun 15 2004. Reboot after panic: TOC, pcsq.pcoq = 0.6a748, isr.ior = 0.6f04c8
Can any tell what this means or what I need to do?
thank you
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2004 01:57 AM
06-16-2004 01:57 AM
Re: System rebooting
You have had a major problem that you need to investigate.
check /var/adm/crash for crashes. Then you can do q4 analysis and HP can tell you what went wrong.
I've attached a doc.
Inadequate patching leads to this.
TOC also happens when the heartbeat on a serviceguard cluster is interupted.
SEP
check /var/adm/crash for crashes. Then you can do q4 analysis and HP can tell you what went wrong.
I've attached a doc.
Inadequate patching leads to this.
TOC also happens when the heartbeat on a serviceguard cluster is interupted.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
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
06-16-2004 02:00 AM
06-16-2004 02:00 AM
Re: System rebooting
This can be hardware or software related.
To eliminate a hardware fault, check /var/tombstones/ts99.
If you see "No HPMC chassis codes logged" at the top of the file are all zeroes, it's very unlikely to have been a hardware error.
If you see a list of codes, you'll need to log a hardware call with HP.
If not a hardware panic, I'd suggest logging a software call with HP giving them your system details (hardware, software and patches). They'll be able to analyse this info and advise you if there are any patches available that can prevent this from happening again.
To eliminate a hardware fault, check /var/tombstones/ts99.
If you see "No HPMC chassis codes logged" at the top of the file are all zeroes, it's very unlikely to have been a hardware error.
If you see a list of codes, you'll need to log a hardware call with HP.
If not a hardware panic, I'd suggest logging a software call with HP giving them your system details (hardware, software and patches). They'll be able to analyse this info and advise you if there are any patches available that can prevent this from happening again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2004 02:09 AM
06-16-2004 02:09 AM
Re: System rebooting
isr.ior is indicative of a HW failure. I'd start with a call to HW support first.
"Downtime is a Crime."
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP