2.6.0-test9 breaks cdrecord w. ide-scsi device

From: P. Christeas (p_christ_at_hol.gr)
Date: 10/30/03

  • Next message: Jeff Garzik: "Re: [Lse-tech] Re: 2.6.0-test9-mjb1" 
    Date:	Fri, 31 Oct 2003 00:12:47 +0200
To: lkml <linux-kernel@vger.kernel.org>

    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...

    -
    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/

  • Next message: Jeff Garzik: "Re: [Lse-tech] Re: 2.6.0-test9-mjb1"

    Relevant Pages

    • dirty md raid5 slab bio leak
      ... Jun 23 11:23:45 c64 sdd: Current: sense key: Aborted Command ... Jun 23 11:23:45 c64 Additional sense: Scsi parity error ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [7/12] Handle NO_SENSE in sd_rw_intr in sd.c
      ... > This fixes Debian BTS #232494. ... > Current sda: sense key No sense ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: ata errors -> read-only root partition. Hardware issue?
      ... sda: Current: sense key: Medium Error ... Additional sense: Unrecovered read error - auto reallocate failed end_request: I/O error, dev sda, sector 67801511 ... To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: Linux 2.6.9-ac5
      ... Oct 31 14:44:43 safari kernel: File system has been set read-only ... Oct 31 14:44:43 safari kernel: Current sdb: sense key No Sense ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)