From owner-freebsd-scsi Sun Mar 29 01:55:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA27717 for freebsd-scsi-outgoing; Sun, 29 Mar 1998 01:55:18 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27712 for ; Sun, 29 Mar 1998 01:55:14 -0800 (PST) (envelope-from dan@math.berkeley.edu) Received: (from dan@localhost) by math.berkeley.edu (8.8.7/8.8.7) id BAA28477; Sun, 29 Mar 1998 01:55:04 -0800 (PST) Date: Sun, 29 Mar 1998 01:55:04 -0800 (PST) From: dan@math.berkeley.edu (Dan Strick) Message-Id: <199803290955.BAA28477@math.berkeley.edu> To: dburr@POBoxes.com, freebsd-scsi@FreeBSD.ORG Subject: Re: Info wanted: Exabyte EXB-8500 Cc: dan@math.berkeley.edu Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm considering the purchase of an Exabyte EXB-8500 tape drive to go with > my FreeBSD system, since I need a decent backup device (Zip disks just > ain't cutting it anymore, especially since I got this new 4.3 GB drive...) > > I thought I'd consult the FreeBSD community, before making my purchase. I > have the following questions: > > 1. Does this drive work OK with FreeBSD? Any weird behavior or other > gotcha's that I should be aware of? > > 2. Will it work with an Adaptec AHA-2940AU PCI UltraSCSI (narrow) adapter? > > 3. Is anyone using this combo? How's it work? > > 4. (I figure I might as well ask this while I've got your attention) > My source for this drive is someone posting in misc.forsale.*. Now, I > usually have pretty good luck buying from the net (in fact, I have had no > ripoffs to date), but this is primarily due to me carefully reading the ad, > judging the person's character, etc. One of the "warning flags" that I > look for is a "too good to be true" price, which usually means that the 1) I have in the past (circa FreeBSD release 2.0.5) used both the EXB-8500 and the EXB-8505 (same thing in half height) on FreeBSD systems. I don't recall any problems. 2) I used the Adaptec 154x ISA controllers at the time. I would be very 3) surprised to find incompatibility with a modern PCI controller. 4) The 8500 is a *very* old drive. I would expect this one to be very well worn and that suggests that the drive will exhibit a high soft error rate that verges on occasional hard errors. The tape heads on these things just wear out. The official specification for 8500 tape head lifetime is something like 2000 tape-motion-hours. Expect this tape drive to require more frequent and more expensive maintenance than a vintage BMW. If you do decide to get the EXB-8500, make sure it is really an EXB-8500C (with data compression) and was not upgraded from a plain EXB-8500. The original EXB-8500s had too slow an internal processor to keep up with the tape, causing lots of tape overruns. Dan Strick dan@math.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 29 19:24:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01289 for freebsd-scsi-outgoing; Sun, 29 Mar 1998 19:24:58 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01153 for ; Sun, 29 Mar 1998 19:24:46 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt3-107.HiWAAY.net [208.147.146.107]) by fly.HiWAAY.net (8.8.8/8.8.6) with ESMTP id VAA17771 for ; Sun, 29 Mar 1998 21:24:38 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.4) with ESMTP id VAA03628 for ; Sun, 29 Mar 1998 21:08:27 -0600 (CST) Message-Id: <199803300308.VAA03628@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-scsi@FreeBSD.ORG From: David Kelly Subject: Re: Signal 11's.. (and SCB problems) In-reply-to: Message from The Hermit Hacker of "Sun, 29 Mar 1998 03:56:01 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Mar 1998 21:08:27 -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The Hermit Hacker writes: > > If so, would SCB explain why, with an adaptec 2940UW controller > and SCB enabled, I'm seeing what *feel* like SCSI bus hangs? Where I can > telnet to the machine, get the beginnings of the 'login', but no login > prompt? Machine is still pingable and everything? > > My configure has the following lines: > > controller ahc0 > options AHC_SCBPAGING_ENABLE > options AHC_TAGENABLE > options AHC_ALLOW_MEMIO > > And the system is running STABLE... > > IF the SCB should be removed, what about the other two? Any > similar problems known with those? I've had 3 similar incidents the past several weeks, also with STABLE (a.k.a. RELENG_2_2, right?) In my situation I have root and swap on a 2G drive on a 2940 (notice this is an old 2940), more swap and my CVS repository on a 9G drive connected to an '875: ahc0 rev 0 int a irq 9 on pci0:9:0 ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "SEAGATE ST32550N 0021" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 2047MB (4194058 512 byte sectors) [...] ncr0 rev 3 int a irq 11 on pci0:11:0 ncr0 waiting for scsi devices to settle (ncr0:0:0): WIDE SCSI (16 bit) enabled(ncr0:0:0): 10.0 MB/s (200 ns, offset 15) (ncr0:0:0): "IBM OEM DCHS09W 2222" type 0 fixed SCSI 2 sd1(ncr0:0:0): Direct-Access sd1(ncr0:0:0): WIDE SCSI (16 bit) enabled sd1(ncr0:0:0): 20.0 MB/s (100 ns, offset 15) 8689MB (17796077 512 byte sectors) Initially I had FAILSAFE commented out of my config. Yeilded a spectacular semi-hang which was able to produce the following message and let me log in on a couple of vty's before finally totally failing to respond: swap_pager: indefinite wait buffer: device 197641, blkno 1472 size 8192 ... a repeating list with 7 different block numbers and 6 unique sizes ranging from 4096 to 28672. I posted this on 3/20 to -stable and didn't get any replies. A good start in diagnosis would be, "what is device 197641?" Other hangs have happened since but none but the first yeilded any messages. Every time I had kernel pppd running, Netscape 3.01 (US version manually replaced export version installed via ports), and "cd /usr && cvs -q update src" running. Am not certian every time, but most times at least the CVS repository partition was mounted async. Async was added after the fact with "mount -u -o async /r/usr". At least once I had also applied async to my /usr partition containing /usr/src. Have not been able to reproduce the problem at will. Have recently removed the swap partition from the 2G disk in /etc/fstab in order to see if that has any effect (I don't know which is device 197641) -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 29 19:30:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03144 for freebsd-scsi-outgoing; Sun, 29 Mar 1998 19:30:03 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from thunderdome.plutotech.com (root@thunderdome.plutotech.com [206.168.67.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03088 for ; Sun, 29 Mar 1998 19:29:58 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by thunderdome.plutotech.com (8.8.7/8.8.5) with ESMTP id PAA00236; Sun, 29 Mar 1998 15:20:28 -0700 (MST) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id PAA03253; Sun, 29 Mar 1998 15:20:26 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199803292220.PAA03253@panzer.plutotech.com> Subject: Re: SDT-7000 and other DDS-2 tapes In-Reply-To: from Simon Shapiro at "Mar 29, 98 02:23:31 pm" To: shimon@simon-shapiro.org Date: Sun, 29 Mar 1998 15:20:26 -0700 (MST) Cc: ken@plutotech.com, semen@iclub.nsu.ru, FreeBSD-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Simon Shapiro wrote... > If you have (something I asked Justin for :-) a list of API routines the > CAM produces ( a brief ``what it does'' will be great!), and entry points > expected of a driver, you will xut my development time by a week or two. Sorry, I don't have anything other than the source and the CAM specs from ftp.symbios.com. I would give you a summary of the interface between the transport layer and the controller drivers, but I haven't written/ported any of the controller drivers for CAM. Justin has done them all so far. My work has been on the peripheral drivers, transport layer, statistics and userland code. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 29 19:30:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03170 for freebsd-scsi-outgoing; Sun, 29 Mar 1998 19:30:05 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from thunderdome.plutotech.com (root@thunderdome.plutotech.com [206.168.67.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03095 for ; Sun, 29 Mar 1998 19:29:59 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by thunderdome.plutotech.com (8.8.7/8.8.5) with ESMTP id OAA00123; Sun, 29 Mar 1998 14:24:23 -0700 (MST) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id OAA02989; Sun, 29 Mar 1998 14:24:21 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199803292124.OAA02989@panzer.plutotech.com> Subject: Re: SDT-7000 and other DDS-2 tapes In-Reply-To: from Simon Shapiro at "Mar 29, 98 01:30:04 pm" To: shimon@simon-shapiro.org Date: Sun, 29 Mar 1998 14:24:21 -0700 (MST) Cc: ken@plutotech.com, FreeBSD-scsi@FreeBSD.ORG, semen@iclub.nsu.ru X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Simon Shapiro wrote... > > On 25-Mar-98 Kenneth D. Merry wrote: > > Simon Shapiro wrote... > >> > >> On 25-Mar-98 Ustimenko Semen wrote: > >> > > >> > Have somebody succesfuly used SDT-7000 under FreeBSD? > >> > >> Yes. Two of them in shared mode on a DPT controller. > > > > What do you mean by "in shared mode"? > > I use most of my SCSI devices on a shared bus between two FreeBSD boxes. > Part of the (still developing) High Availability Server I am working on. Interesting indeed. You might be interested to know that the CAM tape driver does a reserve unit on open, so any other initiators on the bus won't be able to muck with the drive when one initiator has it open. (of course, it cancels the reservation at final close) > I will make one of these servers pulicly open, so people can login and > look-see. Cool. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 29 19:53:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA12597 for freebsd-scsi-outgoing; Sun, 29 Mar 1998 19:53:26 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fddi.Simon-Shapiro.ORG [206.190.148.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA12517 for ; Sun, 29 Mar 1998 19:53:18 -0800 (PST) (envelope-from shimon@simon-shapiro.org) Received: (qmail 20228 invoked from network); 29 Mar 1998 20:55:45 -0000 Received: from localhost.simon-shapiro.org (HELO sendero-fxp0.simon-shapiro.org) (@127.0.0.1) by localhost.simon-shapiro.org with SMTP; 29 Mar 1998 20:55:45 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-032398 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 29 Mar 1998 12:55:45 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Ustimenko Semen Subject: RE: SDT-7000 and other DDS-2 tapes Cc: FreeBSD-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 25-Mar-98 Ustimenko Semen wrote: > On Wed, 25 Mar 1998, Simon Shapiro wrote: >> On 25-Mar-98 Ustimenko Semen wrote: >> > >> > Have somebody succesfuly used SDT-7000 under FreeBSD? >> >> Yes. Two of them in shared mode on a DPT controller. >> > Wow! And it realy gives 600kb/s (I have only 150, and not proper > capacity). Tell me, pls, is it -CURRENT, and what blocksize and density > do you use? And dmesg:) My tests hover around 1-1.2MB/Sec for CPIO or DUMP (But, important BUT below). Here is a fragment of dmesg from sendero sd80: Direct-Access 23834MB (48813696 512 byte sectors) pt5 at scbus5 target 7 lun 0 pt5: type 3 fixed SCSI 2 pt5: Processor sd88 at scbus5 target 8 lun 0 sd88: type 0 fixed SCSI 2 sd88: Direct-Access 23834MB (48812544 512 byte sectors) scbus6 at dpt1 bus 2 worm6 at scbus6 target 4 lun 0 worm6: type 4 removable SCSI 2 worm6: Write-Once st6 at scbus6 target 5 lun 0 st6: type 1 removable SCSI 2 st6: Sequential-Access density code 0x13, 512-byte blocks, write-enabled pt6 at scbus6 target 7 lun 0 pt6: type 3 fixed SCSI 2 pt6: Processor IMPORTANT BUT: The SCSI tape drive is DANGEROUSLY next to useless! If the system uses ANY block size other than 512 bytes, you will silently produce trash tapes. Here are some details: * Do NOT use dump(1). Dump uses blocking that are a multiple of 1K. This produces tapes that cannot be read; The data is trash, there are no EOF maks on the tape, etc. * CPIO must be factored with -C 512, or you will get the same trash problems. * When you run at 512 byte blocks, throughput becomes akin to RS-232C. It is very, very slow. The danger lies in the dumping/writing process NOT producing ANY indication of failure. Things just zoom along nicely. The problem arises when you try to READ the tapes. There will be nothing but trash there. BTW, My answr got delayed, as I had to dump some 30GB of data to tapes, as part of disks upgrade. It took that long to finish (4 days). ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 29 20:17:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08170 for freebsd-scsi-outgoing; Sun, 29 Mar 1998 19:44:28 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from friley585.res.iastate.edu (friley585.res.iastate.edu [129.186.167.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA07626 for ; Sun, 29 Mar 1998 19:42:17 -0800 (PST) (envelope-from ccsanady@friley585.res.iastate.edu) Received: from friley585.res.iastate.edu (loopback [127.0.0.1]) by friley585.res.iastate.edu (8.8.8/8.8.8) with ESMTP id JAA18988; Sun, 29 Mar 1998 09:35:37 -0600 (CST) (envelope-from ccsanady@friley585.res.iastate.edu) Message-Id: <199803291535.JAA18988@friley585.res.iastate.edu> X-Mailer: exmh version 2.0.1 12/23/97 To: The Hermit Hacker cc: freebsd-scsi@freebsd.org Subject: Re: Signal 11's.. (and SCB problems) In-reply-to: Your message of "Sun, 29 Mar 1998 03:56:01 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Mar 1998 09:35:37 -0600 From: Chris Csanady Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk X-Loop: FreeBSD.org >On Sat, 28 Mar 1998, Chris Csanady wrote: > >> While building a world, I recently noticed that I was getting random >> signal 11's. I was under the impression that this was fixed earlier, >> is this correct? >> >> I suppose this is probably related to the SCB problems, but I can't >> say. Is anyone else seeing similar problems? >> >> Regardless, SMP is still miserable here. I seem to have similar SCB >> hangs (that I mentioned earlier) running UP as well, although they >> are fairly rare. > > UP == UniProcessor? Yep. > If so, would SCB explain why, with an adaptec 2940UW controller >and SCB enabled, I'm seeing what *feel* like SCSI bus hangs? Where I can >telnet to the machine, get the beginnings of the 'login', but no login >prompt? Machine is still pingable and everything? Yes, this sounds about right. If you wait a really really long time, you may actually get a login. At least that has been my experience.. > My configure has the following lines: > >controller ahc0 >options AHC_SCBPAGING_ENABLE >options AHC_TAGENABLE >options AHC_ALLOW_MEMIO I have actually tried removing the AHC_SCBPAGING_ENABLE and AHC_TAGENABLE lines, although that does not seem to help under SMP. I have not tried that without SMP though. > And the system is running STABLE... Hmm.. This is not really what I wanted to hear. :( I was under the impression that this was a current breakage. A while back, even SMP was actually stable on my machine. I am currently steping back my machine till late last year to see if it's a hardware issue. If not, I may try to incrementally find where the exact breakage occurred. > IF the SCB should be removed, what about the other two? Any >similar problems known with those? I think it is fairly safe to leave the AHC_ALLOW_MEMIO option in. Chris Csanady To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 29 20:20:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23266 for freebsd-scsi-outgoing; Sun, 29 Mar 1998 20:20:52 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from garlic.acadiau.ca (root@garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA22967; Sun, 29 Mar 1998 20:20:05 -0800 (PST) (envelope-from marc@acadiau.ca) Received: from iceberg (iceberg [131.162.2.91]) by garlic.acadiau.ca (8.8.5/8.8.5) with SMTP id AAA14590; Mon, 30 Mar 1998 00:19:25 -0400 (AST) Date: Mon, 30 Mar 1998 00:19:57 -0400 (AST) From: Marc Fournier X-Sender: marc@iceberg To: freebsd-scsi@FreeBSD.ORG cc: freebsd-stable@FreeBSD.ORG Subject: Adaptec 2940UW with two ?? UW drives... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Morning... Well, tonight, my #$^%#@%@ FreeBSD system is locked up solid...again. It's pretty much a daily occurance now, and I'm at a loss as to what to try next. I just put in a brand new 2940UW controller, with two UW drives (I'd tell you which, except I can't get to the system right now), and there is an IDE drive as the root drive for it... Symptom: if I telnet to the machine, I get: telnet hub.org Trying 209.47.148.200... Connected to hub.org. Escape character is '^]'. And it just sits there... At one persons suggestion, I've disabled SCBPAGING, but that apparently hasn't helped any... I'm running 2.2-STABLE on that machine right now, and reported a problem this morning with a panic: biodone... error message. I'm slowly going through the mailing list search engines, and get the feeling that the 2940 controllers might not be a "good pick" as far as controllers are concerned :( Thoughts? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 29 20:28:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA26348 for freebsd-scsi-outgoing; Sun, 29 Mar 1998 20:28:07 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fddi.Simon-Shapiro.ORG [206.190.148.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA26156 for ; Sun, 29 Mar 1998 20:27:39 -0800 (PST) (envelope-from shimon@simon-shapiro.org) Received: (qmail 20726 invoked from network); 29 Mar 1998 21:30:04 -0000 Received: from localhost.simon-shapiro.org (HELO sendero-fxp0.simon-shapiro.org) (@127.0.0.1) by localhost.simon-shapiro.org with SMTP; 29 Mar 1998 21:30:04 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-032398 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199803251643.JAA02251@panzer.plutotech.com> Date: Sun, 29 Mar 1998 13:30:04 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: "Kenneth D. Merry" Subject: Re: SDT-7000 and other DDS-2 tapes Cc: FreeBSD-scsi@FreeBSD.ORG, semen@iclub.nsu.ru Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 25-Mar-98 Kenneth D. Merry wrote: > Simon Shapiro wrote... >> >> On 25-Mar-98 Ustimenko Semen wrote: >> > >> > Have somebody succesfuly used SDT-7000 under FreeBSD? >> >> Yes. Two of them in shared mode on a DPT controller. > > What do you mean by "in shared mode"? I use most of my SCSI devices on a shared bus between two FreeBSD boxes. Part of the (still developing) High Availability Server I am working on. I will make one of these servers pulicly open, so people can login and look-see. ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 29 20:36:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00453 for freebsd-scsi-outgoing; Sun, 29 Mar 1998 20:36:57 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from lithium.elemental.org (daleg@lithium.elemental.org [204.91.240.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA00404 for ; Sun, 29 Mar 1998 20:36:51 -0800 (PST) (envelope-from daleg@lithium.elemental.org) Received: from localhost (daleg@localhost) by lithium.elemental.org (8.8.8/8.8.4) with SMTP id XAA28462; Sun, 29 Mar 1998 23:24:47 -0500 Date: Sun, 29 Mar 1998 23:24:47 -0500 (EST) From: Ðale Ghent Reply-To: Dale Ghent To: Marc Fournier cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Adaptec 2940UW with two ?? UW drives... In-Reply-To: Message-ID: X-President-Clinton: On Crack X-LART: Homelite Chainsaw MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 30 Mar 1998, Marc Fournier wrote: | I just put in a brand new 2940UW controller, with two UW drives | (I'd tell you which, except I can't get to the system right now), and | there is an IDE drive as the root drive for it... I'm running two 4GB Cheetah drives off a 2940UW, with tag and paging enabled, just fine. This is on 2.2.1, though. -Dale G. "And when the smoke cleared away, and I sought to look upon the earth, I beheld against the background of cold, humorous stars only the dying sun and the pale mournful planets searching for their sister." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 29 20:41:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02300 for freebsd-scsi-outgoing; Sun, 29 Mar 1998 20:41:59 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from thelab.hub.org (tc-43.acadiau.ca [131.162.2.143]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA02191; Sun, 29 Mar 1998 20:41:46 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id RAA07262; Sun, 29 Mar 1998 17:40:17 -0400 (AST) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 29 Mar 1998 17:40:15 -0400 (AST) From: The Hermit Hacker To: Chris Csanady cc: freebsd-stable@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: panic: biodone: buffer not busy (Was: Re: Signal 11's.. (and SCB problems) ) In-Reply-To: <199803291535.JAA18988@friley585.res.iastate.edu> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1369468618-891207615=:1536" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1369468618-891207615=:1536 Content-Type: TEXT/PLAIN; charset=US-ASCII On Sun, 29 Mar 1998, Chris Csanady wrote: > I have actually tried removing the AHC_SCBPAGING_ENABLE and AHC_TAGENABLE > lines, although that does not seem to help under SMP. I have not tried > that without SMP though. Well, I removed the AHC_SCBPAGING_ENABLE option, but left in the TAGENABLE, and it panic'd a few hours later (panic'ng is better then hanging...debuggable, at least)... I've included here both the config file for my machine, as it stands now, as well as the gdb output for the core dump. If there is any more information that I can provide, please feel free to ask...I have lots of space right now for /var/crash, so am in no hurry to remove it... --0-1369468618-891207615=:1536 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=type Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: U2NyaXB0IHN0YXJ0ZWQgb24gU3VuIE1hciAyOSAxNjozMTo1OSAxOTk4DQoj IGdkYiAtayBrZXJuZWwuTWFyMjkgdm1jb3JlLjANCkdEQiBpcyBmcmVlIHNv ZnR3YXJlIGFuZCB5b3UgYXJlIHdlbGNvbWUgdG8gZGlzdHJpYnV0ZSBjb3Bp ZXMgb2YgaXQNCiB1bmRlciBjZXJ0YWluIGNvbmRpdGlvbnM7IHR5cGUgInNo b3cgY29weWluZyIgdG8gc2VlIHRoZSBjb25kaXRpb25zLg0KVGhlcmUgaXMg YWJzb2x1dGVseSBubyB3YXJyYW50eSBmb3IgR0RCOyB0eXBlICJzaG93IHdh cnJhbnR5IiBmb3IgZGV0YWlscy4NCkdEQiA0LjE2IChpMzg2LXVua25vd24t ZnJlZWJzZCksIA0KQ29weXJpZ2h0IDE5OTYgRnJlZSBTb2Z0d2FyZSBGb3Vu ZGF0aW9uLCBJbmMuLi4NCklkbGVQVEQgMWMyMDAwDQpjdXJyZW50IHBjYiBh dCAxYTkwNzANCnBhbmljOiBiaW9kb25lOiBidWZmZXIgbm90IGJ1c3kNCiMw ICBib290IChob3d0bz0yNjApIGF0IC4uLy4uL2tlcm4va2Vybl9zaHV0ZG93 bi5jOjI2Ng0KMjY2CQkJCQlkdW1wcGNiLnBjYl9jcjMgPSByY3IzKCk7DQoo a2dkYikgd2hlcmUNCiMwICBib290IChob3d0bz0yNjApIGF0IC4uLy4uL2tl cm4va2Vybl9zaHV0ZG93bi5jOjI2Ng0KIzEgIDB4ZjAxMGVjNzIgaW4gcGFu aWMgKGZtdD0weGYwMTI5NWI1ICJiaW9kb25lOiBidWZmZXIgbm90IGJ1c3ki KQ0KICAgIGF0IC4uLy4uL2tlcm4va2Vybl9zaHV0ZG93bi5jOjM5MA0KIzIg IDB4ZjAxMjk3MWMgaW4gYmlvZG9uZSAoYnA9MHhmMzY5Yzg1YykgYXQgLi4v Li4va2Vybi92ZnNfYmlvLmM6MTU1Nw0KIzMgIDB4ZjAxNTRlMWMgaW4gc2Nz aV9kb25lICh4cz0weGYxNmVjMTAwKSBhdCAuLi8uLi9zY3NpL3Njc2lfYmFz ZS5jOjQ0OQ0KIzQgIDB4ZjAxOTZkNDEgaW4gYWhjX2RvbmUgKGFoYz0weGYx NjY5ODAwLCBzY2I9MHhmMTY2YWFhMCkNCiAgICBhdCAuLi8uLi9pMzg2L3Nj c2kvYWljN3h4eC5jOjE5NDQNCiM1ICAweGYwMTk0N2M3IGluIGFoY19pbnRy IChhcmc9MHhmMTY2OTgwMCkgYXQgLi4vLi4vaTM4Ni9zY3NpL2FpYzd4eHgu Yzo4MTQNCiM2ICAweGYwMTk4OGVhIGluIGFoY190aW1lb3V0IChhcmc9MHhm MTY2YWE0MCkNCiAgICBhdCAuLi8uLi9pMzg2L3Njc2kvYWljN3h4eC5jOjI4 ODINCiM3ICAweGYwMTA2NjVjIGluIHNvZnRjbG9jayAoKSBhdCAuLi8uLi9r ZXJuL2tlcm5fY2xvY2suYzo3MTUNCiM4ICAweGYwMTc2YWQ3IGluIGRvcmV0 aV9zd2kgKCkNCiM5ICAweGYwMTI5NTYzIGluIGJpb3dhaXQgKGJwPTB4ZjM2 ZTJlMjQpIGF0IC4uLy4uL2tlcm4vdmZzX2Jpby5jOjE1MzINCiMxMCAweGYw MTI3OTFmIGluIGJyZWFkICh2cD0weGYxNjliMjAwLCBibGtubz0zOTMyNDQ4 LCBzaXplPTgxOTIsIGNyZWQ9MHgwLCANCiAgICBicHA9MHhlZmJmZmRmNCkg YXQgLi4vLi4va2Vybi92ZnNfYmlvLmM6MjQ0DQojMTEgMHhmMDE1YzNmZiBp biBmZnNfdXBkYXRlIChhcD0weGVmYmZmZTIwKSBhdCAuLi8uLi91ZnMvZmZz L2Zmc19pbm9kZS5jOjEzNw0KIzEyIDB4ZjAxNWZhZjAgaW4gZmZzX2ZzeW5j IChhcD0weGVmYmZmZTY0KSBhdCB2bm9kZV9pZi5oOjEwMzENCiMxMyAweGYw MTVlNzMwIGluIGZmc19zeW5jIChtcD0weGYxNmI1ZTAwLCB3YWl0Zm9yPTIs IGNyZWQ9MHhmMTAyNGE4MCwgDQogICAgcD0weGYwMWI1ZmQwKSBhdCB2bm9k ZV9pZi5oOjQwNw0KIzE0IDB4ZjAxMmU4YTcgaW4gc3luYyAocD0weGYwMWI1 ZmQwLCB1YXA9MHgwLCByZXR2YWw9MHgwKQ0KICAgIGF0IC4uLy4uL2tlcm4v dmZzX3N5c2NhbGxzLmM6MzYwDQojMTUgMHhmMDEwZTg3ZCBpbiBib290ICho b3d0bz0yNTYpIGF0IC4uLy4uL2tlcm4va2Vybl9zaHV0ZG93bi5jOjE5OQ0K IzE2IDB4ZjAxMGVjNzIgaW4gcGFuaWMgKGZtdD0weGYwMTI5NWI1ICJiaW9k b25lOiBidWZmZXIgbm90IGJ1c3kiKQ0KICAgIGF0IC4uLy4uL2tlcm4va2Vy bl9zaHV0ZG93bi5jOjM5MA0KIzE3IDB4ZjAxMjk3MWMgaW4gYmlvZG9uZSAo YnA9MHhmMzZmNzU5MCkgYXQgLi4vLi4va2Vybi92ZnNfYmlvLmM6MTU1Nw0K IzE4IDB4ZjAxNTRlMWMgaW4gc2NzaV9kb25lICh4cz0weGYxNmVmZjgwKSBh dCAuLi8uLi9zY3NpL3Njc2lfYmFzZS5jOjQ0OQ0KIzE5IDB4ZjAxOTZkNDEg aW4gYWhjX2RvbmUgKGFoYz0weGYxNjY5ODAwLCBzY2I9MHhmMTY2YWE0MCkN CiAgICBhdCAuLi8uLi9pMzg2L3Njc2kvYWljN3h4eC5jOjE5NDQNCiMyMCAw eGYwMTk0N2M3IGluIGFoY19pbnRyIChhcmc9MHhmMTY2OTgwMCkgYXQgLi4v Li4vaTM4Ni9zY3NpL2FpYzd4eHguYzo4MTQNCiMyMSAweDJlZWZkIGluID8/ ICgpDQojMjIgMHgyZDViMiBpbiA/PyAoKQ0KIzIzIDB4MzliNiBpbiA/PyAo KQ0KIzI0IDB4MTZhOCBpbiA/PyAoKQ0KIzI1IDB4MTA5NiBpbiA/PyAoKQ0K KGtnZGIpIHVwDQojMSAgMHhmMDEwZWM3MiBpbiBwYW5pYyAoZm10PTB4ZjAx Mjk1YjUgImJpb2RvbmU6IGJ1ZmZlciBub3QgYnVzeSIpDQogICAgYXQgLi4v Li4va2Vybi9rZXJuX3NodXRkb3duLmM6MzkwDQozOTAJCWJvb3QoYm9vdG9w dCk7DQooa2dkYikgdXANCiMyICAweGYwMTI5NzFjIGluIGJpb2RvbmUgKGJw PTB4ZjM2OWM4NWMpIGF0IC4uLy4uL2tlcm4vdmZzX2Jpby5jOjE1NTcNCjE1 NTcJCQlwYW5pYygiYmlvZG9uZTogYnVmZmVyIG5vdCBidXN5Iik7DQooa2dk YikgbGlzdA0KMTU1Mgl7DQoxNTUzCQlpbnQgczsNCjE1NTQJDQoxNTU1CQlz ID0gc3BsYmlvKCk7DQoxNTU2CQlpZiAoIShicC0+Yl9mbGFncyAmIEJfQlVT WSkpDQoxNTU3CQkJcGFuaWMoImJpb2RvbmU6IGJ1ZmZlciBub3QgYnVzeSIp Ow0KMTU1OAkNCjE1NTkJCWlmIChicC0+Yl9mbGFncyAmIEJfRE9ORSkgew0K MTU2MAkJCXNwbHgocyk7DQoxNTYxCQkJcHJpbnRmKCJiaW9kb25lOiBidWZm ZXIgYWxyZWFkeSBkb25lXG4iKTsNCihrZ2RiKSB1cA0KIzMgIDB4ZjAxNTRl MWMgaW4gc2NzaV9kb25lICh4cz0weGYxNmVjMTAwKSBhdCAuLi8uLi9zY3Np L3Njc2lfYmFzZS5jOjQ0OQ0KNDQ5CQliaW9kb25lKGJwKTsNCihrZ2RiKSBs aXN0DQo0NDQJCQl9DQo0NDUJCQl4cy0+ZmxhZ3MgfD0gSVRTRE9ORTsNCjQ0 NgkJfQ0KNDQ3CQ0KNDQ4CQlmcmVlX3hzKHhzLCBzY19saW5rLCBTQ1NJX05P U0xFRVApOyAvKiBkb2VzIGEgc3RhcnQgaWYgbmVlZGVkICovDQo0NDkJCWJp b2RvbmUoYnApOw0KNDUwCX0NCjQ1MQkNCjQ1MgkvKg0KNDUzCSAqIGFzayB0 aGUgc2NzaSBkcml2ZXIgdG8gcGVyZm9ybSBhIGNvbW1hbmQgZm9yIHVzLg0K KGtnZGIpIHF1aXQNCiMgXkQICGV4aXQNCg0KU2NyaXB0IGRvbmUgb24gU3Vu IE1hciAyOSAxNjozMjo0NyAxOTk4DQoNCg== --0-1369468618-891207615=:1536 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=config Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: bWFjaGluZQkJImkzODYiDQojY3B1CQkiSTQ4Nl9DUFUiDQpjcHUJCSJJNTg2 X0NQVSINCmlkZW50CQlodWJfb3JnDQptYXh1c2VycwkxMjgNCg0Kb3B0aW9u cwkJIkNISUxEX01BWD0xMjgiDQpvcHRpb25zCQkiT1BFTl9NQVg9MTI4Ig0K DQpjb25maWcJCWtlcm5lbAlyb290IG9uIHdkMA0KDQpvcHRpb25zCQkiTUFY TUVNPSgxMjgqMTAyNCkiDQpvcHRpb25zCQkiTUFYRFNJWj0oMjU2VUwqMTAy NCoxMDI0KSINCm9wdGlvbnMJCSJDT01QQVRfNDMiDQpvcHRpb25zCQlTWVNW U0hNDQpvcHRpb25zCQlTWVNWU0VNDQpvcHRpb25zCQlTWVNWTVNHDQojb3B0 aW9ucwkiU0hNU0VHPTEyOCINCiNvcHRpb25zCSJTSE1NQVhQR1M9NDA5NiIN Cm9wdGlvbnMJCUlORVQJCQkjSW50ZXJuZXQgY29tbXVuaWNhdGlvbnMgcHJv dG9jb2xzDQpvcHRpb25zCQlGRlMJCQkjRmFzdCBmaWxlc3lzdGVtDQpvcHRp b25zCQlQUk9DRlMJCQkjUHJvY2VzcyBmaWxlc3lzdGVtDQpvcHRpb25zCQlR VU9UQQkJCSNlbmFibGUgZGlzayBxdW90YXMNCm9wdGlvbnMgICAgICAgICBO U1dBUERFVj0xMA0KDQpwc2V1ZG8tZGV2aWNlCWV0aGVyCQkJI0dlbmVyaWMg RXRoZXJuZXQNCnBzZXVkby1kZXZpY2UJbG9vcAkJCSNOZXR3b3JrIGxvb3Bi YWNrIGRldmljZQ0KcHNldWRvLWRldmljZQlicGZpbHRlcgk0CSNCZXJrZWxl eSBwYWNrZXQgZmlsdGVyDQpwc2V1ZG8tZGV2aWNlCXB0eQk2NAkjUHNldWRv IHR0eXMgLSBjYW4gZ28gYXMgaGlnaCBhcyA2NA0KcHNldWRvLWRldmljZQls b2cJCSNLZXJuZWwgc3lzbG9nIGludGVyZmFjZSAoL2Rldi9rbG9nKQ0KcHNl dWRvLWRldmljZSAgIGNjZCAgICAgOCAgICAgICAjQ29uY2F0ZW5hdGVkIGRp c2sgZHJpdmVyDQoNCmNvbnRyb2xsZXIJaXNhMA0KDQojY29udHJvbGxlcglh aGEwCWF0IGlzYT8gcG9ydCAiSU9fQUhBMCIgYmlvIGlycSA/IGRycSA1IHZl Y3RvciBhaGFpbnRyDQpjb250cm9sbGVyCXNjYnVzMAkjYmFzZSBTQ1NJIGNv ZGUNCmRldmljZQkJc2QwCSNTQ1NJIGRpc2tzDQoNCmRldmljZQkJc2MwCWF0 IGlzYT8gcG9ydCAiSU9fS0JEIiB0dHkgaXJxIDEgdmVjdG9yIHNjaW50cg0K DQpkZXZpY2UJCW5weDAJYXQgaXNhPyBwb3J0ICJJT19OUFgiIGlycSAxMyB2 ZWN0b3IgbnB4aW50cg0KY29udHJvbGxlcglmZGMwCWF0IGlzYT8gcG9ydCAi SU9fRkQxIiBiaW8gaXJxIDYgZHJxIDIgdmVjdG9yIGZkaW50cg0KZGlzawkJ ZmQwCWF0IGZkYzAgZHJpdmUgMA0KDQpvcHRpb25zICAgICAgICAgIkNNRDY0 MCIgICAgICAgICMgd29yayBhcm91bmQgQ01ENjQwIGNoaXAgZGVmaWNpZW5j eQ0KY29udHJvbGxlciAgICAgIHdkYzAgICAgYXQgaXNhPyBwb3J0ICJJT19X RDEiIGJpbyBpcnEgMTQgdmVjdG9yIHdkaW50cg0KZGlzayAgICAgICAgICAg IHdkMCAgICAgYXQgd2RjMCBkcml2ZSAwDQpkaXNrICAgICAgICAgICAgd2Qx ICAgICBhdCB3ZGMwIGRyaXZlIDENCg0KZGV2aWNlCQlzaW8wCWF0IGlzYT8g cG9ydCAiSU9fQ09NMSIgdHR5IGlycSA0IHZlY3RvciBzaW9pbnRyDQpkZXZp Y2UJCXNpbzEJYXQgaXNhPyBwb3J0ICJJT19DT00yIiB0dHkgaXJxIDMgdmVj dG9yIHNpb2ludHINCg0KZGV2aWNlIHZ4MA0KI2RldmljZSBlZDAgYXQgaXNh PyBwb3J0IDB4MjgwIG5ldCBpcnEgNSBpb21lbSAweGQ4MDAwIHZlY3RvciBl ZGludHINCg0KY29udHJvbGxlcglwY2kwDQpkZXZpY2UJCW5jcjANCg0KY29u dHJvbGxlcglhaGMwDQojb3B0aW9ucyBBSENfU0NCUEFHSU5HX0VOQUJMRQ0K b3B0aW9ucyBBSENfVEFHRU5BQkxFDQpvcHRpb25zIEFIQ19BTExPV19NRU1J Tw0KDQo= --0-1369468618-891207615=:1536-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 29 20:42:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02365 for freebsd-scsi-outgoing; Sun, 29 Mar 1998 20:42:11 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from garlic.acadiau.ca (root@garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA02176 for ; Sun, 29 Mar 1998 20:41:42 -0800 (PST) (envelope-from marc@acadiau.ca) Received: from iceberg (iceberg [131.162.2.91]) by garlic.acadiau.ca (8.8.5/8.8.5) with SMTP id AAA15246 for ; Mon, 30 Mar 1998 00:41:00 -0400 (AST) Date: Mon, 30 Mar 1998 00:41:33 -0400 (AST) From: Marc Fournier X-Sender: marc@iceberg To: freebsd-scsi@FreeBSD.ORG Subject: Adaptec 2940UW causing system hangs... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Morning... I'm slowly going through some of the more recent discussions in the archives about the 2940 controllers, and there seems to be alot of 'theories' bouncing around about reducing the transfer rate from 20Mps to 10Mps, in order to eliminate the problem. 2 questions ... 1. doesn't that defeat the point of UW? 2. *where* is the problem? our drivers or the controller themselves? I'm going to downgrade mine to 10Mps tomorrow when someone gets to the office, but it seems me that this would defeat the purpose of *using* UW if its too much to handle :( Thanks... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 29 21:21:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10550 for freebsd-scsi-outgoing; Sun, 29 Mar 1998 21:21:06 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fddi.Simon-Shapiro.ORG [206.190.148.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA10541 for ; Sun, 29 Mar 1998 21:21:03 -0800 (PST) (envelope-from shimon@simon-shapiro.org) Received: (qmail 21734 invoked from network); 29 Mar 1998 22:23:31 -0000 Received: from localhost.simon-shapiro.org (HELO sendero-fxp0.simon-shapiro.org) (@127.0.0.1) by localhost.simon-shapiro.org with SMTP; 29 Mar 1998 22:23:31 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-032398 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199803292124.OAA02989@panzer.plutotech.com> Date: Sun, 29 Mar 1998 14:23:31 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: "Kenneth D. Merry" Subject: Re: SDT-7000 and other DDS-2 tapes Cc: semen@iclub.nsu.ru, FreeBSD-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 29-Mar-98 Kenneth D. Merry wrote: > Simon Shapiro wrote... >> >> On 25-Mar-98 Kenneth D. Merry wrote: >> > Simon Shapiro wrote... >> >> >> >> On 25-Mar-98 Ustimenko Semen wrote: >> >> > >> >> > Have somebody succesfuly used SDT-7000 under FreeBSD? >> >> >> >> Yes. Two of them in shared mode on a DPT controller. >> > >> > What do you mean by "in shared mode"? >> >> I use most of my SCSI devices on a shared bus between two FreeBSD boxes. >> Part of the (still developing) High Availability Server I am working on. > > Interesting indeed. You might be interested to know that the CAM > tape driver does a reserve unit on open, so any other initiators on the bus > won't be able to muck with the drive when one initiator has it open. (of > course, it cancels the reservation at final close) Great, but the DPT controller does that in the firmware already. I cannot wait to move the driver to CAM, but no time so far :-( If you have (something I asked Justin for :-) a list of API routines the CAM produces ( a brief ``what it does'' will be great!), and entry points expected of a driver, you will xut my development time by a week or two. ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 29 22:17:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22165 for freebsd-scsi-outgoing; Sun, 29 Mar 1998 22:17:07 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22156 for ; Sun, 29 Mar 1998 22:17:02 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id XAA26368; Sun, 29 Mar 1998 23:12:13 -0700 (MST) Date: Sun, 29 Mar 1998 23:12:13 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199803300612.XAA26368@narnia.plutotech.com> To: Marc Fournier cc: scsi@FreeBSD.ORG Subject: Re: Adaptec 2940UW causing system hangs... Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 2. *where* is the problem? our drivers or the controller > themselves? UW transfer speeds should work just fine. My guess is that you are running into one of the many bugs that CAM fixes, so maybe you should consider trying it. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 29 22:51:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28590 for freebsd-scsi-outgoing; Sun, 29 Mar 1998 22:51:11 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from our.domaintje.com (our.domaintje.com [194.178.252.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA28582 for ; Sun, 29 Mar 1998 22:51:06 -0800 (PST) (envelope-from frank@our.domaintje.com) Received: from frank@localhost by our.domaintje.com id <8343-182>; Mon, 30 Mar 1998 08:50:45 +0200 Message-ID: <19980330085037.40435@domaintje.com> Date: Mon, 30 Mar 1998 08:50:37 +0200 From: Frank Ederveen To: Marc Fournier , freebsd-scsi@FreeBSD.ORG Subject: Re: Adaptec 2940UW causing system hangs... References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Marc Fournier on Mon, Mar 30, 1998 at 12:41:33AM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Mar 30, 1998 at 12:41:33AM -0400, Marc Fournier wrote: > I'm slowly going through some of the more recent discussions in > the archives about the 2940 controllers, and there seems to be alot of > 'theories' bouncing around about reducing the transfer rate from 20Mps to > 10Mps, in order to eliminate the problem. We run several machines with 3940UW, which I think is just the same chips, without any problems. One machine handles our news peering and has over 100G of traffic a day. 7 disks bouncing around happily day after day.. Never had it crash. It runs 2.2.5-STABLE of Jan 31st. As soon as cam and softupdates are released for 2.2.6 were going to upgrade it. Oh goody, that'd be fun =) Just wanted to let people know someone is _not_ having problems. Regards, Frank Ederveen UUnet-NL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 29 23:07:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00628 for freebsd-scsi-outgoing; Sun, 29 Mar 1998 23:07:15 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA00623 for ; Sun, 29 Mar 1998 23:07:12 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yJYFZ-0000tU-00; Sun, 29 Mar 1998 22:40:53 -0800 Date: Sun, 29 Mar 1998 22:40:52 -0800 (PST) From: Tom To: Marc Fournier cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Adaptec 2940UW causing system hangs... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 30 Mar 1998, Marc Fournier wrote: > I'm slowly going through some of the more recent discussions in > the archives about the 2940 controllers, and there seems to be alot of > 'theories' bouncing around about reducing the transfer rate from 20Mps to > 10Mps, in order to eliminate the problem. > > 2 questions ... > > 1. doesn't that defeat the point of UW? Yes. > 2. *where* is the problem? our drivers or the controller > themselves? Driver + drives. The driver isn't as robust as it could be. If it sees funny stuff on the SCSI bus, it acts similarily :( Picking high-quality UW drives helps a _lot_. Seagate Barracuda 4XL/4LP work wonders. The Seagate Hawks are supposed to be good too. I'm now Quantum-free after our last Quantum died! Still no failures with the Barracuda 4LP or 4XL drives. > I'm going to downgrade mine to 10Mps tomorrow when someone gets to > the office, but it seems me that this would defeat the purpose of *using* > UW if its too much to handle :( Slowing the bus can prevent bus problems that are freaking out the controller. You also might as well check the cable. For real UW applications, don't use that cheap plastic coated ribben cable you get for $5. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 30 04:12:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA23516 for freebsd-scsi-outgoing; Mon, 30 Mar 1998 04:12:19 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from wankers.net (root@host-209-138-26-203.ATL.BELLSOUTH.net [209.138.26.203]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA23489; Mon, 30 Mar 1998 04:12:08 -0800 (PST) (envelope-from dex@wankers.net) Received: from localhost (dex@localhost [127.0.0.1]) by wankers.net (8.8.8/8.8.7) with SMTP id HAA11309; Mon, 30 Mar 1998 07:10:18 -0500 (EST) (envelope-from dex@wankers.net) Date: Mon, 30 Mar 1998 07:10:17 -0500 (EST) From: Dexnation Holodream X-Sender: dex@localhost To: Marc Fournier cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Adaptec 2940UW with two ?? UW drives... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org the 2940UW is a great controller. I have a system that (up to this point) has NEVER crashed. I've run 2.2.5-STABLE and 2.2.6-STABLE on it. My longest uptime was 51 days, 15:31, and that's cause I got really lazy about cvsup, and decided to see how long it would stay up...and then they went and released 2.2.6... here are a few questions for you to answer: 1) can you repeatedly connect to it (but not get a login prompt) 2) how long do you wait for the prompt 3) what is the machine doing 4) do you have any sort of firewall between you and the box 5) what are the loads on the box 6) are there any in.telnetd.core files 7) are there any login.core files 8) what minor release are you running (2, 5, or 6) -Jon On Mon, 30 Mar 1998, Marc Fournier wrote: > > Morning... > > Well, tonight, my #$^%#@%@ FreeBSD system is locked up > solid...again. It's pretty much a daily occurance now, and I'm at a loss > as to what to try next. > > I just put in a brand new 2940UW controller, with two UW drives > (I'd tell you which, except I can't get to the system right now), and > there is an IDE drive as the root drive for it... > > Symptom: if I telnet to the machine, I get: > > telnet hub.org > Trying 209.47.148.200... > Connected to hub.org. > Escape character is '^]'. > > And it just sits there... > > At one persons suggestion, I've disabled SCBPAGING, but that > apparently hasn't helped any... > > I'm running 2.2-STABLE on that machine right now, and reported a > problem this morning with a panic: biodone... error message. > > I'm slowly going through the mailing list search engines, and get > the feeling that the 2940 controllers might not be a "good pick" as far as > controllers are concerned :( > > Thoughts? > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 30 04:49:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA28067 for freebsd-scsi-outgoing; Mon, 30 Mar 1998 04:49:12 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from garlic.acadiau.ca (root@garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA28062 for ; Mon, 30 Mar 1998 04:49:09 -0800 (PST) (envelope-from marc@acadiau.ca) Received: from iceberg (iceberg [131.162.2.91]) by garlic.acadiau.ca (8.8.5/8.8.5) with SMTP id IAA26612; Mon, 30 Mar 1998 08:48:15 -0400 (AST) Date: Mon, 30 Mar 1998 08:48:46 -0400 (AST) From: Marc Fournier X-Sender: marc@iceberg To: "Justin T. Gibbs" cc: scsi@FreeBSD.ORG Subject: Re: Adaptec 2940UW causing system hangs... In-Reply-To: <199803300612.XAA26368@narnia.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 29 Mar 1998, Justin T. Gibbs wrote: > > 2. *where* is the problem? our drivers or the controller > > themselves? > > UW transfer speeds should work just fine. My guess is that you are > running into one of the many bugs that CAM fixes, so maybe you should > consider trying it. On a production machine, with me 2500kilometers away? :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 30 04:55:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA28581 for freebsd-scsi-outgoing; Mon, 30 Mar 1998 04:55:06 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from garlic.acadiau.ca (root@garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA28562; Mon, 30 Mar 1998 04:55:01 -0800 (PST) (envelope-from marc@acadiau.ca) Received: from iceberg (iceberg [131.162.2.91]) by garlic.acadiau.ca (8.8.5/8.8.5) with SMTP id IAA27252; Mon, 30 Mar 1998 08:53:59 -0400 (AST) Date: Mon, 30 Mar 1998 08:54:30 -0400 (AST) From: Marc Fournier X-Sender: marc@iceberg To: Dexnation Holodream cc: Marc Fournier , freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Adaptec 2940UW with two ?? UW drives... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 30 Mar 1998, Dexnation Holodream wrote: > the 2940UW is a great controller. I have a system that (up to this point) > has NEVER crashed. I've run 2.2.5-STABLE and 2.2.6-STABLE on it. My > longest uptime was 51 days, 15:31, and that's cause I got really lazy > about cvsup, and decided to see how long it would stay up...and then they > went and released 2.2.6... > > here are a few questions for you to answer: > > 1) can you repeatedly connect to it (but not get a login prompt) Yes... > 2) how long do you wait for the prompt An hour? > 3) what is the machine doing Not sure what you mean here, but its the CVSup server for PostgreSQL, news feeder/peer to 29 other hosts, WWW server for several domains, only a couple being high traffic... > 4) do you have any sort of firewall between you and the box No... > 5) what are the loads on the box Negligible, as far as I know, but I wasn't watching that at the time :( > 6) are there any in.telnetd.core files Have to check when it comes back up, but I don't think so... > 7) are there any login.core files Same as 6... > 8) what minor release are you running (2, 5, or 6) Whatever 2.2-STABLE is as of two days ago... > > -Jon > > On Mon, 30 Mar 1998, Marc Fournier wrote: > > > > > Morning... > > > > Well, tonight, my #$^%#@%@ FreeBSD system is locked up > > solid...again. It's pretty much a daily occurance now, and I'm at a loss > > as to what to try next. > > > > I just put in a brand new 2940UW controller, with two UW drives > > (I'd tell you which, except I can't get to the system right now), and > > there is an IDE drive as the root drive for it... > > > > Symptom: if I telnet to the machine, I get: > > > > telnet hub.org > > Trying 209.47.148.200... > > Connected to hub.org. > > Escape character is '^]'. > > > > And it just sits there... > > > > At one persons suggestion, I've disabled SCBPAGING, but that > > apparently hasn't helped any... > > > > I'm running 2.2-STABLE on that machine right now, and reported a > > problem this morning with a panic: biodone... error message. > > > > I'm slowly going through the mailing list search engines, and get > > the feeling that the 2940 controllers might not be a "good pick" as far as > > controllers are concerned :( > > > > Thoughts? > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 30 04:55:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA28721 for freebsd-scsi-outgoing; Mon, 30 Mar 1998 04:55:14 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from garlic.acadiau.ca (root@garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA28683 for ; Mon, 30 Mar 1998 04:55:11 -0800 (PST) (envelope-from marc@acadiau.ca) Received: from iceberg (iceberg [131.162.2.91]) by garlic.acadiau.ca (8.8.5/8.8.5) with SMTP id IAA27304; Mon, 30 Mar 1998 08:54:32 -0400 (AST) Date: Mon, 30 Mar 1998 08:55:03 -0400 (AST) From: Marc Fournier X-Sender: marc@iceberg cc: "Justin T. Gibbs" , scsi@FreeBSD.ORG Subject: Re: Adaptec 2940UW causing system hangs... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 30 Mar 1998, Marc Fournier wrote: > On Sun, 29 Mar 1998, Justin T. Gibbs wrote: > > > > 2. *where* is the problem? our drivers or the controller > > > themselves? > > > > UW transfer speeds should work just fine. My guess is that you are > > running into one of the many bugs that CAM fixes, so maybe you should > > consider trying it. > > On a production machine, with me 2500kilometers away? :) But...were I so foolish, what would this involve? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 30 05:29:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA02844 for freebsd-scsi-outgoing; Mon, 30 Mar 1998 05:29:08 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from org.chem.msu.su (org.chem.msu.su [158.250.32.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA01474 for ; Mon, 30 Mar 1998 05:21:15 -0800 (PST) (envelope-from genie@qsar.chem.msu.su) Received: from org-qsar2.chem.msu.su (org-qsar2.chem.msu.su [158.250.48.99]) by org.chem.msu.su (8.8.7/8.8.5) with SMTP id RAA22476 for ; Mon, 30 Mar 1998 17:20:37 +0400 (MSD) Message-ID: <01ad01bd5bde$a8868f20$6330fa9e@org-qsar2.chem.msu.su> From: "Eugene Radchenko" To: Subject: Timeout while idle, again Date: Mon, 30 Mar 1998 17:20:35 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi people! I wonder what exactly do the following errors mean (my machine hangs once in a while during backup). This seems rather common common condition, although I could find no definitive fix on the list archive. Is it tape drive, disk, driver(s) or what? "Timeout while idle" reminds the unlearned me of "Please immediately pay $0.00" ;-)) {sorry for the long log} Thanks in advance Genie --- ######################################################### Eugene V. Radchenko Research associate, Computer Chemistry E-mail: genie@qsar.chem.msu.su http://org.chem.msu.su/~genie =================================================== "There are now new criminals out there that don't have guns. They have computers and many have other weapons of mass destruction." -- Janet Reno, Attorney General of the United States >>>Feb 22 04:31:46 org /kernel: st0(ahc0:3:0): SCB 0x5 - timed out while >idle, LASTPHASE == 0x1, SCSISIGI == 0x0 >>>Feb 22 04:31:46 org /kernel: SEQADDR = 0x9 SCSISEQ = 0x12 SSTAT0 = 0x5 >>SSTAT1 = 0xa >>>Feb 22 04:31:46 org /kernel: st0(ahc0:3:0): Queueing an Abort SCB >>>Feb 22 04:31:46 org /kernel: st0(ahc0:3:0): Abort Message Sent >>>Feb 22 04:31:46 org /kernel: st0(ahc0:3:0): SCB 5 - Abort Completed. >>>Feb 22 04:31:46 org /kernel: st0(ahc0:3:0): no longer in timeout >>>Feb 22 04:33:26 org /kernel: st0(ahc0:3:0): SCB 0x1 - timed out while >idle, LASTPHASE == 0x1, SCSISIGI == 0x0 >>>Feb 22 04:33:26 org /kernel: SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x5 >>SSTAT1 = 0xa >>>Feb 22 04:33:26 org /kernel: st0(ahc0:3:0): Queueing an Abort SCB >>>Feb 22 04:33:26 org /kernel: st0(ahc0:3:0): Abort Message Sent >>>Feb 22 04:33:26 org /kernel: st0(ahc0:3:0): SCB 1 - Abort Completed. >>>Feb 22 04:33:26 org /kernel: st0(ahc0:3:0): no longer in timeout >>>Feb 22 04:33:31 org /kernel: st0(ahc0:3:0): SCB 0x1 - timed out while >idle, LASTPHASE == 0x1, SCSISIGI == 0x0 >>>Feb 22 04:33:31 org /kernel: SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x5 >>SSTAT1 = 0xa >>>Feb 22 04:33:31 org /kernel: st0(ahc0:3:0): Queueing an Abort SCB >>>Feb 22 04:33:31 org /kernel: st0(ahc0:3:0): Abort Message Sent >>>Feb 22 04:33:31 org /kernel: st0(ahc0:3:0): SCB 1 - Abort Completed. >>>Feb 22 04:33:31 org /kernel: st0(ahc0:3:0): no longer in timeout >>>Feb 22 04:33:36 org /kernel: st0(ahc0:3:0): SCB 0x1 - timed out while >idle, LASTPHASE == 0x1, SCSISIGI == 0x0 >>>Feb 22 04:33:36 org /kernel: SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x5 >>SSTAT1 = 0xa >>>Feb 22 04:33:36 org /kernel: st0(ahc0:3:0): Queueing an Abort SCB >>>Feb 22 04:33:36 org /kernel: st0(ahc0:3:0): Abort Message Sent >>>Feb 22 04:33:36 org /kernel: st0(ahc0:3:0): SCB 1 - Abort Completed. >>>Feb 22 04:33:36 org /kernel: st0(ahc0:3:0): no longer in timeout >>>Feb 22 04:33:41 org /kernel: st0(ahc0:3:0): SCB 0x1 - timed out while >idle, LASTPHASE == 0x1, SCSISIGI == 0x0 >>>Feb 22 04:33:41 org /kernel: SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x5 >>SSTAT1 = 0xa >>>Feb 22 04:33:41 org /kernel: st0(ahc0:3:0): Queueing an Abort SCB >>>Feb 22 04:33:41 org /kernel: st0(ahc0:3:0): Abort Message Sent >>>Feb 22 04:33:41 org /kernel: st0(ahc0:3:0): SCB 1 - Abort Completed. >>>Feb 22 04:33:41 org /kernel: st0(ahc0:3:0): no longer in timeout >>>Feb 23 10:56:31 org /kernel: Copyright (c) 1992-1997 FreeBSD Inc. >Feb 23 10:56:31 org /kernel: Copyright (c) 1992-1997 FreeBSD Inc. >Feb 23 10:56:31 org /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 >Feb 23 10:56:31 org /kernel: The Regents of the University of California. >All rights reserved. >Feb 23 10:56:31 org /kernel: >Feb 23 10:56:31 org /kernel: FreeBSD 2.2.2-RELEASE #0: Sat Dec 20 17:26:00 >MSK 1997 >Feb 23 10:56:32 org /kernel: >genie@org.chem.msu.su:/usr/src/sys/compile/ORG >Feb 23 10:56:32 org /kernel: CPU: Pentium (99.47-MHz 586-class CPU) >Feb 23 10:56:32 org /kernel: Origin = "GenuineIntel" Id = 0x525 >Stepping=5 >Feb 23 10:56:32 org /kernel: >Features=0x1bf >Feb 23 10:56:32 org /kernel: real memory = 16777216 (16384K bytes) >Feb 23 10:56:32 org /kernel: Physical memory hole(s): >Feb 23 10:56:32 org /kernel: avail memory = 14901248 (14552K bytes) >Feb 23 10:56:32 org /kernel: Probing for devices on PCI bus 0: >Feb 23 10:56:32 org /kernel: chip0 controller> rev 1 on pci0:0 >Feb 23 10:56:32 org /kernel: chip1 rev 2 on >pci0:7:0 >Feb 23 10:56:32 org /kernel: chip2 rev 2 on >pci0:7:1 >Feb 23 10:56:32 org /kernel: vga0 rev 0 int >a irq 11 on pci0:14 >Feb 23 10:56:32 org /kernel: ahc0 rev >0 int a irq 9 on pci0:15 >Feb 23 10:56:32 org /kernel: ahc0: aic7880 Single Channel, SCSI Id=7, 16/255 >SCBs >Feb 23 10:56:32 org /kernel: ahc0 waiting for scsi devices to settle >Feb 23 10:56:32 org /kernel: ahc0: target 0 Tagged Queuing Device >Feb 23 10:56:32 org /kernel: (ahc0:0:0): "SEAGATE ST31230N 0510" type 0 >fixed SCSI 2 >Feb 23 10:56:32 org /kernel: sd0(ahc0:0:0): Direct-Access 1010MB (2069860 >512 byte sectors) >Feb 23 10:56:32 org /kernel: sd0(ahc0:0:0): with 3992 cyls, 5 heads, and an >average 103 sectors/track >Feb 23 10:56:32 org /kernel: ahc0: target 1 Tagged Queuing Device >Feb 23 10:56:32 org /kernel: (ahc0:1:0): "SEAGATE ST31230N 0510" type 0 >fixed SCSI 2 >Feb 23 10:56:32 org /kernel: sd1(ahc0:1:0): Direct-Access 1010MB (2069860 >512 byte sectors) >Feb 23 10:56:33 org /kernel: sd1(ahc0:1:0): with 3992 cyls, 5 heads, and an >average 103 sectors/track >Feb 23 10:56:33 org /kernel: (ahc0:3:0): "HP C1533A 9503" type 1 removable >SCSI 2 >Feb 23 10:56:33 org /kernel: st0(ahc0:3:0): Sequential-Access density code >0x24, variable blocks, write-enabled >Feb 23 10:56:33 org /kernel: (ahc0:5:0): "TOSHIBA CD-ROM XM-5701TA 0167" >type 5 removable SCSI 2 >Feb 23 10:56:33 org /kernel: cd0(ahc0:5:0): CD-ROM can't get the size >Feb 23 10:56:33 org /kernel: Probing for devices on the ISA bus: >Feb 23 10:56:33 org /kernel: sc0 at 0x60-0x6f irq 1 on motherboard >Feb 23 10:56:33 org /kernel: sc0: VGA color <4 virtual consoles, flags=0x0> >Feb 23 10:56:33 org /kernel: ed0 at 0x240-0x25f irq 5 maddr 0xd8000 msize >8192 on isa >Feb 23 10:56:33 org /kernel: ed0: address 00:00:c0:45:4f:ce, type >SMC8416C/SMC8416BT (16 bit) >Feb 23 10:56:33 org /kernel: ed1 at 0x300-0x31f irq 10 on isa >Feb 23 10:56:33 org /kernel: ed1: address 00:40:05:23:46:50, type NE2000 (16 >bit) >Feb 23 10:56:33 org /kernel: ed2 at 0x320-0x33f irq 12 on isa >Feb 23 10:56:33 org /kernel: ed2: address 00:00:01:23:67:59, type NE2000 (16 >bit) >Feb 23 10:56:33 org /kernel: ed3 at 0x340-0x35f irq 14 on isa >Feb 23 10:56:33 org /kernel: ed3: address 00:40:05:23:46:4f, type NE2000 (16 >bit) >Feb 23 10:56:33 org /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa >Feb 23 10:56:33 org /kernel: sio0: type 16550A >Feb 23 10:56:33 org /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa >Feb 23 10:56:33 org /kernel: sio1: type 16550A >Feb 23 10:56:33 org /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa >Feb 23 10:56:33 org /kernel: fdc0: NEC 72065B >Feb 23 10:56:34 org /kernel: fd0: 1.44MB 3.5in >Feb 23 10:56:34 org /kernel: npx0 on motherboard >Feb 23 10:56:34 org /kernel: npx0: INT 16 interface To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 30 05:36:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA03762 for freebsd-scsi-outgoing; Mon, 30 Mar 1998 05:36:22 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from garlic.acadiau.ca (root@garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA03751 for ; Mon, 30 Mar 1998 05:36:17 -0800 (PST) (envelope-from marc@acadiau.ca) Received: from iceberg (iceberg [131.162.2.91]) by garlic.acadiau.ca (8.8.5/8.8.5) with SMTP id JAA01685 for ; Mon, 30 Mar 1998 09:35:40 -0400 (AST) Date: Mon, 30 Mar 1998 09:36:11 -0400 (AST) From: Marc Fournier X-Sender: marc@iceberg To: freebsd-scsi@FreeBSD.ORG Subject: CAM and 2.2-STABLE... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi... It was suggested that I try out CAM to reduce (eliminate) my current SCSI problems, and I just read the README file for it, and was wondering if there was an ETA on the availability of a 2.2 patch for it? A few weeks? Days? Already exists? Thanks... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 30 06:01:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA06455 for freebsd-scsi-outgoing; Mon, 30 Mar 1998 06:01:07 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA06450 for ; Mon, 30 Mar 1998 06:01:05 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA26332 (5.67b/IDA-1.5 for FreeBSD-scsi@FreeBSD.ORG); Mon, 30 Mar 1998 16:00:41 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.7/8.6.12) id QAA00666; Mon, 30 Mar 1998 16:03:33 +0200 (MET DST) From: Wilko Bulte Message-Id: <199803301403.QAA00666@yedi.iaf.nl> Subject: Re: SDT-7000 and other DDS-2 tapes In-Reply-To: from Simon Shapiro at "Mar 29, 98 01:30:04 pm" To: shimon@simon-shapiro.org Date: Mon, 30 Mar 1998 16:03:33 +0200 (MET DST) Cc: ken@plutotech.com, FreeBSD-scsi@FreeBSD.ORG, semen@iclub.nsu.ru X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL32 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Simon Shapiro wrote... > > On 25-Mar-98 Kenneth D. Merry wrote: > > Simon Shapiro wrote... > >> > >> On 25-Mar-98 Ustimenko Semen wrote: > >> > > >> > Have somebody succesfuly used SDT-7000 under FreeBSD? > >> > >> Yes. Two of them in shared mode on a DPT controller. > > > > What do you mean by "in shared mode"? > > I use most of my SCSI devices on a shared bus between two FreeBSD boxes. Hairy... One machine booting most likely result in a bus reset, with the tape loosing position. You could get lucky and find an adapter that allows disabling bus resets. > Part of the (still developing) High Availability Server I am working on. _ ______________________________________________________________________ | / o / / _ Bulte email: wilko @ yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW: http://www.tcja.nl -------------------------------------------------- Powered by FreeBSD ------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 30 08:54:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01322 for freebsd-scsi-outgoing; Mon, 30 Mar 1998 08:54:45 -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 IAA01317 for ; Mon, 30 Mar 1998 08:54:43 -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 JAA06074; Mon, 30 Mar 1998 09:53:30 -0700 (MST) Message-Id: <199803301653.JAA06074@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: Marc Fournier cc: "Justin T. Gibbs" , scsi@FreeBSD.ORG Subject: Re: Adaptec 2940UW causing system hangs... In-reply-to: Your message of "Mon, 30 Mar 1998 08:48:46 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 30 Mar 1998 09:50:03 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >On Sun, 29 Mar 1998, Justin T. Gibbs wrote: > >> > 2. *where* is the problem? our drivers or the controller >> > themselves? >> >> UW transfer speeds should work just fine. My guess is that you are >> running into one of the many bugs that CAM fixes, so maybe you should >> consider trying it. > > On a production machine, with me 2500kilometers away? :) Wcarchive is at least a 1000 miles away from where David lives. 8-) To put it another way, the code you are running now doesn't seem to work for you, so why not try something else? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 30 08:57:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01542 for freebsd-scsi-outgoing; Mon, 30 Mar 1998 08:57:03 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01537 for ; Mon, 30 Mar 1998 08:57:01 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with SMTP id LAA16305; Mon, 30 Mar 1998 11:56:56 -0500 (EST) Date: Mon, 30 Mar 1998 11:56:55 -0500 (EST) From: The Hermit Hacker To: "Justin T. Gibbs" cc: scsi@FreeBSD.ORG Subject: Re: Adaptec 2940UW causing system hangs... In-Reply-To: <199803301653.JAA06074@pluto.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 30 Mar 1998, Justin T. Gibbs wrote: > >On Sun, 29 Mar 1998, Justin T. Gibbs wrote: > > > >> > 2. *where* is the problem? our drivers or the controller > >> > themselves? > >> > >> UW transfer speeds should work just fine. My guess is that you are > >> running into one of the many bugs that CAM fixes, so maybe you should > >> consider trying it. > > > > On a production machine, with me 2500kilometers away? :) > > Wcarchive is at least a 1000 miles away from where David lives. 8-) That's 10hrs closer by car? *grin* > To put it another way, the code you are running now doesn't seem to > work for you, so why not try something else? Actually, I thought about it afterwards and figure what the hell...but, I checked the README file, and there is nothing available for 2.2 yet (even though Wcarchive is running it)...where can I get it for 2.2-STABLE? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 30 10:25:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17673 for freebsd-scsi-outgoing; Mon, 30 Mar 1998 10:25:02 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17668 for ; Mon, 30 Mar 1998 10:25:00 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id LAA28310; Mon, 30 Mar 1998 11:20:39 -0700 (MST) Date: Mon, 30 Mar 1998 11:20:39 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199803301820.LAA28310@narnia.plutotech.com> To: Wilko Bulte cc: scsi@FreeBSD.ORG Subject: Re: SDT-7000 and other DDS-2 tapes Newsgroups: pluto.freebsd.scsi In-Reply-To: <199803301403.QAA00666@yedi.iaf.nl> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> I use most of my SCSI devices on a shared bus between two FreeBSD boxes. > > Hairy... One machine booting most likely result in a bus reset, with the > tape loosing position. You could get lucky and find an adapter that allows > disabling bus resets. I've always wondered if this is something the tape driver could recover from. I guess if the tape driver is recording partion, FM, and block count as it writes and the target drive allows block level repositioning that it could recover. Do all tape drives lose their position on a reset? How many support the soft reset alternative? I guess it's time to do some experimentation. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 30 10:42:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19238 for freebsd-scsi-outgoing; Mon, 30 Mar 1998 10:42:34 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral.com (root@[209.54.254.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19233 for ; Mon, 30 Mar 1998 10:42:33 -0800 (PST) (envelope-from mjacob@feral.com) Received: from feral-gw (mjacob@gw100.feral.com [192.67.166.129]) by feral.com (8.8.6/8.8.6) with SMTP id KAA01911; Mon, 30 Mar 1998 10:41:46 -0800 Message-ID: <351FE76A.5778EA38@feral.com> Date: Mon, 30 Mar 1998 10:41:46 -0800 From: Matthew Jacob Organization: Feral Software X-Mailer: Mozilla 3.04 (X11; I; Linux 2.0.33 i586) MIME-Version: 1.0 To: "Justin T. Gibbs" CC: Wilko Bulte , scsi@FreeBSD.ORG Subject: Re: SDT-7000 and other DDS-2 tapes References: <199803301820.LAA28310@narnia.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T. Gibbs wrote: > > > I've always wondered if this is something the tape driver could recover > from. I guess if the tape driver is recording partion, FM, and block > count as it writes and the target drive allows block level repositioning > that it could recover. Do all tape drives lose their position on a > reset? How many support the soft reset alternative? I guess it's time > to do some experimentation. Only attempt this if the tape is being read. Even then, it's iffy. It depends really on whether, during reset conditions, you can really believe the tape in the drive is the same one you had. My take is that this is not something that the driver layer should do. This is something that a higher level should ascertain, since only it has knowledge of the information encoding. I would strenuosly argue that it'd better to figure out a much more robust error return mechanism (something a la r/w -> EIO (error state latches) -> MTIOCGETERR, releases latch returns error associated with EIO | -> rw, error message to console, releases latch ) and fix the utilities to deal with this (and the filesystems to deal with similar for removable media disk like devices). Drivers that attempt to be too smart can often lead to data destruction and application termination. I cannot think of a surer route to condemning the OS this happens on than going this way. (This issue has been bandied about at Sun very hotly over the last month or so) -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 30 10:50:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21235 for freebsd-scsi-outgoing; Mon, 30 Mar 1998 10:50:38 -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 KAA21189 for ; Mon, 30 Mar 1998 10:50:29 -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 LAA12168; Mon, 30 Mar 1998 11:50:09 -0700 (MST) Message-Id: <199803301850.LAA12168@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: Matthew Jacob cc: "Justin T. Gibbs" , Wilko Bulte , scsi@FreeBSD.ORG Subject: Re: SDT-7000 and other DDS-2 tapes In-reply-to: Your message of "Mon, 30 Mar 1998 10:41:46 PST." <351FE76A.5778EA38@feral.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 30 Mar 1998 11:46:42 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Only attempt this if the tape is being read. Even then, it's >iffy. It depends really on whether, during reset conditions, you >can really believe the tape in the drive is the same one you >had. As CAM gives you an async notification when a bus reset occurs, you do know that the upcoming UA is for a bus reset, not a power on or media change event. >My take is that this is not something that the driver >layer should do. This is something that a higher level should >ascertain, since only it has knowledge of the information >encoding. I don't understand why the encoding is relevant. The tape peripheral, at least in CAM, can guarantee transaction ordering to the device even across an error condition. Regardless of the information encoding if the sequence of filemarks and blocks laid out on the tape match that of the requesting program (or in the case of reads, the returned data exactly matches what was written on the tape), there can be no confusion. >I would strenuosly argue that it'd better to figure >out a much more robust error return mechanism (something a la > > r/w -> EIO (error state latches) > > -> MTIOCGETERR, releases latch returns > error associated with EIO > | -> rw, error message to console, releases latch I believe that SGI has something like this that allows you to pull the last position, EOF, EOT, EOM flags, etc. I don't recall what they call it though. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 30 12:04:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08237 for freebsd-scsi-outgoing; Mon, 30 Mar 1998 12:04:39 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fddi.Simon-Shapiro.ORG [206.190.148.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA08208 for ; Mon, 30 Mar 1998 12:04:32 -0800 (PST) (envelope-from shimon@simon-shapiro.org) Received: (qmail 3162 invoked from network); 30 Mar 1998 20:13:44 -0000 Received: from localhost.simon-shapiro.org (HELO sendero-fxp0.simon-shapiro.org) (@127.0.0.1) by localhost.simon-shapiro.org with SMTP; 30 Mar 1998 20:13:44 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-032398 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199803301403.QAA00666@yedi.iaf.nl> Date: Mon, 30 Mar 1998 12:13:44 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Wilko Bulte Subject: Re: SDT-7000 and other DDS-2 tapes Cc: semen@iclub.nsu.ru, FreeBSD-scsi@FreeBSD.ORG, ken@plutotech.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 30-Mar-98 Wilko Bulte wrote: ... > Hairy... One machine booting most likely result in a bus reset, with the > tape loosing position. You could get lucky and find an adapter that > allows disabling bus resets. The DPT does that. Works like a champ. ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 30 12:50:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18813 for freebsd-scsi-outgoing; Mon, 30 Mar 1998 12:50:42 -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 MAA18686 for ; Mon, 30 Mar 1998 12:50:13 -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 NAA17743; Mon, 30 Mar 1998 13:47:04 -0700 (MST) Message-Id: <199803302047.NAA17743@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: Marc Fournier cc: "Justin T. Gibbs" , scsi@FreeBSD.ORG Subject: Re: Adaptec 2940UW causing system hangs... In-reply-to: Your message of "Mon, 30 Mar 1998 08:55:03 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 30 Mar 1998 13:43:37 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > But...were I so foolish, what would this involve? I'm working on a new 2.2-stable port, but it won't be ready for a few more days. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 30 12:59:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21280 for freebsd-scsi-outgoing; Mon, 30 Mar 1998 12:59:23 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21275 for ; Mon, 30 Mar 1998 12:59:20 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with SMTP id PAA20422; Mon, 30 Mar 1998 15:58:05 -0500 (EST) Date: Mon, 30 Mar 1998 15:58:00 -0500 (EST) From: The Hermit Hacker To: "Justin T. Gibbs" cc: Marc Fournier , scsi@FreeBSD.ORG Subject: Re: Adaptec 2940UW causing system hangs... In-Reply-To: <199803302047.NAA17743@pluto.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 30 Mar 1998, Justin T. Gibbs wrote: > > But...were I so foolish, what would this involve? > > I'm working on a new 2.2-stable port, but it won't be ready for > a few more days. No probs...its been doing this for a week now, I can live another couple of days :) Thanks... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 30 13:38:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27498 for freebsd-scsi-outgoing; Mon, 30 Mar 1998 13:38:39 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA27491 for ; Mon, 30 Mar 1998 13:38:33 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA23302 (5.67b/IDA-1.5 for scsi@FreeBSD.ORG); Mon, 30 Mar 1998 23:38:22 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.7/8.6.12) id WAA04292; Mon, 30 Mar 1998 22:07:35 +0200 (MET DST) From: Wilko Bulte Message-Id: <199803302007.WAA04292@yedi.iaf.nl> Subject: Re: SDT-7000 and other DDS-2 tapes In-Reply-To: <199803301820.LAA28310@narnia.plutotech.com> from "Justin T. Gibbs" at "Mar 30, 98 11:20:39 am" To: gibbs@narnia.plutotech.com (Justin T. Gibbs) Date: Mon, 30 Mar 1998 22:07:35 +0200 (MET DST) Cc: scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL32 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Justin T. Gibbs wrote... > >> I use most of my SCSI devices on a shared bus between two FreeBSD boxes. > > > > Hairy... One machine booting most likely result in a bus reset, with the > > tape loosing position. You could get lucky and find an adapter that allows > > disabling bus resets. > > I've always wondered if this is something the tape driver could recover > from. I guess if the tape driver is recording partion, FM, and block > count as it writes and the target drive allows block level repositioning > that it could recover. Do all tape drives lose their position on a > reset? How many support the soft reset alternative? I guess it's time > to do some experimentation. You are at the mercy of the device firmware. You don't want to. Some tapes rewind on a bus reset etc. I know that DEC NSR (Legato Networker rebranded) can now handle tapes on a shared bus in a Digital Unix cluster. AFAIK they indeed keep track of where they were on the tape. When a bus reset occurs a rewind follows and then a reposition to the spot they were before. NSR is picky on what devices it wants to support. Most/all (?) of them are either DLT or DLT loaders. Please note: I'm not an NSR expert by any means.. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko @ yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW: http://www.tcja.nl -------------------------------------------------- Powered by FreeBSD ------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 31 15:45:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28693 for freebsd-scsi-outgoing; Tue, 31 Mar 1998 15:45:23 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA28654 for ; Tue, 31 Mar 1998 15:45:20 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yKAKI-0002jJ-00; Tue, 31 Mar 1998 15:20:18 -0800 Date: Tue, 31 Mar 1998 15:20:17 -0800 (PST) From: Tom To: freebsd-scsi@FreeBSD.ORG Subject: DPT PM334UW & 440LX -> no boot? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've heard that the 440LX chipset stomps on the BIOS on the DPT PM33UW causing booting to fail? Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 1 01:50:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25462 for freebsd-scsi-outgoing; Wed, 1 Apr 1998 01:50:09 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA25368 for ; Wed, 1 Apr 1998 01:49:52 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: (from mishania@localhost) by skraldespand.demos.su (8.8.8/D) id NAA04525; Wed, 1 Apr 1998 13:48:54 +0400 (MSD) Posted-Date: Wed, 1 Apr 1998 13:48:54 +0400 (MSD) Message-ID: <19980401134854.42119@demos.su> Date: Wed, 1 Apr 1998 13:48:54 +0400 From: "Mikhail A. Sokolov" To: Tom Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: DPT PM334UW & 440LX -> no boot? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from Tom on Tue, Mar 31, 1998 at 03:20:17PM -0800 Organization: Demos Company, Ltd., Moscow, Russian Federation. X-Point-of-View: Gravity is myth, - the earth sucks. X-Useless-Header: Look ma! It's a # sign! Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Mar 31, 1998 at 03:20:17PM -0800, Tom wrote: # # I've heard that the 440LX chipset stomps on the BIOS on the DPT PM33UW # causing booting to fail? The beast is known to behave when DPT gets 10th IRQ. I.e. check BIOS/ move the card in different slots. Still, irq 10'th can be easily shared with some other hardware then. # Tom # # To Unsubscribe: send mail to majordomo@FreeBSD.org # with "unsubscribe freebsd-scsi" in the body of the message -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 1 09:23:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09281 for freebsd-scsi-outgoing; Wed, 1 Apr 1998 09:23:55 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fddi.Simon-Shapiro.ORG [206.190.148.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA09146 for ; Wed, 1 Apr 1998 09:23:15 -0800 (PST) (envelope-from shimon@simon-shapiro.org) Received: (qmail 1023 invoked from network); 1 Apr 1998 17:32:00 -0000 Received: from localhost.simon-shapiro.org (HELO sendero-fxp0.simon-shapiro.org) (@127.0.0.1) by localhost.simon-shapiro.org with SMTP; 1 Apr 1998 17:32:00 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-032998 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 01 Apr 1998 09:31:59 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Tom Subject: RE: DPT PM334UW & 440LX -> no boot? Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 31-Mar-98 Tom wrote: > > I've heard that the 440LX chipset stomps on the BIOS on the DPT PM33UW > causing booting to fail? On some motherboards. DPT is working on a solution and we will have it as soon as they give it to me. Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 1 09:47:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14166 for freebsd-scsi-outgoing; Wed, 1 Apr 1998 09:47:18 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA14161 for ; Wed, 1 Apr 1998 09:47:15 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yKRD4-0003aD-00; Wed, 1 Apr 1998 09:21:58 -0800 Date: Wed, 1 Apr 1998 09:21:57 -0800 (PST) From: Tom To: "Mikhail A. Sokolov" cc: freebsd-scsi@FreeBSD.ORG Subject: Re: DPT PM334UW & 440LX -> no boot? In-Reply-To: <19980401134854.42119@demos.su> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 1 Apr 1998, Mikhail A. Sokolov wrote: > On Tue, Mar 31, 1998 at 03:20:17PM -0800, Tom wrote: > # > # I've heard that the 440LX chipset stomps on the BIOS on the DPT PM33UW > # causing booting to fail? > > The beast is known to behave when DPT gets 10th IRQ. I.e. check BIOS/ > move the card in different slots. > > Still, irq 10'th can be easily shared with some other hardware then. So the chipset only stomps on the DPT controller if it _not_ on IRQ10? What motherboard have you done this with? Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 1 09:48:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14476 for freebsd-scsi-outgoing; Wed, 1 Apr 1998 09:48:37 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA14455 for ; Wed, 1 Apr 1998 09:48:33 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yKRBs-0003a0-00; Wed, 1 Apr 1998 09:20:44 -0800 Date: Wed, 1 Apr 1998 09:20:43 -0800 (PST) From: Tom To: Simon Shapiro cc: freebsd-scsi@FreeBSD.ORG Subject: RE: DPT PM334UW & 440LX -> no boot? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 1 Apr 1998, Simon Shapiro wrote: > On 31-Mar-98 Tom wrote: > > > > I've heard that the 440LX chipset stomps on the BIOS on the DPT PM33UW > > causing booting to fail? > > On some motherboards. DPT is working on a solution and we will have it as > soon as they give it to me. So in other words, this work around will need to be done in the DPT driver? I would think that if the chipset is at fault, that you would need a firmware upgrade from the motherboard vendor? I guess the ASUS P2L97 is one of the affected motherboards? > Simon Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 1 10:11:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18687 for freebsd-scsi-outgoing; Wed, 1 Apr 1998 10:11:47 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fddi.Simon-Shapiro.ORG [206.190.148.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA18464 for ; Wed, 1 Apr 1998 10:10:35 -0800 (PST) (envelope-from shimon@simon-shapiro.org) Received: (qmail 2052 invoked from network); 1 Apr 1998 18:18:53 -0000 Received: from localhost.simon-shapiro.org (HELO sendero-fxp0.simon-shapiro.org) (@127.0.0.1) by localhost.simon-shapiro.org with SMTP; 1 Apr 1998 18:18:53 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-032998 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 01 Apr 1998 10:18:53 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Tom Subject: RE: DPT PM334UW & 440LX -> no boot? Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 01-Apr-98 Tom wrote: > > On Wed, 1 Apr 1998, Simon Shapiro wrote: > >> On 31-Mar-98 Tom wrote: >> > >> > I've heard that the 440LX chipset stomps on the BIOS on the DPT >> > PM33UW >> > causing booting to fail? >> >> On some motherboards. DPT is working on a solution and we will have it >> as >> soon as they give it to me. > > So in other words, this work around will need to be done in the DPT > driver? I would think that if the chipset is at fault, that you would > need a firmware upgrade from the motherboard vendor? Firmware upgrade will be one definite part of the solution. We may need to do something ugly in the driver, if the solution will have something to do with the DMA engine on the card. > I guess the ASUS P2L97 is one of the affected motherboards? I am not sure. Better ask DPT support. ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 1 11:28:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01096 for freebsd-scsi-outgoing; Wed, 1 Apr 1998 11:28:19 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01088; Wed, 1 Apr 1998 11:28:09 -0800 (PST) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.7/8.8.7) id VAA02535; Wed, 1 Apr 1998 21:30:03 +0200 (MEST) (envelope-from kuku) Date: Wed, 1 Apr 1998 21:30:03 +0200 (MEST) From: Christoph Kukulies Message-Id: <199804011930.VAA02535@gilberto.physik.RWTH-Aachen.DE> To: freebsd-ports@freefall.FreeBSD.org, freebsd-scsi@FreeBSD.ORG Subject: graphics/sane scanner frontend Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The sane (0.61) port is marked BROKEN. it says it doesn't link against our gtk. Since I'm running gimp/gtk the very latest it seems that sane-0.71 could be made working with little effort. I compiled and linked everything and there were only some minor nits: 1\ sanei/sanei_ab306.c: static __inline__ void outb (u_char value, u_long port) { __asm__ __volatile__ ("outb %0,%1" : : "a" (value), "d" ((u_short) port)); } ^ ^ parens missing (I'm not sure whether putting parens there changes something but I believe not) 2\ patch-01/patch-02 applied by hand. 3\ sanei/sanei_scsi.c: #if USE == BSD_INTERFACE # ifndef HAVE_SCSIREQ_ENTER <<<<<< this is defined in config.h static int scsireq_enter (int fd, scsireq_t *hdr) { return ioctl (fd, SCIOCCOMMAND, hdr); } # endif /* !HAVE_SCSIREQ_ENTER */ resulting later in scsireq_enter not being found. I don't know too much about the scsi library that I can tell whether the above substitution is allowed. undefining HAVE_SCSIREQ_ENTER gets it compiled and linked. Now the harder part: What is this libtool horror? This seems to me the greatest mess since Bill Gates invented the DLL. Anyway, seems we have to live with that. But libtool all the time says something about a buggy linker and finally the front- and backends do not get correctly installed. The wrapper /usr/local/bin/xscanimage doesn't find the binary in /usr/local/bin/.libs. Is the port maintainer co-reading? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 1 16:59:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16629 for freebsd-scsi-outgoing; Wed, 1 Apr 1998 16:59:30 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16614 for ; Wed, 1 Apr 1998 16:59:23 -0800 (PST) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.8.8/8.8.8) id TAA02037 for freebsd-scsi@freebsd.org; Wed, 1 Apr 1998 19:58:48 -0500 (EST) (envelope-from larry) Message-ID: <19980401195843.39444@marso.com> Date: Wed, 1 Apr 1998 19:58:43 -0500 From: "Larry S. Marso" To: freebsd-scsi@FreeBSD.ORG Subject: /dev/pt0 causes lockup Mail-Followup-To: freebsd-scsi@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i x-no-archive: yes Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm running 3.0 current. I use an Adaptec 1505. To the scsi card I've attached an Iomega Jazz drive and a HP 6100cse scanner. The Jazz drive works great! However any attempt whatsoever to access the scanner causes an immediate, complete **lock-up** of my system. No warnings of any kind; it just freezes over. (I have tried sane, xvscan and hpscan). My kernel contains: controller scbus0 at aic0 # Single bus device device sd0 device pt0 at scbus? My /dev/directory contains: crw------- 1 root wheel 61, 0 Apr 1 19:07 pt0 crw------- 1 root wheel 61, 0x20000000 Apr 1 19:07 pt0.ctl and lrwxrwxrwx 1 root wheel 8 Apr 1 13:34 scanjet@ -> /dev/pt0 lrwxrwxrwx 1 root wheel 8 Apr 1 18:51 scanner@ -> /dev/pt0 During boot-up, I get the following: Apr 1 19:06:20 lsmarso /kernel: aic0 at 0x140-0x15f irq 9 on isa Apr 1 19:06:20 lsmarso /kernel: aic0: waiting for scsi devices to settle Apr 1 19:06:20 lsmarso /kernel: scbus0 at aic0 bus 0 Apr 1 19:06:20 lsmarso /kernel: sd0 at scbus0 target 4 lun 0 Apr 1 19:06:20 lsmarso /kernel: sd0: type 0 removable SCSI 2 Apr 1 19:06:21 lsmarso /kernel: sd0: Direct-Access Apr 1 19:06:21 lsmarso /kernel: sd0: ILLEGAL REQUEST asc:24,0 Invalid field in CDB Apr 1 19:06:21 lsmarso /kernel: sd0 could not mode sense (4). Using ficticious geometry Apr 1 19:06:21 lsmarso /kernel: 1021MB (2091050 512 byte sectors) Apr 1 19:06:21 lsmarso /kernel: pt0 at scbus0 target 5 lun 0 Apr 1 19:06:21 lsmarso /kernel: pt0: type 3 fixed SCSI 2 Apr 1 19:06:21 lsmarso /kernel: pt0: Processor Hmmmm. It looks OK to me... Any suggestions, as to what next steps I should take to diagnose and solve the problem? (If the next step is, "buy an Adaptec 2940", I guess I can live with that ... if someone can vouch that this is probably the issue). Best regards -- Larry S. Marso larry@marso.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 2 00:52:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00989 for freebsd-scsi-outgoing; Thu, 2 Apr 1998 00:52:48 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from TomQNX.tomqnx.com (ott-pm6-16.comnet.ca [206.75.140.176]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00984 for ; Thu, 2 Apr 1998 00:52:46 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m0yKfi9-00086WC; Thu, 2 Apr 1998 03:51:01 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: Weird SCSI timeout problem To: freebsd-scsi@FreeBSD.ORG Date: Thu, 2 Apr 1998 03:51:01 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mar. 8/98 I reported problems with the trio of old HP drives I had installed on my Adaptec 2740A. They were basically "timed out in message out phase" and "timed out while idle" while the drives were VERY busy. Someone who was having similar problems advised me to remove the various AHC performance options. This did seem to eliminate the symptoms and some system performance as well. FYI: By reducing the maximum xfer rate for the problem drives by 20%, I have been able to re-enable all the AHC options with no problems experienced during the past couple of weeks. Regards, Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 2 02:58:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA20346 for freebsd-scsi-outgoing; Thu, 2 Apr 1998 02:58:58 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA20338 for ; Thu, 2 Apr 1998 02:58:53 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id FAA12944; Thu, 2 Apr 1998 05:56:43 -0500 (EST) From: Peter Dufault Message-Id: <199804021056.FAA12944@hda.hda.com> Subject: Re: /dev/pt0 causes lockup In-Reply-To: <19980401195843.39444@marso.com> from "Larry S. Marso" at "Apr 1, 98 07:58:43 pm" To: larry@marso.com (Larry S. Marso) Date: Thu, 2 Apr 1998 05:56:42 -0500 (EST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm running 3.0 current. I use an Adaptec 1505. To the scsi card I've > attached an Iomega Jazz drive and a HP 6100cse scanner... Is the infamous "But it works in Windows" true, implying at least low performance bus integrity? Have you tried turning on debugging on the SCSI device and seen how far it is getting? Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 2 08:01:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04917 for freebsd-scsi-outgoing; Thu, 2 Apr 1998 08:01:34 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA04890 for ; Thu, 2 Apr 1998 08:01:31 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: (from mishania@localhost) by skraldespand.demos.su (8.8.8/D) id UAA02121; Thu, 2 Apr 1998 20:00:30 +0400 (MSD) Posted-Date: Thu, 2 Apr 1998 20:00:30 +0400 (MSD) Message-ID: <19980402200029.11402@demos.su> Date: Thu, 2 Apr 1998 20:00:29 +0400 From: "Mikhail A. Sokolov" To: Tom Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: DPT PM334UW & 440LX -> no boot? References: <19980401134854.42119@demos.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from Tom on Wed, Apr 01, 1998 at 09:21:57AM -0800 Organization: Demos Company, Ltd., Moscow, Russian Federation. X-Point-of-View: Gravity is myth, - the earth sucks. X-Useless-Header: Look ma! It's a # sign! Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Apr 01, 1998 at 09:21:57AM -0800, Tom wrote: # # On Wed, 1 Apr 1998, Mikhail A. Sokolov wrote: # # > On Tue, Mar 31, 1998 at 03:20:17PM -0800, Tom wrote: # > # # > # I've heard that the 440LX chipset stomps on the BIOS on the DPT PM33UW # > # causing booting to fail? # > # > The beast is known to behave when DPT gets 10th IRQ. I.e. check BIOS/ # > move the card in different slots. # > # > Still, irq 10'th can be easily shared with some other hardware then. # # So the chipset only stomps on the DPT controller if it _not_ on IRQ10? # # What motherboard have you done this with? Redwood (Intel). However, Simon's reply is much more informative. # # Tom -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 3 00:04:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16104 for freebsd-scsi-outgoing; Fri, 3 Apr 1998 00:04:00 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from hslrswi.hasler.ascom.ch (hslrswi.hasler.ascom.ch [139.79.129.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16098 for ; Fri, 3 Apr 1998 00:03:57 -0800 (PST) (envelope-from nbladt@autelca.ascom.ch) Received: from autelca.ascom.ch (aut.autelca.ascom.ch [136.232.4.1]) by hslrswi.hasler.ascom.ch (8.8.7/8.8.7) with SMTP id KAA12268 for ; Fri, 3 Apr 1998 10:03:55 +0200 (MET DST) Received: from sabg20.autelca.ascom.ch ([136.232.135.5]) by autelca.ascom.ch (4.1/SMI-4.1) id AA16681; Fri, 3 Apr 98 10:03:53 +0200 Received: from sun113 by sabg20.autelca.ascom.ch (SMI-8.6/SMI-SVR4) id KAA07508; Fri, 3 Apr 1998 10:03:46 +0200 Message-Id: <35249871.67BE@autelca.ascom.ch> Date: Fri, 03 Apr 1998 10:06:09 +0200 From: Norbert Bladt X-Mailer: Mozilla 3.01 (X11; I; SunOS 5.5.1 sun4m) Mime-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: FBSD 2.2.5 Release: Problem with ahc0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello everyone ! I have a problem booting (and, of course, installing) FreeBSD 2.2.5 on the following hardware: Unisys EISA system with 3COM 3C579 Etherlink III controller (is detected) Adaptec 2740 (twin channel) SCSI controller (is detected, too) 32 MB Ram P5/60 CPU 2 serial 1 parallel ATI Graphics Ultra Pro graphic board with 2 MB of VRAM Quantum Fireball 2.1 GB disk (is found during SCSI bus scan) Toshiba CD-ROM (special Sun version, is found, too) All seems to be fine, i.e. all the hardware is detected, etc. However after showing npx0: INT 16 interface a message ahc0: brkadrint, Illegal Host access at seqaddr = 0x0 appears on the console and that's it. It doesn't matter whether the external Toshiba CD-ROM mentioned above is connected or not. The behaviour is exactly the same. The system will not proceed any further. For what it's worth: This system did run with FreeBSD 1.1.5 years ago. It would be very nice to get some help from you SCSI-experts. Thanks in advance Norbert Bladt. -- Norbert Bladt Payphone Management System Software Development ascom Autelca AG Worbstrasse 201 CH-3073 Guemligen, Switzerland abladtn@autelca.ascom.ch VOICE: +41 31 999 6552, FAX: +41 31 999 6575 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 3 02:32:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12181 for freebsd-scsi-outgoing; Fri, 3 Apr 1998 02:32:33 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA12171 for ; Fri, 3 Apr 1998 02:32:25 -0800 (PST) (envelope-from semen@iclub.nsu.ru) Received: from localhost (semen@localhost) by iclub.nsu.ru (8.8.8/8.8.5) with SMTP id RAA11224 for ; Fri, 3 Apr 1998 17:34:40 +0700 (NSS) Date: Fri, 3 Apr 1998 17:34:40 +0700 (NSS) From: Ustimenko Semen To: freebsd-scsi@FreeBSD.ORG Subject: Strange not fatal messages from sd1 on ahc0 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello! I often get following messages: Apr 3 15:30:25 main /kernel: sd1(ahc0:2:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Apr 3 15:30:25 main /kernel: SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Apr 3 15:30:25 main /kernel: sd1(ahc0:2:0): Queueing an Abort SCB Apr 3 15:30:25 main /kernel: sd1(ahc0:2:0): Abort Message Sent Apr 3 15:30:25 main /kernel: sd1(ahc0:2:0): SCB 0 - Abort Completed. Apr 3 15:30:25 main /kernel: sd1(ahc0:2:0): no longer in timeout It lasts since i have added second SCSI drive (sd1). I haven't discovered any data loss, but it seems strange. Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.5-RELEASE #0: Sun Jan 25 15:53:46 NS 1998 denis@main:/usr/src/sys/compile/OLDHAM CPU: Pentium (166.19-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 62631936 (61164K bytes) Probing for devices on PCI bus 0: chip0 rev 1 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 vga0 rev 0 int a irq 9 on pci0:9 de0 rev 32 int a irq 12 on pci0:10 de0: SMC 9332BDT 21140A [10-100Mb/s] pass 2.0 de0: address 00:00:c0:25:d8:e8 de1 rev 32 int a irq 10 on pci0:11 de1: SMC 9332BDT 21140A [10-100Mb/s] pass 2.0 de1: address 00:00:c0:60:d7:e8 ahc0 rev 0 int a irq 11 on pci0:12 ahc0: aic7880 Single Channel, SCSI Id=7, 16 SCBs (ahc0:0:0): "FUJITSU M2954S-512 0155" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 4149MB (8498506 512 byte sectors) (ahc0:2:0): "FUJITSU M2954S-512 0122" type 0 fixed SCSI 2 sd1(ahc0:2:0): Direct-Access 4149MB (8498506 512 byte sectors) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 at 0x278-0x27f on isa mse0 not found at 0x23c fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 not found at 0x1f0 npx0 flags 0x1 on motherboard npx0: INT 16 interface changing root device to sd0a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 3 05:16:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA01655 for freebsd-scsi-outgoing; Fri, 3 Apr 1998 05:16:42 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA01645; Fri, 3 Apr 1998 05:16:38 -0800 (PST) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.8.8/8.8.8) id IAA21647; Fri, 3 Apr 1998 08:16:05 -0500 (EST) (envelope-from larry) Message-ID: <19980403081559.64189@marso.com> Date: Fri, 3 Apr 1998 08:15:59 -0500 From: "Larry S. Marso" To: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: scanner--*anyone* successful with FreeBSD? Mail-Followup-To: freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i x-no-archive: yes Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am wondering whether *anyone* has a scanner working in the FreeBSD environment, or if it's only a fool's (or a superlative hacker's) quest at the moment. I'm struggling with a brand-spanking new HP6100cse. My system utterly locks up whenever I access the scanner. Anytime I access /dev/pt0, using any of the software that supposedly supports hp scanners (commercial xvscan -- FreeBSD binaries or freshly compiled -- hpscan or sane 0.71), the *entire* system locks up. I'll give a little more info below ... but I'm mainly interested in learning whether this is a solvable problem in a reasonable time frame, or that I should return some of my recent equipment purchases while I still can. So, I ask again: is *anyone* using a scanner with 3.0-current? How about 2.2-? HP or other? /dev/pt0 or other? Best regards -- Larry S. Marso larry@marso.com ------------------------------------------------------------------------- Additional info: On my SERVER, which is a 486 with ISA bus, I use an adaptec 1520. Boot up messages seem fine: Apr 1 19:06:20 lsmarso /kernel: aic0 at 0x140-0x15f irq 9 on isa Apr 1 19:06:20 lsmarso /kernel: aic0: waiting for scsi devices to settle Apr 1 19:06:20 lsmarso /kernel: scbus0 at aic0 bus 0 Apr 1 19:06:20 lsmarso /kernel: sd0 at scbus0 target 4 lun 0 Apr 1 19:06:20 lsmarso /kernel: sd0: type 0 removable SCSI 2 Apr 1 19:06:21 lsmarso /kernel: sd0: Direct-Access Apr 1 19:06:21 lsmarso /kernel: sd0: ILLEGAL REQUEST asc:24,0 Invalid field in CDB Apr 1 19:06:21 lsmarso /kernel: sd0 could not mode sense (4). Using ficticious geometry Apr 1 19:06:21 lsmarso /kernel: 1021MB (2091050 512 byte sectors) Apr 1 19:06:21 lsmarso /kernel: pt0 at scbus0 target 5 lun 0 Apr 1 19:06:21 lsmarso /kernel: pt0: type 3 fixed SCSI 2 Apr 1 19:06:21 lsmarso /kernel: pt0: Processor By the way the jazz drive works great. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 3 06:01:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA07717 for freebsd-scsi-outgoing; Fri, 3 Apr 1998 06:01:01 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA07711 for ; Fri, 3 Apr 1998 06:00:57 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id IAA16102; Fri, 3 Apr 1998 08:58:39 -0500 (EST) From: Peter Dufault Message-Id: <199804031358.IAA16102@hda.hda.com> Subject: Re: scanner--*anyone* successful with FreeBSD? In-Reply-To: <19980403081559.64189@marso.com> from "Larry S. Marso" at "Apr 3, 98 08:15:59 am" To: larry@marso.com (Larry S. Marso) Date: Fri, 3 Apr 1998 08:58:38 -0500 (EST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I am wondering whether *anyone* has a scanner working in the FreeBSD > environment, or if it's only a fool's (or a superlative hacker's) quest > at the moment. I'm struggling with a brand-spanking new HP6100cse. > > My system utterly locks up whenever I access the scanner. Anytime I > access /dev/pt0, using any of the software that supposedly supports hp > scanners (commercial xvscan -- FreeBSD binaries or freshly compiled -- > hpscan or sane 0.71), the *entire* system locks up. Boot into single user mode. Enable debugging on /dev/pt0. Try to do a "dd" from it. See what happens. Or use a serial console with debugging enabled and your X based app. No one has gotten back to me on the patch I suggested earlier to make anything using the generic ioctls work. I'm enclosing it at the end. The patch doesn't hurt my system, but I'm not going to commit it without feedback from someone. My crash box doesn't even have SCSI on it. The patch to scsi_ioctl is for general goodness and isn't needed. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval diff -c -N -r /hosts/rt/sd1/A/dufault/posix4/current/usr/src/sys/kern/kern_physio.c /hosts/rt/sd1/A/dufault/posix4/new/usr/src/sys/kern/kern_physio.c *** /hosts/rt/sd1/A/dufault/posix4/current/usr/src/sys/kern/kern_physio.c Fri Jan 23 21:01:18 1998 --- /hosts/rt/sd1/A/dufault/posix4/new/usr/src/sys/kern/kern_physio.c Tue Mar 17 06:52:50 1998 *************** *** 178,184 **** if (bdsw && bdsw->d_maxio) { maxphys = bdsw->d_maxio; } ! if (bp->b_kvasize < maxphys) maxphys = bp->b_kvasize; if(((vm_offset_t) bp->b_data) & PAGE_MASK) { --- 178,184 ---- if (bdsw && bdsw->d_maxio) { maxphys = bdsw->d_maxio; } ! if (bp->b_kvasize && bp->b_kvasize < maxphys) maxphys = bp->b_kvasize; if(((vm_offset_t) bp->b_data) & PAGE_MASK) { diff -c -N -r /hosts/rt/sd1/A/dufault/posix4/current/usr/src/sys/scsi/scsi_ioctl.c /hosts/rt/sd1/A/dufault/posix4/new/usr/src/sys/scsi/scsi_ioctl.c *** /hosts/rt/sd1/A/dufault/posix4/current/usr/src/sys/scsi/scsi_ioctl.c Sun Feb 1 13:09:46 1998 --- /hosts/rt/sd1/A/dufault/posix4/new/usr/src/sys/scsi/scsi_ioctl.c Tue Mar 17 06:52:52 1998 *************** *** 286,293 **** screq = malloc(sizeof(scsireq_t),M_TEMP,M_WAITOK); bcopy(screq2,screq,sizeof(scsireq_t)); } ! bp = malloc(sizeof (struct buf),M_TEMP,M_WAITOK); ! bzero(bp,sizeof(struct buf)); d_addr = screq->databuf; bp->b_bcount = len = screq->datalen; bp->b_screq = screq; --- 286,292 ---- screq = malloc(sizeof(scsireq_t),M_TEMP,M_WAITOK); bcopy(screq2,screq,sizeof(scsireq_t)); } ! bp = getpbuf(); d_addr = screq->databuf; bp->b_bcount = len = screq->datalen; bp->b_screq = screq; *************** *** 321,327 **** scsistrategy(bp); ret = bp->b_error; } ! free(bp,M_TEMP); #if 0 /* XXX dufault@hda.com: This looks too rev dependent. Do it always? */ if((unsigned int)screq2 < (unsigned int)KERNBASE) #endif --- 320,326 ---- scsistrategy(bp); ret = bp->b_error; } ! relpbuf(bp); #if 0 /* XXX dufault@hda.com: This looks too rev dependent. Do it always? */ if((unsigned int)screq2 < (unsigned int)KERNBASE) #endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 3 11:50:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05103 for freebsd-scsi-outgoing; Fri, 3 Apr 1998 11:50:14 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from kaori.communique.net (kaori.communique.net [204.27.67.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05060 for ; Fri, 3 Apr 1998 11:50:04 -0800 (PST) (envelope-from rzig@verio.net) Received: by kaori.communique.net with Internet Mail Service (5.0.1458.49) id ; Fri, 3 Apr 1998 13:49:52 -0600 Message-ID: From: Raul Zighelboim To: "'shimon@simon-shapiro.org'" , Tom Cc: freebsd-scsi@FreeBSD.ORG Subject: RE: DPT PM334UW & 440LX -> no boot? Date: Fri, 3 Apr 1998 13:49:51 -0600 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just spoke with DPT support... they said that the problem is with the 440LX AND the phoenix bios. Motherboards with other bios _should_ not be affected. ================================================== Raul Zighelboim rzig@verio.net > -----Original Message----- > From: Simon Shapiro [SMTP:shimon@simon-shapiro.org] > Sent: Wednesday, April 01, 1998 12:19 PM > To: Tom > Cc: freebsd-scsi@FreeBSD.ORG > Subject: RE: DPT PM334UW & 440LX -> no boot? > > > On 01-Apr-98 Tom wrote: > > > > On Wed, 1 Apr 1998, Simon Shapiro wrote: > > > >> On 31-Mar-98 Tom wrote: > >> > > >> > I've heard that the 440LX chipset stomps on the BIOS on the DPT > >> > PM33UW > >> > causing booting to fail? > >> > >> On some motherboards. DPT is working on a solution and we will > have it > >> as > >> soon as they give it to me. > > > > So in other words, this work around will need to be done in the > DPT > > driver? I would think that if the chipset is at fault, that you > would > > need a firmware upgrade from the motherboard vendor? > > Firmware upgrade will be one definite part of the solution. We may > need to > do something ugly in the driver, if the solution will have something > to do > with the DMA engine on the card. > > > I guess the ASUS P2L97 is one of the affected motherboards? > > I am not sure. Better ask DPT support. > > ---------- > > > Sincerely Yours, > > Simon Shapiro > Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 3 12:37:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18226 for freebsd-scsi-outgoing; Fri, 3 Apr 1998 12:37:29 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA18205 for ; Fri, 3 Apr 1998 12:37:27 -0800 (PST) (envelope-from bkogawa@primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id NAA27902; Fri, 3 Apr 1998 13:37:22 -0700 (MST) Received: from ip202.sjc.primenet.com(206.165.96.202), claiming to be "foo.primenet.com" via SMTP by smtp04.primenet.com, id smtpd027859; Fri Apr 3 13:37:19 1998 Received: from localhost (bkogawa@localhost) by foo.primenet.com (8.8.8/8.8.6) with SMTP id MAA05168; Fri, 3 Apr 1998 12:37:47 -0800 (PST) X-Authentication-Warning: foo.primenet.com: bkogawa owned process doing -bs Date: Fri, 3 Apr 1998 12:37:46 -0800 (PST) From: "Bryan K. Ogawa" To: freebsd-scsi@FreeBSD.ORG cc: Malte Lance Subject: Will a termination problem cause total hangs? In-Reply-To: <3.0.32.19980403113026.007430fc@cyclone.degnet.baynet.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can a termination problem cause total kernel hangs? Right now, at least two of us on -questions are experiencing problems with total lockups (no pings) when in X, usually when using Netscape (in my case) or in heavy concurrent disk accesses (in Malte's case) on SCSI systems with a number of SCSI devices. (4 to 7). Malte has had success in reducing the hangs by changing the termination, and I'm wondering if the sorts of hangs we're looking at could be caused by termination problems. Both of us have Adaptec 2940UWs. Any ideas or suggestions? I had thought that a SCSI hung kernel would at least return pings? bryan k ogawa http://www.primenet.com/~bkogawa/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 3 12:57:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26468 for freebsd-scsi-outgoing; Fri, 3 Apr 1998 12:57:05 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26385; Fri, 3 Apr 1998 12:56:56 -0800 (PST) (envelope-from bkogawa@primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id NAA24716; Fri, 3 Apr 1998 13:56:52 -0700 (MST) Received: from ip202.sjc.primenet.com(206.165.96.202), claiming to be "foo.primenet.com" via SMTP by smtp01.primenet.com, id smtpd024691; Fri Apr 3 13:56:48 1998 Received: (from bkogawa@localhost) by foo.primenet.com (8.8.8/8.8.6) id MAA05610; Fri, 3 Apr 1998 12:57:16 -0800 (PST) Date: Fri, 3 Apr 1998 12:57:16 -0800 (PST) Message-Id: <199804032057.MAA05610@foo.primenet.com> To: larry@marso.com Subject: Re: scanner--*anyone* successful with FreeBSD? Newsgroups: localhost.freebsd.questions References: <19980403081559.64189@marso.com> From: "Bryan K. Ogawa" Cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG X-Newsreader: NN version 6.5.0 #1 (NOV) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In localhost.freebsd.questions you write: >So, I ask again: is *anyone* using a scanner with 3.0-current? How >about 2.2-? HP or other? /dev/pt0 or other? I have successfully scanned with a Microtek E3 on a BT-948 card using sane-0.67. sane-0.71 doesn't work for me, but it doesn't hang my system, either. I had a Adaptec 1505A (simpler than the 1520, but the same driver) but it would panic when I tried to scan with sane-0.67. It looks like it's just an unimplemented command so someone who had some actual knowledge about SCSI could probably fix it so that it would work. This is using /dev/uk0 , not /dev/pt0 , under 2.2-STABLE (pre 2.2.5). I suspect that sane-0.71 is doing things that aren't quite supported under FreeBSD for the Microtek, but I haven't had a chance to look at it. -- bryan k ogawa http://www.primenet.com/~bkogawa/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 3 14:15:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15525 for freebsd-scsi-outgoing; Fri, 3 Apr 1998 14:15:18 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15473 for ; Fri, 3 Apr 1998 14:15:10 -0800 (PST) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.8.8/8.8.8) id RAA19451; Fri, 3 Apr 1998 17:14:43 -0500 (EST) (envelope-from larry) Message-ID: <19980403171438.18492@marso.com> Date: Fri, 3 Apr 1998 17:14:38 -0500 From: "Larry S. Marso" To: "Bryan K. Ogawa" , freebsd-scsi@FreeBSD.ORG Subject: Re: Will a termination problem cause total hangs? Mail-Followup-To: "Bryan K. Ogawa" , freebsd-scsi@freebsd.org References: <3.0.32.19980403113026.007430fc@cyclone.degnet.baynet.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Bryan K. Ogawa on Fri, Apr 03, 1998 at 12:37:46PM -0800 x-no-archive: yes Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I wrote this morning about a scanner on scsi bus 0, /dev/pt0, causing a "total system lockup". You are correct, the one thing that still seems to happen is that the kernel returns pings. Best regards -- Larry S. Marso larry@marso.com On Fri, Apr 03, 1998 at 12:37:46PM -0800, Bryan K. Ogawa wrote: > > Can a termination problem cause total kernel hangs? > > Right now, at least two of us on -questions are experiencing problems with > total lockups (no pings) when in X, usually when using Netscape (in my > case) or in heavy concurrent disk accesses (in Malte's case) on SCSI > systems with a number of SCSI devices. (4 to 7). > > Malte has had success in reducing the hangs by changing the termination, > and I'm wondering if the sorts of hangs we're looking at could be caused > by termination problems. > > Both of us have Adaptec 2940UWs. > > Any ideas or suggestions? I had thought that a SCSI hung kernel would at > least return pings? > > bryan k ogawa http://www.primenet.com/~bkogawa/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 3 14:23:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17403 for freebsd-scsi-outgoing; Fri, 3 Apr 1998 14:23:38 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17377 for ; Fri, 3 Apr 1998 14:23:27 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id PAA09883; Fri, 3 Apr 1998 15:19:46 -0700 (MST) Date: Fri, 3 Apr 1998 15:19:46 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199804032219.PAA09883@narnia.plutotech.com> To: Norbert Bladt cc: scsi@FreeBSD.ORG Subject: Re: FBSD 2.2.5 Release: Problem with ahc0 Newsgroups: pluto.freebsd.scsi In-Reply-To: <35249871.67BE@autelca.ascom.ch> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > All seems to be fine, i.e. all the hardware is detected, etc. > However after showing > npx0: INT 16 interface > a message > ahc0: brkadrint, Illegal Host access at seqaddr = 0x0 > appears on the console and that's it. disable uha0. It's probe stomps on the Adaptec which makes it a little upset. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 3 16:00:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00445 for freebsd-scsi-outgoing; Fri, 3 Apr 1998 16:00:47 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.rdc1.on.wave.home.com (mta@ha1.rdc1.on.wave.home.com [24.2.9.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00435 for ; Fri, 3 Apr 1998 16:00:44 -0800 (PST) (envelope-from bessel@wave.home.com) Received: from home.com (cr619937-a.yec1.on.wave.home.com [24.112.83.17]) by mail.rdc1.on.wave.home.com (Netscape Messaging Server 3.5) with ESMTP id AAA6A2 for ; Fri, 3 Apr 1998 16:00:41 -0800 Message-ID: <352578D1.CFE5AE71@home.com> Date: Fri, 03 Apr 1998 19:03:29 -0500 From: Mark Wilding X-Mailer: Mozilla 4.05 [en] (WinNT; I) MIME-Version: 1.0 To: "freebsd-scsi@FreeBSD.ORG" Subject: Anyone working on the Buslogic BT-958 driver? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Anyone working on the buslogic driver? I'd like to work on adding synchronous transfer support for it if no one else is currently doing so. Whirl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 3 17:09:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09797 for freebsd-scsi-outgoing; Fri, 3 Apr 1998 17:09:44 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09745; Fri, 3 Apr 1998 17:09:32 -0800 (PST) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.8.8/8.8.8) id UAA11322; Fri, 3 Apr 1998 20:09:07 -0500 (EST) (envelope-from larry) Message-ID: <19980403200901.28899@marso.com> Date: Fri, 3 Apr 1998 20:09:01 -0500 From: "Larry S. Marso" To: freebsd-scsi@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: isa bus scsi card with good driver? Mail-Followup-To: freebsd-scsi@freebsd.org, freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i x-no-archive: yes Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What's a highly reliable scsi card/driver combination available for *ISA* as opposed to PCI? I'm not getting very far with an Adaptec 1520. Best regards -- Larry S. Marso larry@marso.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 3 20:07:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18092 for freebsd-scsi-outgoing; Fri, 3 Apr 1998 20:07:12 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA18082; Fri, 3 Apr 1998 20:07:06 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yLJq1-0004Mb-00; Fri, 3 Apr 1998 19:41:49 -0800 Date: Fri, 3 Apr 1998 19:41:48 -0800 (PST) From: Tom To: "Larry S. Marso" cc: freebsd-scsi@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: isa bus scsi card with good driver? In-Reply-To: <19980403200901.28899@marso.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 3 Apr 1998, Larry S. Marso wrote: > What's a highly reliable scsi card/driver combination available for *ISA* > as opposed to PCI? Adaptec 1542 is pretty good. However, as of late, there have been bounce buffer problems. Still probably the best ISA card available. The 1542 is nice because it has a BIOS, so you can set all kinds of params, do low-level formats, and even boot. (Uses aha driver). > I'm not getting very far with an Adaptec 1520. aic driver? That is not very good. Though my 1510 has been ok for my HP dat, just not very fast. > Best regards > -- > Larry S. Marso > larry@marso.com Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 3 23:36:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA11829 for freebsd-scsi-outgoing; Fri, 3 Apr 1998 23:36:48 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA11824 for ; Fri, 3 Apr 1998 23:36:47 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id AAA10628; Sat, 4 Apr 1998 00:33:00 -0700 (MST) Date: Sat, 4 Apr 1998 00:33:00 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199804040733.AAA10628@narnia.plutotech.com> To: Mark Wilding cc: scsi@FreeBSD.ORG Subject: Re: Anyone working on the Buslogic BT-958 driver? Newsgroups: pluto.freebsd.scsi In-Reply-To: <352578D1.CFE5AE71@home.com> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <352578D1.CFE5AE71@home.com> you wrote: > Anyone working on the buslogic driver? > > I'd like to work on adding synchronous transfer support for it if no > one else is currently doing so. > > Whirl I have the new CAM driver up to the point where I can dump a 4 disk ccd array onto a DDS-2 drive on the same string all off of a BT-948. I will be working on the EISA, VL, and ISA probes as well as the error recovery code this weekend, so it should be ready for prime-time RSN. The driver currently supports: Sync/Wide/Ultra transfers (as did the old driver) Tagged Queueing (New Feature) The following number of simultaneous transactions: 192 BT-948/958/958D 100 BT-946C/956C/956CD/747C/757C/757CD/445C 50 BT-545C/540CF 30 BT-747S/747D/757S/757D/445S/545S/542D/542B/742A (The old driver maxed out at 32 instead of the maximum supported by the particular card model.) The driver has been pretty much rewritten from scratch and is much more careful about determining the feature set availbable in each card and working around peculiarities in different firmware revisions. Once complete, the driver will also have the full complement of error recovery. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 4 04:47:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA11300 for freebsd-scsi-outgoing; Sat, 4 Apr 1998 04:47:39 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from cyclone.degnet.baynet.de (www.degnet.baynet.de [194.95.214.129]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA11281; Sat, 4 Apr 1998 04:47:35 -0800 (PST) (envelope-from malte@webmore.com) Received: from bachus (unverified [194.95.214.162]) by cyclone.degnet.baynet.de (EMWAC SMTPRS 0.83) with SMTP id ; Sat, 04 Apr 1998 14:45:25 +0200 Message-Id: <3.0.32.19980404133529.00749da0@cyclone.degnet.baynet.de> X-Sender: moos@cyclone.degnet.baynet.de X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sat, 04 Apr 1998 13:35:30 -0100 To: questions@FreeBSD.ORG From: Malte Lance Subject: jumper-setting for SONY SDT-7000 Cc: freebsd-scsi@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anyone have detailed info on the meaning of the jumpers "DC Disable" and "Terminator Power" for the SONY SDT-7000 ? Any help and info is highly appreciated. Thanks for your help in advance. Malte Lance malte@webmore.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 4 04:47:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA11335 for freebsd-scsi-outgoing; Sat, 4 Apr 1998 04:47:42 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from cyclone.degnet.baynet.de (www.degnet.baynet.de [194.95.214.129]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA11320 for ; Sat, 4 Apr 1998 04:47:40 -0800 (PST) (envelope-from malte@webmore.com) Received: from bachus (unverified [194.95.214.162]) by cyclone.degnet.baynet.de (EMWAC SMTPRS 0.83) with SMTP id ; Sat, 04 Apr 1998 14:45:30 +0200 Message-Id: <3.0.32.19980404133534.006d1644@cyclone.degnet.baynet.de> X-Sender: moos@cyclone.degnet.baynet.de X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sat, 04 Apr 1998 13:35:35 -0100 To: "Bryan K. Ogawa" From: Malte Lance Subject: Re: Will a termination problem cause total hangs? Cc: freebsd-scsi@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 12:37 03.04.98 -0800, you wrote: > >Can a termination problem cause total kernel hangs? > >Right now, at least two of us on -questions are experiencing problems with >total lockups (no pings) when in X, usually when using Netscape (in my >case) or in heavy concurrent disk accesses (in Malte's case) on SCSI >systems with a number of SCSI devices. (4 to 7). In my case i encounter this hangs also when in X. Since i run XDM i dont know if it would happen without X. This crashes happen always to me on heavy-loaded scsi-bus-activity where more than one device are involved. In my case this is not just related to X or NS. This kind of hangs also happen in Win95. > >Malte has had success in reducing the hangs by changing the termination, >and I'm wondering if the sorts of hangs we're looking at could be caused >by termination problems. > >Both of us have Adaptec 2940UWs. I am using a plain AHA-2940 under FBSD-2.1.5(R) > >Any ideas or suggestions? I had thought that a SCSI hung kernel would at >least return pings? > Malte Lance malte@webmore.com >bryan k ogawa http://www.primenet.com/~bkogawa/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 4 04:47:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA11370 for freebsd-scsi-outgoing; Sat, 4 Apr 1998 04:47:44 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from cyclone.degnet.baynet.de (www.degnet.baynet.de [194.95.214.129]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA11296; Sat, 4 Apr 1998 04:47:38 -0800 (PST) (envelope-from malte@webmore.com) Received: from bachus (unverified [194.95.214.162]) by cyclone.degnet.baynet.de (EMWAC SMTPRS 0.83) with SMTP id ; Sat, 04 Apr 1998 14:45:27 +0200 Message-Id: <3.0.32.19980404133531.0075a824@cyclone.degnet.baynet.de> X-Sender: moos@cyclone.degnet.baynet.de X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sat, 04 Apr 1998 13:35:32 -0100 To: "Bryan K. Ogawa" From: Malte Lance Subject: Re: Advice for diagnosing X hangs / kernel hangs? Cc: questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 12:30 03.04.98 -0800, you wrote: >> >Hm... I agree with you -- this may be a SCSI problem (see the comments in >> >-stable about SCSI stuff). >> >> ??? "-stable" ? What do you mean ??? > >BTW: -stable stands for the mailing list freebsd-stable@freebsd.org . I >recommend it if you are running anything in 2.2 , especially if you run >anything between releases. UUUuuuh ... i am running FreeBSD-2.1.5 and i am happy with it ;) I want to upgrade to something higher but not until i have found a solution for this damned freezes. >Since this may be a SCSI problem, I'll probably send a quick note to >freebsd-scsi as well. Hm ... i really should subscribe to -scsi . >> >I now have a 2nd machine so I can try to telnet when next my system hangs. >> No use. Done it already. As i said. When my machine freezes, it is like >> shock-frozen, nothing works. Not even a ping comes back when pinging >> it. Therefor I dont believe you will be able to telnet into it. >Yeah, my system just hung while running the program I supplied and it was >unpingable. > >However, this isn't the symptom that I had heard of previously in the >-stable list for SCSI bugs. It may be termination, however. So your hangs seem to be the same hangs that i see on my machine and the reason for this hangs should be the same also, without knowing what the real reason is. Our problem is definately not an OS-bug. It is a hardware-problem IMO. That hangs happen on FreeBSD as well as Win95 and always when the scsi-bus is busy with heavy load where more than one device are involved. It never happens when the scsi-bus is heavy-loaded with just one device. >> >I have also had great success in reducing my hangs by running the >> >following program from another virtual console: >> This is fighting the symptoms ... no real solution. But for the time, until >> a solution is found, it is undoubtly useful. >Yes, and if we can find a way to reliably prevent the hangs from software, >then it may help in diagnosing the cause. I dont think you can prevent the hangs by software. My problem for now is, how to reproduce that hangs on demand. Again, my candidate is noise on TERM-POWER. I have just one device that has some jumpers to play with active/passive-termination AND term-power. It is the SONY-SDT-7000 tape-drive. When terminating the scsi-bus passive, i get disastrous crashes at bootup. When terminating the scsi-bus active with term-power-jumper set to "provided" by scsi-bus, i had no hangs so far. When terminating the scsi-bus active with term-power-jumper set to "not provided" by the scsi-bus, i had that hangs. My paper of the jumper-setting on the sony-sdt-7000 is really bad, so i am not sure what the term-power-jumper and the "dc-disable"-jumper really do. I have to guess. All other devices on my bus dont have a jumper for term-power. If they are set to terminate the scsi-bus, they do it active. But i dont know, if they are getting term-power from the scsi-bus or in some other way. Further i dont know if they supply term-power to the scsi-bus. Therefor i set the sony-sdt-7000 as the terminating device. A final answer if noise on term-power is causing this hangs can be obtained by cutting the term-power-line on the scsi-cable at both ends of it. But this is an irreversible step. I am not sure if i should take that step. Do you have a device with jumpers to enable and disable term-power ? Malte Lance malte@webmore.com > >bryan k ogawa http://www.primenet.com/~bkogawa/ > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 4 07:35:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26051 for freebsd-scsi-outgoing; Sat, 4 Apr 1998 07:35:00 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ache.relcom.ru (ache.relcom.ru [193.125.20.108]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26044; Sat, 4 Apr 1998 07:34:51 -0800 (PST) (envelope-from ache@ache.relcom.ru) Received: (from ache@localhost) by ache.relcom.ru (8.8.8/8.8.8) id TAA00250; Sat, 4 Apr 1998 19:34:39 +0400 (MSD) (envelope-from ache) Message-ID: <19980404193439.51330@nagual.pp.ru> Date: Sat, 4 Apr 1998 19:34:39 +0400 From: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= To: scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: SCSI errors with latest -current Mail-Followup-To: scsi@freebsd.org, current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Organization: Biomechanoid Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org With latest -current I start to get this sort of errors for my several SCSI drives. Since they started at once for several drives, I suppose it is not hardware problem. Any ideas? sd1: SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x4 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Ordered Tag queued Ordered Tag sent sd1: SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa sd1: Queueing an Abort SCB sd1: Abort Message Sent sd1: SCB 5 - Abort Tag Completed. sd1: no longer in timeout -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 4 08:12:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01047 for freebsd-scsi-outgoing; Sat, 4 Apr 1998 08:12:37 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00975; Sat, 4 Apr 1998 08:12:33 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id SAA05646; Sat, 4 Apr 1998 18:11:42 +0200 (CEST) To: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= cc: scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: SCSI errors with latest -current In-reply-to: Your message of "Sat, 04 Apr 1998 19:34:39 +0400." <19980404193439.51330@nagual.pp.ru> Date: Sat, 04 Apr 1998 18:11:41 +0200 Message-ID: <5644.891706301@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, based on the hot potato principle I guess my changes are still suspect, although I cannot see any reason why they should be affecting this. Yell at me if you find that the latest round of patches are causing this. If the devices are on the same controller, the cable & termination could be suspected (as well as the controller of course). Poul-Henning In message <19980404193439.51330@nagual.pp.ru>, =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= writes: >With latest -current I start to get this sort of errors for my several >SCSI drives. Since they started at once for several drives, I suppose it >is not hardware problem. Any ideas? > >sd1: SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 >SEQADDR = 0x4 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa >Ordered Tag queued >Ordered Tag sent >sd1: SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 >SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa >sd1: Queueing an Abort SCB >sd1: Abort Message Sent >sd1: SCB 5 - Abort Tag Completed. >sd1: no longer in timeout > >-- >Andrey A. Chernov >http://www.nagual.pp.ru/~ache/ >MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 4 09:09:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10245 for freebsd-scsi-outgoing; Sat, 4 Apr 1998 09:09:36 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from lsd.relcom.eu.net (ache@lsd.relcom.eu.net [193.125.27.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10235; Sat, 4 Apr 1998 09:09:31 -0800 (PST) (envelope-from ache@lsd.relcom.eu.net) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.8/8.8.8) id VAA18128; Sat, 4 Apr 1998 21:07:50 +0400 (MSD) (envelope-from ache) Message-ID: <19980404210749.52044@nagual.pp.ru> Date: Sat, 4 Apr 1998 21:07:49 +0400 From: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= To: Poul-Henning Kamp Cc: scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: SCSI errors with latest -current Mail-Followup-To: Poul-Henning Kamp , scsi@FreeBSD.ORG, current@FreeBSD.ORG References: <19980404193439.51330@nagual.pp.ru> <5644.891706301@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <5644.891706301@critter.freebsd.dk>; from phk@critter.freebsd.dk on Sat, Apr 04, 1998 at 06:11:41PM +0200 Organization: Biomechanoid Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Apr 04, 1998 at 06:11:41PM +0200, Poul-Henning Kamp wrote: > > Well, based on the hot potato principle I guess my changes are still > suspect, although I cannot see any reason why they should be affecting > this. > > Yell at me if you find that the latest round of patches are causing this. This effect is random, but I can't reproduce it with very old kernel, so either latest or previous patches set is under question. > If the devices are on the same controller, the cable & termination could > be suspected (as well as the controller of course). As I say old kernel seems working. At this moment I also know workaround for -current: when I comment out options AHC_SCBPAGING_ENABLE latest kernel works too. So something wrong with SCB paging code. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 4 09:15:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11718 for freebsd-scsi-outgoing; Sat, 4 Apr 1998 09:15:49 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11704; Sat, 4 Apr 1998 09:15:45 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id TAA05780; Sat, 4 Apr 1998 19:14:58 +0200 (CEST) To: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= cc: scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: SCSI errors with latest -current In-reply-to: Your message of "Sat, 04 Apr 1998 21:07:49 +0400." <19980404210749.52044@nagual.pp.ru> Date: Sat, 04 Apr 1998 19:14:58 +0200 Message-ID: <5778.891710098@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <19980404210749.52044@nagual.pp.ru>, =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= writes: >As I say old kernel seems working. At this moment I also know workaround >for -current: when I comment out >options AHC_SCBPAGING_ENABLE >latest kernel works too. So something wrong with SCB paging code. no clues... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 4 09:50:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18695 for freebsd-scsi-outgoing; Sat, 4 Apr 1998 09:50:50 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from lsd.relcom.eu.net (ache@lsd.relcom.eu.net [193.125.27.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18684; Sat, 4 Apr 1998 09:50:45 -0800 (PST) (envelope-from ache@lsd.relcom.eu.net) Received: (from ache@localhost) by lsd.relcom.eu.net (8.8.8/8.8.8) id VAA18433; Sat, 4 Apr 1998 21:48:18 +0400 (MSD) (envelope-from ache) Message-ID: <19980404214817.31715@nagual.pp.ru> Date: Sat, 4 Apr 1998 21:48:17 +0400 From: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= To: Poul-Henning Kamp Cc: scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: SCSI errors with latest -current Mail-Followup-To: Poul-Henning Kamp , scsi@FreeBSD.ORG, current@FreeBSD.ORG References: <19980404210749.52044@nagual.pp.ru> <5778.891710098@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <5778.891710098@critter.freebsd.dk>; from phk@critter.freebsd.dk on Sat, Apr 04, 1998 at 07:14:58PM +0200 Organization: Biomechanoid Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Apr 04, 1998 at 07:14:58PM +0200, Poul-Henning Kamp wrote: > In message <19980404210749.52044@nagual.pp.ru>, =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= writes: > > >As I say old kernel seems working. At this moment I also know workaround > >for -current: when I comment out > >options AHC_SCBPAGING_ENABLE > >latest kernel works too. So something wrong with SCB paging code. > > no clues... Maybe something in timeout/untimeout code (just raw guess)? -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 4 09:55:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20644 for freebsd-scsi-outgoing; Sat, 4 Apr 1998 09:55:52 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20619; Sat, 4 Apr 1998 09:55:42 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id TAA05937; Sat, 4 Apr 1998 19:54:47 +0200 (CEST) To: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= cc: scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: SCSI errors with latest -current In-reply-to: Your message of "Sat, 04 Apr 1998 21:48:17 +0400." <19980404214817.31715@nagual.pp.ru> Date: Sat, 04 Apr 1998 19:54:46 +0200 Message-ID: <5935.891712486@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <19980404214817.31715@nagual.pp.ru>, =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= writes: >On Sat, Apr 04, 1998 at 07:14:58PM +0200, Poul-Henning Kamp wrote: >> In message <19980404210749.52044@nagual.pp.ru>, =?koi8-r?B?4c7E0sXKIP7F0s7P >1w==?= writes: >> >> >As I say old kernel seems working. At this moment I also know workaround >> >for -current: when I comment out >> >options AHC_SCBPAGING_ENABLE >> >latest kernel works too. So something wrong with SCB paging code. >> >> no clues... > >Maybe something in timeout/untimeout code (just raw guess)? I didn't touch that... :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "Drink MONO-tonic, it goes down but it will NEVER come back up!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 4 11:55:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02553 for freebsd-scsi-outgoing; Sat, 4 Apr 1998 11:55:36 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.inreach.com (mail.inreach.com [209.142.0.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02548 for ; Sat, 4 Apr 1998 11:55:34 -0800 (PST) (envelope-from dburr@POBoxes.com) Received: from control.colossus.dyn.ml.org (dburr@199-170-160-152.la.inreach.net [199.107.160.152]) by mail.inreach.com (8.8.8/8.8.6/(InReach)) with SMTP id LAA09784 for ; Sat, 4 Apr 1998 11:51:13 -0800 (PST) Date: Sat, 4 Apr 1998 11:59:30 -0800 (PST) From: Donald Burr X-Sender: dburr@control.colossus.dyn.ml.org To: FreeBSD SCSI Subject: turning on and reprobing scsi devices? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I had always thought that it was a Very Bad Idea to turn on/off SCSI devices while the system is running. But, from some of the things I've been reading in the newsgroups and things I've heard, it seems that there are people that do this fairly frequently, with no ill effects. So what's the definite answer? Also, once I turn on a scsi device, how do I get the system to recognize it (i.e. re-probe the bus)? (also, when I turn a device off, how to get the system to "forget" of its existence?) My scsi controller is the Adaptec AHA-2940AU PCI. And, of course, I am running FreeBSD 2.2.5-RELEASE (soon to be 2.2.6). Any and all help is appreciated. Thanks! Donald Burr - Ask me for my PGP key | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ #1347455 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 4 12:16:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04255 for freebsd-scsi-outgoing; Sat, 4 Apr 1998 12:16:14 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA04234 for ; Sat, 4 Apr 1998 12:16:12 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id NAA00246; Sat, 4 Apr 1998 13:12:30 -0700 (MST) Date: Sat, 4 Apr 1998 13:12:30 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199804042012.NAA00246@narnia.plutotech.com> To: Donald Burr cc: scsi@FreeBSD.ORG Subject: Re: turning on and reprobing scsi devices? Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > I had always thought that it was a Very Bad Idea to turn on/off SCSI > devices while the system is running. But, from some of the things > I've been reading in the newsgroups and things I've heard, it seems > that there are people that do this fairly frequently, with no ill > effects. > > So what's the definite answer? It shouldn't cause a problem. > Also, once I turn on a scsi device, how do I get the system to recognize > it (i.e. re-probe the bus)? In CAM you do this with the camcontrol program. In stable and current, there is a facility to rebrobe the bus (scsi -r???), but I wouldn't suggest using it. If it works, it does so by accident. The old code was not very careful about dealing with open devices that went away and could get really confused in some reprobe scenarios. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 4 12:41:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05960 for freebsd-scsi-outgoing; Sat, 4 Apr 1998 12:41:12 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from zippy.dyn.ml.org (libya-209.ppp.hooked.net [206.169.227.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05940; Sat, 4 Apr 1998 12:41:04 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.8.8/8.8.7) with ESMTP id MAA10337; Sat, 4 Apr 1998 12:40:51 -0800 (PST) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Sat, 4 Apr 1998 12:40:50 -0800 (PST) From: Alex X-Sender: garbanzo@zippy.dyn.ml.org Reply-To: Alex To: =?koi8-r?B?4c7E0sXKIP7F0s7P1w==?= cc: scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: SCSI errors with latest -current In-Reply-To: <19980404193439.51330@nagual.pp.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 4 Apr 1998, [koi8-r] áÎÄÒÅÊ þÅÒÎÏ× wrote: > With latest -current I start to get this sort of errors for my several > SCSI drives. Since they started at once for several drives, I suppose it > is not hardware problem. Any ideas? I find that if your disk system is pushed hard enough, that you will get errors like that with SCB paging and/or TAGGED_QUEUING enabled even before PHKs commits. This is one of the things the CAM code (dunno if it's stable enough to use) fixes. In essence it's a combination hardware and software problem... I think. > sd1: SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR = 0x4 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa > Ordered Tag queued > Ordered Tag sent > sd1: SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa > sd1: Queueing an Abort SCB > sd1: Abort Message Sent > sd1: SCB 5 - Abort Tag Completed. > sd1: no longer in timeout - alex "We are upping our standards ... so up yours." - Pat Paulsen for US of A Prez, 1988 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 4 13:19:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10580 for freebsd-scsi-outgoing; Sat, 4 Apr 1998 13:19:06 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA10571 for ; Sat, 4 Apr 1998 13:18:59 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yLZvG-0005PM-00; Sat, 4 Apr 1998 12:52:18 -0800 Date: Sat, 4 Apr 1998 12:52:05 -0800 (PST) From: Tom To: Donald Burr cc: FreeBSD SCSI Subject: Re: turning on and reprobing scsi devices? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 4 Apr 1998, Donald Burr wrote: > I had always thought that it was a Very Bad Idea to turn on/off SCSI > devices while the system is running. But, from some of the things > I've been reading in the newsgroups and things I've heard, it seems > that there are people that do this fairly frequently, with no ill > effects. > > So what's the definite answer? Yes you can, but some devices can get wedged. The most common problem is locking the entire SCSI bus. If the bus is pretty quiet, you should not have problems even if you have a lot of junk on the bus. Hot swap modules are recommended if you require this to work under load. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 4 22:45:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA03263 for freebsd-scsi-outgoing; Sat, 4 Apr 1998 22:45:36 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from grue.xaqti.com (kitten@grue.xaqti.com [207.88.149.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA03249; Sat, 4 Apr 1998 22:45:34 -0800 (PST) (envelope-from kitten@xaqti.com) Received: (from kitten@localhost) by grue.xaqti.com (8.8.8/8.8.8) id WAA08022; Sat, 4 Apr 1998 22:45:33 -0800 (PST) (envelope-from kitten@snowpaws.com) From: Julie Juracich Message-Id: <199804050645.WAA08022@grue.xaqti.com> Subject: Problems with Adaptec2920 driver To: freebsd-scsi@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Date: Sat, 4 Apr 1998 22:45:33 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I posted this to comp.unix.bsd.freebsd.misc, but have received no response, so I thought I'd try the mailing lists. I have an Adaptec 2920 SCSI controller that has been giving me no end of headaches with FreeBSD. I was able to use the driver from http://www.sbox.tu-graz.ac.at/home/rmike/freebsd/ with a minor alteration for FreeBSD-STABLE (had to remove references to crd.h). I have now gone to FreeBSD-CURRENT, and I have tried both that driver and the patch located here: ftp://ftp.freebsd.org/pub/FreeBSD/2.2.6-RELEASE/xperimnt/aha2920/tmc18c30-sysdif f.gz Neither are working and are spewing errors during my kernel compile such as: (using tmc18c30-sysdiff.gz) ../../pci/aha2920pci.c: At top level: ../../pci/aha2920pci.c:288: redefinition of `ahd_pci_intr' ../../pci/aha2920pci.c:139: `ahd_pci_intr' previously defined here ** Error code 1 (using aha2920-230897.tgz) ../../i386/scsi/scsi_low/scsi_low.c: In function `scsi_low_init_ccbque': ../../i386/scsi/scsi_low/scsi_low.c:250: parse error before `ccbque' ../../i386/scsi/scsi_low/scsi_low.c: In function `scsi_low_get_ccb': ../../i386/scsi/scsi_low/scsi_low.c:250: parse error before `break' Has anyone else gotten this card running successfully with FreeBSD-CURRENT? If so, could you tell me what I need to do to get it working? -- Julie Juracich )\._.,--....,'``. kitten @ snowpaws.com /, _.. \ _\ ;`._ ,. http://www.snowpaws.com/ `._.-(,_..'--(,_..'`-.;.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message