From owner-freebsd-current@FreeBSD.ORG Thu Feb 5 10:34:51 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 C226116A4CE for ; Thu, 5 Feb 2004 10:34:51 -0800 (PST) Received: from sun13.bham.ac.uk (sun13.bham.ac.uk [147.188.128.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B87343D58 for ; Thu, 5 Feb 2004 10:34:47 -0800 (PST) (envelope-from trigonometric@softhome.net) Received: from [147.188.128.127] (helo=bham.ac.uk) by sun13.bham.ac.uk with esmtp (Exim 4.10) id 1AooKs-00038s-00 for freebsd-current@freebsd.org; Thu, 05 Feb 2004 18:34:46 +0000 Received: from sci-fs1.bham.ac.uk ([147.188.118.71]) by bham.ac.uk with esmtp (Exim 4.24) id 1AooKs-0001eG-K9 for freebsd-current@freebsd.org; Thu, 05 Feb 2004 18:34:46 +0000 Received: from SPECULUSHX1THE not authenticated [147.188.140.56] Novell NetWare; Thu, 05 Feb 2004 18:34:46 +0000 Message-ID: <011b01c3ec16$d85f5d70$0601a8c0@SPECULUSHX1THE> From: "Jimmy Firewire" To: Date: Thu, 5 Feb 2004 18:35:35 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: Burncd going into D state in fixation phase 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: Thu, 05 Feb 2004 18:34:52 -0000 Basically, has anyone had any problems with burncd going into D state during the fixation phase, when burning multi-session CDs? This isn't really related to CURRENT but might still be a problem in CURRENT. Here is the message I originally posted somewhere else: Version: 5.1 with a few CVS builds and custom kernel Hardware worth mentioning: KT7A-RAID, AMD, acd1: CD-RW at ata1-slave PIO4 I'm not sure if this is a bug. I was burning some data: mkisofs -max--iso9660-filenames -U -M /dev/acd1 -C `burcd -f /dev/acd1 msinfo` -o temp.iso "$FILENAME" burncd -f /dev/acd1 -s max -m data temp.iso fixate and burncd hung in the fixating phase. Now I'm sure I saw someone say something about this before, but I couldn't find it. The strange thing is I had burned 9 iso's onto this CD earlier on the same day with no problem. This is the first CD I was burning with FreeBSD. When it got stuck in fixating, there was no way to kill because the state was D. I had to reboot. The only thing I did different from the other times was I was using icewm and I switched to a different desktop using CTRL-ALT-RIGHTARROW to read some code, and then everything froze, it eventually unfroze but then burncd was stuck in fixate. The CD is now unwritable but the previously wrote data has not been lost. Strangely du -h reports that 1.9M has been used, whereas df -h reports that 136M has been used. The former is what I expected. Is this a bug? It is worth mentioning that I think my hardware is failing, this is why I mentioned the KT7A-RAID. For example, the soundcard stopped working in this machine, but it works in another machine, but it used to work in this machine. So maybe the problem is a bug in my hardware? But anyway, this is obviously somewhat troublesome to reproduce as if it happens I will have to reboot. Has anyone else had any similar problems? anonymousPseudonym