Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 02 Sep 1997 11:03:33 +0200
From:      Mark R V Murray <markm@iafrica.com>
To:        scsi@freebsd.org
Cc:        markm@iafrica.com
Subject:   Nasty bug in SCSI/3.0-current?
Message-ID:  <199709020903.LAA18339@rodent.iafrica.com>

next in thread | raw e-mail | index | archive | help
Hi

I have just succeded in hosing my hard disk for the second time using 
ports/audio/tosha and my nec SCSI CDROM drive.

Symptoms:

I try to read an audio track from the CDROM drive, and I get the 
following errors logged to the console:


Sep  1 21:31:26 greenpeace /kernel: st0: BLANK CHECK req sz: 1 (decimal) asc:0,5 End-of-data detected
Sep  1 21:31:26 greenpeace /kernel: st0: BLANK CHECK req sz: 1 (decimal) asc:0,5 End-of-data detected
Sep  2 07:50:27 greenpeace login: ROOT LOGIN (root) ON ttyv2
Sep  2 08:43:09 greenpeace /kernel: cd0: ILLEGAL REQUEST asc:64,0 Illegal mode for this track
Sep  2 08:43:09 greenpeace /kernel: cd0: ILLEGAL REQUEST asc:64,0 Illegal mode for this track
Sep  2 08:43:13 greenpeace /kernel: cd0: ILLEGAL REQUEST asc:64,0 Illegal mode for this track
Sep  2 08:43:23 greenpeace /kernel: cd0: ILLEGAL REQUEST asc:24,0 Invalid field in CDB
Sep  2 08:43:13 greenpeace /kernel: cd0: ILLEGAL REQUEST asc:64,0 Illegal mode for this track
Sep  2 08:43:23 greenpeace /kernel: cd0: ILLEGAL REQUEST asc:24,0 Invalid field in CDB
Sep  2 08:45:21 greenpeace /kernel: cd0: SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0
Sep  2 08:45:21 greenpeace /kernel: cd0: SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0
Sep  2 08:45:22 greenpeace /kernel: SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa
Sep  2 08:45:22 greenpeace /kernel: SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa

The system hangs, and after a while panics.

The SCSI disk on the same bus is then HOSED - it needs to be low level 
reformatted, as a very large number of sectors are not readable.

I have a GA586DX motherboard, which has an Adaptec 7660(?) on board. 
(This is the chip that looks like a 2940.)

I am running 3.0-CURRENT (Really current).

I did not have this problem 2 weeks ago. (Last time I tried.)

Hints? Suggestions? Flames? I can't experiment too much, as it takes me 
several hours to recover each time. (I love DAT!)

M
-- 
Mark Murray
Senior Network Engineer, UUNET Internet Africa
Join the anti-SPAM movement: http://www.cauce.org





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709020903.LAA18339>