HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: syslog of k450
Operating System - HP-UX
1832528
Members
7582
Online
110043
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
04-05-2007 01:48 AM
04-05-2007 01:48 AM
syslog of k450
hi pls tell me what is this log tells
vmunix: SCSI: Request Timeout -- lbolt: 2859125, dev: 1f025000
Apr 5 18:40:22 ncc vmunix: lbp->state: 20
Apr 5 18:40:22 ncc vmunix: lbp->offset: ffffffff
Apr 5 18:40:22 ncc vmunix: lbp->uPhysScript: 180000
Apr 5 18:40:22 ncc vmunix: From most recent interrupt:
Apr 5 18:40:22 ncc vmunix: ISTAT: 22, SIST0: 04, SIST1: 00, DSTAT: 80, DSPS: 00000006
Apr 5 18:40:22 ncc vmunix: NCR chip register access history (most recent last): 735961 accesses
Apr 5 18:40:22 ncc vmunix: 161670, ISTAT<-20
Apr 5 18:40:22 ncc vmunix: 0, ISTAT<-20
Apr 5 18:40:22 ncc vmunix: 0, ISTAT<-20
Apr 5 18:40:22 ncc vmunix: 46927, ISTAT<-20
Apr 5 18:40:22 ncc vmunix: 0, ISTAT<-20
Apr 5 18:40:22 ncc vmunix: 0, ISTAT<-20
Apr 5 18:40:22 ncc vmunix: 64541, ISTAT: 22
Apr 5 18:40:22 ncc vmunix: 4, SIST0: 04
Apr 5 18:40:22 ncc vmunix: 12, SIST1: 00
Apr 5 18:40:22 ncc vmunix: 2, DSTAT: 80
Apr 5 18:40:22 ncc vmunix: 2, DSPS: 00000006
Apr 5 18:40:22 ncc vmunix: 2, SCRATCHA: ff000871
Apr 5 18:40:22 ncc vmunix: 8, DSP: 00180058
Apr 5 18:40:22 ncc vmunix: 8, SCRATCHA1<-00
Apr 5 18:40:22 ncc vmunix: 2, CTEST3<-04
Apr 5 18:40:22 ncc vmunix: 1, STEST3<-82
Apr 5 18:40:22 ncc vmunix: lsp: 14ca9400
Apr 5 18:40:22 ncc vmunix: bp->b_dev: 1f025000
Apr 5 18:40:22 ncc vmunix: scb->io_id: 2036d87
Apr 5 18:40:22 ncc vmunix: scb->cdb: 2a 00 00 74 02 00 00 00 10 00
Apr 5 18:40:22 ncc vmunix: lbolt_at_timeout: 2856025, lbolt_at_start: 2856025
Apr 5 18:40:22 ncc vmunix: lsp->state: 10d
Apr 5 18:40:22 ncc vmunix: lbp->owner: 14ca9400
Apr 5 18:40:22 ncc vmunix: scratch_lsp: 0
Apr 5 18:40:22 ncc vmunix: Pre-DSP script dump [15756030]:
Apr 5 18:40:22 ncc vmunix: 78347100 0000000a 78350800 00000000
Apr 5 18:40:22 ncc vmunix: 0e000004 001803c0 80000000 00000000
Apr 5 18:40:22 ncc vmunix: Script dump [15756050]:
Apr 5 18:40:22 ncc vmunix: 9f0b0000 00000006 0a000000 001803c8
Apr 5 18:40:22 ncc vmunix: 721a0000 00000000 c0000004 0018035c
Apr 5 18:40:22 ncc vmunix:
Apr 5 18:40:22 ncc vmunix: SCSI: Abort Tag -- lbolt: 2859125, dev: 1f025000, io_id: 2036d87
regards sachit
vmunix: SCSI: Request Timeout -- lbolt: 2859125, dev: 1f025000
Apr 5 18:40:22 ncc vmunix: lbp->state: 20
Apr 5 18:40:22 ncc vmunix: lbp->offset: ffffffff
Apr 5 18:40:22 ncc vmunix: lbp->uPhysScript: 180000
Apr 5 18:40:22 ncc vmunix: From most recent interrupt:
Apr 5 18:40:22 ncc vmunix: ISTAT: 22, SIST0: 04, SIST1: 00, DSTAT: 80, DSPS: 00000006
Apr 5 18:40:22 ncc vmunix: NCR chip register access history (most recent last): 735961 accesses
Apr 5 18:40:22 ncc vmunix: 161670, ISTAT<-20
Apr 5 18:40:22 ncc vmunix: 0, ISTAT<-20
Apr 5 18:40:22 ncc vmunix: 0, ISTAT<-20
Apr 5 18:40:22 ncc vmunix: 46927, ISTAT<-20
Apr 5 18:40:22 ncc vmunix: 0, ISTAT<-20
Apr 5 18:40:22 ncc vmunix: 0, ISTAT<-20
Apr 5 18:40:22 ncc vmunix: 64541, ISTAT: 22
Apr 5 18:40:22 ncc vmunix: 4, SIST0: 04
Apr 5 18:40:22 ncc vmunix: 12, SIST1: 00
Apr 5 18:40:22 ncc vmunix: 2, DSTAT: 80
Apr 5 18:40:22 ncc vmunix: 2, DSPS: 00000006
Apr 5 18:40:22 ncc vmunix: 2, SCRATCHA: ff000871
Apr 5 18:40:22 ncc vmunix: 8, DSP: 00180058
Apr 5 18:40:22 ncc vmunix: 8, SCRATCHA1<-00
Apr 5 18:40:22 ncc vmunix: 2, CTEST3<-04
Apr 5 18:40:22 ncc vmunix: 1, STEST3<-82
Apr 5 18:40:22 ncc vmunix: lsp: 14ca9400
Apr 5 18:40:22 ncc vmunix: bp->b_dev: 1f025000
Apr 5 18:40:22 ncc vmunix: scb->io_id: 2036d87
Apr 5 18:40:22 ncc vmunix: scb->cdb: 2a 00 00 74 02 00 00 00 10 00
Apr 5 18:40:22 ncc vmunix: lbolt_at_timeout: 2856025, lbolt_at_start: 2856025
Apr 5 18:40:22 ncc vmunix: lsp->state: 10d
Apr 5 18:40:22 ncc vmunix: lbp->owner: 14ca9400
Apr 5 18:40:22 ncc vmunix: scratch_lsp: 0
Apr 5 18:40:22 ncc vmunix: Pre-DSP script dump [15756030]:
Apr 5 18:40:22 ncc vmunix: 78347100 0000000a 78350800 00000000
Apr 5 18:40:22 ncc vmunix: 0e000004 001803c0 80000000 00000000
Apr 5 18:40:22 ncc vmunix: Script dump [15756050]:
Apr 5 18:40:22 ncc vmunix: 9f0b0000 00000006 0a000000 001803c8
Apr 5 18:40:22 ncc vmunix: 721a0000 00000000 c0000004 0018035c
Apr 5 18:40:22 ncc vmunix:
Apr 5 18:40:22 ncc vmunix: SCSI: Abort Tag -- lbolt: 2859125, dev: 1f025000, io_id: 2036d87
regards sachit
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2007 02:26 AM
04-05-2007 02:26 AM
Re: syslog of k450
Hello sachit.
It appears like a SCSI reset in your system
check out dmesg command to see more information, also do an ioscan -fnC disk
and an ioscan -fnC tape and check if some of your hardware is in NO_HW state.
It appears like a SCSI reset in your system
check out dmesg command to see more information, also do an ioscan -fnC disk
and an ioscan -fnC tape and check if some of your hardware is in NO_HW state.
Knowledge is power.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2007 02:32 AM
04-05-2007 02:32 AM
Re: syslog of k450
This is related to the SCSI timeout value of "/dev/dsk/c2t5d0". Is this a SAN disk? If so you might need to bump up the timeout parameter on that specific disk using pvchange(1M). man pvchange(1M) for 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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP