Date: Tue, 8 Dec 1998 10:37:12 +0100 (CET) From: Dirk Lutzebaeck <lutzeb@aeccom.com> To: Doug Ledford <dledford@redhat.com> Cc: "Holger.Lenz" <Holger.Lenz@m.dasa.de>, aic7xxx@FreeBSD.ORG Subject: Re: Async negotiation (Was: 2.0.36/5.1.4 and BIOS settings) Message-ID: <13932.61293.247635.208700@kamet.aeccom.com> In-Reply-To: <Pine.LNX.4.04.9812071937400.1399-100000@kabal.redhat.com> References: <36653337.579550@m.dasa.de> <Pine.LNX.4.04.9812071937400.1399-100000@kabal.redhat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Ledford writes: > drive in question. If that FAQ says to always use async mode regardless > of the make or model of drive then they need to bite me. There are lots > of DAT drives out there that work great at sync speeds. HP and SONY tend > to run forever sync. If Seagate DATs have a problem in specific then > that's another matter, but last I knew, Seagate only says to disable sync > negotiation on the model ST8000N drives or something like that. It's a Doug, I was wrong to say "all drives". This is from "System Lockup or Freezing problems when running the tape backup" of the Seagate site: (1) "Synchronous Negotiation should be disabled for all Python tape drives. Leave Synchronous Negotiation enabled for the Peregrine or Scorpion tape drives." What confuses me is that my Scorpion STD28000 has a dip switch to make the ID-string say it is an ARCHIVE (ie. Python) tape. So it would then need to run in async mode? (1) http://www.seagate.com/support/tape/scsiide/sublinks/s4m_lock.shtml The real problem I have is this during a backup session: (2.0.36, ASUS P2B-DS 7890 on board) Nov 18 13:56:24 kamet kernel: scsi : aborting command due to timeout : pid 186495, scsi0, channel 0, id 0, lun 0 Read (10) 00 00 76 76 95 00 00 98 00 Nov 18 13:56:25 kamet kernel: scsi : aborting command due to timeout : pid 186496, scsi0, channel 0, id 0, lun 0 Write (6) 00 80 65 02 00 [... this goes on and on until ...] Nov 18 14:11:04 kamet kernel: scsi : aborting command due to timeout : pid 186495, scsi0, channel 0, id 0, lun 0 Read (10) 00 00 76 76 95 00 00 98 00 Nov 18 14:11:06 kamet kernel: SCSI host 0 abort (pid 186494) timed out - resetting Nov 18 14:11:06 kamet kernel: SCSI bus is being reset for host 0 channel 0. Nov 18 14:11:06 kamet kernel: (scsi0:0:0:0) Synchronous at 20.0 Mbyte/sec, offset 15. Nov 18 14:11:24 kamet kernel: st0: Error 26030000. Nov 18 14:11:26 kamet kernel: st0: Error 26030000. This is my IBM DDRS-UW on id 0 gets a timeout and after 5min (!) the kernel seems to issue a bus reset. The strange thing is that this always happens with amanda but never with just a simple tar on st0 (of several 100MBs). Dirk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-aic7xxx" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?13932.61293.247635.208700>