Getting message in syslog. Back Nov. -

[Michael Connolly_4]

Nov 27 11:58:00 snowhite vmunix: c8xx BUS: 6 SCSI C1010 Ultra160 Wide LVD assigned CPU: 4 Nov 27 11:58:00 snowhite vmunix: 1/0/1/0/0/1/0 c8xx Nov 27 11:58:00 snowhite vmunix: SCSI: isrEscape Controller at 1/0/1/0/0/1/0.
Nov 27 11:58:00 snowhite vmunix:
Nov 27 11:58:00 snowhite vmunix: SCSI: Parity error -- lbolt: 8468, dev:
cb061002
Nov 27 11:58:00 snowhite vmunix: lbp->state: 30008
Nov 27 11:58:00 snowhite vmunix: lbp->offset: ffffffff
Nov 27 11:58:00 snowhite vmunix: lbp->nominalOffset: 360
Nov 27 11:58:00 snowhite vmunix: lbp->Cmdindex: 2
Nov 27 11:58:00 snowhite vmunix: lbp->last_nexus_index: 0
Nov 27 11:58:00 snowhite vmunix: lbp->nexus_index: 0
Nov 27 11:58:00 snowhite vmunix: uCmdSent: 1000000
uNexus_offset: 0
Nov 27 11:58:00 snowhite vmunix: last lbp->puStatus
[00000000c0e15600]:
Nov 27 11:58:00 snowhite vmunix: 00000000 00000000
00000000 00000000
Nov 27 11:58:00 snowhite vmunix: next lbp->puStatus
[00000000c0e157f0]:
Nov 27 11:58:00 snowhite vmunix: From most recent interrupt:
Nov 27 11:58:00 snowhite vmunix: ISTAT: 0a, SIST0: c1,
SIST1: 00, DSTAT: 80, DSPS: 00000000
Nov 27 11:58:00 snowhite vmunix: lsp: 0x00000000ba808890
Nov 27 11:58:00 snowhite vmunix: 00000000 00000000
00000000 00000000
.

[Vishwas Pai]

dev: cb061002 ; major 0xCB suggests some access to scsi controller device.

#ll /dev/rscsi/* | grep 0x61002

will tell you which device is causing this (most likely /dev/rscsi/c6t1d0s2). You may want to check the integrity of this controller. The thread below may also be of some use.

http://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1203814865958+28353475&threadId=218001

--vishwas.

[Michael Connolly_4]

Quick follow up !! I will let you know the out come tomorrow.... Lets see where this takes me.......