From: Ville Herva <vherva@vianova.fi>
To: linux-kernel@vger.kernel.org
Subject: 2.6.14-rc4: broken DVD-R recording [Re: Upgrade 2.6.12-rc4 -> 2.6.13.1 broke DVD-R writing (fails consistently in OPC phase)]
Date: Sun, 16 Oct 2005 20:07:18 +0300 [thread overview]
Message-ID: <20051016170718.GK24760@vianova.fi> (raw)
In-Reply-To: <20050925142825.GB24742@viasys.com>
On Sun, Sep 25, 2005 at 05:28:25PM +0300, you [Ville Herva] wrote:
> On Sun, Sep 25, 2005 at 04:04:36PM +0300, you [Ville Herva] wrote:
> > On Sun, Sep 25, 2005 at 02:46:39PM +0200, you [Simon Strandman] wrote:
> > > Ville Herva skrev:
> > >
> > > >The .config from 2.6.12-rc4 and 2.6.13.1 is nearly identical, but with
> > > >2.6.13.1 I use HZ=250 (that being the default nowadays) and
> > > >2.6.13.1 has CONFIG_PREEMPT_VOLUNTARY=y instead of 2.6.12-rc4's
> > > >CONFIG_PREEMPT=y and CONFIG_PREEMPT_BKL=y ².
> > > >
> > > >Any ideas?
> > >
> > > Have you tried with HZ=1000?
> >
> > No yet.
> >
> > I did see the HZ=250 problem wrt DVD recording thread earlier, but I got the
> > impression it had to do with not being able to supply data fast enough to
> > the drive.
> >
> > In my case, it fails before it even write a single byte to the disc.
> > (Fortunately it means it doesn't ruin the disc each time I try to write.)
>
> Recompiled the same 2.6.13.1 kernel with HZ=1000. DVD-R writing still fails
> with the exact same error.
Still happens with 2.6.14-rc4.
Peter Österlund's suggestion to kill hald and kded in the pktcdvd thread did
not help either. This is a Fedora rawhide installation, though.
-- v --
v@iki.fi
next prev parent reply other threads:[~2005-10-16 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-25 12:30 Upgrade 2.6.12-rc4 -> 2.6.13.1 broke DVD-R writing (fails consistenly in OPC phase) Ville Herva
2005-09-25 12:46 ` Simon Strandman
2005-09-25 13:04 ` Ville Herva
2005-09-25 14:28 ` Ville Herva
2005-10-16 17:07 ` Ville Herva [this message]
2005-11-20 14:53 ` Ville Herva
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=20051016170718.GK24760@vianova.fi \
--to=vherva@vianova.fi \
--cc=linux-kernel@vger.kernel.org \
/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