Last time we worked on this, the way to detect it was to notice that the
unit had reset itself after you got the 2 bytes but before you got the rest
of the data -- that is, the ASC/ASCQ of the failed full-length mode sense
command would indicated that the unit had just been reset and was becoming
ready.

Note that this behavior hasn't changed from 1.10a4 which worked until now.
cdrecord used to print a warning along the lines of "controler generates
hard failure when retrieveing capabilities page" or somesuch -- I'm still
unpacking, so I can't do a setup and test with teh version of cdrecord that
I have been using.

Did you change this behavior for a reason?  I remember pointing out to you
that this is actually the firmware in the OEM Phillips drive (which you
pointed out had been failing elsewhere but didn't know why) doing bad
things.

Matt

On Sat, Mar 31, 2001 at 09:05:07PM +0200, Joerg Schilling wrote:
> 
> >From: Matthew Dharm <[EMAIL PROTECTED]>
> 
> >Can you check something for me?  I'm not seeing in these cdrecord output
> >the "warning:" message that says that the hard reset occured after the mode
> >sense.
> 
> The big problem with Linux in general is that due to a design bug,
> there is no way to detect  DMA count errors.
> Linux does not check the DMA count at all.
> 
> OTOS On my Sony VAIO, I get at least the SCSI transport error set to retryable.
> 
> With the trace send with the original mail, the mode sense command
> which request 2 bytes appears to work 100% correctly. For this reason,
> cdrecord has no way to detect the DMA problem.
> 
> >This looks very much like the original problem we had with these drives --
> >you do the mode sense for 2 bytes (the length data), the drive goes nuts,
> >the bridge declares an error, the driver forces a bridge reset, and cdrecord
> >gives up.  The fix, IIRC, was to have cdrecord realize that reset occured
> >and retry the full mode sense data transfer.
> 
> >But I don't see the retry happening here.... is that right?
> 
> 
> Right, if the command appears to work how should I see the problem.
> 
> Jörg
> 
>  EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
>        [EMAIL PROTECTED]             (uni)  If you don't have iso-8859-1
>        [EMAIL PROTECTED]         (work) chars I am J"org Schilling
>  URL:  http://www.fokus.gmd.de/usr/schilling   ftp://ftp.fokus.gmd.de/pub/unix

-- 
Matthew Dharm                              Home: [EMAIL PROTECTED] 
Senior Software Designer, Momentum Computer

I'm a pink gumdrop! How can anything be worse?!!
                                        -- Erwin
User Friendly, 10/4/1998

PGP signature

Reply via email to