From owner-freebsd-bugs@FreeBSD.ORG Wed Feb 13 02:40:04 2008 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F337516A41B for ; Wed, 13 Feb 2008 02:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E760513C4E9 for ; Wed, 13 Feb 2008 02:40:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m1D2e3nr006435 for ; Wed, 13 Feb 2008 02:40:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m1D2e3FM006434; Wed, 13 Feb 2008 02:40:03 GMT (envelope-from gnats) Date: Wed, 13 Feb 2008 02:40:03 GMT Message-Id: <200802130240.m1D2e3FM006434@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Yuri Cc: Subject: Re: bin/118207: burncd(8) gives I/O error writing CD on Pioneer DVDR-112D/1.21 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Yuri List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2008 02:40:04 -0000 The following reply was made to PR bin/118207; it has been noted by GNATS. From: Yuri To: bug-followup@FreeBSD.org Cc: Subject: Re: bin/118207: burncd(8) gives I/O error writing CD on Pioneer DVDR-112D/1.21 Date: Tue, 12 Feb 2008 18:35:11 -0800 Hi Remko, With the current 7.0 I can't burn any audio CDs at all, even with the command 'cdrecord -v -dao -force dev=1,0,0 speed=4 driveropts=burnfree *.cdr' from cdrtools-2.01_6 that used to work fine few months ago. cdrecord finishes but produces unreadable CD. cdrecord doesn't work on the older SONY writer and current 70 as well. Seems like something has changed in kernel that prevents cdrecord from succeeding. This makes the only workaround not working, therefore this is a major issue. Should this be added as 7.0 stopper issue? Should I file a separate PR for this? Yuri