From owner-freebsd-scsi Sun Feb 22 09:35:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14784 for freebsd-scsi-outgoing; Sun, 22 Feb 1998 09:35:28 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14776 for ; Sun, 22 Feb 1998 09:35:24 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id KAA06313; Sun, 22 Feb 1998 10:35:07 -0700 (MST) Message-Id: <199802221735.KAA06313@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: Andreas Klemm cc: gibbs@plutotech.com, scsi@FreeBSD.ORG Subject: Re: cam driver: Timedout SCP handeled by another timeout In-reply-to: Your message of "Sun, 22 Feb 1998 11:02:39 +0100." <19980222110239.52637@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Feb 1998 10:32:14 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Hi Justin ! > >First of all, thanks for your work in the cam driver it really >looks very promising and it solved the write append error with >my TDC 4222, 'though I still don't have amanda running, but >that's another story ;-) You're welcome. >On system halt or reboot it happens, that the following >message is printed on the console multiple times: > >Timedout SCB handeled by another timeout. >Timedout SCB handeled by another timeout. >Timedout SCB handeled by another timeout. >... That sounds like your SMP system is disabling interrupts during the last sync in shutdown. I've never seen this happen on a uniprocessor system. Ken Merry also runs CAM on SMP, but I don't know how recent his kernel is. >Here what dmesg tells about my system: >Additionally I have strange problems with my Tandberg SCSI streamer. >mt status only tells one density. > >Present Mode: Density = 0x00 Blocksize = 512 bytes >---------available modes--------- >Mode 0: Density = 0x00 Blocksize = 512 bytes >Mode 1: Density = 0x00 Blocksize = 512 bytes >Mode 2: Density = 0x00 Blocksize = 512 bytes >Mode 3: Density = 0x00 Blocksize = 512 bytes That's not strange at all. The "sa" driver is a rewrite but I haven't had time to add additional density or compression support. Those features should show up next week though. It looks like your tape drive does not honor the immediate flag for rewind commands. It should return an error when that happens instead of ignoring it. I guess I'll have to add a quirk entry for that or up the timeout value for immediate rewinds. >options AHC_TAGENABLE # tagged command queueing >options AHC_SCBPAGING_ENABLE These options have no effect in cam. They are always enabled. >Andreas Klemm >powered by ,,symmetric multiprocessor FreeBSD'' -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message