From owner-freebsd-current@FreeBSD.ORG Sun Oct 24 14:00:01 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 6689716A4CE for ; Sun, 24 Oct 2004 14:00:01 +0000 (GMT) Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 988C843D4C for ; Sun, 24 Oct 2004 13:59:59 +0000 (GMT) (envelope-from jhay@icomtek.csir.co.za) Received: from zibbi.icomtek.csir.co.za (localhost [127.0.0.1]) i9ODxuZV084870; Sun, 24 Oct 2004 15:59:56 +0200 (SAST) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: (from jhay@localhost)i9ODxtOt084869; Sun, 24 Oct 2004 15:59:55 +0200 (SAST) (envelope-from jhay) Date: Sun, 24 Oct 2004 15:59:55 +0200 From: John Hay To: Ryan Freeman Message-ID: <20041024135955.GA84189@zibbi.icomtek.csir.co.za> References: <4177BA5D.4080505@portaone.com> <417AAE2F.3080701@portaone.com> <417AB000.50502@freebsd.org> <20041024002250.GA92944@slipgate.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041024002250.GA92944@slipgate.org> User-Agent: Mutt/1.4.1i cc: FreeBSD Mailing List Subject: Re: 5.3-BETA "burncd blank" hangs in 50% of cases 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: Sun, 24 Oct 2004 14:00:01 -0000 > > >> > > >>I've noticed that burncd blank command hangs in 50% of cases (at least > > >>with CD-RWs). Every time symptoms are the same: progress goes to 29% > > >>and then just hangs indefinitely. ^C allows to close burncd. However, > > >>the disk appears to be blanked just fine, since the following burncd > > >>data starts writing from LBA 0 as expected. > > >> > > >>In remaining 50% of cases, the progress indicator goes slowly to > > >>20-something%, then quickly jumps to 90-something% and then burncd > > >>exits correctly. > > >> > > >>As I said the problem is easily reproducible so that I am ready to > > >>provide any necessary debugging information. > > >> > > >>My CD-RW runs in UDMA33 mode, but the problem persists in PIO mode as > > >>well. Other than that, it burns and reads CD-RWs without any problems. > > >> > > >>It would be nice to have this fixed before 5.3 goes out. > > >> > > >>-Maxim > > > > > > Sorry, I assumed that others would have jumped in by now. I see similar > > issues myself, and sometimes even fixating a CD will 'hang'. Since it's > > not fatal, just annoying, I don't consider it a show-stopper. Of course > > it will be nice to fix it at some point. My guess is that either the > > driver and burncd aren't using the correct command to get status from > > the drives, or the drives are just generally marginal and refuse to give > > accurate status. We can investigate it further at a later time, I guess. > > > > Well I'll throw in my two cents here. I haven't yet had an issue with my > burner and burncd. I burned 32 audio cds in one night for a co-worker (a whole > spindle!) Anyway, I blanked a cdrw last night, and it went perfect as i hoped. > Just to make sure I'll blank another cdrw right now. > > --snip-- > ryan@ryan:~% burncd -f /dev/acd0 blank > blanking CD - 99 % done > ryan@ryan:~% > --snip-- > > Well seems to be in order still, I'll be sure to post results if I ever see > anything otherwise. FWIW, I have a 40x12x48 Liteon burner, (burnproof, never > ever had a buffer underrun) and I've never had ANY problem with it making > coasters in the 3 years I've had it. Used it in linux, windowsxp and freebsd. > The only coasters are the ones I force upon myself when I over do it trying > to stuff stuff onto a cdr (720mb on a 700mb cdr anyone?) > > - ryan > > By the way, this is on FreeBSD 5.3-RC1. No DMA settings have been disabled, > and its an asus nforce2 motherboard. I think it depends on the type of cd writer. Maybe they don't report blanking operations in the same way? I have two that never return from a blank command. The one in my Dell at work: acd1: CDRW <_NEC CD-RW NR-7900A/1.08> at ata1-slave UDMA33 and a brand new one at home: acd0: CDRW at ata1-master UDMA33 The NEC one in my Dell computer did use to return from blank operations a long time ago. Long being 1.5+ years ago. At the moment the way I use them is to start the blank command and then watch the disk LED. When it goes inactive, I do a ^C. John -- John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org