From owner-freebsd-stable Wed Dec 26 12:55:31 2001 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by hub.freebsd.org (Postfix) with ESMTP id 95B3837B405; Wed, 26 Dec 2001 12:55:27 -0800 (PST) Received: from eskimo.com (ripper@eskimo.com [204.122.16.13]) by mx1.eskimo.com (8.9.1a/8.8.8) with ESMTP id MAA20181; Wed, 26 Dec 2001 12:55:21 -0800 Received: (from ripper@localhost) by eskimo.com (8.9.1a/8.9.1) id MAA02202; Wed, 26 Dec 2001 12:55:20 -0800 (PST) Date: Wed, 26 Dec 2001 12:55:20 -0800 (PST) Message-Id: <200112262055.MAA02202@eskimo.com> From: Ross Lippert To: stable@FreeBSD.ORG Cc: freebsd-stable-digest@FreeBSD.ORG In-reply-to: (owner-freebsd-stable-digest@FreeBSD.ORG) Subject: Re: that atapi cdrom (really dvdrom) problem Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG OK, I take it back. I don't think it is a signed versus unsigned issue, though I still think it is dangerous the way atapi_read mixes them. I've been trying to follow the two pr's (kern/31530 and kern/31460) to see if the panics they're getting were related to the problem I reported earlier. It doesn't look like I am having the same kind of bytecount corruption problems reported in those pr's -- at least I'm not getting way large bytecounts. What seems to be happening is an atapi_read is partially completing and then an ATA_S_ERROR comes back on the status flag and this somehow leads me to an error message. Is anyone else, delving into this? And are there good places to read up on the specs for atapi-dvd-roms so I can make more sense as to how the drive should behave? -r To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message