From: Droebbel <droebbel.melta@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [Problem] slow write to dvd-ram since 2.6.7-bk8
Date: Mon, 14 Feb 2005 13:34:48 +0100 [thread overview]
Message-ID: <1108384488.9495.24.camel@localhost.localdomain> (raw)
In-Reply-To: <20050214105332.GA7163@dose.home.local>
On Mo, 2005-02-14 at 11:53 +0100, Tino Keitel wrote:
>On Mon, Feb 14, 2005 at 11:25:34 +0100, Droebbel wrote:
>> Which 2.6.7 did you use?
>
>Only 2.6.7 with a -mm patch, since vanilla 2.6.7 screwed up my system
>clock, and the noapic option which was suggested to unscrew the clock
>screwed up the USB driver etc... :-(
Which -mm patch? If that patch contains the error, the bk8 contains it
as well and the bk7 doesn't, that might already make serching a bit
easier. Or maybe 2.6.6, if you want a stable release. Not tested yet.
>What kernels do you suggest me to test?
You might try the last working one, 2.6.7 with bk7. You might as well
have to replace the drivers/cdrom/cdrom.c with on from a later virsion
(>bk15), as the cdrom device is generally marked write-protected with
bk2 to bk14.
But instead of just trying those kernel versions, I think we might try
and find the changes that might have had the unfortunate side effect. I
am admittedly not too good at that, as I do not even know C (shame on
me).
>And what test procedure? Thisis what I do in such cases:
>
>time { dd if=/dev/zero of=<path/to/bighile> bs=1024k count=<bignum> ; sync ; }
This is what I did.
>I'd be very happy to see a fix for this since backups to DVD-RAM are
>awfully slow at the moment.
I've been after this for months now, before finally posting here...
Regards
David
next prev parent reply other threads:[~2005-02-14 12:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-13 13:36 [Problem] slow write to dvd-ram since 2.6.7-bk8 Droebbel
2005-02-13 14:26 ` Wakko Warner
2005-02-14 8:53 ` Tino Keitel
2005-02-14 10:28 ` Droebbel
[not found] ` <1108376734.9495.8.camel@localhost.localdomain>
[not found] ` <20050214105332.GA7163@dose.home.local>
2005-02-14 12:34 ` Droebbel [this message]
[not found] ` <1108379351.9495.22.camel@localhost.localdomain>
[not found] ` <20050214111819.GA7691@dose.home.local>
2005-02-16 21:55 ` Droebbel
2005-02-16 22:29 ` Droebbel
2005-02-17 23:10 ` Tino Keitel
2005-02-18 22:21 ` Droebbel
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=1108384488.9495.24.camel@localhost.localdomain \
--to=droebbel.melta@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.