[1720] in linux-scsi channel archive

home help back first fref pref prev next nref lref last post

wierd philips scsi cdrom drive

daemon@ATHENA.MIT.EDU (Paul Mackerras)
Fri Apr 18 02:24:26 1997

Date: 	Fri, 18 Apr 1997 16:15:25 +1000
From: Paul Mackerras <paulus@cs.anu.edu.au>
To: linux-scsi@vger.rutgers.edu
Reply-to: Paul.Mackerras@cs.anu.edu.au

I've got Linux running on a Power Computing Powerbase 180 (not mine,
it belongs to a friend), and I'm having an unusual problem with the
SCSI CDROM during the scsi probing at startup.  It's a Philips drive,
but I don't have the model number at present.  We are running
linux-2.1.24.

What happens is this: we send a test-unit-ready command (00) which
works fine; we get back a command-complete message and a "good" status
(0).  Then we send an inquiry command (0x12).  The cdrom accepts the
command, doesn't transfer any data, but immediately returns a
command-complete message and a status byte of 0x12, which is not a
value defined in the scsi-2 standard.  The scsi mid-level driver gets
confused by this, of course, and prints messages like "Internal error
scsi.c line 1672" and "status byte = 9".  This happens whether or not
there is a CD in the drive.  I tried changing the code to make it
retry, but the same behaviour just kept occurring, so it's not a
matter of the drive needing time to get its act together.

Has anyone seen this sort of behaviour before, or does anyone know
what the 0x12 status value means?

Paul.

home help back first fref pref prev next nref lref last post