On Tue, 25 Jan 2005 00:02:54 +0100, Alessandro Suardi
<[EMAIL PROTECTED]> wrote:
> On Mon, 24 Jan 2005 21:44:06 +0000, Alan Cox <[EMAIL PROTECTED]> 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...
> 
> [EMAIL PROTECTED] tmpburn]# strace -p 2337
> ...
> ioctl(5, SG_IO, 0xbffff7d8)             = 0
> ioctl(5, SG_IO, 0xbffff7d8)             = 0
> ioctl(5, SG_IO <unfinished ...>
> Process 2337 detached
> [EMAIL PROTECTED] 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:
> 
> [EMAIL PROTECTED] 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 :(

Now of course, after Ctrl-C'ing the growisofs session, a new
 attempt yielded this

[EMAIL PROTECTED] 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'
/dev/hdc: "Current Write Speed" is 2.0x1385KBps.
   1409024/4608387072 ( 0.0%) @0.0x, remaining 326:57
   1409024/4608387072 ( 0.0%) @0.0x, remaining 544:56
   1409024/4608387072 ( 0.0%) @0.0x, remaining 708:25
   1409024/4608387072 ( 0.0%) @0.0x, remaining 871:53
   1409024/4608387072 ( 0.0%) @0.0x, remaining 1089:52
:-[ [EMAIL PROTECTED] failed with SK=3h/ASC=0Ch/ACQ=00h]: Input/output error
builtin_dd: 688*2KB out @ average 0.0x1385KBps
:-( write failed: Input/output error
/dev/hdc: flushing cache
/dev/hdc: stopping de-icing
/dev/hdc: writing lead-out
[EMAIL PROTECTED] tmpburn]# 

Then, ejecting the disc and trying again, it went through.

[EMAIL PROTECTED] tmpburn]# growisofs -Z /dev/hdc=myfile.iso
Executing 'builtin_dd if=myfile.iso of=/dev/hdc obs=32k seek=0'
/dev/hdc: "Current Write Speed" is 2.0x1385KBps.
  13107200/4608387072 ( 0.3%) @2.4x, remaining 40:54
  24412160/4608387072 ( 0.5%) @2.4x, remaining 31:17
  35717120/4608387072 ( 0.8%) @2.4x, remaining 29:52
  47022080/4608387072 ( 1.0%) @2.4x, remaining 27:29
...
4592205824/4608387072 (99.6%) @2.4x, remaining 0:04
4603510784/4608387072 (99.9%) @2.4x, remaining 0:01
builtin_dd: 2250192*2KB out @ average 2.4x1385KBps
/dev/hdc: flushing cache
/dev/hdc: stopping de-icing
/dev/hdc: writing lead-out


Only thing I note is that after reloading, the WARNING about
 disc already carrying isofs disappeared.


I guess my next move will be borrowing a Windows CD and
 installing it on my former RedHat 9 partition, then trying
 to burn DVDs from there...

--alessandro
 
 "And every dream, every, is just a dream after all"
  
    (Heather Nova, "Paper Cup")
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to