Date: Sun, 24 Oct 2004 19:03:22 +0400 From: Sergey Zaharchenko <doublef@tele-kom.ru> To: John Hay <jhay@icomtek.csir.co.za> Cc: FreeBSD Mailing List <freebsd-current@freebsd.org> Subject: Re: 5.3-BETA "burncd blank" hangs in 50% of cases Message-ID: <20041024150322.GA1714@shark.localdomain> In-Reply-To: <20041024135955.GA84189@zibbi.icomtek.csir.co.za> References: <4177BA5D.4080505@portaone.com> <417AAE2F.3080701@portaone.com> <417AB000.50502@freebsd.org> <20041024002250.GA92944@slipgate.org> <20041024135955.GA84189@zibbi.icomtek.csir.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
--ikeVEW9yuYc//A+q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 24, 2004 at 03:59:55PM +0200, John Hay probably wrote: > > > >> > > > >>I've noticed that burncd blank command hangs in 50% of cases (at le= ast=20 > > > >>with CD-RWs). Every time symptoms are the same: progress goes to 29= %=20 > > > >>and then just hangs indefinitely. ^C allows to close burncd. Howeve= r,=20 > > > >>the disk appears to be blanked just fine, since the following burnc= d=20 > > > >>data starts writing from LBA 0 as expected. > > > >> > > > >>In remaining 50% of cases, the progress indicator goes slowly to=20 > > > >>20-something%, then quickly jumps to 90-something% and then burncd= =20 > > > >>exits correctly. > > > >> > > > >>As I said the problem is easily reproducible so that I am ready to= =20 > > > >>provide any necessary debugging information. > > > >> > > > >>My CD-RW runs in UDMA33 mode, but the problem persists in PIO mode = as=20 > > > >>well. Other than that, it burns and reads CD-RWs without any proble= ms. > > > >> > > > >>It would be nice to have this fixed before 5.3 goes out. > > > >> > > > >>-Maxim > > >=20 > > >=20 > > > Sorry, I assumed that others would have jumped in by now. I see simi= lar=20 > > > issues myself, and sometimes even fixating a CD will 'hang'. Since i= t's > > > not fatal, just annoying, I don't consider it a show-stopper. Of cou= rse > > > it will be nice to fix it at some point. My guess is that either the= =20 > > > 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 g= ive > > > accurate status. We can investigate it further at a later time, I gu= ess. > > > > >=20 > > 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. > >=20 > > --snip-- > > ryan@ryan:~% burncd -f /dev/acd0 blank > > blanking CD - 99 % done =20 > > ryan@ryan:~% > > --snip-- > >=20 > > 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 maki= ng=20 > > coasters in the 3 years I've had it. Used it in linux, windowsxp and fr= eebsd. > > The only coasters are the ones I force upon myself when I over do it tr= ying > > to stuff stuff onto a cdr (720mb on a 700mb cdr anyone?) > >=20 > > - ryan > >=20 > > By the way, this is on FreeBSD 5.3-RC1. No DMA settings have been disab= led, > > and its an asus nforce2 motherboard. >=20 > 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: >=20 > acd1: CDRW <_NEC CD-RW NR-7900A/1.08> at ata1-slave UDMA33 >=20 > and a brand new one at home: >=20 > acd0: CDRW <HL-DT-ST GCE-8526B/1.03> at ata1-master UDMA33 >=20 > 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. >=20 I see the same problem on a not-so-recent 6-CURRENT; there are two FYI points: a) it also seems to depend on the type of the disk you put in; b) the `erase' command works fine (at least it correctly erased all the disks I offered it without a hiccup). Not that it's a good option, though. HTH, --=20 DoubleF If you think the United States has stood still, who built the largest shopping center in the world? -- Richard Nixon --ikeVEW9yuYc//A+q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBe8Q5wo7hT/9lVdwRArneAJ9R3xaWUYUEQFjUVu8xiui/CeKccQCePsyj rMRCWWzQyiF+evzEbQIC4pw= =js3q -----END PGP SIGNATURE----- --ikeVEW9yuYc//A+q--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041024150322.GA1714>