cancel
Showing results for 
Search instead for 
Did you mean: 

Bus Reset

Mauro Livi
Valued Contributor

Bus Reset

Hi,
I'm pretty new to some of these things and I've noticed lately that one of our servers has reset a bus a couple of times. Nothing seems to be wrong with the hardware and after a lenghty conversation with HP support they verified that fact. The support rep also mentioned that this is somewhat "normal" and is a software error as opposed to anything being wrong with the hardware.
I did insist that my case be followed up by the software folks because I'd like to know "why" this happens even if it is "normal", and thought that some of you may have come across something like this. I basically see the information depicted below in my syslog which ultimately results in the reset bus.
Any help would be greatly appreciated.
Thanks
Mauro


Dec 8 02:36:03 svr033 vmunix: SCSI Gross Error on 1/0/14/0/0:
Dec 8 02:36:03 svr033 vmunix: shadowed SIST0 10 shadowed SIST1 04.
Dec 8 02:36:03 svr033 vmunix: SCSI: isrEscape Controller at 1/0/14/0/0.
Dec 8 02:36:03 svr033 vmunix:
Dec 8 02:36:03 svr033 vmunix: SCSI: -- lbolt: 1966461918, dev: 1f078000
Dec 8 02:36:03 svr033 vmunix: lbp->state: 30008
Dec 8 02:36:03 svr033 vmunix: lbp->offset: ffffffff
Dec 8 02:36:03 svr033 vmunix: lbp->nominalOffset: 4f8
Dec 8 02:36:03 svr033 vmunix: lbp->Cmdindex: 6
Dec 8 02:36:03 svr033 vmunix: lbp->last_nexus_index: 63
Dec 8 02:36:03 svr033 vmunix: lbp->nexus_index: 64
Dec 8 02:36:03 svr033 vmunix: uCmdSent: 6005980 uNexus_offset: 5790
Dec 8 02:36:03 svr033 vmunix: last lbp->puStatus [0000000070bd5770]:
Dec 8 02:36:03 svr033 vmunix: 0003004a 0003004a 0003004a 0003004a
Dec 8 02:36:03 svr033 vmunix: next lbp->puStatus [0000000070bd5780]:
Dec 8 02:36:03 svr033 vmunix: 0003004c 00030042 0003007c 00030070
Dec 8 02:36:03 svr033 vmunix: From most recent interrupt:
Dec 8 02:36:03 svr033 vmunix: ISTAT: 02, SIST0: 0c, SIST1: 00, DSTAT:0
Dec 8 02:36:03 svr033 vmunix: lsp: 0x00000000909f8400
Dec 8 02:36:03 svr033 vmunix: bp->b_dev: 1f078000
Dec 8 02:36:03 svr033 vmunix: scb->io_id: 74ff964
Dec 8 02:36:03 svr033 vmunix: scb->cdb: 28 00 00 bb 5b 30 00 00 50 00
Dec 8 02:36:03 svr033 vmunix: lbolt_at_timeout: 0, lbolt_at_start: 0
Dec 8 02:36:03 svr033 vmunix: lsp->state: 4005
Dec 8 02:36:03 svr033 vmunix: Jump Table entry [fffffff470020e48]: ff01004a 00
Dec 8 02:36:03 svr033 vmunix: lsp->puScript [0000000070bd1140]:
Dec 8 02:36:03 svr033 vmunix: 09001000 089a2000 004cc002 09001000
Dec 8 02:36:03 svr033 vmunix: 7e1f8000 004c8000 09001000 3d1b8000
Dec 8 02:36:03 svr033 vmunix: DSAtbl->host_iocb_index: 6
Dec 8 02:36:03 svr033 vmunix: DSAtbl->host_iocb_addr: 5980
Dec 8 02:36:03 svr033 vmunix: stored scratcha: 0xff03004a
Dec 8 02:36:03 svr033 vmunix: scratch_lsp: 0x00000000909f8400
Dec 8 02:36:03 svr033 vmunix: c8xx_iocb [fffffff470020b00]:
Dec 8 02:36:03 svr033 vmunix: 06005980 ff000066 00001000 9f081f80
Dec 8 02:36:03 svr033 vmunix: 00000003 00005960 0000000a 00005968
Dec 8 02:36:03 svr033 vmunix: Pre-DSP script dump [0000000070bd1130]:
Dec 8 02:36:03 svr033 vmunix: 09001000 78ca5000 0071c000 09001000
Dec 8 02:36:03 svr033 vmunix: 09001000 089a2000 004cc002 09001000
Dec 8 02:36:03 svr033 vmunix: Script dump [0000000070bd1150]:
Dec 8 02:36:03 svr033 vmunix: 7e1f8000 004c8000 09001000 3d1b8000
Dec 8 02:36:03 svr033 vmunix: 004c4002 09001000 0f4ca000 004c0000
Dec 8 02:36:03 svr033 vmunix: NCR chip register dump for: 0x400200a
00 SCNTL0: da
Dec 8 02:36:03 svr033 vmunix: 04: GPREG: 0b SDID: 08 SXFER: 7
Dec 8 02:36:03 svr033 vmunix: 08: SBCL: 00 SSID: 88 SOCL: 1
Dec 8 02:36:03 svr033 vmunix: 0c: SSTAT2: 0a SSTAT1: 00 SSTAT0: 0
Dec 8 02:36:03 svr033 vmunix: 10: DSA: f0020b00
Dec 8 02:36:03 svr033 vmunix: 14: MBOX1: 00 MBOX0: 00 ISTAT1: 0
Dec 8 02:36:03 svr033 vmunix: 1c: TEMP: 00001140
Dec 8 02:36:03 svr033 vmunix: 24: DCMDDBC: 0d0008d0
Dec 8 02:36:03 svr033 vmunix: 28: DNAD: 7e1f8730
Dec 8 02:36:03 svr033 vmunix: 2c: DSP: 00001158
Dec 8 02:36:03 svr033 vmunix: 30: DSPS: 7e1f8000
Dec 8 02:36:03 svr033 vmunix: 34: SCRATCHA: ff03004a
Dec 8 02:36:03 svr033 vmunix: 38: DCNTL: a1 DWT: 00 DIEN: c
Dec 8 02:36:03 svr033 vmunix: 3c: ADDER: 001f9158
Dec 8 02:36:03 svr033 vmunix: 40: SIST1: 00 SIST0: 00 SIEN1: f
Dec 8 02:36:03 svr033 vmunix: 44: GPCNTL: 2f MACNTL: 00 SWIDE: 0
Dec 8 02:36:03 svr033 vmunix: 48: RESPID1: 00 RESPID0: 80 STIME1: c
Dec 8 02:36:03 svr033 vmunix: 4c: STEST3: 80 STEST2: 00 STEST1: 4
Dec 8 02:36:03 svr033 vmunix: 50: RESV50: 10 RESV51: c0 SIDL1: a
Dec 8 02:36:03 svr033 vmunix: 54: CCNTL1: 01 CCNTL0: 01 SODL1: 0
Dec 8 02:36:03 svr033 vmunix: 58: RESV58: 00 RESV59: 00 SBDL1: 0
Dec 8 02:36:03 svr033 vmunix: 5c: SCRATCHB: 00080003
Dec 8 02:36:03 svr033 vmunix: 60: SCRATCHC: c0ffffff
Dec 8 02:36:03 svr033 vmunix: 64: SCRATCHD: 00001140
Dec 8 02:36:03 svr033 vmunix: 68: SCRATCHE: f0020e4c
Dec 8 02:36:03 svr033 vmunix: 6c: SCRATCHF: 00000f00
Dec 8 02:36:03 svr033 vmunix: 70: SCRATCHG: 9f081f06
Dec 8 02:36:03 svr033 vmunix: 74: SCRATCHH: 00005790
Dec 8 02:36:03 svr033 vmunix: 78: SCRATCHI: 09819f1f
Dec 8 02:36:03 svr033 vmunix: 7c: SCRATCHJ: 06005980
Dec 8 02:36:03 svr033 vmunix: bc: SCNTL4: 80
Dec 8 02:36:03 svr033 vmunix: PCI configuration register dump:
Dec 8 02:36:03 svr033 vmunix: Command: 0157
Dec 8 02:36:03 svr033 vmunix: Latency Timer: ff
Dec 8 02:36:03 svr033 vmunix: Cache Line Size: 10
Dec 8 02:36:04 svr033 vmunix:
Dec 8 02:36:04 svr033 vmunix: SCSI: Resetting SCSI -- lbolt: 1966462018, bus: 0
Dec 8 02:36:04 svr033 vmunix: SCSI: Reset detected -- lbolt: 1966462018, bus: 0
5 REPLIES
Bill Hassell
Honored Contributor

Re: Bus Reset

There is likely an incompatibility between the disk driver you are using and the firmware in the disk(s) you are using. Did HP suggest upgrading both? This looks to be a fairly serious error. Resetting the SCSI bus is not exactly normal.


Bill Hassell, sysadmin
Niceguy_2
Advisor

Re: Bus Reset

Hi Livi,

The Scsi reset might be happened due to the same scsi id Please check that and find out any scsi cable is unplugged in the server this might also cause scsi reset.

Regards,
Niceguy
Mauro Livi
Valued Contributor

Re: Bus Reset

Thanks for the replies. HP did not suggest upgrading anything. Furthermore nothing has changed on this system so it seems strange that this should be happening at this time.

I'm escalating this with HP as I don't exactly buy the this is "normal" answer.

If you have any other suggestions I'd love to hear them. I'll let you know how it goes.

Thanks all
Mauro
Mauro Livi
Valued Contributor

Re: Bus Reset

Hi all,
By the way, this looked to have been a BCC bus controller issue...at least that's what HP determined.
Thanks anyway,

Mauro
Mauro Livi
Valued Contributor

Re: Bus Reset

BCC bus controller problem