- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: System Panic - Tru64 Version 4.0F
Operating System - Tru64 Unix
1754021
Members
7623
Online
108811
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
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
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
08-25-2009 07:01 AM
08-25-2009 07:01 AM
System Panic - Tru64 Version 4.0F
I have a custom SCSI device running on an ES40 running Tru64 version 4.0F. I have reviewed the patch list for possible solutions, but only find a Patch 1147.00, which was for version 4.0D (patch kit 009). I have PK8 installed with my version (4.0F).
Would anyone know of a specific patch for 4.0F that would address this issue?
I encountered the following events.
----- EVENT INFORMATION -----
EVENT CLASS ERROR EVENT
OS EVENT TYPE 199. CAM SCSI
SEQUENCE NUMBER 553.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Mon Aug 24 06:23:48 2009
OCCURRED ON SYSTEM s6
SYSTEM ID x000D0022
SYSTYPE x00000000
PROCESSOR COUNT 2.
PROCESSOR WHO LOGGED x00000000
----------------------------------------
EVENT CLASS ERROR EVENT
OS EVENT TYPE 302. PANIC
SEQUENCE NUMBER 554.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Mon Aug 24 06:32:12 2009
OCCURRED ON SYSTEM s6
SYSTEM ID x000D0022
SYSTYPE x00000000
PROCESSOR COUNT 2.
PROCESSOR WHO LOGGED x00000000
MESSAGE panic (cpu 0): lw_remove: light weight
_wiring(s) found
ANY HELP IS APPRECIATED.
Would anyone know of a specific patch for 4.0F that would address this issue?
I encountered the following events.
----- EVENT INFORMATION -----
EVENT CLASS ERROR EVENT
OS EVENT TYPE 199. CAM SCSI
SEQUENCE NUMBER 553.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Mon Aug 24 06:23:48 2009
OCCURRED ON SYSTEM s6
SYSTEM ID x000D0022
SYSTYPE x00000000
PROCESSOR COUNT 2.
PROCESSOR WHO LOGGED x00000000
----------------------------------------
EVENT CLASS ERROR EVENT
OS EVENT TYPE 302. PANIC
SEQUENCE NUMBER 554.
OPERATING SYSTEM DEC OSF/1
OCCURRED/LOGGED ON Mon Aug 24 06:32:12 2009
OCCURRED ON SYSTEM s6
SYSTEM ID x000D0022
SYSTYPE x00000000
PROCESSOR COUNT 2.
PROCESSOR WHO LOGGED x00000000
MESSAGE panic (cpu 0): lw_remove: light weight
_wiring(s) found
ANY HELP IS APPRECIATED.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-25-2009 09:48 AM
08-25-2009 09:48 AM
Re: System Panic - Tru64 Version 4.0F
As far as I can tell, there has never been a report of this panic on V4.0F. Also, the fix you found from patch 1147 for V4.0D should certainly already be included in your current version. So no existing patch will resolve this, and because V4.0F is long past the end of engineering support, there's no way to get one.
However, since there /are/ no other reports, it's possible that this was a "one off" panic and will never recur. If it does recur, you could try turning off light-weight wiring, by setting new_wire_method=0 in the vm subsystem. That's kind of a shot in the dark, but unfortunately you're not likely to get a more definitive resolution.
Another thought is to check the firmware version on your ES40 ("consvar -g version" will provide this information.) If it's very old (say older than 6.6) you might want to update it. Again, this is another shot in the dark.
Martin
However, since there /are/ no other reports, it's possible that this was a "one off" panic and will never recur. If it does recur, you could try turning off light-weight wiring, by setting new_wire_method=0 in the vm subsystem. That's kind of a shot in the dark, but unfortunately you're not likely to get a more definitive resolution.
Another thought is to check the firmware version on your ES40 ("consvar -g version" will provide this information.) If it's very old (say older than 6.6) you might want to update it. Again, this is another shot in the dark.
Martin
I work for HPE
A quick resolution to technical issues for your HPE products is just a click away HPE Support Center
See Self Help Post for more details
A quick resolution to technical issues for your HPE products is just a click away HPE Support Center
See Self Help Post for more details
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP