From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 4 16:09:57 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3961516A4CF for ; Thu, 4 Nov 2004 16:09:57 +0000 (GMT) Received: from mail.komvista.lt (ns.komvista.lt [213.190.36.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0318F43D5C for ; Thu, 4 Nov 2004 16:09:56 +0000 (GMT) (envelope-from ssmailys@komvista.lt) Received: by mail.komvista.lt (Postfix, from userid 23) id D4184BDCA; Thu, 4 Nov 2004 19:09:39 +0200 (EET) Received: from [192.168.127.253] (omega64.komvista.lt [192.168.127.253]) by mail.komvista.lt (Postfix) with ESMTP id D986CBDC9; Thu, 4 Nov 2004 19:09:37 +0200 (EET) Message-ID: <418A544F.7090903@komvista.lt> Date: Thu, 04 Nov 2004 18:09:51 +0200 From: Stasys Smailys User-Agent: Mozilla Thunderbird 0.8 (X11/20041102) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "[FreeBSD-AMD64]" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ioctl() 64-bit issues X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Nov 2004 16:09:57 -0000 Hi all! > Still not working. System is > > [deepred at omega64]:[~] > uname -a > FreeBSD omega64.komvista.lt 5.3-STABLE FreeBSD 5.3-STABLE #0: Tue Nov 2 > 10:04:01 EET 2004 > root at omega64.komvista.lt:/usr/obj/usr/src/sys/GENERAL amd64 > > ata_queue_request() returns zeros in request->u.atapi.sense_data.sk* > after calling acd_get_progress() in dev/ata/atapi-cd.c. If > request->u.atapi.sense_data.sksv is 0, then *finished is 0. That's why > pct always gets zero, even if it has a value. Other functions don't care > about second value when calling acd_get_progress() so they are not > sensitive. Could it be that acd_get_progress() is deprecated and should > not return anything excluding 0 or ENOMEM? First of all I'm sorry for the false alarm. It appeared that the problem was in CDRW drive. After changing NEC NR-7700A to LiteOn SOHR-5238S everything works just fine. It seems to be a hardware bug because I can't change transfer mode to anything more than WDMA2 (by default it starts at PIO4). I would never thought that it was the hardware issue. Thanks anyway. -- WBR Stasys Smailys