HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Reboot failed after installing QPK1100
Operating System - HP-UX
1836436
Members
2520
Online
110100
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
02-17-2002 11:32 PM
02-17-2002 11:32 PM
Reboot failed after installing QPK1100
After Installing the QPK1100 December 2001 for HP-UX 11.00
I got the following error from the gsp of our L1000 (Processor PA-8500 440MHz, Firmware Revison 40.48):
Log Entry # 1 :
SYSTEM NAME: lds3gsp
DATE: 02/14/2002 TIME: 16:31:57
ALERT LEVEL: 3 = System blocked waiting for operator input
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: E = system warning STATUS: F
CALLER SUBACTIVITY: FF = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00
0xF8E000301100EFFF 00000000 0000EFFF type 31 = legacy PA HEX chassis-code
0x58E008301100EFFF 00006601 0E101F39 type 11 = Timestamp 02/14/2002 16:31:57
Log Entry # 2 :
SYSTEM NAME: lds3gsp
DATE: 02/14/2002 TIME: 16:31:54
ALERT LEVEL: 3 = System blocked waiting for operator input
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: E = system warning STATUS: 0
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00
0xF8E000301100E000 00000000 0000E000 type 31 = legacy PA HEX chassis-code
0x58E008301100E000 00006601 0E101F36 type 11 = Timestamp 02/14/2002 16:31:54
Log Entry # 3 :
SYSTEM NAME: lds3gsp
DATE: 02/14/2002 TIME: 16:31:42
ALERT LEVEL: 12 = Software failure
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: B = system panic STATUS: 0
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00
0xA0E000C01100B000 00000000 000005E9 type 20 = major change in system state
0x58E008C01100B000 00006601 0E101F2A type 11 = Timestamp 02/14/2002 16:31:42
Log Entry # 4 :
SYSTEM NAME: lds3gsp
DATE: 02/14/2002 TIME: 16:31:42
ALERT LEVEL: 12 = Software failure
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: B = system panic STATUS: 0
CALLER SUBACTIVITY: 80 = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00
0xF8E000C01100B800 00000000 0000B800 type 31 = legacy PA HEX chassis-code
0x58E008C01100B800 00006601 0E101F2A type 11 = Timestamp 02/14/2002 16:31:42
With the newly build kernel form the QPK it is not possible to boot the kernel.
Luckily the old kernel works.
What is the reason? Any ideas to fix the problem?
Thanks,
F. Wagner
I got the following error from the gsp of our L1000 (Processor PA-8500 440MHz, Firmware Revison 40.48):
Log Entry # 1 :
SYSTEM NAME: lds3gsp
DATE: 02/14/2002 TIME: 16:31:57
ALERT LEVEL: 3 = System blocked waiting for operator input
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: E = system warning STATUS: F
CALLER SUBACTIVITY: FF = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00
0xF8E000301100EFFF 00000000 0000EFFF type 31 = legacy PA HEX chassis-code
0x58E008301100EFFF 00006601 0E101F39 type 11 = Timestamp 02/14/2002 16:31:57
Log Entry # 2 :
SYSTEM NAME: lds3gsp
DATE: 02/14/2002 TIME: 16:31:54
ALERT LEVEL: 3 = System blocked waiting for operator input
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: E = system warning STATUS: 0
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00
0xF8E000301100E000 00000000 0000E000 type 31 = legacy PA HEX chassis-code
0x58E008301100E000 00006601 0E101F36 type 11 = Timestamp 02/14/2002 16:31:54
Log Entry # 3 :
SYSTEM NAME: lds3gsp
DATE: 02/14/2002 TIME: 16:31:42
ALERT LEVEL: 12 = Software failure
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: B = system panic STATUS: 0
CALLER SUBACTIVITY: 00 = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00
0xA0E000C01100B000 00000000 000005E9 type 20 = major change in system state
0x58E008C01100B000 00006601 0E101F2A type 11 = Timestamp 02/14/2002 16:31:42
Log Entry # 4 :
SYSTEM NAME: lds3gsp
DATE: 02/14/2002 TIME: 16:31:42
ALERT LEVEL: 12 = Software failure
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: B = system panic STATUS: 0
CALLER SUBACTIVITY: 80 = implementation dependent
REPORTING ENTITY TYPE: E = HP-UX REPORTING ENTITY ID: 00
0xF8E000C01100B800 00000000 0000B800 type 31 = legacy PA HEX chassis-code
0x58E008C01100B800 00006601 0E101F2A type 11 = Timestamp 02/14/2002 16:31:42
With the newly build kernel form the QPK it is not possible to boot the kernel.
Luckily the old kernel works.
What is the reason? Any ideas to fix the problem?
Thanks,
F. Wagner
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2002 12:47 AM
02-18-2002 12:47 AM
Re: Reboot failed after installing QPK1100
I would imagine it's something to do with PHKL_18543
in any case, you may have needed to install the XSHWCR____ before the QPK.
Did you read the release notes!
I installed that recently, but installed on top of a Sept 2001 clean install and had no problems (apart from a reflectionX telnet issue - need to add a telnet patch after.)
Later,
Bill
in any case, you may have needed to install the XSHWCR____ before the QPK.
Did you read the release notes!
I installed that recently, but installed on top of a Sept 2001 clean install and had no problems (apart from a reflectionX telnet issue - need to add a telnet patch after.)
Later,
Bill
It works for me (tm)
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