All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kasper Sandberg <lkml@metanurb.dk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jens Axboe <axboe@suse.de>,
	Alessandro Suardi <alessandro.suardi@gmail.com>,
	Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: DVD burning still have problems
Date: Fri, 28 Jan 2005 14:42:55 +0100	[thread overview]
Message-ID: <1106919775.13188.2.camel@localhost> (raw)
In-Reply-To: <1106610498.10239.108.camel@localhost.localdomain>

On Mon, 2005-01-24 at 23:48 +0000, Alan Cox wrote:
> On Llu, 2005-01-24 at 23:01, Kasper Sandberg wrote:
> > > there are certainly chipset and CPU errata in this area.
> > would this mean that i should not use cpu frequency scaling?
> 
> Worth an experiment but I'd be suprised if it was your fix. The more
> data the better however 
I disabled cpufreq in the kernel, acpi i still have in kernel.. when i
booted i did acpi=off, and changed IO scheduler to anticipatory
i just burned a DVD, and it works ;D pretty neat, im not sure what
caused it. but im glad.. i still have the small change in scsi_ioctl.h,
however nothing appears in dmesg.. gonna burn one more dvd in a little
bit, if it doesent work, i will let you know, if you dont hear more
about it, assume it works :DD

btw: the reason i changed to anticipatory from cfq is that i noticed
that sometimes the speed dropped abit, and thought it might have
something to do with it, and, with as it did not
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


  reply	other threads:[~2005-01-28 13:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-23 20:26 DVD burning still have problems Volker Armin Hemmann
2005-01-23 20:59 ` Alessandro Suardi
2005-01-24  1:46   ` Tim Fairchild
2005-01-24 17:26     ` Kasper Sandberg
2005-01-24 17:34       ` Jens Axboe
2005-01-24 15:07   ` Jens Axboe
2005-01-24 16:48     ` Alessandro Suardi
2005-01-24 17:21       ` Jens Axboe
2005-01-24 17:24     ` Kasper Sandberg
2005-01-24 17:32       ` Jens Axboe
2005-01-24 19:37     ` Alan Cox
2005-01-24 20:45       ` Jens Axboe
2005-01-24 20:56         ` Alessandro Suardi
2005-01-24 21:44         ` Alan Cox
2005-01-24 23:01           ` Kasper Sandberg
2005-01-24 23:48             ` Alan Cox
2005-01-28 13:42               ` Kasper Sandberg [this message]
2005-01-28 13:47                 ` Jens Axboe
2005-01-28 14:05                   ` Kasper Sandberg
2005-01-28 14:45                     ` Kasper Sandberg
2005-01-24 23:02           ` Alessandro Suardi
2005-01-24 23:44             ` Alessandro Suardi
  -- strict thread matches above, loose matches on Subject: below --
2005-01-23 16:06 Kasper Sandberg
2005-01-23 16:28 ` Alessandro Suardi

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=1106919775.13188.2.camel@localhost \
    --to=lkml@metanurb.dk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=alessandro.suardi@gmail.com \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=volker.armin.hemmann@tu-clausthal.de \
    /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.