Date: Thu, 7 Feb 2002 20:18:03 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= <groudier@free.fr> To: Brian <bellsso@telocity.com> Cc: <freebsd-scsi@FreeBSD.ORG> Subject: Re: SCSI Errors Message-ID: <20020207200643.W1513-100000@gerard> In-Reply-To: <029601c1b050$b05c8450$1e01a8c0@ellefson.local>
next in thread | previous in thread | raw e-mail | index | archive | help
Just quoting messages related to SCSI errors:
> Feb 5 21:35:52 db1 /kernel: sym0:1: ERROR (0:c) (8-0-0) (3e/18) @ (scrip=
ta
^
Bit 4 =3D Unexpected Disconnect
Bit 8 =3D SCSI GROSS ERROR
Thats a double error. Never seen before. :)
> Feb 5 21:35:52 db1 /kernel: sym0: script cmd =3D 11000000
The scripts instruction having been interrupted is a CHMOV in DATA IN
phase.
> Feb 7 12:56:41 db1 /kernel: sym0: unexpected disconnect
> Feb 7 12:56:42 db1 /kernel: sym0: unexpected disconnect
No additional comments for these ones.
On Thu, 7 Feb 2002, Brian wrote:
> Hello,
>
> Recently I have started seeing errors in the SCSI subsystem. I am running
> 4.5 RC from Jan 27th. I am seeing erorrs in the logs like the following:
>
> Feb 5 09:23:09 db1 /kernel: (da1:sym0:0:1:0): Invalidating pack
> Feb 5 09:23:11 db1 /kernel: (da1:sym0:0:1:0): Invalidating pack
> Feb 5 21:35:52 db1 /kernel: sym0: <1010-33> port 0xa400-0xa4ff mem
> 0xe7002000-0xe7003fff,0xe7005000
> -0xe70053ff irq 10 at device 13.0 on pci0
> Feb 5 21:35:52 db1 /kernel: sym0: Symbios NVRAM, ID 7, Fast-80, LVD, par=
ity
> checking
> Feb 5 21:35:52 db1 /kernel: sym0: open drain IRQ line driver, using on-c=
hip
> SRAM
> Feb 5 21:35:52 db1 /kernel: sym0: using LOAD/STORE-based firmware.
> Feb 5 21:35:52 db1 /kernel: sym0: handling phase mismatch from SCRIPTS.
> Feb 5 21:35:52 db1 /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS reset
> delivered.
> Feb 5 21:35:52 db1 /kernel: da0 at sym0 bus 0 target 0 lun 0
> Feb 5 21:35:52 db1 /kernel: da1 at sym0 bus 0 target 1 lun 0
> Feb 5 21:35:52 db1 /kernel: sym0:1: ERROR (0:c) (8-0-0) (3e/18) @ (scrip=
ta
> 5f8:15000246).
> Feb 5 21:35:52 db1 /kernel: sym0: script cmd =3D 11000000
> Feb 5 21:35:52 db1 /kernel: sym0: regdump: da 00 c0 18 47 3e 01 0f 6e 08=
81
> 00 80 00 05 02 00 52 a6
> 2e 00 00 00 00.
> Feb 5 21:35:52 db1 /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS reset
> detected.
> Feb 7 12:56:41 db1 /kernel: sym0: unexpected disconnect
> Feb 7 12:56:42 db1 /kernel: sym0: unexpected disconnect
> Feb 7 12:56:46 db1 /kernel: (da1:sym0:0:1:0): Invalidating pack
> Feb 7 12:56:49 db1 /kernel: (da1:sym0:0:1:0): Invalidating pack
> Feb 7 14:22:30 db1 /kernel: sym0: <1010-33> port 0xa400-0xa4ff mem
> 0xe7002000-0xe7003fff,0xe7005000
> -0xe70053ff irq 10 at device 13.0 on pci0
> Feb 7 14:22:30 db1 /kernel: sym0: Symbios NVRAM, ID 7, Fast-80, LVD, par=
ity
> checking
> Feb 7 14:22:30 db1 /kernel: sym0: open drain IRQ line driver, using on-c=
hip
> SRAM
> Feb 7 14:22:30 db1 /kernel: sym0: using LOAD/STORE-based firmware.
> Feb 7 14:22:30 db1 /kernel: sym0: handling phase mismatch from SCRIPTS.
> Feb 7 14:22:31 db1 /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS reset
> delivered.
> Feb 7 14:22:31 db1 /kernel: da0 at sym0 bus 0 target 0 lun 0
> Feb 7 14:22:31 db1 /kernel: da1 at sym0 bus 0 target 1 lun 0
>
> I am running a Tekram SCSI card, but it has been OK before. Could this be=
a
> card going bad? A drive getting ready to die? Termination?
The SCSI BUS has signalling problems for sure. You may check your SCSI BUS
first and possibly try another cable if you have one and see if it makes
difference. There are many many possible causes that can trigger such
SCSI problems and the ones you suggest are among them.
Regards,
G=E9rard.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020207200643.W1513-100000>