From: Alessandro Suardi <alessandro.suardi@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jens Axboe <axboe@suse.de>,
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: Tue, 25 Jan 2005 00:02:54 +0100 [thread overview]
Message-ID: <5a4c581d0501241502750214ff@mail.gmail.com> (raw)
In-Reply-To: <1106598811.6154.93.camel@localhost.localdomain>
On Mon, 24 Jan 2005 21:44:06 +0000, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Llu, 2005-01-24 at 20:45, Jens Axboe wrote:
> > > I've got several reports like this that only happen with ACPI, and one
> > > user whose burns report fine but are corrupted if ACPI is allowed to do
> > > power manglement.
> >
> > Really weird, I cannot begin to explain that. Perhaps the two reporters
> > in this thread can try it as well?
>
> I can sort of guess - the CPU frequency changes (either from ACPI or
> perhaps also from cpuspeed if in use ?) involve the CPU disconnecting
> from the bus and reconnecting. There is much magic involved in this and
> there are certainly chipset and CPU errata in this area.
Well, booted into 2.6.11-rc2-bk2 (ACPI config'd out) and my
first growisofs session decided to die at 60% with the usual EIO :/
The fun thing is that retrying now shows growisofs calling a
HUGE amount of these babies...
[root@donkey tmpburn]# strace -p 2337
...
ioctl(5, SG_IO, 0xbffff7d8) = 0
ioctl(5, SG_IO, 0xbffff7d8) = 0
ioctl(5, SG_IO <unfinished ...>
Process 2337 detached
[root@donkey tmpburn]# strace -c -p 2337
Process 2337 attached - interrupt to quit
Process 2337 detached
% time seconds usecs/call calls errors syscall
------ ----------- ----------- --------- --------- ----------------
100.00 7.762805 239 32445 ioctl
------ ----------- ----------- --------- --------- ----------------
100.00 7.762805 32445 total
while sitting in its initial prompt:
[root@donkey tmpburn]# growisofs -Z /dev/hdc=myfile.iso
WARNING: /dev/hdc already carries isofs!
About to execute 'builtin_dd if=myfile.iso of=/dev/hdc obs=32k seek=0'
Sleeping for 0 sec...
It looks like every kernel has its own :(
--alessandro
"And every dream, every, is just a dream after all"
(Heather Nova, "Paper Cup")
next prev parent reply other threads:[~2005-01-25 0:04 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
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 [this message]
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=5a4c581d0501241502750214ff@mail.gmail.com \
--to=alessandro.suardi@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox