From owner-freebsd-current  Mon Jan 24  6:18:36 2000
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP id 38B9014E79
	for <freebsd-current@FreeBSD.org>; Mon, 24 Jan 2000 06:18:33 -0800 (PST)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id PAA15926;
	Mon, 24 Jan 2000 15:18:14 +0100 (CET)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <200001241418.PAA15926@freebsd.dk>
Subject: Re: problem of burncd
In-Reply-To: <200001242250.DAC50547.DOBPZIV@kosy.gr.jp> from Yosuke Koshino at "Jan 24, 2000 10:50:20 pm"
To: youchan@kosy.gr.jp (Yosuke Koshino)
Date: Mon, 24 Jan 2000 15:18:14 +0100 (CET)
Cc: freebsd-current@FreeBSD.org
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Yosuke Koshino wrote:
> "Soren Schmidt <sos@freebsd.dk>" wrote:
> > > The message is "burncd: ioctl(CDRIOCCLOSEDISK) : Device busy".
> > > Then, I add "sleep(10);" in 'fixate' code of burncd.c.
> > 
> > You didn't get any other error messages ??
> I didn't get no other error message.

OK, it could be a sideeffect of something else going wrong.
>
> > Hmm, acd_close_track waits uptil 5 mins for the flush to complete
> > that should be more than enough. Maybe you drive return to ready
> > state before it actually did write out the contents, hmmm

> If it is true, the firmware of my drive has bug. Do you think so?

Could be, I have a drive with 2M of buffer, and I've never seen it
do this, and since the driver waits for the device to get ready
before returning from the close_track function, it shouldn't happen.

-Søren


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message