From owner-freebsd-scsi Sun Feb 28 12:17: 6 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id BF4461529F for ; Sun, 28 Feb 1999 12:17:04 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id MAA10682; Sun, 28 Feb 1999 12:16:38 -0800 Date: Sun, 28 Feb 1999 12:16:38 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Tom Torrance at home Cc: scsi@FreeBSD.ORG Subject: Re: RELENG_3 sa0 driver 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 I cannot reproduce this problem. Are you sure that it wasn't an I/O error which caused the tape to rewind? I did put in code that tries to unload the tape after an error that can cause an uncertainty in position. On Fri, 26 Feb 1999, Tom Torrance at home wrote: > I cvsup'd and rebuilt my system last night. > Today, I did a system backup, and discovered that > although dump was using /dev/nrsa0, the tape was automatically > rewinding when closed. Easy to miss, and pretty dangerous > when multi-file backup tapes are involved. > > Cheers, > Tom > > > > 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 Sun Feb 28 16:23:15 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from moe.nycrc.net (gabriel.nycrc.net [209.73.202.6]) by hub.freebsd.org (Postfix) with SMTP id 5EF1B15018 for ; Sun, 28 Feb 1999 16:23:11 -0800 (PST) (envelope-from vince@nycrc.net) Received: (qmail 276 invoked by uid 1000); 1 Mar 1999 00:23:53 -0000 Message-ID: <19990228192353.A271@nycrc.net> Date: Sun, 28 Feb 1999 19:23:53 -0500 From: Vince Gonzalez To: freebsd-scsi@freebsd.org Subject: 2940U2W supported? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just a fast question: How well are the Adaptec 2940U2W controllers supported? Are the controllers based on the 7896 supported as well? Any opinions? I'm looking into some of the motherboards with integrated SCSI, and I'm curious to hear anyone's experience. --vince To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Feb 28 20:12:20 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E2FD1511C for ; Sun, 28 Feb 1999 20:12:17 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id VAA69529; Sun, 28 Feb 1999 21:11:48 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903010411.VAA69529@panzer.plutotech.com> Subject: Re: 2940U2W supported? In-Reply-To: <19990228192353.A271@nycrc.net> from Vince Gonzalez at "Feb 28, 1999 7:23:53 pm" To: vince@nycrc.net (Vince Gonzalez) Date: Sun, 28 Feb 1999 21:11:48 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Vince Gonzalez wrote... > Just a fast question: > > How well are the Adaptec 2940U2W controllers supported? Are the controllers > based on the 7896 supported as well? Any opinions? I'm looking into some > of the motherboards with integrated SCSI, and I'm curious to hear anyone's > experience. They're both supported and should both work fine. 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 Feb 28 20:16:52 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (Postfix) with ESMTP id 18CFE150D1 for ; Sun, 28 Feb 1999 20:16:47 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.9.1/8.8.7) with ESMTP id XAA77580; Sun, 28 Feb 1999 23:16:16 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: "Kenneth D. Merry" Cc: vince@nycrc.net (Vince Gonzalez), freebsd-scsi@FreeBSD.ORG From: "Gary Palmer" Subject: Re: 2940U2W supported? In-reply-to: Your message of "Sun, 28 Feb 1999 21:11:48 MST." <199903010411.VAA69529@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Feb 1999 23:16:16 -0500 Message-ID: <77576.920261776@gjp.erols.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" wrote in message ID <199903010411.VAA69529@panzer.plutotech.com>: > They're both supported and should both work fine. In 3.0 or later, that is :) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 1 2:45:24 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from kremvax.demos.su (kremvax.demos.su [194.87.0.20]) by hub.freebsd.org (Postfix) with SMTP id 6B9B91533A for ; Mon, 1 Mar 1999 02:45:19 -0800 (PST) (envelope-from sinbin.demos.su!bag@kremvax.demos.su) Received: by kremvax.demos.su (8.6.13/D) from 0@sinbin.demos.su [194.87.5.31] with ESMTP id NAA03507; Mon, 1 Mar 1999 13:39:07 +0300 Received: by sinbin.demos.su id NAA11096; (8.6.12/D) Mon, 1 Mar 1999 13:38:37 +0300 From: bag@sinbin.demos.su (Alex G. Bulushev) Message-Id: <199903011038.NAA11096@sinbin.demos.su> Subject: Re: RAID saga In-Reply-To: from spork at "Feb 26, 1999 2:43:23 pm" To: spork@super-g.com (spork) Date: Mon, 1 Mar 1999 13:38:37 +0300 (MSK) Cc: freebsd-scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2652 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi, > > We've just about given up on CMD as a SCSI-SCSI controller, so now we're > looking around to see what else is out there. So far I've heard good > things about two others: > > Mylex DAC960-S(X/U)I (Does anyone see what the differences in these two > controllers are? The specs seem the same) > See www.mylex.com - this is intel 960-based > > Infortrend ??A Lots of models there, not real detailed info. See > www.infortrend.com.tw for more info. This one > is 486 based. we use several IFT3102 without problems, it can work with fbsd cam as is or with path to scsi_da.c 127,135d126 < * Infortrend RAID controller doesn't like the < * synchronize cache command. < */ < {T_DIRECT, SIP_MEDIA_FIXED, "IFT", "3102", "01*"}, < /*quirks*/ DA_Q_NO_SYNC_CACHE < < }, < { < /* we dont check new firmware that support growing, firmware in our controllers is 1-1.5 years old > > Anyone have any experience with either of these? I know one of the Mylex > models is being used for wcarchive, I assume under CAM. It appears each > of these controllers support growing the array, which is something not > possible with the CMD. Of course the most important factor is whether any > quirks show up under FreeBSD (in this case a 2.2.7 SNAP with CAM patches). > > Our issue with the CMD is that under load we get timeouts unless I disable > disconnection in the Adaptec card (2940UW) bios. Checked cabling, > termination, swapped cables, etc... > > > CMD has been incredibly lame in dealing with this as well, the ol' "I > never heard of that OS" line after we buy the product specifically because > it "works with any OS". At this point they are telling us to go to our > reseller for support, which is kind of silly as the problem seems beyond > tech support and more like something that needs some developer attention. > If anyone else is running the CRD-5440 with two host channels and two > drive channels, please contact me so we can compare notes. The drive side > seems OK, the only thing the cmd logs is the reset that the scsi layer > sends to wack it back into shape... > > > Thanks, > > Charles > > --- > Charles Sprickman > spork@super-g.com > --- > "...there's no idea that's so good you can't > ruin it with a few well-placed idiots." > > > > 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 Mon Mar 1 6:22:53 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail1.WorldMediaCo.com (unknown [207.252.121.17]) by hub.freebsd.org (Postfix) with ESMTP id 13CFE15213 for ; Mon, 1 Mar 1999 06:22:51 -0800 (PST) (envelope-from opsys@omaha.com) Received: from freebsd.omaha.com ([207.252.122.220]) by mail1.WorldMediaCo.com (Post.Office MTA v3.5.3 release 223 ID# 0-55573U2500L250S0V35) with SMTP id com; Mon, 1 Mar 1999 08:14:44 -0600 Date: Mon, 1 Mar 1999 08:22:34 -0600 (CST) From: opsys@omaha.com (opsys) To: Vince Gonzalez Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: 2940U2W supported? In-Reply-To: <19990228192353.A271@nycrc.net> 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 man ahc Yes they are supported. -- "Paranoia, Paranoia, Everybody's coming to get me" Chris cwatson@worldmediaco.com opsys@open-systems.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 1 7:48:27 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ns2.michweb.net (ns2.michweb.net [208.246.108.3]) by hub.freebsd.org (Postfix) with SMTP id DF749150BD for ; Mon, 1 Mar 1999 07:48:25 -0800 (PST) (envelope-from matt@ns2.michweb.net) Received: (qmail 3148 invoked by uid 101); 1 Mar 1999 15:48:08 -0000 Date: Mon, 1 Mar 1999 10:48:08 -0500 (EST) From: Matt Simerson To: Vince Gonzalez Cc: freebsd-scsi@freebsd.org Subject: Re: 2940U2W supported? In-Reply-To: <19990228192353.A271@nycrc.net> 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 have one in use. Matt On Sun, 28 Feb 1999, Vince Gonzalez wrote: > Just a fast question: > > How well are the Adaptec 2940U2W controllers supported? Are the controllers > based on the 7896 supported as well? Any opinions? I'm looking into some > of the motherboards with integrated SCSI, and I'm curious to hear anyone's > experience. > > --vince > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > > `````````````````````````````````````````````````````````````````` Matt Simerson http://users.michweb.net/~matt MichWeb Inc. - President http://www.michweb.net The Art Farm - Technical Wizard http://www.theartfarm.com ISP/C - Treasurer http://www.ispc.org No one can make you feel inferior without your consent. -- Eleanor Roosevelt `````````````````````````````````````````````````````````````````` To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 1 12:18:30 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (Postfix) with ESMTP id B64A915399 for ; Mon, 1 Mar 1999 12:18:27 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m10HZ8T-000I1kC; Mon, 1 Mar 1999 15:17:53 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: Re: RELENG_3 sa0 driver In-Reply-To: from Matthew Jacob at "Feb 28, 1999 12:16:38 pm" To: mjacob@feral.com Date: Mon, 1 Mar 1999 15:17:53 -0500 (EST) Cc: tom@tomqnx.com, scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2279 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I cannot reproduce this problem. Are you sure that it wasn't an I/O error > which caused the tape to rewind? I did put in code that tries to unload > the tape after an error that can cause an uncertainty in position. I'm pretty positive, Matt - no I/O errors. Also it works consistently the same with different tapes. However, you will remember that you decided to take the route of allowing (but ignore) the prevent/allow media removal command to the HP T4000s although it doesn't handle it. It would be greatly preferable to have the 'quirk' for the T4000s prevent the issuance of the command, if that is possible. It is quite possible that your routine is interpreting the ignored invalid command as an I/O error. Other 'quirks' for other units could produce the same results. If I might venture an opinion, the driver is the wrong layer to take this kind of decision. "dump" is supposed to make its own decisions about fault tolerance on I/O errors. If you don't agree, there should definitely be a nice "big" error message if that were to legitimately be done. Even that is not too good as someone running X would not see the message. The "dump" program should abort if its media is removed from play... For other reasons, I scraped this system down to the "bare metal" and loaded RELEASE-3.1 on it. The "dump" program running with /dev/nrsa0 definitely rewinds as part of the end of job "close" function. It is (and was with Feb 25 RELENG_3) demonstrable here with: dump 0abuf 64 /dev/nrsa0 / (that "dump" program has a pretty non-standard command line interface!!) It hangs on the CLOSE console comment waiting for the rewind to complete before giving the command prompt. Unless it has been fixed since 3.1 it is the same still. Regards, Tom > > > > On Fri, 26 Feb 1999, Tom Torrance at home wrote: > > > I cvsup'd and rebuilt my system last night. > > Today, I did a system backup, and discovered that > > although dump was using /dev/nrsa0, the tape was automatically > > rewinding when closed. Easy to miss, and pretty dangerous > > when multi-file backup tapes are involved. > > > > Cheers, > > Tom > > > > > > > > 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 Mon Mar 1 12:20:39 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9AF9C15460 for ; Mon, 1 Mar 1999 12:20:36 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id MAA15799; Mon, 1 Mar 1999 12:20:03 -0800 Date: Mon, 1 Mar 1999 12:20:03 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Tom Torrance at home Cc: scsi@FreeBSD.ORG Subject: Re: RELENG_3 sa0 driver 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 Well, like I said I can't reproduce the rewind behavior in -current. On Mon, 1 Mar 1999, Tom Torrance at home wrote: > > I cannot reproduce this problem. Are you sure that it wasn't an I/O error > > which caused the tape to rewind? I did put in code that tries to unload > > the tape after an error that can cause an uncertainty in position. > > I'm pretty positive, Matt - no I/O errors. Also it works > consistently the same with different tapes. However, you will > remember that you decided to take the route of allowing (but ignore) > the prevent/allow media removal command to the HP T4000s although > it doesn't handle it. It would be greatly preferable to have the > 'quirk' for the T4000s prevent the issuance of the command, if that > is possible. It is quite possible that your routine is interpreting > the ignored invalid command as an I/O error. Other 'quirks' for other > units could produce the same results. > > If I might venture an opinion, the driver is the wrong layer to > take this kind of decision. "dump" is supposed to make its own > decisions about fault tolerance on I/O errors. If you don't agree, > there should definitely be a nice "big" error message if that > were to legitimately be done. Even that is not too good as > someone running X would not see the message. The "dump" program > should abort if its media is removed from play... > > For other reasons, I scraped this system down to the "bare metal" > and loaded RELEASE-3.1 on it. The "dump" program running with > /dev/nrsa0 definitely rewinds as part of the end of job "close" > function. > > It is (and was with Feb 25 RELENG_3) demonstrable here with: > dump 0abuf 64 /dev/nrsa0 / > (that "dump" program has a pretty non-standard command line > interface!!) > It hangs on the CLOSE console comment waiting for the rewind > to complete before giving the command prompt. > > Unless it has been fixed since 3.1 it is the same still. > > > Regards, > Tom > > > > > > > > > On Fri, 26 Feb 1999, Tom Torrance at home wrote: > > > > > I cvsup'd and rebuilt my system last night. > > > Today, I did a system backup, and discovered that > > > although dump was using /dev/nrsa0, the tape was automatically > > > rewinding when closed. Easy to miss, and pretty dangerous > > > when multi-file backup tapes are involved. > > > > > > Cheers, > > > Tom > > > > > > > > > > > > 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 Mon Mar 1 12:32: 2 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from news.IAEhv.nl (news.IAEhv.nl [194.151.64.4]) by hub.freebsd.org (Postfix) with ESMTP id 9F72D15422 for ; Mon, 1 Mar 1999 12:30:22 -0800 (PST) (envelope-from volf@oasis.IAEhv.nl) Received: from oasis.IAEhv.nl (uucp@localhost) by news.IAEhv.nl (8.9.1/8.9.1) with IAEhv.nl id VAA07558; Mon, 1 Mar 1999 21:29:41 +0100 (MET) Received: from LOCAL (volf@localhost) by avalon.oasis.IAEhv.nl (8.9.2/1.63); pid 10704 on Mon, 1 Mar 1999 20:06:03 GMT; id UAA10704 efrom: volf; eto: UNKNOWN From: volf@oasis.IAEhv.nl (Frank Volf) Message-Id: <199903012006.UAA10704@avalon.oasis.IAEhv.nl> Subject: Re: ahc error message In-Reply-To: <199902272040.NAA62936@panzer.plutotech.com> from "Kenneth D. Merry" at "Feb 27, 1999 1:40:47 pm" To: ken@plutotech.com (Kenneth D. Merry) Date: Mon, 1 Mar 1999 21:06:03 +0100 (CET) Cc: volf@oasis.IAEhv.nl, freebsd-scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (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 Kenneth D. Merry wrote: > > Quantum has firmware upgrades and a firmware upgrade utility on > ftp.quantum.com. (it seems to be down now) You'll need a bootable DOS > floppy with ASPI drivers for your SCSI card to run the firmware loader and > do the upgrade. > > You'll probably want to back your system up first, although I have done > four firmware upgrades, and haven't lost any data. Yep, works perfectly. Thanks for your help. Frank ---------------------------------------------------------------------------- Frank Volf - Internet Access Eindhoven ---------------------------------------------------------------------------- || volf@oasis.IAEhv.nl - use for personal mail || || volf@IAEhv.nl - use for Internet Access Eindhoven related mail || ---------------------------------------------------------------------------- IAE Public Access Unix System - Dial +31.40.2439436 and login as new. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 1 12:32: 3 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 23B1F15437 for ; Mon, 1 Mar 1999 12:31:08 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id MAA15854; Mon, 1 Mar 1999 12:30:39 -0800 Date: Mon, 1 Mar 1999 12:30:39 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Tom Torrance at home Cc: scsi@FreeBSD.ORG Subject: Re: RELENG_3 sa0 driver 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 > I'm pretty positive, Matt - no I/O errors. Also it works > consistently the same with different tapes. However, you will > remember that you decided to take the route of allowing (but ignore) > the prevent/allow media removal command to the HP T4000s although Another key item is a recent discovery of a variant such that recognition of a T4000s failed because the string to match was T4000S. It's unlikely things work at all in this case. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 1 13:45:46 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (Postfix) with ESMTP id D128215433 for ; Mon, 1 Mar 1999 13:44:50 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m10HaU7-000I1kC; Mon, 1 Mar 1999 16:44:19 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: Re: ncr timeout w/ RELENG_3 In-Reply-To: <000501be6403$0aef7fa0$5c069a8e@stomp.xe.org> from Calvin Yee at "Mar 1, 1999 11:46:23 am" To: calvin@xe.org (Calvin Yee) Date: Mon, 1 Mar 1999 16:44:19 -0500 (EST) Cc: scsi@freebsd.org, tom@tomqnx.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 381 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi Tom, > > I too have the same problem w/ the "ncr0: timeout nccb= xxxxxxxx (skip)" > error message. > Did anyone respond to your email? Do you know have a solution? No, Cal, to both questions. Matt Jacob tells me that no one wants to "own" that driver. My take is that if someone modifies it they should at least own their changes :-\ > Thanks, > > Cal > Cheers, 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 1 13:57:17 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E4C0514EA2 for ; Mon, 1 Mar 1999 13:56:06 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id NAA16221; Mon, 1 Mar 1999 13:55:24 -0800 Date: Mon, 1 Mar 1999 13:55:24 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Tom Torrance at home Cc: Calvin Yee , scsi@FreeBSD.ORG Subject: Re: ncr timeout w/ RELENG_3 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 All of this is fine, but remember that people here work mostly on a volunteer effort, so pushing too hard will get you at best a snort and a mail delete button... On Mon, 1 Mar 1999, Tom Torrance at home wrote: > > Hi Tom, > > > > I too have the same problem w/ the "ncr0: timeout nccb= xxxxxxxx (skip)" > > error message. > > Did anyone respond to your email? Do you know have a solution? > > No, Cal, to both questions. Matt Jacob tells me that no one > wants to "own" that driver. My take is that if someone modifies it > they should at least own their changes :-\ > > > Thanks, > > > > Cal > > > > Cheers, > Tom > > > > 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 Mon Mar 1 14:10:36 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (Postfix) with ESMTP id C4A4815403 for ; Mon, 1 Mar 1999 14:10:32 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m10Hat6-000I1kC; Mon, 1 Mar 1999 17:10:08 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: Re: ncr timeout w/ RELENG_3 In-Reply-To: from Matthew Jacob at "Mar 1, 1999 1:55:24 pm" To: mjacob@feral.com Date: Mon, 1 Mar 1999 17:10:07 -0500 (EST) Cc: tom@tomqnx.com, calvin@xe.org, scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1147 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > All of this is fine, but remember that people here work mostly on a > volunteer effort, so pushing too hard will get you at best a snort and a > mail delete button... > Hey Matt, I did not want to come across as "pushing" at all. The problem was only reported at 16:00 EST Friday, after all. It is far more likely that the relevent volunteer hasn't even seen the message yet! Might not for a week or two for all I know. Nobody is more grateful to you volunteers than I am! Cheers, Tom > > On Mon, 1 Mar 1999, Tom Torrance at home wrote: > > > > Hi Tom, > > > > > > I too have the same problem w/ the "ncr0: timeout nccb= xxxxxxxx (skip)" > > > error message. > > > Did anyone respond to your email? Do you know have a solution? > > > > No, Cal, to both questions. Matt Jacob tells me that no one > > wants to "own" that driver. My take is that if someone modifies it > > they should at least own their changes :-\ > > > > > Thanks, > > > > > > Cal > > > > > > > Cheers, > > Tom > > > > > > > > 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 Mon Mar 1 16:18:59 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ikhala.tcimet.net (ikhala.tcimet.net [198.109.166.215]) by hub.freebsd.org (Postfix) with ESMTP id ECC2015494 for ; Mon, 1 Mar 1999 16:18:13 -0800 (PST) (envelope-from dervish@ikhala.tcimet.net) Received: (from dervish@localhost) by ikhala.tcimet.net (8.9.3/8.9.3) id TAA02033 for scsi@freebsd.org; Mon, 1 Mar 1999 19:42:16 -0500 (EST) (envelope-from dervish) Date: Mon, 1 Mar 1999 19:42:16 -0500 From: Natty Rebel To: scsi@freebsd.org Subject: Problems with teac cdroms + symbios based adapters? Message-ID: <19990301194216.A2001@ikhala.tcimet.net> References: <19990301143418.A1225@ikhala.tcimet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990301143418.A1225@ikhala.tcimet.net>; from Natty Rebel on Mon, Mar 01, 1999 at 02:34:18PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT i386 X-PGP-Fingerprint: 2C CE A5 D7 FA 4D D5 FD 9A CC 2B 23 04 46 48 F8 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hey all (I had posted this message to hackers, but scsi is more appropriate ...) I've recently purchased a Teac 516s 16x cdrom along with a Kouwell 801V10B Fast SCSI adapter (Symbios 53C810a chipset). My problem is that the cdrom drive fails to recognise any cd's placed in it. Here are some results using camcontrol: # camcontrol tur -n cd -v (pass0:ncr0:0:3:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (pass0:ncr0:0:3:0): NOT READY asc:3a,0 (pass0:ncr0:0:3:0): Medium not present Unit is not ready the above is the main message that i see (i.e. 'medium not present' and 'unit is not ready'). what's funny is that i can send the eject command and the tray will eject. i've called teac tech support and the rep said there were some known issues with cam and symbios based chipsets. is this correct? the mailing list archives are off-line at the moment so i could not check if this is indeed an issue. here are some other outputs: # camcontrol devlist -v scbus-1 on xpt1116471295 bus 0: < > at scbus-1 target -1 lun -1 (xpt0) scbus0 on ncr0 bus 0: at scbus0 target 3 lun 0 (pass0,cd0) < > at scbus0 target -1 lun -1 () # camcontrol inquiry -n cd Removable CD-ROM SCSI-2 device Serial Number 10.0MB/s transfers (10.0MHz, offset 8) # camcontrol reset -n cd Reset of bus 0 was successful # camcontrol periphlist -n cd pass0: generation: 6 index: 1 status: MORE cd0: generation: 6 index: 2 status: LAST any help is appreciated ... #;^) -- natty rebel harder than the rest ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 1 18:38:33 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 7EB3A154F4 for ; Mon, 1 Mar 1999 18:38:30 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id TAA16211; Mon, 1 Mar 1999 19:29:22 -0700 (MST) Date: Mon, 1 Mar 1999 19:29:22 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199903020229.TAA16211@narnia.plutotech.com> To: bag@sinbin.demos.su (Alex G. Bulushev) Cc: scsi@FreeBSD.org Subject: Re: RAID saga X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <199903011038.NAA11096@sinbin.demos.su> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > we use several IFT3102 without problems, it can work with fbsd cam as is > or with path to scsi_da.c > > 127,135d126 > < * Infortrend RAID controller doesn't like the > < * synchronize cache command. > < */ > < {T_DIRECT, SIP_MEDIA_FIXED, "IFT", "3102", "01*"}, > < /*quirks*/ DA_Q_NO_SYNC_CACHE > < > < }, This will disable tagged queueing (min and max tags default to 0 since they are not initialized). Was this your intention? I would not expect to see good performance from this array without tagged queueing turned on. -- 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 1 18:40:29 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 10C1F14BE4 for ; Mon, 1 Mar 1999 18:40:27 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-216-180-15-244.dialup.HiWAAY.net [216.180.15.244]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id UAA30390; Mon, 1 Mar 1999 20:40:08 -0600 (CST) Received: from nospam.hiwaay.net (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.2/8.9.2) with ESMTP id UAA01989; Mon, 1 Mar 1999 20:39:55 -0600 (CST) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199903020239.UAA01989@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: tom@tomqnx.com (Tom Torrance at home) Cc: scsi@FreeBSD.ORG From: David Kelly Subject: Re: ncr timeout w/ RELENG_3 In-reply-to: Message from tom@tomqnx.com (Tom Torrance at home) of "Mon, 01 Mar 1999 17:10:07 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 01 Mar 1999 20:39:55 -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Tom Torrance at home writes: > > > > All of this is fine, but remember that people here work mostly on a > > volunteer effort, so pushing too hard will get you at best a snort and a > > mail delete button... > > > Hey Matt, > > I did not want to come across as "pushing" at all. The problem was > only reported at 16:00 EST Friday, after all. It is far more likely > that the relevent volunteer hasn't even seen the message yet! Might > not for a week or two for all I know. > > Nobody is more grateful to you volunteers than I am! Ditto! I wonder how much affect the NCR BIOS has on a running FreeBSD system? Could it initialize something funny? Or load misbehaving code in the SCSI chip? Am thinking if there is a BIOS upgrade for your board then this might be the time to give it a try. My Asus SC875 has Symbios's 4.0.11 BIOS, but there is a 4.3 (?) available for the download. *Had* to apply that upgrade to cards at work to get them to work in another Asus motherboard. -- 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 Mon Mar 1 21:11:16 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id A9A581512E for ; Mon, 1 Mar 1999 21:11:09 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id WAA76988; Mon, 1 Mar 1999 22:10:49 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903020510.WAA76988@panzer.plutotech.com> Subject: Re: Problems with teac cdroms + symbios based adapters? In-Reply-To: <19990301194216.A2001@ikhala.tcimet.net> from Natty Rebel at "Mar 1, 1999 7:42:16 pm" To: dervish@ikhala.tcimet.net (Natty Rebel) Date: Mon, 1 Mar 1999 22:10:49 -0700 (MST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Natty Rebel wrote... > Hey all (I had posted this message to hackers, but scsi is more appropriate ...) > > I've recently purchased a Teac 516s 16x cdrom along with a Kouwell 801V10B > Fast SCSI adapter (Symbios 53C810a chipset). My problem is that the cdrom > drive fails to recognise any cd's placed in it. Here are some results > using camcontrol: > > # camcontrol tur -n cd -v > (pass0:ncr0:0:3:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > (pass0:ncr0:0:3:0): NOT READY asc:3a,0 > (pass0:ncr0:0:3:0): Medium not present > Unit is not ready > > the above is the main message that i see (i.e. 'medium not present' and > 'unit is not ready'). Hmm, interesting. > what's funny is that i can send the eject command > and the tray will eject. That's not surprising at all. In fact, I would expect that with tray-type drives. > i've called teac tech support and the rep said > there were some known issues with cam and symbios based chipsets. is this correct? How would someone from Teac know about CAM at all? Sure, there are some bugs in the NCR/Symbios driver. They mainly due to the fact that no one is actively maintaining it. > the mailing list archives are off-line at the moment so i could not check if this > is indeed an issue. > > here are some other outputs: > > # camcontrol devlist -v > scbus-1 on xpt1116471295 bus 0: > < > at scbus-1 target -1 lun -1 (xpt0) > scbus0 on ncr0 bus 0: > at scbus0 target 3 lun 0 (pass0,cd0) > < > at scbus0 target -1 lun -1 () > > # camcontrol inquiry -n cd > Removable CD-ROM SCSI-2 device > Serial Number > 10.0MB/s transfers (10.0MHz, offset 8) > > # camcontrol reset -n cd > Reset of bus 0 was successful > > # camcontrol periphlist -n cd > pass0: generation: 6 index: 1 status: MORE > cd0: generation: 6 index: 2 status: LAST > > any help is appreciated ... Well, I'm not sure what we can really do about it. If the drive says there's no media present, there's probably not a whole lot you can do to convince it otherwise. Does that controller/drive combination work on any other OS? I kinda suspect that it won't. At least if you can tell them "it doesn't work under Windows", they might take the drive back and give you one that works. 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 Mon Mar 1 23:33:48 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from kremvax.demos.su (kremvax.demos.su [194.87.0.20]) by hub.freebsd.org (Postfix) with SMTP id CFF92154D5 for ; Mon, 1 Mar 1999 23:33:43 -0800 (PST) (envelope-from sinbin.demos.su!bag@kremvax.demos.su) Received: by kremvax.demos.su (8.6.13/D) from 0@sinbin.demos.su [194.87.5.31] with ESMTP id KAA16372; Tue, 2 Mar 1999 10:30:29 +0300 Received: by sinbin.demos.su id KAA17873; (8.6.12/D) Tue, 2 Mar 1999 10:29:40 +0300 From: bag@sinbin.demos.su (Alex G. Bulushev) Message-Id: <199903020729.KAA17873@sinbin.demos.su> Subject: Re: RAID saga In-Reply-To: <199903020229.TAA16211@narnia.plutotech.com> from "Justin T. Gibbs" at "Mar 1, 1999 7:29:22 pm" To: gibbs@narnia.plutotech.com (Justin T. Gibbs) Date: Tue, 2 Mar 1999 10:29:40 +0300 (MSK) Cc: scsi@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1757 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > we use several IFT3102 without problems, it can work with fbsd cam as is > > or with path to scsi_da.c > > > > 127,135d126 > > < * Infortrend RAID controller doesn't like the > > < * synchronize cache command. > > < */ > > < {T_DIRECT, SIP_MEDIA_FIXED, "IFT", "3102", "01*"}, > > < /*quirks*/ DA_Q_NO_SYNC_CACHE > > < > > < }, > > This will disable tagged queueing (min and max tags default to 0 since > they are not initialized). Was this your intention? I would not expect > to see good performance from this array without tagged queueing turned > on. we dont use this patch, but without this patch we have message (see below) when syncing disks, but all works (between panics :) GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc...(no debugging symbols found)... IdlePTD 2764800 initial pcb at 231cc4 panicstr: ffs_valloc: dup alloc panic messages: --- panic: ffs_valloc: dup alloc mp_lock = 01000001; cpuid = 1; lapic.id = 00000000 boot() called on cpu#1 syncing disks... 22 22 13 1 done (da1:ahc1:0:1:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da1:ahc1:0:1:0): ILLEGAL REQUEST asc:20,0 (da1:ahc1:0:1:0): Invalid command operation code (da2:ahc1:0:2:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da2:ahc1:0:2:0): ILLEGAL REQUEST asc:20,0 (da2:ahc1:0:2:0): Invalid command operation code (da3:ahc1:0:3:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da3:ahc1:0:3:0): ILLEGAL REQUEST asc:20,0 (da3:ahc1:0:3:0): Invalid command operation code dumping to dev 20401, offset 2215594 > > -- > Justin > > > 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 Tue Mar 2 5: 5:11 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (Postfix) with ESMTP id DAB9214D37 for ; Tue, 2 Mar 1999 05:05:02 -0800 (PST) (envelope-from mike@sentex.net) Received: from ospf-wat.sentex.net (ospf-wat.sentex.net [209.167.248.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id IAA24117; Tue, 2 Mar 1999 08:04:43 -0500 (EST) From: mike@sentex.net (Mike Tancsa) To: dkelly@hiwaay.net (David Kelly) Cc: scsi@FreeBSD.ORG Subject: Re: ncr timeout w/ RELENG_3 Date: Tue, 02 Mar 1999 13:13:46 GMT Message-ID: <36dbe3cd.1586321619@mail.sentex.net> References: In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1 Mar 1999 21:41:44 -0500, in sentex.lists.freebsd.misc you wrote: > >I wonder how much affect the NCR BIOS has on a running FreeBSD system? >Could it initialize something funny? Or load misbehaving code in the >SCSI chip? Am thinking if there is a BIOS upgrade for your board then >this might be the time to give it a try. > >My Asus SC875 has Symbios's 4.0.11 BIOS, but there is a 4.3 (?) >available for the download. *Had* to apply that upgrade to cards at work >to get them to work in another Asus motherboard. Interesting. I had the same problem with the card not working with a BX chipset board. Where can I download the 875BIOS from ? ---Mike Mike Tancsa (mdtancsa@sentex.net) Sentex Communications Corp, Waterloo, Ontario, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 2 7:18:37 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 7251114CF2 for ; Tue, 2 Mar 1999 07:18:21 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id IAA79167; Tue, 2 Mar 1999 08:17:36 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903021517.IAA79167@panzer.plutotech.com> Subject: Re: RAID saga In-Reply-To: <199903020229.TAA16211@narnia.plutotech.com> from "Justin T. Gibbs" at "Mar 1, 1999 7:29:22 pm" To: gibbs@pluto.plutotech.com Date: Tue, 2 Mar 1999 08:17:36 -0700 (MST) Cc: bag@sinbin.demos.su, scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Justin T. Gibbs wrote... > > we use several IFT3102 without problems, it can work with fbsd cam as is > > or with path to scsi_da.c > > > > 127,135d126 > > < * Infortrend RAID controller doesn't like the > > < * synchronize cache command. > > < */ > > < {T_DIRECT, SIP_MEDIA_FIXED, "IFT", "3102", "01*"}, > > < /*quirks*/ DA_Q_NO_SYNC_CACHE > > < > > < }, > > This will disable tagged queueing (min and max tags default to 0 since > they are not initialized). Was this your intention? I would not expect > to see good performance from this array without tagged queueing turned > on. The quirk is for the DA driver, not the transport layer. (i.e., it won't affect tags) 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 Tue Mar 2 7:25:35 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ns2.ge.com (ns2.ge.com [192.35.39.25]) by hub.freebsd.org (Postfix) with ESMTP id 4D63E14D9E for ; Tue, 2 Mar 1999 07:25:22 -0800 (PST) (envelope-from Paul.Bauer@amermsx.med.ge.com) Received: from thomas.ge.com (thomas-o.ge.com [10.47.28.21]) by ns2.ge.com (8.9.3/8.9.3) with ESMTP id KAA18484 for ; Tue, 2 Mar 1999 10:25:04 -0500 (EST) Received: from gemed.med.ge.com (gemed.med.ge.com [3.7.12.4]) by thomas.ge.com (8.9.3/8.9.3) with SMTP id KAA00655 for ; Tue, 2 Mar 1999 10:25:03 -0500 (EST) Received: from uswaumsxbhmedge.med.ge.com by gemed.med.ge.com (SMI-8.6/SMI-SVR4) id JAA04677; Tue, 2 Mar 1999 09:26:38 -0600 Received: by uswaumsxbhmedge.med.ge.com with Internet Mail Service (5.5.2232.9) id ; Tue, 2 Mar 1999 09:25:01 -0600 Message-ID: <6791DA0AB4B0D21199490060B0672B341ABF67@USWAUMSX01MEDGE> From: "Bauer, Paul (MED)" To: "'scsi@FreeBSD.ORG'" Subject: Tekram scsi support? Date: Tue, 2 Mar 1999 09:24:58 -0600 X-Mailer: Internet Mail Service (5.5.2232.9) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I recently got the 3.1 release and was glad to see that the Tekram DC390 based on the AMD chipset was supported. This is at least what it says on the back panel. But I have been unable to find any driver support for it. Upon closer reading of the release notes it is not supported. So which is correct? Is the back panel mislabeled? If so when will the Tekram be supported? thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 2 8:38:30 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 355C814D9F for ; Tue, 2 Mar 1999 08:37:48 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id JAA79573; Tue, 2 Mar 1999 09:37:29 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903021637.JAA79573@panzer.plutotech.com> Subject: Re: Tekram scsi support? In-Reply-To: <6791DA0AB4B0D21199490060B0672B341ABF67@USWAUMSX01MEDGE> from "Bauer, Paul (MED)" at "Mar 2, 1999 9:24:58 am" To: Paul.Bauer@amermsx.med.ge.com (Bauer Paul (MED)) Date: Tue, 2 Mar 1999 09:37:29 -0700 (MST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Bauer, Paul (MED) wrote... > I recently got the 3.1 release and was glad to see that the Tekram DC390 > based on the AMD chipset was supported. This is at least what it says > on the back panel. But I have been unable to find any driver support > for it. Upon closer reading of the release notes it is not supported. > So which is correct? Is the back panel mislabeled? If so when will the > Tekram be supported? thanks The AMD chipsets aren't supported yet. We have a CAM AMD driver written by a guy at Tekram, but haven't had a chance to try it out yet. (no hardware) It should go in the tree before too long, but of course that won't change your 3.1 CD. Sorry. 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 Tue Mar 2 17:54:58 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 3614315492 for ; Tue, 2 Mar 1999 17:54:55 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-216-180-15-176.dialup.HiWAAY.net [216.180.15.176]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id TAA00054; Tue, 2 Mar 1999 19:54:37 -0600 (CST) Received: from nospam.hiwaay.net (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.2/8.9.2) with ESMTP id TAA10176; Tue, 2 Mar 1999 19:54:26 -0600 (CST) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199903030154.TAA10176@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: mike@sentex.net (Mike Tancsa) Cc: dkelly@hiwaay.net (David Kelly), scsi@FreeBSD.ORG From: David Kelly Subject: Re: ncr timeout w/ RELENG_3 In-reply-to: Message from mike@sentex.net (Mike Tancsa) of "Tue, 02 Mar 1999 13:13:46 GMT." <36dbe3cd.1586321619@mail.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Mar 1999 19:54:25 -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Tancsa writes: > >My Asus SC875 has Symbios's 4.0.11 BIOS, but there is a 4.3 (?) > >available for the download. *Had* to apply that upgrade to cards at work > >to get them to work in another Asus motherboard. > > Interesting. I had the same problem with the card not working with a BX > chipset board. Where can I download the 875BIOS from ? I started at http://www.asus.com/. Think the German mirror had the latest SC875 images a month or more before the other sites. It might be ftp://ftp.asus.com.tw/pub/ASUS/Drivers/ncr40-1.zip and ftp://ftp.asus.com.tw/pub/ASUS/Drivers/ncr40-2.zip but those might still be the old versions. When I downloaded there was a choice of mirror sites and some had different stuff than others. Am downloading the above again to see if any of the files inside the zip look familiar. Unzip shows this in ncr40-1.zip, am sure its too old to be the newest: 32768 09-23-96 16:02 BIOS/8XX40302.ROM Think the same BIOS is available on the Symbios web site too. http://www.lsilogic.com/products/download.htm Ah ha! Found it under the above: Boot ROM Filename: bios41x.zip (106Kb zip file) bios41x.exe (127Kb self-extracting file for Windows '95/98 or NT) Version: PCI 4.13.00 - 11/06/98 Description: The SCSI expansion ROM used for Symbios PCI-SCSI devices. Also contains a flash utility to update Symbios host adapters. They ask you to click thru a license agreement, else I'd post the URL's directly. -- 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 Tue Mar 2 19: 1:43 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ikhala.tcimet.net (ikhala.tcimet.net [198.109.166.215]) by hub.freebsd.org (Postfix) with ESMTP id AF21C14E3D for ; Tue, 2 Mar 1999 19:01:23 -0800 (PST) (envelope-from dervish@ikhala.tcimet.net) Received: (from dervish@localhost) by ikhala.tcimet.net (8.9.3/8.9.3) id WAA04794; Tue, 2 Mar 1999 22:25:25 -0500 (EST) (envelope-from dervish) Date: Tue, 2 Mar 1999 22:25:25 -0500 From: Natty Rebel To: "Kenneth D. Merry" Cc: scsi@freebsd.org Subject: Re: Problems with teac cdroms + symbios based adapters? Message-ID: <19990302222525.A4752@ikhala.tcimet.net> References: <19990301194216.A2001@ikhala.tcimet.net> <199903020510.WAA76988@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199903020510.WAA76988@panzer.plutotech.com>; from Kenneth D. Merry on Mon, Mar 01, 1999 at 10:10:49PM -0700 X-Operating-System: FreeBSD 4.0-CURRENT i386 X-PGP-Fingerprint: 2C CE A5 D7 FA 4D D5 FD 9A CC 2B 23 04 46 48 F8 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Quoting Kenneth D. Merry (ken@plutotech.com): > Natty Rebel wrote... > > Hey all (I had posted this message to hackers, but scsi is more appropriate ...) > > > > I've recently purchased a Teac 516s 16x cdrom along with a Kouwell 801V10B > > Fast SCSI adapter (Symbios 53C810a chipset). My problem is that the cdrom > > drive fails to recognise any cd's placed in it. Here are some results > > using camcontrol: > > > > # camcontrol tur -n cd -v > > (pass0:ncr0:0:3:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > > (pass0:ncr0:0:3:0): NOT READY asc:3a,0 > > (pass0:ncr0:0:3:0): Medium not present > > Unit is not ready > > > > the above is the main message that i see (i.e. 'medium not present' and > > 'unit is not ready'). > > Hmm, interesting. > > > what's funny is that i can send the eject command > > and the tray will eject. > > That's not surprising at all. In fact, I would expect that with tray-type > drives. I'm curious as to why this is? > > > i've called teac tech support and the rep said > > there were some known issues with cam and symbios based chipsets. is this correct? > > How would someone from Teac know about CAM at all? Sure, there are some > bugs in the NCR/Symbios driver. They mainly due to the fact that no one is > actively maintaining it. Since that's the case I'll see what I can do. Since the drive does respond to the eject command, maybe this combo can be made to work. [snippage ...] > Well, I'm not sure what we can really do about it. If the drive says > there's no media present, there's probably not a whole lot you can do to > convince it otherwise. > > Does that controller/drive combination work on any other OS? Not sure, but I'll check with the other BSD's and Linux groups. > I kinda suspect that it won't. At least if you can tell them "it doesn't work > under Windows", they might take the drive back and give you one that works. Well my wife has a win95 box. Maybe I'll do some tinkering late one nite, while she's asleep of course ... #;^) > > Ken > -- > Kenneth Merry > ken@plutotech.com Thanks for the help ... #;^) -- natty rebel harder than the rest ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 2 21:31:33 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 1556614E93 for ; Tue, 2 Mar 1999 21:30:52 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id WAA82754; Tue, 2 Mar 1999 22:30:32 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903030530.WAA82754@panzer.plutotech.com> Subject: Re: Problems with teac cdroms + symbios based adapters? In-Reply-To: <19990302222525.A4752@ikhala.tcimet.net> from Natty Rebel at "Mar 2, 1999 10:25:25 pm" To: dervish@ikhala.tcimet.net (Natty Rebel) Date: Tue, 2 Mar 1999 22:30:32 -0700 (MST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Natty Rebel wrote... > Quoting Kenneth D. Merry (ken@plutotech.com): > > Natty Rebel wrote... > > > Hey all (I had posted this message to hackers, but scsi is more appropriate ...) > > > > > > I've recently purchased a Teac 516s 16x cdrom along with a Kouwell 801V10B > > > Fast SCSI adapter (Symbios 53C810a chipset). My problem is that the cdrom > > > drive fails to recognise any cd's placed in it. Here are some results > > > using camcontrol: > > > > > > # camcontrol tur -n cd -v > > > (pass0:ncr0:0:3:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > > > (pass0:ncr0:0:3:0): NOT READY asc:3a,0 > > > (pass0:ncr0:0:3:0): Medium not present > > > Unit is not ready > > > > > > the above is the main message that i see (i.e. 'medium not present' and > > > 'unit is not ready'). > > > > Hmm, interesting. > > > > > what's funny is that i can send the eject command > > > and the tray will eject. > > > > That's not surprising at all. In fact, I would expect that with tray-type > > drives. > I'm curious as to why this is? Why not? It's a way to pop the tray open from software. > > > > > i've called teac tech support and the rep said > > > there were some known issues with cam and symbios based chipsets. is this correct? > > > > How would someone from Teac know about CAM at all? Sure, there are some > > bugs in the NCR/Symbios driver. They mainly due to the fact that no one is > > actively maintaining it. > Since that's the case I'll see what I can do. Since the drive does respond > to the eject command, maybe this combo can be made to work. > > [snippage ...] > > Well, I'm not sure what we can really do about it. If the drive says > > there's no media present, there's probably not a whole lot you can do to > > convince it otherwise. > > > > Does that controller/drive combination work on any other OS? > Not sure, but I'll check with the other BSD's and Linux groups. > > > I kinda suspect that it won't. At least if you can tell them "it doesn't work > > under Windows", they might take the drive back and give you one that works. > Well my wife has a win95 box. Maybe I'll do some tinkering late one nite, > while she's asleep of course ... #;^) Yep, that's a good idea. Another thing to try is putting the CDROM drive on another SCSI card. I suspect it may be broken, but you'll want to try it with Windows to be sure it's not the NCR driver or something. 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 Wed Mar 3 2:12:42 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 97BC4154F6 for ; Wed, 3 Mar 1999 02:12:16 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA87343; Wed, 3 Mar 1999 10:11:49 GMT (envelope-from dfr@nlsystems.com) Date: Wed, 3 Mar 1999 10:11:49 +0000 (GMT) From: Doug Rabson To: "Kenneth D. Merry" Cc: "Bauer Paul (MED)" , scsi@freebsd.org Subject: Re: Tekram scsi support? In-Reply-To: <199903021637.JAA79573@panzer.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 Tue, 2 Mar 1999, Kenneth D. Merry wrote: > Bauer, Paul (MED) wrote... > > I recently got the 3.1 release and was glad to see that the Tekram DC390 > > based on the AMD chipset was supported. This is at least what it says > > on the back panel. But I have been unable to find any driver support > > for it. Upon closer reading of the release notes it is not supported. > > So which is correct? Is the back panel mislabeled? If so when will the > > Tekram be supported? thanks > > The AMD chipsets aren't supported yet. We have a CAM AMD driver written > by a guy at Tekram, but haven't had a chance to try it out yet. (no hardware) > > It should go in the tree before too long, but of course that won't change > your 3.1 CD. Sorry. I have an AMD PCI controller in the docking station of my laptop which I can test if you want. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 3 8: 6:32 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ns.uk1.vbc.net (ns.uk1.vbc.net [194.207.2.1]) by hub.freebsd.org (Postfix) with ESMTP id E0D2114F09 for ; Wed, 3 Mar 1999 08:06:27 -0800 (PST) (envelope-from grant@vbc.net) Received: from gromit (gromit.uk1.vbc.net [194.207.2.6]) by ns.uk1.vbc.net (8.8.8/8.8.8) with SMTP id QAA16607 for ; Wed, 3 Mar 1999 16:06:10 GMT (envelope-from grant@vbc.net) Message-ID: <01b401be658f$97489e40$0602cfc2@gromit.uk1.vbc.net> From: "Grant Beckerleg" To: Subject: Remote RAID Date: Wed, 3 Mar 1999 16:04:59 -0000 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.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello there, I am a newbie to FreeBSD and I have been building a RAID system that will be have to be administered remotely. My employer wants 3.1 Release on it. I was given a DPT 3444UW controller with 2 channels. This is causing problems as the 'Storage Manager' software does not seem to be able to reside on FreeBSD 3-1 release. This means NO remote maintenance of the arrays. Can anyone help with a remote configuration or is anyone using DPT's Storage Manager remotely? I have 8 x 4.5Gb drives - 2 will RAID1 and 6 will be RAID5. I have been told that I have to knock down the transfer rate, on the 6 drive array, to 10Mhz(10Mb per second) is this correct? Any help gratefully accepted. Rgds, Grant Beckerleg VBCnet GB Ltd http://www.vbc.net tel +44 117 929 1316 fax +44 117 927 2015 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 3 18:58:57 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with SMTP id 0787D14ECC for ; Wed, 3 Mar 1999 18:58:54 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with esmtp (Exim 1.82 #3) id 10INKQ-000339-00; Wed, 3 Mar 1999 17:53:34 -0800 Date: Wed, 3 Mar 1999 17:52:53 -0800 (PST) From: Tom To: Grant Beckerleg Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Remote RAID In-Reply-To: <01b401be658f$97489e40$0602cfc2@gromit.uk1.vbc.net> 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, 3 Mar 1999, Grant Beckerleg wrote: > Hello there, > I am a newbie to FreeBSD and I have been building a > RAID system that will be have to be administered remotely. My employer > wants 3.1 Release on it. > > I was given a DPT 3444UW controller with 2 channels. This is causing > problems as the 'Storage Manager' software does not seem to be able to > reside on FreeBSD 3-1 release. This means NO remote maintenance of the > arrays. > > Can anyone help with a remote configuration or is anyone using DPT's > Storage Manager remotely? No, it can't be done at this point. Remote configuration or any configuration is not really necessary after building the initial array. > I have 8 x 4.5Gb drives - 2 will RAID1 and 6 will be RAID5. > I have been told that I have to knock down the transfer rate, on the 6 > drive array, to 10Mhz(10Mb per second) is this correct? No. No idea why anyone would say or think that either. BTW, 10Mhz is 20MB/s as this card uses wide channels. > Any help gratefully accepted. > Rgds, > Grant Beckerleg VBCnet GB Ltd http://www.vbc.net > tel +44 117 929 1316 fax +44 117 927 2015 Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 3 20:31:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id B0D7E15025 for ; Wed, 3 Mar 1999 20:31:15 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id VAA91537; Wed, 3 Mar 1999 21:30:48 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903040430.VAA91537@panzer.plutotech.com> Subject: Re: Tekram scsi support? In-Reply-To: from Doug Rabson at "Mar 3, 1999 10:11:49 am" To: dfr@nlsystems.com (Doug Rabson) Date: Wed, 3 Mar 1999 21:30:48 -0700 (MST) Cc: Paul.Bauer@amermsx.med.ge.com, scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (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 Doug Rabson wrote... > On Tue, 2 Mar 1999, Kenneth D. Merry wrote: > > > Bauer, Paul (MED) wrote... > > > I recently got the 3.1 release and was glad to see that the Tekram DC390 > > > based on the AMD chipset was supported. This is at least what it says > > > on the back panel. But I have been unable to find any driver support > > > for it. Upon closer reading of the release notes it is not supported. > > > So which is correct? Is the back panel mislabeled? If so when will the > > > Tekram be supported? thanks > > > > The AMD chipsets aren't supported yet. We have a CAM AMD driver written > > by a guy at Tekram, but haven't had a chance to try it out yet. (no hardware) > > > > It should go in the tree before too long, but of course that won't change > > your 3.1 CD. Sorry. > > I have an AMD PCI controller in the docking station of my laptop which I > can test if you want. I just got a new version of the driver today from a guy at Tekram. I will send it to you, and anyone else who asks for it, via private email. It compiles and links just fine, but of course I can't test it. 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 Wed Mar 3 21:13:25 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 94FBA14D64 for ; Wed, 3 Mar 1999 21:13:20 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id VAA27655; Wed, 3 Mar 1999 21:12:54 -0800 Date: Wed, 3 Mar 1999 21:12:54 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Tom Torrance at home Cc: scsi@FreeBSD.ORG Subject: Re: RELENG_3 sa0 driver 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 > > I cannot reproduce this problem. Are you sure that it wasn't an I/O error > > which caused the tape to rewind? I did put in code that tries to unload > > the tape after an error that can cause an uncertainty in position. > > I'm pretty positive, Matt - no I/O errors. Also it works Spotted a case- I forgot that I haven't done the 'EOM early warning on writes' code yet (doing it now). If you're writing to end of tape, you'll actually get a hard error because you've written all the way to end of physical media, so the final filemarks will fail, and because I'm such a nice guy I'll eject the tape (or try to) because the failure won't let me know really where the tape is actually at. Only for QIC drives, that's a rewind. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 4 12:59:31 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from rm-rstar.sfu.ca (rm-rstar.sfu.ca [142.58.120.21]) by hub.freebsd.org (Postfix) with ESMTP id 34CC414D6F for ; Thu, 4 Mar 1999 12:59:22 -0800 (PST) (envelope-from btrigona@sfu.ca) Received: from fraser.sfu.ca (fraser.sfu.ca [192.168.0.101]) by rm-rstar.sfu.ca (8.9.1/8.9.1/SFU-5.0H) with SMTP id MAA23134 for ; Thu, 4 Mar 1999 12:59:04 -0800 (PST) Received: from localhost by fraser.sfu.ca with SMTP (950413.SGI.8.6.12/SFU-2.6C) id MAA15191 for (from btrigona@sfu.ca); Thu, 4 Mar 1999 12:59:04 -0800 Date: Thu, 4 Mar 1999 12:59:04 -0800 (PST) From: Benjamin Oliver Trigona-Harany X-Sender: btrigona@fraser To: freebsd-scsi@freebsd.org Subject: Tape drive Help Please!! 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 have a FreeBSD 2.2.6 system and I'm trying to install a HP SureStore DAT 5000i tape drive with an Adaptec 1502B SCSI card. I am fairly sure that my kernel is configured properly (default) and infact both the card and tape drive are detected properly (shown below) but when I try and execute any command involving the tape drive (like tar -tvf /dev/rst0 or mt status) I get the following message several times: st0(aic0:2:0): timed out What am I doing wrong?? Here's the relevant boot info, if seems to be detecting everything properly. aic0 at 0x340-0x35f irq 11 on isa aic0 waiting for scsi devices to settle (aic0:2:0): "HP HP35480A T603" type 1 removable SCSI 2 st0(aic0:2:0): Sequential-Access density code 0x13, variable blocks, write-enabled Thanks for any help! Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 5 2:48:45 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from kremvax.demos.su (kremvax.demos.su [194.87.0.20]) by hub.freebsd.org (Postfix) with SMTP id 6D866150D5 for ; Fri, 5 Mar 1999 02:48:41 -0800 (PST) (envelope-from sinbin.demos.su!bag@kremvax.demos.su) Received: by kremvax.demos.su (8.6.13/D) from 0@sinbin.demos.su [194.87.5.31] with ESMTP id NAA23556; Fri, 5 Mar 1999 13:46:29 +0300 Received: by sinbin.demos.su id NAA77228; (8.6.12/D) Fri, 5 Mar 1999 13:45:19 +0300 From: bag@sinbin.demos.su (Alex G. Bulushev) Message-Id: <199903051045.NAA77228@sinbin.demos.su> Subject: Re: RAID saga In-Reply-To: <199903021517.IAA79167@panzer.plutotech.com> from "Kenneth D. Merry" at "Mar 2, 1999 8:17:36 am" To: ken@plutotech.com (Kenneth D. Merry) Date: Fri, 5 Mar 1999 13:45:19 +0300 (MSK) Cc: gibbs@pluto.plutotech.com, scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1513 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Justin T. Gibbs wrote... > > > we use several IFT3102 without problems, it can work with fbsd cam as is > > > or with path to scsi_da.c > > > > > > 127,135d126 > > > < * Infortrend RAID controller doesn't like the > > > < * synchronize cache command. > > > < */ > > > < {T_DIRECT, SIP_MEDIA_FIXED, "IFT", "3102", "01*"}, > > > < /*quirks*/ DA_Q_NO_SYNC_CACHE > > > < > > > < }, > > > > This will disable tagged queueing (min and max tags default to 0 since > > they are not initialized). Was this your intention? I would not expect > > to see good performance from this array without tagged queueing turned > > on. > > The quirk is for the DA driver, not the transport layer. (i.e., it won't > affect tags) so this patch disable only sync cache command and it is usefull commit it in -stable and -carrent, without this patch we see not good messages when syncing disks: syncing disks... 22 22 13 1 done (da1:ahc1:0:1:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da1:ahc1:0:1:0): ILLEGAL REQUEST asc:20,0 (da1:ahc1:0:1:0): Invalid command operation code (da2:ahc1:0:2:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da2:ahc1:0:2:0): ILLEGAL REQUEST asc:20,0 (da2:ahc1:0:2:0): Invalid command operation code (da3:ahc1:0:3:0): SYNCHRONIZE CACHE. CDB: 35 0 0 0 0 0 0 0 0 0 (da3:ahc1:0:3:0): ILLEGAL REQUEST asc:20,0 (da3:ahc1:0:3:0): Invalid command operation 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 Fri Mar 5 8:26:17 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 93F191524A for ; Fri, 5 Mar 1999 08:26:07 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id RAA29005 for freebsd-scsi@FreeBSD.ORG; Fri, 5 Mar 1999 17:25:50 +0100 (CET) (envelope-from olli) Date: Fri, 5 Mar 1999 17:25:50 +0100 (CET) From: Oliver Fromme Message-Id: <199903051625.RAA29005@dorifer.heim3.tu-clausthal.de> To: freebsd-scsi@FreeBSD.ORG Subject: Re: 2940U2W supported? Newsgroups: list.freebsd-scsi Organization: Administration Heim 3 Reply-To: freebsd-scsi@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry wrote in list.freebsd-scsi: > Vince Gonzalez wrote... > > How well are the Adaptec 2940U2W controllers supported? Are the controllers > > based on the 7896 supported as well? Any opinions? I'm looking into some > > of the motherboards with integrated SCSI, and I'm curious to hear anyone's > > experience. > > They're both supported and should both work fine. I'm afraid they do not work fine. :-( Every once in a while, it _hangs_ forever when it displays "waiting for SCSI devices to settle" during boot (I'd guess it happens at every 10th reboot or something like that). This happens both with the Adaptec 2940-U2W and with the onboard Adaptec U2W of an ASUS P2B-LS, using 3.1-RELEASE. It's extremely annoying, because you cannot reboot such a machine remotely and be sure that it comes up again. :-( It renders the Adaptec controllers essentially unusable for production use. Is this bug known? Maybe even fixed in -STABLE? Should I file a PR? Anything else I could do? Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 5 8:28:52 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ns2.michweb.net (ns2.michweb.net [208.246.108.3]) by hub.freebsd.org (Postfix) with SMTP id 64F5A15194 for ; Fri, 5 Mar 1999 08:28:49 -0800 (PST) (envelope-from matt@ns2.michweb.net) Received: (qmail 5347 invoked by uid 101); 5 Mar 1999 16:28:31 -0000 Date: Fri, 5 Mar 1999 11:28:31 -0500 (EST) From: Matt Simerson To: freebsd-scsi@FreeBSD.ORG Subject: Re: 2940U2W supported? In-Reply-To: <199903051625.RAA29005@dorifer.heim3.tu-clausthal.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 On Fri, 5 Mar 1999, Oliver Fromme wrote: > Kenneth D. Merry wrote in list.freebsd-scsi: > > Vince Gonzalez wrote... > > > How well are the Adaptec 2940U2W controllers supported? Are the controllers > > > based on the 7896 supported as well? Any opinions? I'm looking into some > > > of the motherboards with integrated SCSI, and I'm curious to hear anyone's > > > experience. > > > > They're both supported and should both work fine. > > I'm afraid they do not work fine. :-( > > Every once in a while, it _hangs_ forever when it displays > "waiting for SCSI devices to settle" during boot (I'd guess > it happens at every 10th reboot or something like that). > This happens both with the Adaptec 2940-U2W and with the > onboard Adaptec U2W of an ASUS P2B-LS, using 3.1-RELEASE. I can confirm this behavior. > It's extremely annoying, because you cannot reboot such a > machine remotely and be sure that it comes up again. :-( > It renders the Adaptec controllers essentially unusable for > production use. Why do you have to reboot production servers? > Is this bug known? Maybe even fixed in -STABLE? > Should I file a PR? Anything else I could do? It's not fixed in -STABLE. I'm tracking -STABLE. Matt `````````````````````````````````````````````````````````````````` Matt Simerson http://users.michweb.net/~matt MichWeb Inc. - President http://www.michweb.net The Art Farm - Technical Wizard http://www.theartfarm.com ISP/C - Treasurer http://www.ispc.org No one can make you feel inferior without your consent. -- Eleanor Roosevelt `````````````````````````````````````````````````````````````````` To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 5 9:13:35 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id AD3D6151C1 for ; Fri, 5 Mar 1999 09:11:42 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id SAA29488 for freebsd-scsi@FreeBSD.ORG; Fri, 5 Mar 1999 18:11:22 +0100 (CET) (envelope-from olli) Date: Fri, 5 Mar 1999 18:11:22 +0100 (CET) From: Oliver Fromme Message-Id: <199903051711.SAA29488@dorifer.heim3.tu-clausthal.de> To: freebsd-scsi@FreeBSD.ORG Subject: Re: 2940U2W supported? Newsgroups: list.freebsd-scsi Organization: Administration Heim 3 Reply-To: freebsd-scsi@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matt Simerson wroye in list.freebsd-scsi: > On Fri, 5 Mar 1999, Oliver Fromme wrote: > > Kenneth D. Merry wrote in list.freebsd-scsi: > > > They're both supported and should both work fine. > > > > I'm afraid they do not work fine. :-( > > > > Every once in a while, it _hangs_ forever when it displays > > "waiting for SCSI devices to settle" during boot (I'd guess > > it happens at every 10th reboot or something like that). > > This happens both with the Adaptec 2940-U2W and with the > > onboard Adaptec U2W of an ASUS P2B-LS, using 3.1-RELEASE. > > I can confirm this behavior. > > > It's extremely annoying, because you cannot reboot such a > > machine remotely and be sure that it comes up again. :-( > > It renders the Adaptec controllers essentially unusable for > > production use. > > Why do you have to reboot production servers? We were tracking -stable, too, so we had to reboot sometimes for a new kernel. (We stopped tracking at 3.1-Release, though). But we still have to reboot sometimes, e.g. when we fiddled with some kernel options or something like that. It happens seldom, but that doesn't matter. This particular box is the server for a bunch of diskless icafe terminals, which are used only during the day. In the evening and at night we can experiment and reboot without interrupting any important service -- BUT it's important that the server comes up again after a reboot without having to travel to the room where it's physically located to press the reset button if necessary. > > > Is this bug known? Maybe even fixed in -STABLE? > > Should I file a PR? Anything else I could do? > > It's not fixed in -STABLE. I'm tracking -STABLE. :-( Thanks for the confirmation. By the way, what kind of SCSI devices do you have? Maybe the problem only occurs with some devices. We have: Waiting 5 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.0MB/s transfers (10.0MHz, offset 32) changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da2: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) cd0 at ahc0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.0MB/s transfers (20.0MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present All of them work fine, once the machine has booted. The DDS3 streamer and the CD-ROM drive are connected to the narrow connector, the HDs are connected to the U2W/LVD one. Cabling and termination is OK. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 5 9:56:29 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.6.53]) by hub.freebsd.org (Postfix) with ESMTP id 78F0315225 for ; Fri, 5 Mar 1999 09:56:27 -0800 (PST) (envelope-from stephw@xs4all.nl) Received: from xs3.xs4all.nl (stephw@xs3.xs4all.nl [194.109.6.44]) by smtp3.xs4all.nl (8.8.8/8.8.8) with ESMTP id SAA04296 for ; Fri, 5 Mar 1999 18:56:07 +0100 (CET) From: stephw@xs4all.nl Received: (from stephw@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) id SAA07849 for freebsd-scsi@freebsd.org; Fri, 5 Mar 1999 18:56:06 +0100 (CET) Date: Fri, 5 Mar 1999 18:56:06 +0100 To: freebsd-scsi@freebsd.org Subject: Re: 2940U2W supported? Message-ID: <19990305185606.A7516@xs3.xs4all.nl> Reply-To: freebsd-scsi@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org n Fri, 5 Mar 1999, Oliver Fromme wrote: > > Kenneth D. Merry wrote in list.freebsd-scsi: > > > They're both supported and should both work fine. > > > > I'm afraid they do not work fine. :-( > > > > Every once in a while, it _hangs_ forever when it displays > > > "waiting for SCSI devices to settle" during boot (I'd guess > > > it happens at every 10th reboot or something like that). > > > This happens both with the Adaptec 2940-U2W and with the > > > onboard Adaptec U2W of an ASUS P2B-LS, using 3.1-RELEASE. > > > > I can confirm this behavior. unfortunately I can confirm this as well :( we have 3 freebsd machines with two adaptec 2940U2W each as news machines, all three of them have this problem. > > > It's extremely annoying, because you cannot reboot such a > > > machine remotely and be sure that it comes up again. :-( > > > It renders the Adaptec controllers essentially unusable for > > > production use. > > > > Why do you have to reboot production servers? hm well, 3.1R is maybe not that reliable yet, and it's really annoying if you make a say new kernel, then reboot and then realize after 5-10mins you have to remote power cycle the thing. > By the way, what kind of SCSI devices do you have? Maybe the > problem only occurs with some devices. We have: We got some seagate st39102 ultra2lv. We also tried just attaching only one to one adapter and the problem's still there. bye, Stephanie ----------------------------<> _@r4k.net <>-----------------<> FreeBSD <>--- "I had to hit him -- he was starting to make sense." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 5 11:47:45 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 17BB815242 for ; Fri, 5 Mar 1999 11:47:41 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id LAA72621 for scsi@freebsd.org; Fri, 5 Mar 1999 11:47:24 -0800 (PST) From: Archie Cobbs Message-Id: <199903051947.LAA72621@bubba.whistle.com> Subject: Temporary hang To: scsi@freebsd.org Date: Fri, 5 Mar 1999 11:47:24 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL38 (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 My machine locked up .. but only temporarily. Any ideas what's going on? Here's the relevant kernel output: 11:38:47 swap_pager: indefinite wait buffer: device: 0x20401, blkno: 46000, size: 8192 11:39:17 swap_pager: indefinite wait buffer: device: 0x20401, blkno: 46000, size: 8192 11:39:17 (da0:ahc0:0:0:0): SCB 0x12 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xb 11:39:17 (da0:ahc0:0:0:0): Queuing a BDR SCB 11:39:18 (da0:ahc0:0:0:0): Bus Device Reset Message Sent 11:39:18 (da0:ahc0:0:0:0): no longer in timeout, status = 353 11:39:18 Unexpected busfree. LASTPHASE == 0xa0 11:39:18 SEQADDR == 0x155 11:40:17 (da0:ahc0:0:0:0): SCB 0x1d - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xb 11:40:17 (da0:ahc0:0:0:0): Queuing a BDR SCB 11:40:17 (da0:ahc0:0:0:0): Bus Device Reset Message Sent 11:40:17 (da0:ahc0:0:0:0): no longer in timeout, status = 353 11:40:17 Unexpected busfree. LASTPHASE == 0xa0 11:40:17 SEQADDR == 0x155 11:41:17 (da0:ahc0:0:0:0): SCB 0x8 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xc 11:41:17 (da0:ahc0:0:0:0): Queuing a BDR SCB 11:41:17 (da0:ahc0:0:0:0): Bus Device Reset Message Sent 11:41:17 (da0:ahc0:0:0:0): no longer in timeout, status = 353 11:41:17 Unexpected busfree. LASTPHASE == 0xa0 11:41:17 SEQADDR == 0x155 11:42:17 (da0:ahc0:0:0:0): SCB 0x1e - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xc 11:42:17 (da0:ahc0:0:0:0): Queuing a BDR SCB 11:42:17 (da0:ahc0:0:0:0): Bus Device Reset Message Sent 11:42:17 (da0:ahc0:0:0:0): no longer in timeout, status = 353 11:42:17 Unexpected busfree. LASTPHASE == 0xa0 11:42:17 SEQADDR == 0x155 11:43:17 (da0:ahc0:0:0:0): SCB 0xe - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xa 11:43:17 (da0:ahc0:0:0:0): Queuing a BDR SCB 11:43:17 (da0:ahc0:0:0:0): Bus Device Reset Message Sent 11:43:17 (da0:ahc0:0:0:0): no longer in timeout, status = 353 11:43:17 Unexpected busfree. LASTPHASE == 0xa0 11:43:17 SEQADDR == 0x155 11:44:17 (da0:ahc0:0:0:0): SCB 0x13 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xb 11:44:17 (da0:ahc0:0:0:0): Queuing a BDR SCB 11:44:17 (da0:ahc0:0:0:0): Bus Device Reset Message Sent 11:44:17 (da0:ahc0:0:0:0): no longer in timeout, status = 353 11:44:17 Unexpected busfree. LASTPHASE == 0xa0 11:44:17 SEQADDR == 0x155 And the boot log: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-19990201-STABLE #1: Wed Feb 3 16:40:07 PST 1999 root@bubba.whistle.com:/usr/src/sys/compile/BUBBA Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II (267.27-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping=4 Features=0x80f9ff real memory = 67108864 (65536K bytes) config> quit avail memory = 62341120 (60880K bytes) Preloaded elf kernel "kernel" at 0xf02bf000. Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x01 on pci0.4.0 ide_pci0: rev 0x01 on pci0.4.1 chip3: rev 0x01 on pci0.4.3 ahc0: rev 0x00 int a irq 9 on pci0.6.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs de0: rev 0x22 int a irq 10 on pci0.11.0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:c0:f0:17:ec:60 vga0: rev 0x00 int a irq 11 on pci0.12.0 Probing for devices on PCI bus 1: Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 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 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 1628MB (3335472 sectors), 3309 cyls, 16 heads, 63 S/T, 512 B/S vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Waiting 3 seconds for SCSI devices to settle de0: enabling 10baseT port changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4341MB (8890760 512 byte sectors: 64H 32S/T 4341C) WARNING: / was not properly dismounted cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.0MB/s transfers (20.0MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 5 12: 1:58 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from bubba.whistle.com (s205m7.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 0BFA815229 for ; Fri, 5 Mar 1999 12:01:56 -0800 (PST) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id LAA72621 for scsi@freebsd.org; Fri, 5 Mar 1999 11:47:24 -0800 (PST) From: Archie Cobbs Message-Id: <199903051947.LAA72621@bubba.whistle.com> Subject: Temporary hang To: scsi@freebsd.org Date: Fri, 5 Mar 1999 11:47:24 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL38 (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 My machine locked up .. but only temporarily. Any ideas what's going on? Here's the relevant kernel output: 11:38:47 swap_pager: indefinite wait buffer: device: 0x20401, blkno: 46000, size: 8192 11:39:17 swap_pager: indefinite wait buffer: device: 0x20401, blkno: 46000, size: 8192 11:39:17 (da0:ahc0:0:0:0): SCB 0x12 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xb 11:39:17 (da0:ahc0:0:0:0): Queuing a BDR SCB 11:39:18 (da0:ahc0:0:0:0): Bus Device Reset Message Sent 11:39:18 (da0:ahc0:0:0:0): no longer in timeout, status = 353 11:39:18 Unexpected busfree. LASTPHASE == 0xa0 11:39:18 SEQADDR == 0x155 11:40:17 (da0:ahc0:0:0:0): SCB 0x1d - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xb 11:40:17 (da0:ahc0:0:0:0): Queuing a BDR SCB 11:40:17 (da0:ahc0:0:0:0): Bus Device Reset Message Sent 11:40:17 (da0:ahc0:0:0:0): no longer in timeout, status = 353 11:40:17 Unexpected busfree. LASTPHASE == 0xa0 11:40:17 SEQADDR == 0x155 11:41:17 (da0:ahc0:0:0:0): SCB 0x8 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xc 11:41:17 (da0:ahc0:0:0:0): Queuing a BDR SCB 11:41:17 (da0:ahc0:0:0:0): Bus Device Reset Message Sent 11:41:17 (da0:ahc0:0:0:0): no longer in timeout, status = 353 11:41:17 Unexpected busfree. LASTPHASE == 0xa0 11:41:17 SEQADDR == 0x155 11:42:17 (da0:ahc0:0:0:0): SCB 0x1e - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xc 11:42:17 (da0:ahc0:0:0:0): Queuing a BDR SCB 11:42:17 (da0:ahc0:0:0:0): Bus Device Reset Message Sent 11:42:17 (da0:ahc0:0:0:0): no longer in timeout, status = 353 11:42:17 Unexpected busfree. LASTPHASE == 0xa0 11:42:17 SEQADDR == 0x155 11:43:17 (da0:ahc0:0:0:0): SCB 0xe - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xa 11:43:17 (da0:ahc0:0:0:0): Queuing a BDR SCB 11:43:17 (da0:ahc0:0:0:0): Bus Device Reset Message Sent 11:43:17 (da0:ahc0:0:0:0): no longer in timeout, status = 353 11:43:17 Unexpected busfree. LASTPHASE == 0xa0 11:43:17 SEQADDR == 0x155 11:44:17 (da0:ahc0:0:0:0): SCB 0x13 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xb 11:44:17 (da0:ahc0:0:0:0): Queuing a BDR SCB 11:44:17 (da0:ahc0:0:0:0): Bus Device Reset Message Sent 11:44:17 (da0:ahc0:0:0:0): no longer in timeout, status = 353 11:44:17 Unexpected busfree. LASTPHASE == 0xa0 11:44:17 SEQADDR == 0x155 And the boot log: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-19990201-STABLE #1: Wed Feb 3 16:40:07 PST 1999 root@bubba.whistle.com:/usr/src/sys/compile/BUBBA Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II (267.27-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping=4 Features=0x80f9ff real memory = 67108864 (65536K bytes) config> quit avail memory = 62341120 (60880K bytes) Preloaded elf kernel "kernel" at 0xf02bf000. Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x01 on pci0.4.0 ide_pci0: rev 0x01 on pci0.4.1 chip3: rev 0x01 on pci0.4.3 ahc0: rev 0x00 int a irq 9 on pci0.6.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs de0: rev 0x22 int a irq 10 on pci0.11.0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:c0:f0:17:ec:60 vga0: rev 0x00 int a irq 11 on pci0.12.0 Probing for devices on PCI bus 1: Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 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 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 1628MB (3335472 sectors), 3309 cyls, 16 heads, 63 S/T, 512 B/S vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Waiting 3 seconds for SCSI devices to settle de0: enabling 10baseT port changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4341MB (8890760 512 byte sectors: 64H 32S/T 4341C) WARNING: / was not properly dismounted cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.0MB/s transfers (20.0MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 5 12:21:41 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id B83B315151 for ; Fri, 5 Mar 1999 12:21:37 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id NAA01602; Fri, 5 Mar 1999 13:21:07 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903052021.NAA01602@panzer.plutotech.com> Subject: Re: Temporary hang In-Reply-To: <199903051947.LAA72621@bubba.whistle.com> from Archie Cobbs at "Mar 5, 1999 11:47:24 am" To: archie@whistle.com (Archie Cobbs) Date: Fri, 5 Mar 1999 13:21:07 -0700 (MST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Archie Cobbs wrote... > My machine locked up .. but only temporarily. Any ideas what's > going on? > > Here's the relevant kernel output: [ ... ] > 11:44:17 (da0:ahc0:0:0:0): SCB 0x13 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xb > 11:44:17 (da0:ahc0:0:0:0): Queuing a BDR SCB > 11:44:17 (da0:ahc0:0:0:0): Bus Device Reset Message Sent > 11:44:17 (da0:ahc0:0:0:0): no longer in timeout, status = 353 > 11:44:17 Unexpected busfree. LASTPHASE == 0xa0 > 11:44:17 SEQADDR == 0x155 [ ... ] > And the boot log: > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da0: 4341MB (8890760 512 byte sectors: 64H 32S/T 4341C) Your problem is right there. You need to upgrade to the Atlas II LYK8 firmware. It's on ftp.quantum.com. You'll need a bootable DOS floppy with ASPI drivers for your SCSI card to run their firmware loader. You'll probably want to back up the disk before you upgrade the firmware, although I doubt you'll lose any data. I've upgraded 4 Atlas IIs (one of them twice) and haven't lost any data. 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 Fri Mar 5 13:49:11 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from liquid.tpb.net (drum-n-bass.party-animals.com [194.134.94.34]) by hub.freebsd.org (Postfix) with ESMTP id 1C58314C35 for ; Fri, 5 Mar 1999 13:49:07 -0800 (PST) (envelope-from niels@bakker.net) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.3/8.8.8/Debian/GNU) with ESMTP id WAA28280 for ; Fri, 5 Mar 1999 22:48:49 +0100 Date: Fri, 5 Mar 1999 22:48:48 +0100 (CET) From: N X-Sender: niels@liquid.tpb.net To: freebsd-scsi@FreeBSD.ORG Subject: Re: 2940U2W supported? In-Reply-To: Message-ID: <9903052245550.28252-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 5 Mar 1999, Matt Simerson wrote: >> "waiting for SCSI devices to settle" during boot (I'd guess >> it happens at every 10th reboot or something like that). >> This happens both with the Adaptec 2940-U2W and with the >> onboard Adaptec U2W of an ASUS P2B-LS, using 3.1-RELEASE. > I can confirm this behavior. Me too (3.0-CURRENT dating back to January, doing fine until then, and afterwards too. P2B-LS, with another 2940U2W card in a PCI slot. Only LVD devices on the two SCSI buses; one IDE disk.) >> It's extremely annoying, because you cannot reboot such a >> machine remotely and be sure that it comes up again. :-( >> It renders the Adaptec controllers essentially unusable for >> production use. > Why do you have to reboot production servers? Because this particular one crashed. Had to send someone out to lean on the reset button, which worked. -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 5 13:55:15 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from relay8.uu.net (relay8.uu.net [192.48.96.84]) by hub.freebsd.org (Postfix) with ESMTP id 7DBB7152BC for ; Fri, 5 Mar 1999 13:54:57 -0800 (PST) (envelope-from louie@UU.NET) Received: from neserve0.uu.net by relay8.uu.net with ESMTP (peer crosschecked as: neserve0.uu.net [153.39.50.135]) id QQgfgx28824 for ; Fri, 5 Mar 1999 16:54:36 -0500 (EST) Received: from sayshell.corp.us.uu.net by neserve0.uu.net with ESMTP (peer crosschecked as: sayshell.corp.us.uu.net [153.39.251.30]) id QQgfgx21040; Fri, 5 Mar 1999 16:54:18 -0500 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-scsi@freebsd.org From: "Louis A. Mamakos" Subject: problem with aic7880 SCSI controller on CompactPCI system Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_16937519200" Date: Fri, 05 Mar 1999 16:54:18 -0500 Message-ID: <79487.920670858@sayshell.corp.us.uu.net> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multipart MIME message. --==_Exmh_16937519200 Content-Type: text/plain; charset=us-ascii I've got a Motorola CPV5000 CompactPCI based system I'm trying to get FreeBSD running on. This is Pentium-based single board computer in a CompactPCI form factor, with a bunch of on-board peripherals. This board, absent the use of the SCSI controller is known to work pretty will with FreeBSD varients in an embedded system environment. There seems to be a problem with the support of the on-board aic7880 Ultra SCSI controller on the board. If I disable the SCSI controller in the BIOS, then I can boot up just fine, and FreeBSD discovers the on-board 80MB IDE Flash "disk" and starts up sysinstall. When the SCSI controller is enabled, I have the problem listed below. I know that the SCSI bus actually works; I can put a FreeBSD distribution CD in the CDROM drive (SCSI target 6), and boot up just fine, but this is done via the BIOS I/O in /boot/loader. The adaptec SCSI BIOS also finds the two targets on the SCSI bus (the other being a Seagate ST34573W as SCSI target 0). The boot sequence below, captured from the serial console is a result of waiting a few hours for all of the probes to timeout, etc. I think that the complaint about the cable configuration is bogus, in the sense that termination is done automatically based upon connectors being plugged into either of the front panel or internal 68pin SCSI connector; this board doesn't even have a physical 50 pin connector available. There are terminators that are enabled automatically should a SCSI bus connector not have a cable attached. Before I dive into trying to figure this code out, I'd appreciate it if someone has a hint or fix for this these symptoms, or has seen something like this before. I've tried this with a fairly recent 4.0-current, the 3.1-release CD as well as a 3.0 snapshot from last August; I see the same sort of symptoms. Even after enduring the multi-hour wait for all this to happen, the disk and CDROM drive don't get attached as da0 and cd0; the best that happens is they get attached as pass0 and pass1. Thanks in advance for any pointers, hints or fixes. Louis Mamakos --==_Exmh_16937519200 Content-Type: text/plain ; name="boot2.log"; charset=us-ascii Content-Description: boot.log Content-Disposition: attachment; filename="cpciboot2.log" Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 FreeBSD/i386 bootstrap loader, Revision 0.5 639/65535kB (root@usw2.freebsd.org, Wed Mar 3 13:32:57 GMT 1999) /kernel text=0x1b8f82 data=0x1dc50+0x20978 syms=[0x4+0x25660+0x2508a] Please insert MFS root floppy and press enter: BIOS basemem (639K) != RTC basemem (640K), setting to BIOS value Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #2: Fri Mar 5 10:06:52 EST 1999 louie@sayshell.corp.us.uu.net:/y/louie/src/sys/compile/GENERIC Calibrating clock(s) ... TSC clock: 233915951 Hz, i8254 clock: 1193450 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 233864239 Hz CPU: Pentium/P55C (233.86-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping=3 Features=0x8001bf real memory = 134217728 (131072K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00621000 - 0x07ff3fff, 127741952 bytes (31187 pages) avail memory = 124293120 (121380K bytes) Found BIOS32 Service Directory header at 0xf00fdb70 Entry = 0xfdb80 (0xf00fdb80) Rev = 0 Len = 1 PCI BIOS entry at 0xdba1 SMIBIOS header at 0xf00f0070 Version 2.0 Table at 0xf0480, 24 entries, 920 bytes, largest entry 116 bytes DMI header at 0xf00f0080 Version 2.0 Table at 0xf0480, 24 entries, 920 bytes Other BIOS signatures found: ACPI: 00000000 $PnP: 000f7c10 Preloaded elf kernel "kernel" at 0xf0614000. Preloaded mfs_root "/mfsroot" at 0xf061409c. Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x80000058 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=12508086) Probing for devices on PCI bus 0: found-> vendor=0x8086, dev=0x1250, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip0: rev 0x03 on pci0.0.0 found-> vendor=0x8086, dev=0x7000, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip1: rev 0x01 on pci0.7.0 I/O Recovery Timing: 8-bit 1 clocks, 16-bit 1 clocks Extended BIOS: enabled Lower BIOS: enabled Coprocessor IRQ13: enabled Mouse IRQ12: enabled Interrupt Routing: A: disabled, B: IRQ9, C: disabled, D: IRQ10 MB0: IRQ15, MB1: found-> vendor=0x8086, dev=0x7010, revid=0x00 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 0000ffa0, size 4 ide_pci0: rev 0x00 on pci0.7.1 intel_piix_status: primary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: primary master fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled intel_piix_status: primary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 0 status: 04 from port: 0000ffa2 intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: secondary master fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 1 status: 04 from port: 0000ffaa found-> vendor=0x8086, dev=0x7020, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=10 map[0]: type 4, range 32, base 0000ef40, size 5 found-> vendor=0x9004, dev=0x8078, revid=0x01 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 4, range 32, base 0000ec00, size 8 map[1]: type 1, range 32, base ffaf7000, size 12 ahc0: rev 0x01 int a irq 10 on pci0.17.0 ahc0: Reading SEEPROM...done. ahc0: internal 50 cable is present, internal 68 cable is present ahc0: external cable is present ahc0: BIOS eeprom not present ahc0: Illegal cable configuration!!. Only two connectors on the adapter may be used at a time! ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: Downloading Sequencer Program... 413 instructions downloaded found-> vendor=0x1011, dev=0x0022, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 chip2: rev 0x03 on pci0.18.0 found-> vendor=0x1013, dev=0x00b8, revid=0x00 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 3, range 32, base fd000000, size 24 vga0: rev 0x00 on pci0.19.0 found-> vendor=0x8086, dev=0x1229, revid=0x05 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 3, range 32, base febff000, size 12 map[1]: type 4, range 32, base 0000ef80, size 5 map[2]: type 1, range 32, base ff900000, size 20 fxp0: rev 0x05 int a irq 9 on pci0.20.0 fxp0: Ethernet address 08:00:3e:28:ff:b9 Probing for devices on PCI bus 1: found-> vendor=0x12e2, dev=0x4013, revid=0x02 class=ff-ff-ff, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 1, range 32, base ff5ff000, size 12 map[1]: type 1, range 32, base ff5fe000, size 12 Initializing PnP override table Probing for PnP devices: Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 No Plug-n-Play devices were found Probing for devices on the ISA bus: atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa sc0 on isa sc0: fb0 kbd0 sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 fe0 not found at 0x300 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0: atkbd0, AT 101/102 (2), config:0x10000, flags:0x3d0000 psm0: current command byte:0065 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 psm0: failed to reset the aux device. psm0 not found sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A, console sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2: disabled, not probed. sio3: disabled, not probed. ppc0 not found fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 80MB (163840 sectors), 640 cyls, 8 heads, 32 S/T, 512 B/S wd0: ATA INQUIRE valid = 0001, dmamword = 0000, apio = 0000, udma = 0000 wdc1 not found at 0x170 wt0 not found at 0x300 mcd0: timeout getting status mcd0 not found at 0x300 matcdc0 not found at 0x230 scd0 not found at 0x230 ie0: unknown board_id: f000 ie0 not found at 0x300 ep0 not found at 0x300 ex0 not found le0 not found at 0x300 lnc0 not found at 0x280 ze0 not found at 0x300 zp0 not found at 0x300 cs0 not found at 0x300 adv0 not found at 0x330 bt0: Failed Status Reg Test - ff bt0: Failed Status Reg Test - ff bt0: Failed Status Reg Test - ff bt0: Failed Status Reg Test - ff bt0: Failed Status Reg Test - ff bt0: Failed Status Reg Test - ff bt0 not found at 0x134 aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff aha0 not found at 0x134 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xf00b8000 size:32k gran:32k, buf:0x0 size:0k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff npx0 on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 175377060 bytes/sec bzero() bandwidth = 88589652 bytes/sec apm0: disabled, not probed. imasks: bio c0084040, tty c007021a, net c007021a BIOS Geometries: 0:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 1:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 2:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 3:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 4:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 5:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 6:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 7:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 0 accounted for Device configuration finished. Intel Pentium detected, installing workaround for F00F bug new masks: bio c0084040, tty c007021a, net c007021a Waiting 15 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. (probe0:ahc0:0:0:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): Queuing a BDR SCB (probe0:ahc0:0:0:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 15 SCBs aborted (probe1:ahc0:0:1:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:1:0): Queuing a BDR SCB (probe1:ahc0:0:1:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:1:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 15 SCBs aborted (probe2:ahc0:0:2:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe2:ahc0:0:2:0): Queuing a BDR SCB (probe2:ahc0:0:2:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe2:ahc0:0:2:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 15 SCBs aborted ahc0: Selection Timeout on A:3. 1 SCBs aborted (probe4:ahc0:0:4:0): SCB 0xe - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe4:ahc0:0:4:0): Queuing a BDR SCB (probe4:ahc0:0:4:0): SCB 0xe - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe4:ahc0:0:4:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 14 SCBs aborted ahc0: Selection Timeout on A:5. 1 SCBs aborted (probe6:ahc0:0:6:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): Queuing a BDR SCB (probe6:ahc0:0:6:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 13 SCBs aborted ahc0: Selection Timeout on A:8. 1 SCBs aborted (probe8:ahc0:0:9:0): SCB 0xd - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe8:ahc0:0:9:0): Queuing a BDR SCB (probe8:ahc0:0:9:0): SCB 0xd - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe8:ahc0:0:9:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 12 SCBs aborted ahc0: Selection Timeout on A:10. 1 SCBs aborted ahc0: Selection Timeout on A:11. 1 SCBs aborted (probe11:ahc0:0:12:0): SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe11:ahc0:0:12:0): Queuing a BDR SCB (probe11:ahc0:0:12:0): SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe11:ahc0:0:12:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 10 SCBs aborted ahc0: Selection Timeout on A:13. 1 SCBs aborted (probe13:ahc0:0:14:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe13:ahc0:0:14:0): Queuing a BDR SCB (probe13:ahc0:0:14:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe13:ahc0:0:14:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 9 SCBs aborted (probe14:ahc0:0:15:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe14:ahc0:0:15:0): Queuing a BDR SCB (probe14:ahc0:0:15:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe14:ahc0:0:15:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 9 SCBs aborted ahc0: Selection Timeout on A:1. 1 SCBs aborted (probe2:ahc0:0:2:0): SCB 0xa - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe2:ahc0:0:2:0): Queuing a BDR SCB (probe2:ahc0:0:2:0): SCB 0xa - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe2:ahc0:0:2:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 8 SCBs aborted (probe4:ahc0:0:4:0): SCB 0xa - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe4:ahc0:0:4:0): Queuing a BDR SCB (probe4:ahc0:0:4:0): SCB 0xa - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe4:ahc0:0:4:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 8 SCBs aborted (probe6:ahc0:0:6:0): SCB 0xa - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): Queuing a BDR SCB (probe6:ahc0:0:6:0): SCB 0xa - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 8 SCBs aborted (probe8:ahc0:0:9:0): SCB 0xa - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe8:ahc0:0:9:0): Queuing a BDR SCB (probe8:ahc0:0:9:0): SCB 0xa - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe8:ahc0:0:9:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 8 SCBs aborted ahc0: Selection Timeout on A:12. 1 SCBs aborted ahc0: Selection Timeout on A:14. 1 SCBs aborted (probe14:ahc0:0:15:0): SCB 0x8 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe14:ahc0:0:15:0): Queuing a BDR SCB (probe14:ahc0:0:15:0): SCB 0x8 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe14:ahc0:0:15:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 6 SCBs aborted (probe0:ahc0:0:0:0): SCB 0x8 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): Queuing a BDR SCB (probe0:ahc0:0:0:0): SCB 0x8 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 6 SCBs aborted ahc0: Selection Timeout on A:2. 1 SCBs aborted (probe4:ahc0:0:4:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe4:ahc0:0:4:0): Queuing a BDR SCB (probe4:ahc0:0:4:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe4:ahc0:0:4:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 5 SCBs aborted (probe6:ahc0:0:6:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): Queuing a BDR SCB (probe6:ahc0:0:6:0): SCB 0x7 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 5 SCBs aborted ahc0: Selection Timeout on A:9. 1 SCBs aborted (probe14:ahc0:0:15:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe14:ahc0:0:15:0): Queuing a BDR SCB (probe14:ahc0:0:15:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe14:ahc0:0:15:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 4 SCBs aborted (probe0:ahc0:0:0:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): Queuing a BDR SCB (probe0:ahc0:0:0:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 4 SCBs aborted (probe6:ahc0:0:6:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): Queuing a BDR SCB (probe6:ahc0:0:6:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 4 SCBs aborted ahc0: Selection Timeout on A:15. 1 SCBs aborted (probe0:ahc0:0:0:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): Queuing a BDR SCB (probe0:ahc0:0:0:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 3 SCBs aborted (probe4:ahc0:0:4:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe4:ahc0:0:4:0): Queuing a BDR SCB (probe4:ahc0:0:4:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe4:ahc0:0:4:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 3 SCBs aborted (probe0:ahc0:0:0:0): SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): Queuing a BDR SCB (probe0:ahc0:0:0:0): SCB 0x5 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 3 SCBs aborted ahc0: Selection Timeout on A:4. 1 SCBs aborted (probe6:ahc0:0:6:0): SCB 0x4 - timed out in message in phase, SEQADDR == 0x18c (probe6:ahc0:0:6:0): BDR message in message buffer (probe6:ahc0:0:6:0): SCB 0x4 - timed out in message in phase, SEQADDR == 0x18c (probe6:ahc0:0:6:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe0:ahc0:0:0:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): Queuing a BDR SCB (probe0:ahc0:0:0:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe6:ahc0:0:6:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): Queuing a BDR SCB (probe6:ahc0:0:6:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe0:ahc0:0:0:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): Queuing a BDR SCB (probe0:ahc0:0:0:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe6:ahc0:0:6:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): Queuing a BDR SCB (probe6:ahc0:0:6:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe0:ahc0:0:0:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): Queuing a BDR SCB (probe0:ahc0:0:0:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe6:ahc0:0:6:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): Queuing a BDR SCB (probe6:ahc0:0:6:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe0:ahc0:0:0:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): Queuing a BDR SCB (probe0:ahc0:0:0:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe6:ahc0:0:6:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): Queuing a BDR SCB (probe6:ahc0:0:6:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe6:ahc0:0:6:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe0:ahc0:0:0:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): Queuing a BDR SCB (probe0:ahc0:0:0:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe0:ahc0:0:0:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): Queuing a BDR SCB (probe0:ahc0:0:0:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted ahc0: target 6 synchronous at 10.0MHz, offset = 0xf (probe0:ahc0:0:0:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): Queuing a BDR SCB (probe0:ahc0:0:0:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: target 6 using asynchronous transfers ahc0: Issued Channel A Bus Reset. 2 SCBs aborted ahc0: target 6 synchronous at 10.0MHz, offset = 0xf (probe0:ahc0:0:0:1): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:1): Queuing a BDR SCB (probe0:ahc0:0:0:1): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:1): no longer in timeout, status = 34b ahc0: target 6 using asynchronous transfers ahc0: Issued Channel A Bus Reset. 2 SCBs aborted ahc0: target 6 synchronous at 10.0MHz, offset = 0xf (probe0:ahc0:0:0:1): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:1): Queuing a BDR SCB (probe0:ahc0:0:0:1): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:1): no longer in timeout, status = 34b ahc0: target 6 using asynchronous transfers ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe1:ahc0:0:6:4): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:4): Queuing a BDR SCB (probe1:ahc0:0:6:4): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:4): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe0:ahc0:0:0:1): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:1): Queuing a BDR SCB (probe0:ahc0:0:0:1): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:1): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted ahc0: target 6 synchronous at 10.0MHz, offset = 0xf (probe0:ahc0:0:0:1): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:1): Queuing a BDR SCB (probe0:ahc0:0:0:1): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:1): no longer in timeout, status = 34b ahc0: target 6 using asynchronous transfers ahc0: Issued Channel A Bus Reset. 2 SCBs aborted ahc0: target 6 synchronous at 10.0MHz, offset = 0xf (probe0:ahc0:0:0:1): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:1): Queuing a BDR SCB (probe0:ahc0:0:0:1): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:1): no longer in timeout, status = 34b ahc0: target 6 using asynchronous transfers ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe1:ahc0:0:6:6): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:6): Queuing a BDR SCB (probe1:ahc0:0:6:6): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:6): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted ahc0: target 0 using 16bit transfers ahc0: target 0 synchronous at 10.0MHz, offset = 0x8 (probe0:ahc0:0:0:2): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:2): Queuing a BDR SCB (probe0:ahc0:0:0:2): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:2): no longer in timeout, status = 34b ahc0: target 0 using 8bit transfers ahc0: target 0 using asynchronous transfers ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe0:ahc0:0:0:2): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:2): Queuing a BDR SCB (probe0:ahc0:0:0:2): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:2): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe1:ahc0:0:6:6): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:6): Queuing a BDR SCB (probe1:ahc0:0:6:6): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:6): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe0:ahc0:0:0:2): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:2): Queuing a BDR SCB (probe0:ahc0:0:0:2): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:2): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe1:ahc0:0:6:6): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:6): Queuing a BDR SCB (probe1:ahc0:0:6:6): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:6): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe0:ahc0:0:0:2): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:2): Queuing a BDR SCB (probe0:ahc0:0:0:2): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:2): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe1:ahc0:0:6:6): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:6): Queuing a BDR SCB (probe1:ahc0:0:6:6): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:6): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe0:ahc0:0:0:2): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:2): Queuing a BDR SCB (probe0:ahc0:0:0:2): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:2): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe1:ahc0:0:6:6): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:6): Queuing a BDR SCB (probe1:ahc0:0:6:6): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:6): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe0:ahc0:0:0:3): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:3): Queuing a BDR SCB (probe0:ahc0:0:0:3): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:3): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe1:ahc0:0:6:7): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:7): Queuing a BDR SCB (probe1:ahc0:0:6:7): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:7): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe0:ahc0:0:0:3): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:3): Queuing a BDR SCB (probe0:ahc0:0:0:3): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:3): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe1:ahc0:0:6:7): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:7): Queuing a BDR SCB (probe1:ahc0:0:6:7): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:7): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted ahc0: target 0 using 16bit transfers ahc0: target 0 synchronous at 10.0MHz, offset = 0x8 (probe0:ahc0:0:0:3): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:3): Queuing a BDR SCB (probe0:ahc0:0:0:3): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:3): no longer in timeout, status = 34b ahc0: target 0 using 8bit transfers ahc0: target 0 using asynchronous transfers ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe0:ahc0:0:0:3): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:3): Queuing a BDR SCB (probe0:ahc0:0:0:3): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:3): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe1:ahc0:0:6:7): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:7): Queuing a BDR SCB (probe1:ahc0:0:6:7): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:7): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe0:ahc0:0:0:3): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:3): Queuing a BDR SCB (probe0:ahc0:0:0:3): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:3): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe1:ahc0:0:6:7): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:7): Queuing a BDR SCB (probe1:ahc0:0:6:7): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:7): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe0:ahc0:0:0:4): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:4): Queuing a BDR SCB (probe0:ahc0:0:0:4): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:4): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe1:ahc0:0:6:7): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:7): Queuing a BDR SCB (probe1:ahc0:0:6:7): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe1:ahc0:0:6:7): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe0:ahc0:0:0:4): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:4): Queuing a BDR SCB (probe0:ahc0:0:0:4): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:4): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted ahc0: target 0 using 16bit transfers ahc0: target 0 synchronous at 10.0MHz, offset = 0x8 (probe0:ahc0:0:0:5): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:5): Queuing a BDR SCB (probe0:ahc0:0:0:5): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:5): no longer in timeout, status = 34b ahc0: target 0 using 8bit transfers ahc0: target 0 using asynchronous transfers ahc0: Issued Channel A Bus Reset. 1 SCBs aborted (probe0:ahc0:0:0:5): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:5): Queuing a BDR SCB (probe0:ahc0:0:0:5): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:5): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted (probe0:ahc0:0:0:5): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:5): Queuing a BDR SCB (probe0:ahc0:0:0:5): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:5): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted (probe0:ahc0:0:0:5): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:5): Queuing a BDR SCB (probe0:ahc0:0:0:5): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:5): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted (probe0:ahc0:0:0:5): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:5): Queuing a BDR SCB (probe0:ahc0:0:0:5): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:5): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted (probe0:ahc0:0:0:6): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:6): Queuing a BDR SCB (probe0:ahc0:0:0:6): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:6): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted (probe0:ahc0:0:0:6): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:6): Queuing a BDR SCB (probe0:ahc0:0:0:6): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:6): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted (probe0:ahc0:0:0:6): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:6): Queuing a BDR SCB (probe0:ahc0:0:0:6): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:6): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted (probe0:ahc0:0:0:6): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:6): Queuing a BDR SCB (probe0:ahc0:0:0:6): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:6): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted (probe0:ahc0:0:0:6): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:6): Queuing a BDR SCB (probe0:ahc0:0:0:6): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:6): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted (probe0:ahc0:0:0:7): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:7): Queuing a BDR SCB (probe0:ahc0:0:0:7): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:7): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted (probe0:ahc0:0:0:7): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:7): Queuing a BDR SCB (probe0:ahc0:0:0:7): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:7): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted (probe0:ahc0:0:0:7): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:7): Queuing a BDR SCB (probe0:ahc0:0:0:7): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (probe0:ahc0:0:0:7): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted ahc0: target 0 using 16bit transfers ahc0: target 0 synchronous at 10.0MHz, offset = 0x8 pass0 at ahc0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled pass1 at ahc0 bus 0 target 6 lun 0 pass1: Removable CD-ROM SCSI-2 device pass1: 3.300MB/s transfers Considering MFS root f/s. changing root device to fd0c rootfs is 2880 Kbyte compiled in MFS /stand/sysinstall running as init on serial console These are the predefined terminal types available to sysinstall when running stand-alone. Please choose the closest match for your particular terminal. 1 ...................... Standard ANSI terminal. 2 ...................... VT100 or compatible terminal. 3 ...................... FreeBSD system console (color). 4 ...................... FreeBSD system console (monochrome). Your choice: (1-4) (da0:ahc0:0:0:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (da0:ahc0:0:0:0): Queuing a BDR SCB (da0:ahc0:0:0:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (da0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: target 0 using 8bit transfers ahc0: target 0 using asynchronous transfers ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (da0:ahc0:0:0:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (da0:ahc0:0:0:0): SCB 4: Immediate reset. Flags = 0x4040 (da0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (da0:ahc0:0:0:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (da0:ahc0:0:0:0): Queuing a BDR SCB (da0:ahc0:0:0:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (da0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (da0:ahc0:0:0:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (da0:ahc0:0:0:0): SCB 4: Immediate reset. Flags = 0x4040 (da0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted ahc0: target 0 using 16bit transfers ahc0: target 0 synchronous at 10.0MHz, offset = 0x8 (da0:ahc0:0:0:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (da0:ahc0:0:0:0): Queuing a BDR SCB (da0:ahc0:0:0:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (da0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: target 0 using 8bit transfers ahc0: target 0 using asynchronous transfers ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (da0:ahc0:0:0:0): got CAM status 0x14b (da0:ahc0:0:0:0): fatal error, failed to attach to device (da0:ahc0:0:0:0): lost device (da0:ahc0:0:0:0): removing device entry (cd0:ahc0:0:6:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (cd0:ahc0:0:6:0): Queuing a BDR SCB (cd0:ahc0:0:6:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (cd0:ahc0:0:6:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted (cd0:ahc0:0:6:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (cd0:ahc0:0:6:0): Queuing a BDR SCB (cd0:ahc0:0:6:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x18c (cd0:ahc0:0:6:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted (cd0:ahc0:0:6:0): got CAM status 0x14b (cd0:ahc0:0:6:0): fatal error, failed to attach to device (cd0:ahc0:0:6:0): lost device (cd0:ahc0:0:6:0): removing device entry Invalid choice, please try again. These are the predefined terminal types available to sysinstall when running stand-alone. Please choose the closest match for your particular terminal. 1 ...................... Standard ANSI terminal. 2 ...................... VT100 or compatible terminal. 3 ...................... FreeBSD system console (color). 4 ...................... FreeBSD system console (monochrome). Your choice: (1-4) Invalid choice, please try again. These are the predefined terminal types available to sysinstall when running stand-alone. Please choose the closest match for your particular terminal. 1 ...................... Standard ANSI terminal. 2 ...................... VT100 or compatible terminal. 3 ...................... FreeBSD system console (color). 4 ...................... FreeBSD system console (monochrome). Your choice: (1-4) --==_Exmh_16937519200-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 5 14:53: 5 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id 9C36A14E31 for ; Fri, 5 Mar 1999 14:53:01 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.1/8.9.1) with ESMTP id PAA24095; Fri, 5 Mar 1999 15:52:04 -0700 (MST) (envelope-from gibbs@plutotech.com) Message-Id: <199903052252.PAA24095@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Louis A. Mamakos" Cc: scsi@FreeBSD.org Subject: Re: problem with aic7880 SCSI controller on CompactPCI system In-reply-to: Your message of "Fri, 05 Mar 1999 16:54:18 EST." <79487.920670858@sayshell.corp.us.uu.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Mar 1999 15:43:07 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I've got a Motorola CPV5000 CompactPCI based system I'm trying to get >FreeBSD running on. The CPV5000 uses the Intel 430HX (rev 3.) chipset. There is an incompatibility between this particular revision of this particular intel chipset and the Adaptec aic7880 Rev B. The only workaround I know of to this problem is to disable memory write line and memory read line PCI transactions performed by the adaptec part. You can do this by setting the cache size as known to the aic7880 to 0. Somewhere in sys/pci/ahc_pci.c:ahc_pci_attach(), add code similar to this: u_int32_t csize_lattime; csize_lattime = pci_conf_read(config_id, CSIZE_LATTIME); csize_lattime &= ~CACHESIZE; pci_conf_write(config_id, CSIZE_LATTIME, csize_lattime); There is likely a more efficient work around for this problem, but I have not been able to get sufficient information from Adaptec to develop one. Since I have not had the necessary equipment to reproduce this error here (where I have a PCI bus analyzer) my hope of determining a better solution myself are rather slim. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 5 17:22:41 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from k6n1.znh.org (unknown [207.109.235.16]) by hub.freebsd.org (Postfix) with ESMTP id 6C9A2152AD for ; Fri, 5 Mar 1999 17:20:42 -0800 (PST) (envelope-from zach@uffdaonline.net) Received: (from zach@localhost) by k6n1.znh.org (8.9.3/8.9.1) id BAA26788 for scsi@freebsd.org; Sat, 6 Mar 1999 01:19:14 GMT (envelope-from zach) Message-ID: <19990305191914.A26718@znh.org> Date: Fri, 5 Mar 1999 19:19:14 -0600 From: Zach Heilig To: scsi@freebsd.org Subject: 'camcontrol rescan' wierdness Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I had a CD-ROM temporarily attached to one of the SCSI busses in my computer. All SCSI devices at this point (from boot-up messages): [the drives are on the slower narrow scsi controller because one is a wide drive, and I didn't have a wide cable when I assembled this computer] ahc0: rev 0x00 int a irq 10 on pci0.11.0 ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs ncr0: rev 0x04 int a irq 10 on pci0.13.0 Waiting 2 seconds for SCSI devices to settle changing root device to da0s1a da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 2014MB (4124736 512 byte sectors: 255H 63S/T 256C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 4095MB (8386733 512 byte sectors: 255H 63S/T 522C) cd1 at ncr0 bus 0 target 5 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 10.000MB/s transfers (10.000MHz, offset 8) cd1: Attempt to query device size failed: NOT READY, Medium not present - tray closed da2 at ncr0 bus 0 target 6 lun 0 da2: Removable Direct Access SCSI-2 device da2: 3.300MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present cd0 at ahc0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: cd present [195547 x 2048 byte records] Later, I removed cd0, and re-scanned both busses: [and noted that external CDR on ncr0 was powered off (oops!), and rescanned the ncr bus]: (cd0:ahc0:0:5:0): lost device (cd0:ahc0:0:5:0): removing device entry (da3:ahc0:0:1:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 (da3:ahc0:0:1:1): ILLEGAL REQUEST asc:25,0 (da3:ahc0:0:1:1): Logical unit not supported sks:c0,1 (da3:ahc0:0:1:1): fatal error, failed to attach to device (da3:ahc0:0:1:1): lost device (da3:ahc0:0:1:1): removing device entry (cd1:ncr0:0:5:0): lost device (cd1:ncr0:0:5:0): removing device entry cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed (da1:ahc0:0:1:0): SCB 0x53 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xb (da1:ahc0:0:1:0): Queuing a BDR SCB (da1:ahc0:0:1:0): Bus Device Reset Message Sent (da1:ahc0:0:1:0): no longer in timeout, status = 353 Unexpected busfree. LASTPHASE == 0xa0 SEQADDR == 0x151 (probe0:ahc0:0:1:2): SCB 0x22 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xa (probe0:ahc0:0:1:2): Queuing a BDR SCB (probe0:ahc0:0:1:2): Bus Device Reset Message Sent (probe0:ahc0:0:1:2): no longer in timeout, status = 353 Unexpected busfree. LASTPHASE == 0xa0 SEQADDR == 0x151 (probe0:ahc0:0:1:3): SCB 0x22 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xc (probe0:ahc0:0:1:3): Queuing a BDR SCB (probe0:ahc0:0:1:3): Bus Device Reset Message Sent (probe0:ahc0:0:1:3): no longer in timeout, status = 353 Unexpected busfree. LASTPHASE == 0xa0 SEQADDR == 0x151 (probe0:ahc0:0:1:4): SCB 0x22 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xb (probe0:ahc0:0:1:4): Queuing a BDR SCB (probe0:ahc0:0:1:4): Bus Device Reset Message Sent (probe0:ahc0:0:1:4): no longer in timeout, status = 353 Unexpected busfree. LASTPHASE == 0xa0 SEQADDR == 0x151 (probe0:ahc0:0:1:5): SCB 0x22 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x9 (probe0:ahc0:0:1:5): Queuing a BDR SCB (probe0:ahc0:0:1:5): Bus Device Reset Message Sent (probe0:ahc0:0:1:5): no longer in timeout, status = 353 Unexpected busfree. LASTPHASE == 0xa0 SEQADDR == 0x151 (probe0:ahc0:0:1:6): SCB 0x22 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x9 (probe0:ahc0:0:1:6): Queuing a BDR SCB (probe0:ahc0:0:1:6): Bus Device Reset Message Sent (probe0:ahc0:0:1:6): no longer in timeout, status = 353 Unexpected busfree. LASTPHASE == 0xa0 SEQADDR == 0x151 (probe0:ahc0:0:1:7): SCB 0x22 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x9 (probe0:ahc0:0:1:7): Queuing a BDR SCB (probe0:ahc0:0:1:7): Bus Device Reset Message Sent (probe0:ahc0:0:1:7): no longer in timeout, status = 353 Unexpected busfree. LASTPHASE == 0xa0 SEQADDR == 0x151 and 'camcontrol devlist' now prints out: < > at scbus-1 target -1 lun -1 (xpt0) at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 1 lun 0 (pass1,da1) < > at scbus0 target 1 lun 1 (pass2) < > at scbus0 target -1 lun -1 () at scbus1 target 5 lun 0 (cd0,pass3) at scbus1 target 6 lun 0 (pass4,da2) < > at scbus1 target -1 lun -1 () [note the bogus pass2 entry] -- Zach Heilig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 5 19:58: 7 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6B18A14E51 for ; Fri, 5 Mar 1999 19:57:58 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony [10.0.0.6]) by rover.village.org (8.9.3/8.6.6) with ESMTP id DAA45007; Sat, 6 Mar 1999 03:57:41 GMT Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id UAA04203; Fri, 5 Mar 1999 20:57:34 -0700 (MST) Message-Id: <199903060357.UAA04203@harmony.village.org> To: Benjamin Oliver Trigona-Harany Subject: Re: Tape drive Help Please!! Cc: freebsd-scsi@FreeBSD.ORG In-reply-to: Your message of "Thu, 04 Mar 1999 12:59:04 PST." References: Date: Fri, 05 Mar 1999 20:57:34 -0700 From: Warner Losh Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Benjamin Oliver Trigona-Harany writes: : st0(aic0:2:0): timed out : What am I doing wrong?? Here's the relevant boot info, if seems to be : detecting everything properly. You are using the aic drive. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 5 20:16: 6 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id D8B8515043 for ; Fri, 5 Mar 1999 20:15:41 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-216-180-14-195.dialup.HiWAAY.net [216.180.14.195]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id WAA16853 for ; Fri, 5 Mar 1999 22:15:22 -0600 (CST) Received: from nospam.hiwaay.net (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.2/8.9.2) with ESMTP id WAA04371 for ; Fri, 5 Mar 1999 22:15:17 -0600 (CST) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199903060415.WAA04371@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-scsi@freebsd.org From: David Kelly Subject: SA performance (was: rc5des slows tape thruput) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Mar 1999 22:15:17 -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Started this in -stable last week and got some useful suggestions such as to increase the kernel HZ, or to alter real-time priorities. Haven't pursued either as both would be useful for characterizing the problem but not for solving it. Just as my observation that rc5des was a simple way to illustrate the problem with only one tape drive. The other reason is while I installed this particular system last month its now at another contractor and I have to use it now as a regular user. :-( Background: the machine is a P-II 233 MHz with 64MB of RAM, onboard Adaptec UW-SCSI, and two Asus SC875 UW-SCSI PCI cards. Seagate 9G HD is on the Adaptec. Two Seagate Scorpion-24 DDS-3 tape drives are on each of the two SC875's for a total of 4 tape drives. We like to make tapes. I've written (copied) 180 tapes on this system in the past several weeks. What I usually do is use tcopy or dd to copy the original tape to disk. Then tcopy it to the new tapes, running 4 instances of tcopy, one per tape drive. Strangely on DDS-1 tape this runs just under 700k/sec per tape drive. But on DDS-3 it drops to 550k. Reading a single DDS-3 tape generated this way runs right at 1MB/sec. Doesn't much matter if its tcopy or tar doing the reading or writing. Tcopy DDS-3 tape to DDS-3 tape crawls at 300k/sec. Doesn't seem to matter if the tape drives are on the same SCSI controller or not. When its 5G of data and it only runs at 1/3 the expected rate, its a concern. Also when writing a tape slowly like this one puts more tape between blocks and/or causes the drive to start/stop a lot. Am guessing only one chunk of data gets queued to be written then the calling process (tcopy) blocks until the tape drive completes the transfer. Then tcopy is placed in the runable queue and restarted by the scheduler the next time around. It may be the process is blocked not because the write hasn't completed but because another chunk was queued and the tape drive reports its busy? Reading the Conner "DAT Tape Drives and Autoloaders SCSI Manual, October 1995" suggests this should not happen until the tape drive's RAM buffers are filled. These drives have 2M of RAM and should be able to suck up a lot of data before throttling. Watching with "systat -v" doesn't show any such burst of I/O. If this is the case then could CAM be interpreting the result codes from the tape wrong, that the tape really could accept more data? Preventing the user process from blocking? Reading scsi_sa.c reinforces the feeling I'm way over my head. Reading mtio(4) thought I'd found gold, MTCACHE, but I can make enough sense out of scsi_sa.c that MTCACHE/MTNOCACHE are no-ops. The Conner book says, "Buffered Mode allows the most efficient operation of the DAT drive. the drive defaults to Buffered mode." (exact quote including screwy capitalization.) Page 26. So buffered mode is the default? Then how is it disabled and/or enabled? Somewhere in physio() and sastrategy() are probably the keys to the blocking behavior. Top(1) shows the process run state is "physst". With any luck this message won't be a waste of your time and mine, and somebody will make sense of what I'm observing and produce a cure. Would expect this to increase everybody's backup performance. -- 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 Fri Mar 5 21:25: 1 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DF1114FC3 for ; Fri, 5 Mar 1999 21:24:45 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id WAA04079; Fri, 5 Mar 1999 22:23:44 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199903060523.WAA04079@panzer.plutotech.com> Subject: Re: 'camcontrol rescan' wierdness In-Reply-To: <19990305191914.A26718@znh.org> from Zach Heilig at "Mar 5, 1999 7:19:14 pm" To: zach@uffdaonline.net (Zach Heilig) Date: Fri, 5 Mar 1999 22:23:44 -0700 (MST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (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 Zach Heilig wrote... > I had a CD-ROM temporarily attached to one of the SCSI busses in my computer. > All SCSI devices at this point (from boot-up messages): > > [the drives are on the slower narrow scsi controller because one is a > wide drive, and I didn't have a wide cable when I assembled this computer] > > ahc0: rev 0x00 int a irq 10 on pci0.11.0 > ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs > ncr0: rev 0x04 int a irq 10 on pci0.13.0 > > Waiting 2 seconds for SCSI devices to settle > changing root device to da0s1a > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > da1: 2014MB (4124736 512 byte sectors: 255H 63S/T 256C) > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > da0: 4095MB (8386733 512 byte sectors: 255H 63S/T 522C) > cd1 at ncr0 bus 0 target 5 lun 0 > cd1: Removable CD-ROM SCSI-2 device > cd1: 10.000MB/s transfers (10.000MHz, offset 8) > cd1: Attempt to query device size failed: NOT READY, Medium not present - tray closed > da2 at ncr0 bus 0 target 6 lun 0 > da2: Removable Direct Access SCSI-2 device > da2: 3.300MB/s transfers > da2: Attempt to query device size failed: NOT READY, Medium not present > cd0 at ahc0 bus 0 target 5 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 10.000MB/s transfers (10.000MHz, offset 15) > cd0: cd present [195547 x 2048 byte records] > > Later, I removed cd0, and re-scanned both busses: [and noted that external > CDR on ncr0 was powered off (oops!), and rescanned the ncr bus]: > > (cd0:ahc0:0:5:0): lost device > (cd0:ahc0:0:5:0): removing device entry That looks normal, cd0 goes away. > (da3:ahc0:0:1:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 > (da3:ahc0:0:1:1): ILLEGAL REQUEST asc:25,0 > (da3:ahc0:0:1:1): Logical unit not supported sks:c0,1 > (da3:ahc0:0:1:1): fatal error, failed to attach to device > (da3:ahc0:0:1:1): lost device > (da3:ahc0:0:1:1): removing device entry It looks like that disk may have trouble with multi-lun probing. It's hard to say. > (cd1:ncr0:0:5:0): lost device > (cd1:ncr0:0:5:0): removing device entry Yeah, the CD-R was powered off. > cd0 at ncr0 bus 0 target 5 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 10.000MB/s transfers (10.000MHz, offset 8) > cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed Okay, this is interesting. Did you turn the power back on or something? > (da1:ahc0:0:1:0): SCB 0x53 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xb > (da1:ahc0:0:1:0): Queuing a BDR SCB > (da1:ahc0:0:1:0): Bus Device Reset Message Sent > (da1:ahc0:0:1:0): no longer in timeout, status = 353 > Unexpected busfree. LASTPHASE == 0xa0 > SEQADDR == 0x151 > (probe0:ahc0:0:1:2): SCB 0x22 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xa > (probe0:ahc0:0:1:2): Queuing a BDR SCB > (probe0:ahc0:0:1:2): Bus Device Reset Message Sent > (probe0:ahc0:0:1:2): no longer in timeout, status = 353 > Unexpected busfree. LASTPHASE == 0xa0 > SEQADDR == 0x151 > (probe0:ahc0:0:1:3): SCB 0x22 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xc > (probe0:ahc0:0:1:3): Queuing a BDR SCB > (probe0:ahc0:0:1:3): Bus Device Reset Message Sent > (probe0:ahc0:0:1:3): no longer in timeout, status = 353 > Unexpected busfree. LASTPHASE == 0xa0 > SEQADDR == 0x151 [ ... ] It appears that your Quantum disk is getting confused and responding on multiple LUNs. > and 'camcontrol devlist' now prints out: > < > at scbus-1 target -1 lun -1 (xpt0) > at scbus0 target 0 lun 0 (pass0,da0) > at scbus0 target 1 lun 0 (pass1,da1) > < > at scbus0 target 1 lun 1 (pass2) > < > at scbus0 target -1 lun -1 () > at scbus1 target 5 lun 0 (cd0,pass3) > at scbus1 target 6 lun 0 (pass4,da2) > < > at scbus1 target -1 lun -1 () > > [note the bogus pass2 entry] Hmm, I suppose that device didn't completely go away. Can you try putting a quirk entry for the Quantum in cam_xpt.c to disable multi-LUN probing? (CAM_QUIRK_NOLUNS) That may fix the problem. The other thing I wonder about is your bus topology. You say you "removed cd0". Where was it on the SCSI chain? How did you remove it? Was the bus still terminated once you removed it? Taking things off an active SCSI bus only works in controlled circumstances. If the device removed was the one terminating the chain, you would be leaving the bus unterminated. 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 Fri Mar 5 21:51:39 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ns2.michweb.net (ns2.michweb.net [208.246.108.3]) by hub.freebsd.org (Postfix) with SMTP id 20BBF14D35 for ; Fri, 5 Mar 1999 21:51:30 -0800 (PST) (envelope-from matt@ns2.michweb.net) Received: (qmail 1117 invoked by uid 101); 6 Mar 1999 05:51:13 -0000 Date: Sat, 6 Mar 1999 00:51:13 -0500 (EST) From: Matt Simerson To: freebsd-scsi@FreeBSD.ORG Subject: Re: 2940U2W supported? In-Reply-To: <199903051711.SAA29488@dorifer.heim3.tu-clausthal.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 On Fri, 5 Mar 1999, Oliver Fromme wrote: > > > Every once in a while, it _hangs_ forever when it displays > > > "waiting for SCSI devices to settle" during boot (I'd guess > > > it happens at every 10th reboot or something like that). > > > This happens both with the Adaptec 2940-U2W and with the > > > onboard Adaptec U2W of an ASUS P2B-LS, using 3.1-RELEASE. > > > > I can confirm this behavior. > > :-( > > Thanks for the confirmation. > > By the way, what kind of SCSI devices do you have? Maybe the > problem only occurs with some devices. We have: Our lists aren't that similar. A 9GB Viking II, a 4GB Seagate, and a CD. The CD is on the narrow, the other two on the U2W. Matt da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enable d da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enable d da0: 8709MB (17836668 512 byte sectors: 255H 63S/T 1110C) cd0 at ahc0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present (da0:ahc0:0:0:0): tagged openings now 63 I wish I understood that message. Matt `````````````````````````````````````````````````````````````````` Matt Simerson http://users.michweb.net/~matt MichWeb Inc. - President http://www.michweb.net The Art Farm - Technical Wizard http://www.theartfarm.com ISP/C - Treasurer http://www.ispc.org No one can make you feel inferior without your consent. -- Eleanor Roosevelt `````````````````````````````````````````````````````````````````` To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 5 23: 3:47 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id D658215022 for ; Fri, 5 Mar 1999 23:03:42 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id IAA07640 for freebsd-scsi@FreeBSD.ORG; Sat, 6 Mar 1999 08:03:24 +0100 (CET) (envelope-from olli) Date: Sat, 6 Mar 1999 08:03:24 +0100 (CET) From: Oliver Fromme Message-Id: <199903060703.IAA07640@dorifer.heim3.tu-clausthal.de> To: freebsd-scsi@FreeBSD.ORG Subject: Re: 2940U2W supported? Newsgroups: list.freebsd-scsi Organization: Administration Heim 3 Reply-To: freebsd-scsi@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matt Simerson wrote in list.freebsd-scsi: > On Fri, 5 Mar 1999, Oliver Fromme wrote: > > > > Every once in a while, it _hangs_ forever when it displays > > > > "waiting for SCSI devices to settle" during boot (I'd guess > > > > it happens at every 10th reboot or something like that). > > > > This happens both with the Adaptec 2940-U2W and with the > > > > onboard Adaptec U2W of an ASUS P2B-LS, using 3.1-RELEASE. > > > > > > I can confirm this behavior. > > Our lists aren't that similar. A 9GB Viking II, a 4GB Seagate, and a CD. > The CD is on the narrow, the other two on the U2W. > > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing > Enable > d > da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing > Enable > d Any reason why you run the U2W disks as UW only? > (da0:ahc0:0:0:0): tagged openings now 63 > > I wish I understood that message. That's normal (as long as it's the only message of that kind for that disk). It's only informational, telling that the driver has detected that the HD can grok 63 queued commands at once. 63 should be pretty good (our IBM DDRS' do 64). Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 5 23:16:55 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from k6n1.znh.org (unknown [207.109.235.35]) by hub.freebsd.org (Postfix) with ESMTP id 380AA14D34 for ; Fri, 5 Mar 1999 23:16:38 -0800 (PST) (envelope-from zach@uffdaonline.net) Received: (from zach@localhost) by k6n1.znh.org (8.9.3/8.9.1) id HAA01331; Sat, 6 Mar 1999 07:14:49 GMT (envelope-from zach) Message-ID: <19990306011448.A1224@znh.org> Date: Sat, 6 Mar 1999 01:14:48 -0600 From: Zach Heilig To: "Kenneth D. Merry" , Zach Heilig Cc: scsi@FreeBSD.ORG Subject: Re: 'camcontrol rescan' wierdness References: <19990305191914.A26718@znh.org> <199903060523.WAA04079@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199903060523.WAA04079@panzer.plutotech.com>; from Kenneth D. Merry on Fri, Mar 05, 1999 at 10:23:44PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Mar 05, 1999 at 10:23:44PM -0700, Kenneth D. Merry wrote: > > cd0 at ncr0 bus 0 target 5 lun 0 > > cd0: Removable CD-ROM SCSI-2 device > > cd0: 10.000MB/s transfers (10.000MHz, offset 8) > > cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed > Okay, this is interesting. Did you turn the power back on or something? Yes. > It appears that your Quantum disk is getting confused and responding on > multiple LUNs. > > and 'camcontrol devlist' now prints out: > > < > at scbus-1 target -1 lun -1 (xpt0) > > at scbus0 target 0 lun 0 (pass0,da0) > > at scbus0 target 1 lun 0 (pass1,da1) > > < > at scbus0 target 1 lun 1 (pass2) > > < > at scbus0 target -1 lun -1 () > > at scbus1 target 5 lun 0 (cd0,pass3) > > at scbus1 target 6 lun 0 (pass4,da2) > > < > at scbus1 target -1 lun -1 () > > > > [note the bogus pass2 entry] > > Hmm, I suppose that device didn't completely go away. The CDROM? That was SCSI #5.. The bogusly found da3? probably.. da0 and da1 were accessable [and they didn't seem slow] while the several minute rescan was happening. > Can you try putting a quirk entry for the Quantum in cam_xpt.c to disable > multi-LUN probing? (CAM_QUIRK_NOLUNS) That may fix the problem. It doesn't happen on boot. It also doesn't give problems if I avoid plugging the CDROM in [which I no longer have a real need to do]. For example, I can rescan now (I rebooted it to get rid of the bugus entries), and nothing happens, other than $ camcontrol rescan 0 Re-scan of bus 0 was successful $ camcontrol rescan 1 Re-scan of bus 1 was successful $ camcontrol rescan 0:1:0 Re-scan of 0:1:0 was successful $ camcontrol rescan 0:1:1 Re-scan of 0:1:1 was successful [no kernel messages or pauses]. $ camcontrol devlist < > at scbus-1 target -1 lun -1 (xpt0) at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 1 lun 0 (pass1,da1) < > at scbus0 target -1 lun -1 () at scbus1 target 5 lun 0 (pass2,cd0) at scbus1 target 6 lun 0 (pass3,da2) < > at scbus1 target -1 lun -1 () I think I will suspect that NEC CDROM -- it doesn't play well with other devices [it really slowed down access to the two disks -- it may not have disconnected while reading CD-audio -- and it would only read at 1x]. The only reason it was there is I had no other place to attach it, and I have 5 or 6 audio cd's that wedge the cd-writer [this has nothing to do with FreeBSD -- it wedges while reading the TOC]. > The other thing I wonder about is your bus topology. You say you "removed > cd0". Where was it on the SCSI chain? How did you remove it? Was the bus > still terminated once you removed it? yes... NEC CD Seagate Quantum terminator ahc0 cd0 da0 da1 |-------+-------+--------+-------| [internal cable] CW-7502 zip [termination switch turned on] ncr0 cd1/cd0 da2 |---------| |---------| [external cables] > Taking things off an active SCSI bus only works in controlled > circumstances. If the device removed was the one terminating the chain, > you would be leaving the bus unterminated. I yanked the power plug before removing the scsi connector... There is a separate terminator on the last connector. It may have been a mistake to avoid rebooting to temporarily add the CD-ROM... It surely didn't gain me anything this time [I ended up rebooting twice anyway]. -- Zach Heilig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Mar 6 17:23:24 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ns2.michweb.net (ns2.michweb.net [208.246.108.3]) by hub.freebsd.org (Postfix) with SMTP id 372EB15199 for ; Sat, 6 Mar 1999 17:23:15 -0800 (PST) (envelope-from matt@ns2.michweb.net) Received: (qmail 21513 invoked by uid 101); 7 Mar 1999 01:22:58 -0000 Date: Sat, 6 Mar 1999 20:22:58 -0500 (EST) From: Matt Simerson To: freebsd-scsi@FreeBSD.ORG Subject: Re: 2940U2W supported? In-Reply-To: <199903060703.IAA07640@dorifer.heim3.tu-clausthal.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 On Sat, 6 Mar 1999, Oliver Fromme wrote: > > da1 at ahc0 bus 0 target 1 lun 0 > > da1: Fixed Direct Access SCSI-2 device > > da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing > > Enable > > d > > da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C) > > da0 at ahc0 bus 0 target 0 lun 0 > > da0: Fixed Direct Access SCSI-2 device > > da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing > > Enabled > > Any reason why you run the U2W disks as UW only? Hmmm, I dunno? The Seagate drive is UW only so maybe you the bus operates at the fastest capabilities of the slowest drive? Matt `````````````````````````````````````````````````````````````````` Matt Simerson http://users.michweb.net/~matt MichWeb Inc. - President http://www.michweb.net The Art Farm - Technical Wizard http://www.theartfarm.com ISP/C - Treasurer http://www.ispc.org No one can make you feel inferior without your consent. -- Eleanor Roosevelt `````````````````````````````````````````````````````````````````` To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message