From owner-freebsd-scsi Mon Dec 27 16:25:51 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id F2A9914FBD for ; Mon, 27 Dec 1999 16:25:48 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA87287; Mon, 27 Dec 1999 17:24:58 -0700 (MST) (envelope-from ken) Date: Mon, 27 Dec 1999 17:24:58 -0700 From: "Kenneth D. Merry" To: John Savitsky Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SCB 0x34 timed out in dataout phase, Again (sorry) Message-ID: <19991227172458.A87258@panzer.kdm.org> References: <19991221112014.A5291@kspu.kr.ua> <19991225164151.A24504@kspu.kr.ua> <19991226143408.A26528@kspu.kr.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991226143408.A26528@kspu.kr.ua>; from john@kspu.kr.ua on Sun, Dec 26, 1999 at 02:34:08PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Dec 26, 1999 at 14:34:08 +0200, John Savitsky wrote: > > I'm sorry for the previous posting. Yesterday I cold-reboot the > machine and saw that I missed one word from the detected hardware. > :-( It is a Ultra2-SE devices (showed by Adaptec SCSI-Setup). > > Also yesterday I upgraded 3.2-RELEASE to 3.4-STABLE. The nightly > backup finished with no errors. Will see... It could be that your problem was that you were running 3.2. There is a bug in the 7890 that Justin worked around shortly after 3.3 was released. So with 3.4, you've got the fix. Anyway, if you continue to have problems, send mail to the list. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message