public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "P. Christeas" <p_christ@hol.gr> (by way of P. Christeas <p_christ@hol.gr>)
To: lkml <linux-kernel@vger.kernel.org>
Subject: 2.6.0-test9 breaks cdrecord w. ide-scsi device
Date: Fri, 31 Oct 2003 00:12:47 +0200	[thread overview]
Message-ID: <200310310012.47580.p_christ@hol.gr> (raw)

Just rebooted my long-running machine and now strongly suspect that it is a 
kernel bug:
I try to burn (dummy mode) 20 tracks of audio on a 'PIONEER DVD-RW  DVR-106D' 
drive.
At -test8 it would work (tested 4 times now, several with even older kernels).
On -test 9 I always (> 15 times tested) get the messages quoted.
The drive is on ide-scsi [M],  sg is built-in, sr is a module. Ask me anything 
else you may want me to try..


cdrecord 2.01.xx :
Track 01:   31 of   38 MB written (fifo 100%) [buf  90%]  19.8x.cdrecord:
 Input/output error. write_g1: scsi sendcmd: no error CDB:  2A 00 00 00 36 F3
 00 00 1B 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 04 00 D3 10 FA 0E 26 01 30 FE 08 01 00 00
Sense Key: 0x4 Hardware Error, Segment 0
Sense Code: 0x08 Qual 0x01 (logical unit communication time-out) Fru 0x0
Sense flags: Blk 13832442 (not valid)
cmd finished after 2.004s timeout 200s

write track data: error after 33085584 bytes
cdrecord: A write error occured.
cdrecord: Please properly read the error message above.
Writing  time:   28.974s
Average write speed 154.5x.
Min drive buffer fill was 79%
Fixating...


cdrecord 1.10:
Track 04:   1 of  33 MB written (fifo  98%).cdrecord.old: Input/output error.
 write_g1: scsi sendcmd: no error CDB:  2A 00 00 00 BE 9D 00 00 1B 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 04 00 D3 10 FA 0E 26 01 30 FE 08 01 00 00
Sense Key: 0x4 Hardware Error, Segment 0
Sense Code: 0x08 Qual 0x01 (logical unit communication time-out) Fru 0x0
Sense flags: Blk 13832442 (not valid)
cmd finished after 2.004s timeout 200s

write track data: error after 1460592 bytes
Sense Bytes: 70 00 00 00 00 00 00 0E 00 00 00 00 00 00 00 00 00 00
Writing  time:   57.892s
Fixating...


             reply	other threads:[~2003-10-30 21:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-30 22:12 P. Christeas [this message]
     [not found] ` <20031030171432.03dcaa76.mikeserv@bmts.com>
2003-10-31 15:35   ` 2.6.0-test9 breaks cdrecord w. ide-scsi device P. Christeas
2003-11-01 10:19   ` P. Christeas
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=200310310012.47580.p_christ@hol.gr \
    --to=p_christ@hol.gr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox