public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Francesco Biscani <biscani@pd.astro.it>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: libata PATA patch for 2.6.16-rc5
Date: Wed, 1 Mar 2006 00:06:38 +0100	[thread overview]
Message-ID: <200603010006.38366.biscani@pd.astro.it> (raw)
In-Reply-To: <1141054370.3089.0.camel@localhost.localdomain>

I don't know if this is to be expected, but blanking of a cdrw fails here. 
Output of cdrecord is:

Cdrecord-Clone 2.01 (i686-pc-linux-gnu) Copyright (C) 1995-2004 J�g Schilling
cdrecord: Warning: Running on Linux-2.6.16-rc5-morph1
cdrecord: There are unsettled issues with Linux-2.5 and newer.
cdrecord: If you have unexpected problems, please try Linux-2.4 or Solaris.
scsidev: '/dev/sr0'
devname: '/dev/sr0'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
Device type    : Removable CD-ROM
Version        : 5
Response Format: 2
Capabilities   :
Vendor_info    : 'HL-DT-ST'
Identifikation : 'RW/DVD GCC-4241N'
Revision       : '0C29'
Device seems to be: Generic mmc2 DVD-ROM.
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-3 SWABAUDIO BURNFREE
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
cdrecord: Input/output error. 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 0A 00 00 00 00 3A 00 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.008s timeout 40s
cdrecord: No disk / Wrong disk

Regards,

  Francesco

-- 
Dr. Francesco Biscani
Dipartimento di Astronomia
Università di Padova
biscani@pd.astro.it

  parent reply	other threads:[~2006-02-28 23:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-27 15:32 libata PATA patch for 2.6.16-rc5 Alan Cox
2006-02-27 17:55 ` Mathieu Chouquet-Stringer
2006-02-28  0:19   ` Alan Cox
2006-02-28 12:12     ` Krzysztof Halasa
2006-02-28 13:32       ` Alan Cox
2006-02-28 13:34       ` Alan Cox
2006-02-27 20:46 ` Matthieu CASTET
     [not found]   ` <1141086963.3089.26.camel@localhost.localdomain>
2006-03-05 18:49     ` matthieu castet
     [not found]     ` <4404D05C.8070407@free.fr>
     [not found]       ` <1141231247.23170.0.camel@localhost.localdomain>
     [not found]         ` <44061F96.80900@free.fr>
2006-03-13 19:52           ` matthieu castet
2006-02-28  0:30 ` Christian Trefzer
2006-02-28  9:49   ` Alan Cox
2006-02-28 10:05     ` Christian Trefzer
2006-02-28 10:20     ` [PATCH] Add pata_pdc_2ß27x to Kconfig and Makefile (was: Re: libata PATA patch for 2.6.16-rc5) Christian Trefzer
2006-02-28 10:41       ` Christian Trefzer
2006-02-28 10:58         ` Christian Trefzer
2008-10-14  1:28         ` [PATCH] Add pata_pdc_2ß27x to Kconfig and Makefile Tejun Heo
2008-10-14  8:01           ` Christian Trefzer
2008-10-14  8:09             ` Tejun Heo
2006-02-28 22:32 ` libata PATA patch for 2.6.16-rc5 Francesco Biscani
2006-02-28 23:06 ` Francesco Biscani [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-28 23:42 Chris Boot

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=200603010006.38366.biscani@pd.astro.it \
    --to=biscani@pd.astro.it \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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