From owner-freebsd-ports@FreeBSD.ORG Thu Dec 25 09:33:07 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13B7016A4CE for ; Thu, 25 Dec 2003 09:33:07 -0800 (PST) Received: from out007.verizon.net (out007pub.verizon.net [206.46.170.107]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69A1543D3F for ; Thu, 25 Dec 2003 09:33:04 -0800 (PST) (envelope-from cswiger@mac.com) Received: from mac.com ([68.161.96.170]) by out007.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20031225173303.FJHY9064.out007.verizon.net@mac.com>; Thu, 25 Dec 2003 11:33:03 -0600 Message-ID: <3FEB1F2E.2060201@mac.com> Date: Thu, 25 Dec 2003 12:32:30 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031208 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andy Polyakov References: <3FE8A7BF.CE892878@fy.chalmers.se> <3FE9D410.5080604@pkix.net> <3FEAD61F.241FB1C0@fy.chalmers.se> In-Reply-To: <3FEAD61F.241FB1C0@fy.chalmers.se> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out007.verizon.net from [68.161.96.170] at Thu, 25 Dec 2003 11:33:03 -0600 cc: ports@FreeBSD.org Subject: Re: dvd+rw-tools-5.15.4.8.5 and FreeBSD 5-current X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Dec 2003 17:33:07 -0000 Andy Polyakov wrote: [ ... ] >> Would the symptoms of this problem include returning invalid sense codes >> in the event of a problem? > > Yes. OK, that helps. > Well, the problem I'm referring to is believed to be specific to FreeBSD > 5.2 only, at least downgrading to 5.1 reportedly helps. Meaning that if > user in question can confirm that he experienced the problem under 5.0 or > 5.1, then we might have to have another look, as it must be failing for > *another* reason. But in either case... The user was following 5-CURRENT and the problem report was dated several months after 5.1 was released, so it's likely that his system was running ATA/CAM code with this bug. Again, thanks to you and for looking into the problem. A PR has been submitted to update the port: http://www.freebsd.org/cgi/query-pr.cgi?pr=60548 -- -Chuck