From: Valdis.Kletnieks@vt.edu
To: Joerg.Schilling@fokus.fraunhofer.de (Joerg Schilling)
Cc: linux-kernel@vger.kernel.org, shawn.starr@rogers.com
Subject: Re: [PROBLEM][2.6.31.1] - Cannot burn DVDs - PIONEER DVD-RW DVR-111D
Date: Mon, 05 Oct 2009 17:55:00 -0400 [thread overview]
Message-ID: <172428.1254779700@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 05 Oct 2009 13:11:51 +0200." <4ac9d477.7gleZfWVJq3++UDn%Joerg.Schilling@fokus.fraunhofer.de>
[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]
On Mon, 05 Oct 2009 13:11:51 +0200, Joerg Schilling said:
> >Model is:
> >Unable to burn DVDs with 2.6.31.x
>
> >ata7.00: ATAPI: PIONEER DVD-RW DVR-111D, 1.29, max UDMA/66
> >scsi 6:0:0:0: CD-ROM PIONEER DVD-RW DVR-111D 1.29 PQ: 0 ANSI: 5
>
> >sr 6:0:0:0: [sr0] Unhandled sense code
> Please note that this is not cdrecord but a defective fork where someone
Please note that it doesn't matter if it's Joerg's Officially Blessed Cdrecord
or not - the question is if userspace should be able to cause that error
to happen *at all*.
Also, it's quite possible that we're looking at a *kernel* regression, that
the userspace software managed to actually *work* with previous kernels, even
if it wasn't blessed by you:
>> I thought maybe this was due to something with kernel config but I'm not sure
>> now. This used to work fine.
If it breaks when somebody upgrades their kernel, it's probably the kernel's
fault, not the user's fault for using a distro that ships The Other Fork.
> It is very likely that this problem does not occur with the original
> cdrecord from:
> ftp://ftp.berlios.de/pub/cdrecord/alpha/
Yes, but his distro probably feels it can't ship the original cdrecord
so it ships wodim instead. And if it's indeed a kernel bug, replacing
a forked userspace program to work around a kernel bug is The Wrong Answer.
It forked 3 whole years ago, Joerg. Let it go already. And if you can't
let it go, at least ask the user *helpful* questions, like Jeff Garzik did:
> Can you post full dmesg output? And you have verified that vanilla
> 2.6.30 kernel works OK?
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2009-10-05 21:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 11:11 Joerg Schilling
2009-10-05 21:55 ` Valdis.Kletnieks [this message]
2009-10-05 22:15 ` Joerg Schilling
2009-10-06 3:43 ` Valdis.Kletnieks
2009-10-06 7:35 ` Shawn Starr
2009-10-06 13:55 ` Joerg Schilling
2009-10-06 11:20 ` Joerg Schilling
-- strict thread matches above, loose matches on Subject: below --
2009-10-02 2:15 Shawn Starr
2009-10-02 14:46 ` Jeff Garzik
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=172428.1254779700@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=Joerg.Schilling@fokus.fraunhofer.de \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.starr@rogers.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
all inboxes | Powered by JetHome®