From owner-freebsd-current@FreeBSD.ORG Wed Nov 5 13:10:16 2003 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 4FDD416A4CE for ; Wed, 5 Nov 2003 13:10:16 -0800 (PST) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D9BB43F85 for ; Wed, 5 Nov 2003 13:10:15 -0800 (PST) (envelope-from sos@spider.deepcore.dk) Received: from spider.deepcore.dk (localhost [127.0.0.1]) by spider.deepcore.dk (8.12.10/8.12.10) with ESMTP id hA5LApBb001627; Wed, 5 Nov 2003 22:10:51 +0100 (CET) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.10/8.12.10/Submit) id hA5LApGS001626; Wed, 5 Nov 2003 22:10:51 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200311052110.hA5LApGS001626@spider.deepcore.dk> In-Reply-To: <3FA963B6.8040805@isi.edu> To: Lars Eggert Date: Wed, 5 Nov 2003 22:10:51 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 X-mail-scanned: by DeepCore Virus & Spam killer v1.3 cc: freebsd-current@FreeBSD.ORG Subject: Re: ATAng regression: cdcontrol close not working 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: Wed, 05 Nov 2003 21:10:16 -0000 It seems Lars Eggert wrote: > Bruce Evans wrote: > > On Thu, 30 Oct 2003, Soren Schmidt wrote: > >> > >>Anyhow if you loose the test for error in atapi-cd.c::acd_tray in the > >>close case, does it work then ? Problem is that the call to read toc > >>might fail early, but its worth a shot.. > > I tried this, but it didn't change anything. (See my mail from last week.) Then I'm out of tricks since the close command fails then... > > I was mistaken in thinking that my patch fixed this. It only works for > > 1 drive, as does at acd^H^Htapi-cd.c rev.1.148. > > Is there any other patch I can try? I've just confirmed that this bug > still exists with today's kernel. I cant reproduce the no matter what I try, sorry... -Søren