From owner-freebsd-current@FreeBSD.ORG Fri Jun 11 16:29:17 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6704B16A4CE for ; Fri, 11 Jun 2004 16:29:17 +0000 (GMT) Received: from hanoi.cronyx.ru (hanoi.cronyx.ru [144.206.181.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE58643D31 for ; Fri, 11 Jun 2004 16:29:16 +0000 (GMT) (envelope-from rik@cronyx.ru) Received: (from root@localhost) by hanoi.cronyx.ru id i5BGQ3ZB051904 for freebsd-current@freebsd.org.checked; (8.12.8/vak/2.1) Fri, 11 Jun 2004 20:26:03 +0400 (MSD) (envelope-from rik@cronyx.ru) Received: from cronyx.ru (hi.cronyx.ru [144.206.181.94]) by hanoi.cronyx.ru with ESMTP id i5BGN6D2051778; (8.12.8/vak/2.1) Fri, 11 Jun 2004 20:23:06 +0400 (MSD) (envelope-from rik@cronyx.ru) Message-ID: <40C9DC25.1030700@cronyx.ru> Date: Fri, 11 Jun 2004 20:21:57 +0400 From: Roman Kurakin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031208 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Maxime Henrion References: <200406101254260359.250C5C0A@coolarrow.com> <40C9D0DB.5030305@cronyx.ru> <20040611155710.GX9228@elvis.mu.org> In-Reply-To: <20040611155710.GX9228@elvis.mu.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Bug report 64462 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Jun 2004 16:29:17 -0000 Maxime Henrion wrote: >Roman Kurakin wrote: > > >>Chris wrote: >> >> >>>I submitted a bug report: >>> >>>http://www.freebsd.org/cgi/query-pr.cgi?pr=64462 >>> >>>back in March,and didn't notice any followup on it yet. Is there any way >>>to know if/when the bug will be addressed, or if someone found a fix for >>>it? >>> >>> >>It is not a bug. Since cd driver cant guess that it should re-read disk >>it is rather behaviour. >> >> >I highly doubt this - I'm also seeing this problem, and it wasn't showing >up before ATAng happened. It definitely looks like a bug in the ATA >drivers. > > Probably it were some kind of optimisation. Adding a state caching or smt like that. Any way I assign it to sos@. He author of both ata driver and burncd. So I guess he knows this better, and, I hope, solve it in a best way. rik >Cheers, >Maxime > > > >