Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 14 Mar 1999 21:02:54 -0500 (EST)
From:      "Matthew N. Dodd" <winter@jurai.net>
To:        Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>
Cc:        freebsd-scsi@FreeBSD.ORG
Subject:   Re: SONY SMO-C501-09 not recognized under CAM
Message-ID:  <Pine.BSF.4.02.9903142046190.2158-100000@sasami.jurai.net>
In-Reply-To: <19990314142415.23439@uriah.heep.sax.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 14 Mar 1999, J Wunsch wrote:
> Thanks!, i was hoping for some advice like this.  (Btw., it's IMHO
> safe to only test for SONY SMO-*, they are all such old devices.)

<HP       5.25 MF Drv  000>
<HP       S6300.650A>

Just different names in the firmware for the same bridge/mechanism.

> Alas, it doesn't work. :(  Right after probing the CD-ROM drive (which
> is on the other bus), it now jams its SCSI bus.
> 
> (The following has been written on a sheet of paper, so typos are
> mine.)
> 
> ncr1: SCSI phase error fixup: CCB already dequeued (0xc07b0000)
> ncr1: timeout nccb=0xc07b0000 (skip)
> ncr1: timeout nccb=0xc07b0000 (skip)
> ncr1: timeout nccb=0xc07b0000 (skip)
> (da2:ncr1:0:3:0) got CAM status 0x4b
> (da2:ncr1:0:3:0) fatal error, failed to attach device
> (da2:ncr1:0:3:0) lost device
> (da2:ncr1:0:3:0) removing device entry
> 
> At this point, the system effectively halts.  Upon waiting
> indefinitely, it would eventually timeout a few more CCBs, but i lost
> my patience and hit reset.
> 
> With a spinning medium in the drive, it boots well (and da2 even
> `arrives' before da1).
> 
> > I'm not sure why the da driver didn't attach when you rescanned the
> > drive.  I'd have to think on that to figure it out, and it's too
> > late for thinking too much. :)
> 
> Understood.
> 
> My suspicion (just guessing, i don't have an idea of the program flow
> in the CAM code) is that my attempt to spinup the drive using the pass
> device (which succeeded) caused the drive to become `half-known', as a
> subsequent camcontrol devlist seems to confirm (device assigned to
> pass4, but not to any other driver).  A following camcontrol rescan
> didn't notice it as a new entry, so nothing happened.
> 
> I played a little, turned off the drive, camcontrol rescan so it had
> to remove the entry completely.  Then turned on the drive again (which
> also causes it to spin up), and voilá, the next camcontrol rescan
> makes the drive accessible as both, pass4 and da2.

Same thing I get.

-- 
| Matthew N. Dodd  | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS |
| winter@jurai.net |      This Space For Rent     | ix86,sparc,m68k,pmax,vax  |
| http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage?   |



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.02.9903142046190.2158-100000>