From owner-freebsd-current@FreeBSD.ORG  Fri Jun 11 15:57:23 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 5C8D016A4CE
	for <freebsd-current@freebsd.org>;
	Fri, 11 Jun 2004 15:57:23 +0000 (GMT)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4131143D1D
	for <freebsd-current@freebsd.org>;
	Fri, 11 Jun 2004 15:57:23 +0000 (GMT)	(envelope-from mux@freebsd.org)
Received: by elvis.mu.org (Postfix, from userid 1920)
	id 41D4A5C854; Fri, 11 Jun 2004 08:57:10 -0700 (PDT)
Date: Fri, 11 Jun 2004 17:57:10 +0200
From: Maxime Henrion <mux@freebsd.org>
To: Roman Kurakin <rik@cronyx.ru>
Message-ID: <20040611155710.GX9228@elvis.mu.org>
References: <200406101254260359.250C5C0A@coolarrow.com>
	<40C9D0DB.5030305@cronyx.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <40C9D0DB.5030305@cronyx.ru>
User-Agent: Mutt/1.4.2.1i
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jun 2004 15:57:23 -0000

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.

Cheers,
Maxime