From owner-freebsd-bugs Tue Apr 4 15:50: 7 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id DD88A37B6D1 for ; Tue, 4 Apr 2000 15:50:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id PAA56062; Tue, 4 Apr 2000 15:50:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Tue, 4 Apr 2000 15:50:04 -0700 (PDT) Message-Id: <200004042250.PAA56062@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Nick Hibma Subject: Re: kern/16153: no more parallel port zip drive Reply-To: Nick Hibma Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/16153; it has been noted by GNATS. From: Nick Hibma To: freebsd-gnats-submit@FreeBSD.org, jfh@jfh00.fernuni-hagen.de Cc: Subject: Re: kern/16153: no more parallel port zip drive Date: Tue, 04 Apr 2000 22:46:50 +0000 FYI, a piece of log file to show that the bug must be lower down and most probably is not the drives fault: vpo0: XPT_SCSI_IO (0x12) request count = 0, r = 0xa8 count = 1, r = 0xa8 count = 2, r = 0xa8 .... count = 35, r = 0xa8 count = 36, r = 0xa8 vpo_do_scsi = 0, status = 0x0, count = 36, vpo_error = 5 12 0 0 0 24 0 vpo0: VP0 error/timeout (5) vpo0: XPT_SCSI_IO (0x12) request vpo_do_scsi = 0, status = 0x0, count = 36, vpo_error = 2 12 0 0 0 24 0 vpo0: VP0 error/timeout (2) vpo0: XPT_SCSI_IO (0x12) request vpo_do_scsi = 0, status = 0x0, count = 36, vpo_error = 2 12 0 0 0 24 0 count = 36, r = 0xa8 vpo_do_scsi = 0, status = 0x0, count = 36, vpo_error = 5 12 0 0 0 24 0 vpo0: VP0 error/timeout (5) vpo0: XPT_SCSI_IO (0x12) request vpo_do_scsi = 0, status = 0x0, count = 36, vpo_error = 2 12 0 0 0 24 0 vpo0: VP0 error/timeout (2) The last error is most probably caused by the fact that the drive is confused. When count = 36, r should have been 0xb8. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message