From owner-freebsd-current Mon Jan 24 5:49: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from tama.kosy.gr.jp (tama.kosy.gr.jp [210.141.104.50]) by hub.freebsd.org (Postfix) with ESMTP id F09E41528D for ; Mon, 24 Jan 2000 05:48:56 -0800 (PST) (envelope-from youchan@kosy.gr.jp) Received: from KEI (d0.kosy.gr.jp [192.168.1.30]) by tama.kosy.gr.jp (8.9.3/3.7W) with ESMTP id WAA14736; Mon, 24 Jan 2000 22:48:33 +0900 To: sos@freebsd.dk Cc: freebsd-current@FreeBSD.ORG Subject: Re: problem of burncd From: Yosuke Koshino References: <200001242225.FIC98286.DBZPOIV@kosy.gr.jp> <200001241336.OAA06146@freebsd.dk> In-Reply-To: <200001241336.OAA06146@freebsd.dk> Message-Id: <200001242250.DAC50547.DOBPZIV@kosy.gr.jp> X-Mailer: Winbiff [Version 2.30PL4] Date: Mon, 24 Jan 2000 22:50:20 +0900 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Soren Schmidt " 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. > 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? Yosuke Koshino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message