HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Panic after add cell to partition
Operating System - HP-UX
1829166
Members
2312
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
11-05-2009 02:04 PM
11-05-2009 02:04 PM
Panic after add cell to partition
Hi
We have Itanium based SD16. One of the npar configured with one cell. On this npar already installed HP-UX 11.23. HPUX boots via SAN from EVA5000 (active-passive). We use secure path software for multi-passing.
And now we add one more cell and get panic while boot:
-------------------
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!
System Panic:
panic: spinlock: locker forgot to unlock
Stack Trace:
IP Function Name
0xe000000001607060 spinlocks_held_leaving_processor+0xb0
0xe000000000740540 exit+0x120held_leaving_processor+0xb0
0xe00000000071fd90 execve+0x1210d_leaving_processor+0xb0
0xe00000000069de70 syscall+0x920d_leaving_processor+0xb0
End of Stack Trace
-----------------------------
That means this panic? How to solve this problem?
Thanks
We have Itanium based SD16. One of the npar configured with one cell. On this npar already installed HP-UX 11.23. HPUX boots via SAN from EVA5000 (active-passive). We use secure path software for multi-passing.
And now we add one more cell and get panic while boot:
-------------------
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!
System Panic:
panic: spinlock: locker forgot to unlock
Stack Trace:
IP Function Name
0xe000000001607060 spinlocks_held_leaving_processor+0xb0
0xe000000000740540 exit+0x120held_leaving_processor+0xb0
0xe00000000071fd90 execve+0x1210d_leaving_processor+0xb0
0xe00000000069de70 syscall+0x920d_leaving_processor+0xb0
End of Stack Trace
-----------------------------
That means this panic? How to solve this problem?
Thanks
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-05-2009 02:18 PM
11-05-2009 02:18 PM
Re: Panic after add cell to partition
Shalom,
More details please.
You did this with the system up, or did you bring down the superdome complex?
Please provide more information on what you are doing.
With I/O cards, you need to run olrad before pulling them and replacing them.
My assumption is to add a cell to an npar the npar needs to be down. Your message does not make that clear.
SEP
More details please.
You did this with the system up, or did you bring down the superdome complex?
Please provide more information on what you are doing.
With I/O cards, you need to run olrad before pulling them and replacing them.
My assumption is to add a cell to an npar the npar needs to be down. Your message does not make that clear.
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
11-05-2009 06:23 PM
11-05-2009 06:23 PM
Re: Panic after add cell to partition
Assuming that you rebooted the nPar for reconfiguration -- you're going to have to engage support to solve the problem.
It would need to be determined:
+ If the nPartition correctly added the cell or is in an incorrect state (causing O/S issues).
or
+ If the additional cpus triggered an O/S issue instead (bug in the kernel) which would almost certainly entail finding out what lock was held on exit, and how it was acquired.
(Is that also really what the console showed on output? Because that stack trace shouldn't have picked up the "d_leaving_processor+0xb0" on the subsequent lines -- looks rather like the string buffer wasn't terminating with the '\0' character as it should... may be related).
Neither of which is likely something folks can walk you through/determine through forum posts.
I'd expect Support to start with full partstatus output of the pertinent partition, Firmware versions/levels and then to attempt to acquire the dump [if this is in a panic/boot loop as it sounds, that would likely involve removing the cell first -- but I wouldn't do that until they asked you to so they can understand the nPar state causing the issue].
It would need to be determined:
+ If the nPartition correctly added the cell or is in an incorrect state (causing O/S issues).
or
+ If the additional cpus triggered an O/S issue instead (bug in the kernel) which would almost certainly entail finding out what lock was held on exit, and how it was acquired.
(Is that also really what the console showed on output? Because that stack trace shouldn't have picked up the "d_leaving_processor+0xb0" on the subsequent lines -- looks rather like the string buffer wasn't terminating with the '\0' character as it should... may be related).
Neither of which is likely something folks can walk you through/determine through forum posts.
I'd expect Support to start with full partstatus output of the pertinent partition, Firmware versions/levels and then to attempt to acquire the dump [if this is in a panic/boot loop as it sounds, that would likely involve removing the cell first -- but I wouldn't do that until they asked you to so they can understand the nPar state causing the issue].
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