From owner-freebsd-scsi Wed Mar 13 12:38:45 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA22265 for freebsd-scsi-outgoing; Wed, 13 Mar 1996 12:38:45 -0800 (PST) Received: from Sisyphos (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id MAA22247 for ; Wed, 13 Mar 1996 12:37:55 -0800 (PST) Received: by Sisyphos id AA17835 (5.67b/IDA-1.5 for freebsd-scsi@freebsd.org); Wed, 13 Mar 1996 21:37:37 +0100 Message-Id: <199603132037.AA17835@Sisyphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Wed, 13 Mar 1996 21:37:36 +0100 In-Reply-To: Jim Lowe "Re: NCR disk controller, hp disk" (Mar 13, 13:59) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: Jim Lowe Subject: Re: NCR disk controller, hp disk Cc: freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mar 13, 13:59, Jim Lowe wrote: } Subject: Re: NCR disk controller, hp disk } OK... I wasn't able to save all the output from the boot up } as the message buffer isn't large enough. In any case, it } looks like I got enough info (I hope). Here is is with } SCSI_DEBUG_FLAGS=0x600. The drive is sd1. I also attached } the output from a ``disklabel sd1''. This time the output proves that tags work in principle ... But it shows another interesting detail, too :) Thanks! (No, I won't tell, and it doesn't cause any harm, at least in your case, but I'll have to change it anyway ... ;-) } (ncr0:1:0): command: 0,0,0,0,0,0-[0 bytes] } code70 valid0 seg0 key6 ili0 eom0 fmark0 } (ncr0:1:0): command: 12,0,0,0,2c,0-[44 bytes] } sd1(ncr0:1:0): using tag #1. } sd1(ncr0:1:0): sync msgout: 1-3-1-19-8. } sd1(ncr0:1:0): sync msgin: 1-3-1-19-8. } sd1(ncr0:1:0): sync: per=25 ofs=8 fak=0 chg=0. } sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. } ncr0: actlink: diff=1, new=2, req=2 } sd1(ncr0:1:0): scsi_done Ok. This command worked fine with tag "1" ... } sd1(ncr0:1:0): command: 1a,0,4,0,20,0-[35 bytes] } sd1(ncr0:1:0): using tag #2. ... as did this one with tag "2". } sd1(ncr0:1:0): command: 25,0,0,0,0,0,0,0,0,0-[8 bytes] } (ncr0:2:0): "TOSHIBA CD-ROM XM-3401TA 2873" type 5 removable SCSI 2 } cd0(ncr0:2:0): CD-ROM } cd0(ncr0:2:0): sync msgout: 1-3-1-19-8. } cd0(ncr0:2:0): sync msgin: 1-3-1-3b-8. } cd0(ncr0:2:0): sync: per=59 ofs=8 fak=6 chg=0. } cd0(ncr0:2:0): 250ns (4 Mb/sec) offset 8. } cd0(ncr0:2:0): NOT READY asc:3a,0 Medium not present } can't get the size } (ncr0:2:2): sync msgout: 1-3-1-19-8. } (ncr0:2:2): sync msgin: 1-3-1-3b-8. } (ncr0:2:2): sync: per=59 ofs=8 fak=6 chg=0. } (ncr0:2:3): sync msgout: 1-3-1-19-8. } (ncr0:2:3): sync msgin: 1-3-1-3b-8. } (ncr0:2:3): sync: per=59 ofs=8 fak=6 chg=0. } (ncr0:2:4): sync msgout: 1-3-1-19-8. } (ncr0:2:4): sync msgin: 1-3-1-3b-8. } (ncr0:2:4): sync: per=59 ofs=8 fak=6 chg=0. } (ncr0:2:5): sync msgout: 1-3-1-19-8. } (ncr0:2:5): sync msgin: 1-3-1-3b-8. } (ncr0:2:5): sync: per=59 ofs=8 fak=6 chg=0. } (ncr0:2:6): sync msgout: 1-3-1-19-8. } (ncr0:2:6): sync msgin: 1-3-1-3b-8. } (ncr0:2:6): sync: per=59 ofs=8 fak=6 chg=0. } (ncr0:2:7): sync msgout: 1-3-1-19-8. } (ncr0:2:7): sync msgin: 1-3-1-3b-8. } (ncr0:2:7): sync: per=59 ofs=8 fak=6 chg=0. Well, that's the thing I'd never seen before: The code tries to negotiate sync. transfer rate with every LUN of target 2, which is one and the same CDROM drive. This doesn't hurt, but it is, well, at least a waste of msgbuf space :) } sd1(ncr0:1:0): sd_open: dev=0x10d0a (unit 1, partition 2) } sd1(ncr0:1:0): scsi_cmd } sd1(ncr0:1:0): using tag #3. } ncr0: actlink: diff=1, new=4, req=4 } sd1(ncr0:1:0): scsi_done Ok: TEST UNIT READY } sd1(ncr0:1:0): command: 0,0,0,0,0,0-[0 bytes] } sd1(ncr0:1:0): calling private start() } sd1(ncr0:1:0): sdstart sd1(ncr0:1:0): scsi_cmd } sd1(ncr0:1:0): using tag #4. } cr0:1:0): scsi_done } sd1(ncr0:1:0): command: 0,0,0,0,0,0-[0 bytes] } sd1(ncr0:1:0): calling private start() } sd1(ncr0:1:0): sdstart sd1(ncr0:1:0): scsi_cmd } sd1(ncr0:1:0): scsi_done Ok: TEST UNIT READY (don't know, why so many are issued, this is implemented in the GENERIC SCSI code ...) } sd1(ncr0:1:0): command: 1e,0,0,0,1,0-[0 bytes] } sd1(ncr0:1:0): calling private start() } sd1(ncr0:1:0): sdstart sd1(ncr0:1:0): } sdstrategy sd1(ncr0:1:0): 512 bytes @ blk0 } sd1(ncr0:1:0): sdstart sd1(ncr0:1:0): scsi_cmd } sd1(ncr0:1:0): scsi_done Tags are only reported, when they are used for the first time. This command doesn't tell which tag had been assigned, but it was in the range 1 to 4 for sure ... } sd1(ncr0:1:0): command: 28,0,0,0,0,0,0,0,1,0-[512 bytes] } ------------------------------ } 000: 00 58 e3 f0 00 00 00 00 00 00 00 00 00 00 00 00 } 016: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 } 032: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 } 048: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 } ------------------------------ } code70 valid0 seg0 keyb ili0 eom0 fmark0 } info: 0 0 0 0 followed by 20 extra bytes } extra: 0 0 0 0 4e 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 } sd1(ncr0:1:0): calling private err_handler() } sd1(ncr0:1:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted } , retries:4 } sd1(ncr0:1:0): private err_handler() returned -2 } sd1(ncr0:1:0): scsi_done Ok. I have removed the remaining lines, since they only duplicate what appeared above ... Hmmm, all I can tell you now is, that several commands succeed, before the first read fails. I'm posting this to the freebsd-scsi list, too, in the hope that somebody has a really good idea ... :) Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se