Date: Sun, 26 Jan 1997 20:58:43 +0100 From: andreas@klemm.gtn.com (Andreas Klemm) To: gibbs@narnia.plutotech.com (Justin T. Gibbs) Cc: scsi@freebsd.org Subject: Re: fbsd-current: data overrun of 510 bytes detected. Forcing a retry. Message-ID: <Mutt.19970126205843.andreas@klemm.gtn.com> In-Reply-To: <199701261830.KAA16660@narnia.plutotech.com>; from "Justin T. Gibbs" on Jan 26, 1997 10:30:02 -0800 References: <Mutt.19970126120446.andreas@klemm.gtn.com> <199701261830.KAA16660@narnia.plutotech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Justin ! Justin T. Gibbs writes: > I can reproduce this here and will look into it later today. Ok, thanks. > >When running bonnie on my 3rd SCSI disk I get the following messages > >after a couple of seconds: > > > >sd2 at scbus0 target 2 lun 0: data overrun of 510 bytes detected. =20 Another thing. Backups using dump still fail when using AHC_TAGENABLE. I started with the following kernel options: options AHC_TAGENABLE options AHC_SCBPAGING_ENABLE options AHC_ALLOW_MEMIO This freezes the SCSI bus when dump starts writing to the=20 QIC tape (5 GB Tandberg). After that I only tried=20 options AHC_SCBPAGING_ENABLE options AHC_ALLOW_MEMIO This resulted in these error messages, which didn't freeze the system. Jan 26 13:16:22 klemm /kernel: st0 at scbus0 target 4 lun 0: timed out whil= e idle, LASTPHASE =3D=3D 0x1, SCSISIGI =3D=3D 0x0 Jan 26 13:16:22 klemm /kernel: SEQADDR =3D=3D 0xc =00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00= =00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00= =00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00= =00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00= =00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00=00Jan 26 13:16:22 klemm /k= ernel: SEQADDR =3D=3D 0xc Jan 26 13:16:22 klemm /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs abo= rted Jan 26 13:16:22 klemm /kernel: sd0 at scbus0 target 0 lun 0: UNIT ATTENTION= asc:29,0 Jan 26 13:16:22 klemm /kernel: sd0 at scbus0 target 0 lun 0: Power on, res= et, or bus device reset occurred Jan 26 13:16:23 klemm /kernel: , retries:4 Jan 26 13:16:23 klemm /kernel: st0 at scbus0 target 4 lun 0: UNIT ATTENTION= asc:29,0 Jan 26 13:16:23 klemm /kernel: st0 at scbus0 target 4 lun 0: Power on, res= et, or bus device reset occurred Jan 26 13:16:23 klemm /kernel: st0: oops not queued Jan 26 13:16:23 klemm /kernel: sd0 at scbus0 target 0 lun 0: NOT READY asc:= 4,1 Jan 26 13:16:23 klemm /kernel: sd0 at scbus0 target 0 lun 0: Logical unit = is in process of becoming ready Jan 26 13:16:23 klemm /kernel: , retries:3 Jan 26 13:16:23 klemm /kernel: sd0 at scbus0 target 0 lun 0: NOT READY asc:= 4,1 Jan 26 13:16:23 klemm /kernel: sd0 at scbus0 target 0 lun 0: Logical unit = is in process of becoming ready Jan 26 13:16:23 klemm /kernel: , retries:2 Jan 26 13:16:23 klemm /kernel: sd0 at scbus0 target 0 lun 0: NOT READY asc:= 4,1 Jan 26 13:16:23 klemm /kernel: sd0 at scbus0 target 0 lun 0: Logical unit = is in process of becoming ready Jan 26 13:16:23 klemm /kernel: , retries:1 Jan 26 13:16:23 klemm /kernel: sd0 at scbus0 target 0 lun 0: NOT READY asc:= 4,1 Jan 26 13:16:23 klemm /kernel: sd0 at scbus0 target 0 lun 0: Logical unit = is in process of becoming ready Jan 26 13:16:23 klemm /kernel: , FAILURE Jan 26 13:16:23 klemm /kernel: sd0 at scbus0 target 0 lun 0: NOT READY asc:= 4,1 Jan 26 13:16:23 klemm /kernel: sd0 at scbus0 target 0 lun 0: Logical unit = is in process of becoming ready Jan 26 13:16:23 klemm /kernel: , retries:4 Jan 26 13:16:23 klemm /kernel: sd0 at scbus0 target 0 lun 0: NOT READY asc:= 4,1 Jan 26 13:16:23 klemm /kernel: sd0 at scbus0 target 0 lun 0: Logical unit = is in process of becoming ready Jan 26 13:16:24 klemm /kernel: , retries:3 Jan 26 13:16:24 klemm /kernel: sd0 at scbus0 target 0 lun 0: NOT READY asc:= 4,1 Jan 26 13:16:24 klemm /kernel: sd0 at scbus0 target 0 lun 0: Logical unit = is in process of becoming ready Jan 26 13:16:24 klemm /kernel: , retries:2 Jan 26 13:16:24 klemm /kernel: sd0 at scbus0 target 0 lun 0: NOT READY asc:= 4,1 Jan 26 13:16:24 klemm /kernel: sd0 at scbus0 target 0 lun 0: Logical unit = is in process of becoming ready Jan 26 13:16:24 klemm /kernel: , retries:1 Jan 26 13:16:24 klemm /kernel: sd0 at scbus0 target 0 lun 0: NOT READY asc:= 4,1 Jan 26 13:16:24 klemm /kernel: sd0 at scbus0 target 0 lun 0: Logical unit = is in process of becoming ready Jan 26 13:16:24 klemm /kernel: , FAILURE Jan 26 13:16:24 klemm /kernel: sd0 at scbus0 target 0 lun 0: NOT READY asc:= 4,1 Jan 26 13:16:24 klemm /kernel: sd0 at scbus0 target 0 lun 0: Logical unit = is in process of becoming ready Jan 26 13:16:24 klemm /kernel: , retries:4 Jan 26 13:16:24 klemm /kernel: sd0 at scbus0 target 0 lun 0: NOT READY asc:= 4,1 Jan 26 13:16:24 klemm /kernel: sd0 at scbus0 target 0 lun 0: Logical unit = is in process of becoming ready Jan 26 13:16:24 klemm /kernel: , retries:3 Jan 26 13:16:24 klemm /kernel: sd0 at scbus0 target 0 lun 0: NOT READY asc:= 4,1 Jan 26 13:16:24 klemm /kernel: sd0 at scbus0 target 0 lun 0: Logical unit = is in process of becoming ready Jan 26 13:16:24 klemm /kernel: , retries:2 Jan 26 13:16:24 klemm /kernel: sd0 at scbus0 target 0 lun 0: NOT READY asc:= 4,1 Jan 26 13:16:25 klemm /kernel: sd0 at scbus0 target 0 lun 0: Logical unit = is in process of becoming ready Jan 26 13:16:25 klemm /kernel: , retries:1 Jan 26 13:16:25 klemm /kernel: sd0 at scbus0 target 0 lun 0: NOT READY asc:= 4,1 Jan 26 13:16:25 klemm /kernel: sd0 at scbus0 target 0 lun 0: Logical unit = is in process of becoming ready Jan 26 13:16:25 klemm /kernel: , FAILURE Jan 26 13:16:25 klemm /kernel: sd0 at scbus0 target 0 lun 0: NOT READY asc:= 4,1 Jan 26 13:16:25 klemm /kernel: sd0 at scbus0 target 0 lun 0: Logical unit = is in process of becoming ready Jan 26 13:16:25 klemm /kernel: , retries:4 Jan 26 13:16:25 klemm /kernel: sd0 at scbus0 target 0 lun 0: NOT READY asc:= 4,1 Jan 26 13:16:25 klemm /kernel: sd0 at scbus0 target 0 lun 0: Logical unit = is in process of becoming ready Jan 26 13:16:25 klemm /kernel: , retries:3 Jan 26 13:17:39 klemm /kernel: sd2 at scbus0 target 2 lun 0: UNIT ATTENTION= asc:29,0 Jan 26 13:17:39 klemm /kernel: sd2 at scbus0 target 2 lun 0: Power on, res= et, or bus device reset occurred Jan 26 13:17:39 klemm /kernel: , retries:4 Jan 26 13:18:02 klemm /kernel: st0 at scbus0 target 4 lun 0: timed out whil= e idle, LASTPHASE =3D=3D 0x1, SCSISIGI =3D=3D 0x0 Jan 26 13:18:02 klemm /kernel: SEQADDR =3D=3D 0x10 Jan 26 13:18:04 klemm /kernel: st0 at scbus0 target 4 lun 0: timed out whil= e idle, LASTPHASE =3D=3D 0x1, SCSISIGI =3D=3D 0x0 Jan 26 13:18:04 klemm /kernel: SEQADDR =3D=3D 0xd Jan 26 13:18:04 klemm /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs abo= rted Jan 26 13:18:05 klemm /kernel: sd0 at scbus0 target 0 lun 0: UNIT ATTENTION= asc:29,0 Jan 26 13:18:05 klemm /kernel: sd0 at scbus0 target 0 lun 0: Power on, res= et, or bus device reset occurred Jan 26 13:18:05 klemm /kernel: , retries:4 Jan 26 13:18:05 klemm /kernel: sd2 at scbus0 target 2 lun 0: UNIT ATTENTION= asc:29,0 Jan 26 13:18:05 klemm /kernel: sd2 at scbus0 target 2 lun 0: Power on, res= et, or bus device reset occurred Jan 26 13:18:05 klemm /kernel: , retries:4 Jan 26 13:20:01 klemm /kernel: sd1 at scbus0 target 1 lun 0: UNIT ATTENTION= asc:29,0 Jan 26 13:20:01 klemm /kernel: sd1 at scbus0 target 1 lun 0: Power on, res= et, or bus device reset occurred Jan 26 13:20:01 klemm /kernel: , retries:4 Jan 26 13:30:10 klemm reboot: rebooted by root using only this option doesn't make trouble. options AHC_ALLOW_MEMIO Andreas ///
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Mutt.19970126205843.andreas>