HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- ioscan h/w path explaination needed and core dump
Operating System - HP-UX
1829146
Members
2103
Online
109986
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
05-17-2006 03:32 AM
05-17-2006 03:32 AM
ioscan h/w path explaination needed and core dump
Dears,
anyone can explain abt h/w path which provided by ioscan result,
what are the max possibilitied O.S make core dump
and what are the causions
thanks
siva baskara
anyone can explain abt h/w path which provided by ioscan result,
what are the max possibilitied O.S make core dump
and what are the causions
thanks
siva baskara
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2006 03:41 AM
05-17-2006 03:41 AM
Re: ioscan h/w path explaination needed and core dump
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2006 04:27 AM
05-17-2006 04:27 AM
Re: ioscan h/w path explaination needed and core dump
Hi Siva,
You can find more information about H/W paths at http://docs.hp.com/en/AB379-96001/ch01s12.html
When you get a core, analysis with file and adb. It should give where exactly it got core.
-Arun
You can find more information about H/W paths at http://docs.hp.com/en/AB379-96001/ch01s12.html
When you get a core, analysis with file and adb. It should give where exactly it got core.
-Arun
"A ship in the harbor is safe, but that is not what ships are built for"
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-17-2006 02:26 PM
05-17-2006 02:26 PM
Re: ioscan h/w path explaination needed and core dump
HP-UX runs on hundreds of different models and the hardware path is unique to each model. So the two references may be of some use but not if you have an older machine. Your system's hardware reference manual should have the I/O slots referenced. What model computer do you have?
As far as an O.S. core dump (which is a system crash), there are thousands of ways it can crash. The cause could be bad hardware, a bad program that modifies kernel memory, or lack of patches. Of all the reasons for a system crash, lack of current patches is the most common reason.
Bill Hassell, sysadmin
As far as an O.S. core dump (which is a system crash), there are thousands of ways it can crash. The cause could be bad hardware, a bad program that modifies kernel memory, or lack of patches. Of all the reasons for a system crash, lack of current patches is the most common reason.
Bill Hassell, sysadmin
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