From owner-freebsd-bugs Tue Apr 4 15:20: 4 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 CC45537B77C for ; Tue, 4 Apr 2000 15:20:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id PAA53708; Tue, 4 Apr 2000 15:20:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Tue, 4 Apr 2000 15:20:02 -0700 (PDT) Message-Id: <200004042220.PAA53708@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:21:20 +0000 I've spent some time trying to track this down, but failed unfortunately. As far as I can see the problem is somewhere in the inner core of the ppbus. The drive responds fairly normally and returns the 36 bytes CAM requested (INQUIRY command). But then ppbus/vpo bails out with a DATA_OVERFLOW error '...error/timeout (5)'. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message