- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Kernel hang on Ignite
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-16-2008 11:03 AM
тАО05-16-2008 11:03 AM
Kernel hang on Ignite
* Installing fileset "Asian-UTILITY.MFCONV-JPN-COM,r=B.11.31" (660 of
1378).
* Installing fileset "Asian-UTILITY.MFCONV-JPN-RUN,r=B.11.31" (661 of
1378).
Stored message buffer up to system crash:
MFS is not defined.
krs_read_mfs: Error 5 opening MFS.
Found adjacent data tr. Growing size. 0x21d9000 -> 0x61d9000.
Loaded ACPI revision 2.0 tables.
krs_read_mfs: Error 5 opening MFS.
MCA recovery subsystem disabled, not supported on this platform.
montecito_proc_features: PROC_GET_FEATURES returned 0xfffffffffffffff8
bad_kern_reference: 0xec6031.0x6, fault = 0x1c
===========After reboot==========
panic: Fault when executing in kernel mode
Stack Trace:
IP Function Name
0xe000000002767460
0xe0000000013cdd00
0xe000000000ce0010
0xe000000002268780
0xe000000000cb25a1
0xe000000000d45520
0xe000000000d13e30
0xe000000000d14550
0xe000000000ce0010
0xe000000002268780
End of Stack Trace
linkstamp: Wed Feb 06 17:16:26 MST 2008
_release_version: @(#) $Revision: vmunix: B.11.31_LR FLAVOR=perf
Calling function e000000001c9c6c0 for Shutdown State 1 type 0x2
THE SPINLOCK CODE HAS NOT FAILED!
You are seeing this message because some kernel code has
attempted to yield the processor holding spinlocks.
Please look for the code that did not drop the spinlock!
It appears to be a bug but maybe not? I previously set up the array with distinct virtual disks and had no problem installing the VM's.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2008 11:18 AM
тАО05-16-2008 11:18 AM
Re: Kernel hang on Ignite
Even the latest release quotes some IVM issues.
http://www.docs.hp.com/en/IUX/docs/release_note.pdf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-19-2008 04:01 PM
тАО06-19-2008 04:01 PM
Re: Kernel hang on Ignite
I recently used ignite to backup & restore, I got the same error msg as this:
MFS is not defined.
krs_read_mfs: Error 5 opening MFS.
Found adjacent data tr. Growing size. 0x2131000 -> 0x6131000.
Loaded ACPI revision 2.0 tables.
krs_read_mfs: Error 5 opening MFS.
Can you explain a solution, thanks a lot.
Charlie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-20-2008 09:26 AM
тАО06-20-2008 09:26 AM
Re: Kernel hang on Ignite
I have several rx6600's. Those with the P400 array card work fine with IVM-those that just use the SAS Controller card fail miserably at IVM but work fine as standalone machines. I ended up simply using the machine above as a single host.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-20-2008 10:33 AM
тАО06-20-2008 10:33 AM
Re: Kernel hang on Ignite
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2008 12:01 PM
тАО06-26-2008 12:01 PM
Re: Kernel hang on Ignite
* Installing fileset "hpuxwsXML.BATIK,r=A.2.03" (1472 of 1476).
* Installing fileset "hpuxwsXML.COCOON,r=A.2.03" (1473 of 1476).
* Installing fileset "hpuxwsXML.FOP,r=A.2.03" (1474 of 1476).
* Installing fileset "hpuxwsXML.XALANJ,r=A.2.03" (1475 of 1476).
* Installing fileset "hpuxwsXML.XERCESJ,r=A.2.03" (1476 of 1476).
Stored message buffer up to system crash:
MFS is not defined.
krs_read_mfs: Error 5 opening MFS.
Found adjacent data tr. Growing size. 0x21d9000 -> 0x61d9000.
Loaded ACPI revision 2.0 tables.
krs_read_mfs: Error 5 opening MFS.
MCA recovery subsystem disabled, not supported on this platform.
montecito_proc_features: PROC_GET_FEATURES returned 0xfffffffffffffff8
The system then re-booted and died. I've attached a complete screenshot.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2008 12:19 PM
тАО06-26-2008 12:19 PM
Re: Kernel hang on Ignite
Side note: I found a reference somewhere to corrupted 11.31 install disks on the 1207 release. I just got the 0308 set but haven't tried them yet.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2008 01:08 PM
тАО06-26-2008 01:08 PM
Re: Kernel hang on Ignite
The screen shot posted with the similar issue shows 12Gb (and most of yours were 4Gb or more without a report of different behavior), so it isn't likely the same.
Too bad there's only the addresses on the stack... the screen shot does interestingly show a SCSI bus reset just before the NULL pointer dereference in the kernel.. but that doesn't really narrow anything down without a dump (which you won't get during install without jumping through a lot of hoops Support would need to walk you through).
Be interested to know if the updated media addresses things -- otherwise, please use any support channels you have to try to get this into analysis.