From owner-freebsd-current@FreeBSD.ORG Mon Jan 12 16:02:49 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 341C4106566B for ; Mon, 12 Jan 2009 16:02:49 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (merlin.alerce.com [64.62.142.94]) by mx1.freebsd.org (Postfix) with ESMTP id 1BAE18FC0A for ; Mon, 12 Jan 2009 16:02:48 +0000 (UTC) (envelope-from hartzell@alerce.com) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id 9C46A33C62; Mon, 12 Jan 2009 08:02:48 -0800 (PST) Received: from merlin.alerce.com (localhost [127.0.0.1]) by merlin.alerce.com (Postfix) with ESMTP id 050F933C5B; Mon, 12 Jan 2009 08:02:47 -0800 (PST) From: George Hartzell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18795.27048.855213.465843@almost.alerce.com> Date: Mon, 12 Jan 2009 08:02:48 -0800 To: Jaakko Heinonen In-Reply-To: <20090110084012.GA1979@a91-153-125-115.elisa-laajakaista.fi> References: <1de79840901080935s130f647r36815df468a9220b@mail.gmail.com> <18791.65426.128568.526167@almost.alerce.com> <20090110084012.GA1979@a91-153-125-115.elisa-laajakaista.fi> X-Mailer: VM 7.19 under Emacs 22.1.50.1 X-Virus-Scanned: ClamAV using ClamSMTP X-Mailman-Approved-At: Mon, 12 Jan 2009 17:13:55 +0000 Cc: Michael Proto , Alexander Best , freebsd-current@freebsd.org Subject: Re: patch to fix burncd bug X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hartzell@alerce.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jan 2009 16:02:49 -0000 Jaakko Heinonen writes: > > Hi, > > On 2009-01-09, George Hartzell wrote: > > I have a mac pro running 7.1-PRERELEASE system (not sure when I last > > updated it) on which burncd seems to successfully burn the data but > > then fails while fixating. > > > > I applied the above patch by hand, with a little bit of fuzz, and now > > it fails to burn the data but fixating no longer bombs out. > > It can't see how it could be possible that the patch (correctly applied) > causes this. Are you sure that this is repeatable behavior and burning > always works with an unpatched kernel? Does dmesg show any error > messages after failed burn? I'm willing to believe that I messed it up.... Alex has suggested that I upgrade the system to 7.1, which is on my list of things to do this week (just been waiting for gnome to update). I'll let you know as soon as I try it out. Thanks, g.