- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: kern.log messages!
Operating System - Tru64 Unix
1752309
Members
6161
Online
108786
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-06-2006 01:10 PM
08-06-2006 01:10 PM
kern.log messages!
Aug 6 04:25:37 yj8202 vmunix: KZPSA adapter misc error, asr=0x10, afar=0x0, afp
r=0x5e0508
Aug 6 04:25:37 yj8202 vmunix: pzaintr: KZPSA adapter misc error, asr=0x10, afar
=0x0, afpr=0x5e0508
Aug 6 04:25:37 yj8202 vmunix:
Aug 6 04:25:37 yj8202 vmunix: pza_read_log_regs: KZPSA log regs: 1 0x109907, 2
0x11, 3 0xffffffff, 4 0xffffffff, 5 0x0, 6 0x0, 7 0x0, 8 0x0, 9 0x0, a 0x0
Aug 6 04:25:37 yj8202 vmunix:
what's wrong with our system
Dec8200 Digital Unix 4.0D
DiskArray :HSZ70
r=0x5e0508
Aug 6 04:25:37 yj8202 vmunix: pzaintr: KZPSA adapter misc error, asr=0x10, afar
=0x0, afpr=0x5e0508
Aug 6 04:25:37 yj8202 vmunix:
Aug 6 04:25:37 yj8202 vmunix: pza_read_log_regs: KZPSA log regs: 1 0x109907, 2
0x11, 3 0xffffffff, 4 0xffffffff, 5 0x0, 6 0x0, 7 0x0, 8 0x0, 9 0x0, a 0x0
Aug 6 04:25:37 yj8202 vmunix:
what's wrong with our system
Dec8200 Digital Unix 4.0D
DiskArray :HSZ70
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-07-2006 01:19 AM
08-07-2006 01:19 AM
Re: kern.log messages!
Well... it sure sounds like a KZPSA has gone bad.
Did anything change recently which might have triggered this? Power problems recently?
While at console check around with 'show config' and maybe run a test.
Is your KZPSA firmware up to date?
Which IO module plugged into the system backplane?
The 'multi-purpose' KFTIA or PCI only KFTHA?
Is it still properly connected/seated?
pop out and push back? Jiggle cables and retighten as needed?
If this was my system then I would first doublecheck the scsi cabling. Anyting changed? Properly terminated and Y cables/trilinks still properly attached?
It should not take down the adapter, but it is the easiest to check.
Are there other error on the systems, poiting
Next, if that does not fix it, then 'reseat' the adapter. Slide out the PCI cage, open side, pop adapter, push back, try again.
Finally, grab a spare adapter and replace the suspect one.
hth,
Hein.
Did anything change recently which might have triggered this? Power problems recently?
While at console check around with 'show config' and maybe run a test.
Is your KZPSA firmware up to date?
Which IO module plugged into the system backplane?
The 'multi-purpose' KFTIA or PCI only KFTHA?
Is it still properly connected/seated?
pop out and push back? Jiggle cables and retighten as needed?
If this was my system then I would first doublecheck the scsi cabling. Anyting changed? Properly terminated and Y cables/trilinks still properly attached?
It should not take down the adapter, but it is the easiest to check.
Are there other error on the systems, poiting
Next, if that does not fix it, then 'reseat' the adapter. Slide out the PCI cage, open side, pop adapter, push back, try again.
Finally, grab a spare adapter and replace the suspect one.
hth,
Hein.
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