- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Running HP-UX 11iv2 in debugging mode
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
тАО05-02-2011 11:13 PM
тАО05-02-2011 11:13 PM
Running HP-UX 11iv2 in debugging mode
I have a kernel module, which as per one of the consumer, is causing panic. Looking at the dump, it seems, that memory it was using is wiped out. The command used by customer was very simple and we tried to run that 1000s of the time in multiprocess environment(through scripts) but couldn't reproduce it. From the panic dump, we checked that it was free call to a variable. We have made sure that for sure, that double free call can not come to that variable, through locking mechanism.
I think, If I enable kernel in debug mode it may help if this problem repeats or even help in reproducing it. Is there any way to start kernel/OS in debug mode ?
Regards,
Tarun
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-02-2011 11:51 PM
тАО05-02-2011 11:51 PM
Re: Running HP-UX 11iv2 in debugging mode
Although I do not have very much experience with this topic, I believe what you are looking for is KWDB:
http://h21007.www2.hp.com/portal/site/dspp/menuitem.863c3e4cbcdc3f3515b49c108973a801/?jumpid=reg_R1002_USEN&ciid=aa089099cee021109099cee02110275d6e10RCRD
Pay special attention to Chapter 3 of the manual which describes the various boot options you will need to use:
http://h21007.www2.hp.com/portal/download/files/unprot/ddk/kwdb3-1-3/chap3.pdf
Hope that helps,
sangilak
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-04-2011 01:25 AM
тАО05-04-2011 01:25 AM
Re: Running HP-UX 11iv2 in debugging mode
First, catch the EFI shell:
Next:
hpux -dconsole
(Boot your existing kernel with the console debugger).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-04-2011 08:24 PM
тАО05-04-2011 08:24 PM
Re: Running HP-UX 11iv2 in debugging mode
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-06-2011 11:49 PM
тАО05-06-2011 11:49 PM
Re: Running HP-UX 11iv2 in debugging mode
Only HP has that. There is a -v option for progress messages.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-07-2011 07:31 AM
тАО05-07-2011 07:31 AM
Re: Running HP-UX 11iv2 in debugging mode
Since you mention a "free call to a variable" causing a panic, I'm assuming this is a dynamic kernel allocation that the variable is a pointer to, and even if it uses the old FREE() macro -- that means it is almost certainly an Arena allocation.
Whether it is a double-free (which your statements imply is unlikely but that's what you've been looking at) or a buffer overrun (that's what it sounds like to me - the variable itself may be innocent but the metadata before it or the value stored within it could have been overwritten), I would think your next steps would be to use your support contact and request support help you in using the vmtrace utility. I'd expect the Standard Corruption mode would probably be the way to go here as long as the arena in question isn't too much memory (i.e. not >60% of the system already, there's an extra overhead in Corruption detection modes that adds up).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-08-2011 07:05 AM
тАО05-08-2011 07:05 AM
Re: Running HP-UX 11iv2 in debugging mode
now for double free logging & light weight corruption vmtrace is usually enough, and has a very limited perf impact.
Now there is a problem to analyze the results. All the tools which permit to read the vmtrace data are hp confidential.
Also some arena when vmtraced need to disable some cache features, else the result doesn't mean anything.