From: Robert Hancock <hancockrwd@gmail.com>
To: Richard Jonsson <richard_jonsson@hotmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Unable to write dvd+r on 3 systems
Date: Sat, 14 Feb 2009 20:16:56 -0600 [thread overview]
Message-ID: <49977B18.1030303@gmail.com> (raw)
In-Reply-To: <BAY108-W52F43AD46BC7BE27057F0B9DB90@phx.gbl>
Richard Jonsson wrote:
>
>
> ----------------------------------------
>> Date: Sat, 14 Feb 2009 15:53:15 -0600
>> From: hancockrwd@gmail.com
>> To: richard_jonsson@hotmail.com
>> CC: linux-kernel@vger.kernel.org
>> Subject: Re: Unable to write dvd+r on 3 systems
>>
>> Richard Jonsson wrote:
>>> It seems I am the last person on earth burning dvd's. I have tried on three different systems, using a mix of growisofs, xfburn, brasero and k3b. They all give the same result for their respective system.
>>>
>>> On system 1 it takes forever to complete the process. The system is completely useless while burning. IO wait is 50% and hardIRQ is 10-20%. If audio is playing at the same time it stutters in a way that it sounds as it's playing slow. Mouse cursor jerks and it takes eons to even open a new terminal.
>>>
>>> On system 2 growisofs will try for half a minute and then fail with a message in dmesg. The disc isn't even touched. Tried homebuilt kernel.org kernels from 2.6.25 to current git with no difference. See attachment "growisofs_system2.txt". I have been able to burn exactly 1 disc in total, which magically started recording immediately.
>>>
>>> System 3 burns at decent speed and always reports success, but about half the time only part of the disc is actually burned. It is visible to the eye, and it will not work. Tried at 4x too.
>> It sounds like you may have multiple problems. System 1 sounds like
>> maybe DMA is not being used for some reason, the dmesg output would be
>> useful. On System 2 it looks like a write timed out, and system 3 is
>> having burn quality problems. System 1 may have a kernel issue that
>> should be looked into, but as for the other two, I would tend to suspect
>> the quality of the discs you are using. There is a lot of crap media out
>> there, and also some burners don't like discs with media codes that they
>> don't have preprogrammed burn strategies for.
>
> Thanks for your reply.
>
> System 1 is affected by
> http://bugzilla.kernel.org/show_bug.cgi?id=12309
Not sure if that is related, that's referring to heavy disk write IO
where yours is CD burning, which is a rather different workload.
> Also, just noticed that it doesn't appear to have udma capability?!
> (see attachment).
Not too unusual for a lot of burners..
>
> Regarding system 3, should there not be an error raised or some such?
> It appears to complete the process, but halfway through the laser is
> cut?
That's up to the drive. If it chooses not to provide an error to the
burning software when something goes wrong, there's not much that can be
done about it. (It's possible the burning software is failing to report
the error, but that isn't usually the case as far as I've seen.)
>
> As for the media, I currently use branded discs (tdk), any
> recommendations what to shop for?
Verbatim (MCC or MKM media code) are the ones I usually use. Anything
made by Taiyo Yuden is fairly well regarded as well. It depends a lot on
what is available in your area..
next prev parent reply other threads:[~2009-02-15 2:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 18:54 Unable to write dvd+r on 3 systems Richard Jonsson
2009-02-14 21:53 ` Robert Hancock
2009-02-14 22:30 ` Richard Jonsson
2009-02-15 2:16 ` Robert Hancock [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-14 19:14 Richard Jonsson
2009-02-20 17:02 ` Lennart Sorensen
2009-02-22 10:22 ` Richard Jonsson
2009-02-23 14:50 ` Lennart Sorensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49977B18.1030303@gmail.com \
--to=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard_jonsson@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox