From: "P. Christeas" <p_christ@hol.gr>
To: Mike Houston <mikeserv@bmts.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test9 breaks cdrecord w. ide-scsi device
Date: Sat, 1 Nov 2003 12:19:21 +0200 [thread overview]
Message-ID: <200311011219.21890.p_christ@hol.gr> (raw)
In-Reply-To: <20031030171432.03dcaa76.mikeserv@bmts.com>
> Hello
>
> ...
>
> There is now ide-cd writing support, and cdrecord 2 supports it. I build
> that stuff modular, so I just load the ide-cd and isofs modules (modprobe
> takes care of the rest). I achieve the fastest writing speeds I've ever
> had, using this driver. Far better than ide-scsi or even Sleazy CD Creator
> in Windows.
>
>...
Tried it. Now used /dev/hdd there..
This time it worked a few times and some other times it failed.
It now seems that I got a buffer underrun, although I do have 'realtime
priority' for the process.
Note that I'm not using 'burnfree'. That's why I have linux anyway :) .
Can anybody examine why is the buffer of cdrecord less than 100% with
RR-scheduling? That would never happen in 2.4, cdrecord 1.10 ..
Track 10: 25 of 32 MB written (fifo 25%) [buf 94%] 15.8x.cdrecord:
Success. write_g1: scsi sendcmd: no error
CDB: 2A 00 00 02 3C 76 00 00 1B 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: F1 00 05 00 32 35 73 0E 00 00 00 00 21 02 00 00
Sense Key: 0x5 Illegal Request, deferred error, Segment 0
Sense Code: 0x21 Qual 0x02 (invalid address for write) Fru 0x0
Sense flags: Blk 3290483 (valid)
resid: 63504
cmd finished after 0.006s timeout 200s
write track data: error after 27179712 bytes
cdrecord: The current problem looks like a buffer underrun.
cdrecord: Try to use 'driveropts=burnfree'.
cdrecord: Make sure that you are root, enable DMA and check your HW/OS set up.
cdrecord: Success. test unit ready: scsi sendcmd: no error
CDB: 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 0E 00 00 00 00 30 00 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x30 Qual 0x00 (incompatible medium installed) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.005s timeout 200s
Writing time: 139.113s
Average write speed 32.0x.
Min drive buffer fill was 80%
Fixating...
WARNING: Some drives don't like fixation in dummy mode.
cdrecord: Success. flush cache: scsi sendcmd: no error
CDB: 35 00 00 00 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 0E 00 00 00 00 30 00 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x30 Qual 0x00 (incompatible medium installed) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.005s timeout 200s
Trouble flushing the cache
cdrecord: Success. test unit ready: scsi sendcmd: no error
CDB: 00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 0E 00 00 00 00 30 00 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x30 Qual 0x00 (incompatible medium installed) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.006s timeout 200s
Fixating time: 26.117s
hdparm:
IO_support = 3 (32-bit w/sync)
unmaskirq = 1 (on)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 1 (on)
next prev parent reply other threads:[~2003-11-01 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 22:12 2.6.0-test9 breaks cdrecord w. ide-scsi device P. Christeas
[not found] ` <20031030171432.03dcaa76.mikeserv@bmts.com>
2003-10-31 15:35 ` P. Christeas
2003-11-01 10:19 ` P. Christeas [this message]
2003-11-21 17:34 ` bill davidsen
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=200311011219.21890.p_christ@hol.gr \
--to=p_christ@hol.gr \
--cc=linux-kernel@vger.kernel.org \
--cc=mikeserv@bmts.com \
/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.