From owner-freebsd-current@FreeBSD.ORG Sat Jan 10 08:40:19 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 2BAD31065670 for ; Sat, 10 Jan 2009 08:40:19 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from emh01.mail.saunalahti.fi (emh01.mail.saunalahti.fi [62.142.5.107]) by mx1.freebsd.org (Postfix) with ESMTP id D83C18FC12 for ; Sat, 10 Jan 2009 08:40:18 +0000 (UTC) (envelope-from jh@saunalahti.fi) Received: from saunalahti-vams (vs3-10.mail.saunalahti.fi [62.142.5.94]) by emh01-2.mail.saunalahti.fi (Postfix) with SMTP id CAE151AC54; Sat, 10 Jan 2009 10:40:17 +0200 (EET) Received: from emh04.mail.saunalahti.fi ([62.142.5.110]) by vs3-10.mail.saunalahti.fi ([62.142.5.94]) with SMTP (gateway) id A03810C814C; Sat, 10 Jan 2009 10:40:17 +0200 Received: from a91-153-125-115.elisa-laajakaista.fi (a91-153-125-115.elisa-laajakaista.fi [91.153.125.115]) by emh04.mail.saunalahti.fi (Postfix) with SMTP id 41A8C41BEB; Sat, 10 Jan 2009 10:40:13 +0200 (EET) Date: Sat, 10 Jan 2009 10:40:13 +0200 From: Jaakko Heinonen To: George Hartzell Message-ID: <20090110084012.GA1979@a91-153-125-115.elisa-laajakaista.fi> References: <1de79840901080935s130f647r36815df468a9220b@mail.gmail.com> <18791.65426.128568.526167@almost.alerce.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <18791.65426.128568.526167@almost.alerce.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-Antivirus: VAMS 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 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jan 2009 08:40:19 -0000 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? -- Jaakko