From owner-freebsd-scsi Sun Jul 16 10: 0:23 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from anchor-post-30.mail.demon.net (anchor-post-30.mail.demon.net [194.217.242.88]) by hub.freebsd.org (Postfix) with ESMTP id 5886237B77C for ; Sun, 16 Jul 2000 10:00:18 -0700 (PDT) (envelope-from maillist@page-designer.co.uk) Received: from divinenature.demon.co.uk ([194.222.162.90] helo=windows) by anchor-post-30.mail.demon.net with smtp (Exim 2.12 #1) id 13Drm3-0006x3-0U for freebsd-scsi@freebsd.org; Sun, 16 Jul 2000 18:00:15 +0100 Message-ID: <000401bfef47$8f6460e0$5aa2dec2@windows> From: "Graham Allen" To: Subject: FreeBSD 4.0-RELEASE and Adaptec AIC7892 Date: Sun, 16 Jul 2000 17:57:25 +0100 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 I've been having trouble installing FreeBSD 4.0-RELEASE onto a dual PIII 600Mhz system with a Supermicro PIIIDM3 Motherboard, and 2 x 128Mb non-ECC DIMMs. The board has an Adaptec AIC-7892 Ultra160 onboard SCSI Controller. I have searched through the mailing list archives, and noted that there is no support for 160Mb/sec yet, however the problems still occur when we set the speed to 80Mb/sec (or even 40Mb/sec) manually using the SCSISelect utility with the card. I've tried using the latest -STABLE snapshot, but this doesnt help. I'm assuming that the chip is actually supported, as AIC-789x chips are listed in the supported hardware list. The installer gets as far as unpacking and installing the 'bin' set, and sometimes a bit further, but then all disk activity stops, and the following messages appear on the console: (da0:ahc0:0:0:0): SCB 0x1e - timed out while idle, SEQADDR == 0xc (da0:ahc0:0:0:0): Queuing a BDR SCB (da0:ahc0:0:0:0): SCB 0x1e - timed out while idle, SEQADDR == 0x9 (da0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 125 SCBs aborted ahc0:A:0: ahc_intr - referenced scb not valid during seqinit 0x71 scb(30) ahc0: WARNING no command for scb 30 (cmdcmplt) QOUTPOS = 0 (da0:ahc0:0:0:0): SCB 0x1e - timed out while idle, SEQADDR == 0xb (da0:ahc0:0:0:0): Queuing a BDR SCB (da0:ahc0:0:0:0): SCB 0xe - timed out while idle, SEQADDR == 0x157 (da0:ahc0:0:0:0): Queuing a BDR SCB ahc0: WARNING no command for scb 30 (cmdcmplt) QOUTPOS = 2 (da0:ahc0:0:0:0): Bus Device Reset Message Sent (da0:ahc0:0:0:0): no longer in timeout, status 34b ahc0: Bus Device Reset on A:0. 73 SCBs aborted (da0:ahc0:0:0:0): SCB 0xe - timed out while idle, SEQADDR == 0xb ahc0: Issued Channel A Bus Reset. 0 SCBs aborted Any ideas on what may be causing this problem, or what we can do to fix it? Graham Allen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 17 0:33:23 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from zeus.tassie.net.au (zeus.tassie.net.au [203.57.213.21]) by hub.freebsd.org (Postfix) with ESMTP id 03E4937B8A8 for ; Mon, 17 Jul 2000 00:33:15 -0700 (PDT) (envelope-from Scott.Donovan@tassie.net.au) Received: from ante (ante.hbt.off.tassie.net.au [203.57.212.22]) by zeus.tassie.net.au (8.8.8/8.8.8) with SMTP id RAA20835 for ; Mon, 17 Jul 2000 17:33:12 +1000 (EST) From: "Scott Donovan" To: Subject: FW: Smart Cache VI and FBSD 4.0 Date: Mon, 17 Jul 2000 17:21:58 +1000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all, I have been trying to find unsuccessfully if very 4.0 (release) or any other modern versino of freebsd supports the DPT SmartCache VI. Any hints in this area would be great. Regards, Scott D. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 17 0:42:18 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id EA70B37B90C for ; Mon, 17 Jul 2000 00:42:15 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id AAA07205; Mon, 17 Jul 2000 00:50:49 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007170750.AAA07205@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Scott Donovan" Cc: freebsd-scsi@freebsd.org Subject: Re: FW: Smart Cache VI and FBSD 4.0 In-reply-to: Your message of "Mon, 17 Jul 2000 17:21:58 +1000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 17 Jul 2000 00:50:49 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hello all, > > I have been trying to find unsuccessfully if very 4.0 (release) or any other > modern versino of freebsd supports the DPT SmartCache VI. > > Any hints in this area would be great. It does not. DPT support was being engineered by Simon Shapiro, who hasn't surfaced for quite some time now. You might want to consider controllers from Mylex or AMI as alternatives. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 17 2: 8:57 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from viper.dmpriest.com (viper.dmpriest.com [195.188.177.3]) by hub.freebsd.org (Postfix) with ESMTP id 4EB3D37B6F0 for ; Mon, 17 Jul 2000 02:08:53 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca.tdx.co.uk [195.188.177.195]) by viper.dmpriest.com (8.9.3/8.9.3/Kp) with ESMTP id KAA11433; Mon, 17 Jul 2000 10:08:40 +0100 (BST) Message-ID: <3972CD18.76BD3B3@tdx.co.uk> Date: Mon, 17 Jul 2000 10:08:40 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Scott Donovan Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: FW: Smart Cache VI and FBSD 4.0 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Scott Donovan wrote: > > Hello all, > > I have been trying to find unsuccessfully if very 4.0 (release) or any other > modern versino of freebsd supports the DPT SmartCache VI. > > Any hints in this area would be great. Closest we've got is FreeBSD 3.5-STABLE running with Simon's i2o drivers (And it is running very well)... I believe he is working on a port to 4.0 - but AFAIK there were a number of internal changes in 3.X to 4.X which means moving it isn't the walk in the park that keeping it on 3.X is :) Simon does have a web site, and a mailing list - if you visit www.simon-shapiro.org, it's probably worth you signing up to the mailing list for more details... -Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 17 7:20:32 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from athena.lightningone.net (athena.lightningone.net [12.34.104.3]) by hub.freebsd.org (Postfix) with ESMTP id 480CD37B8A6 for ; Mon, 17 Jul 2000 07:20:18 -0700 (PDT) (envelope-from john@essenz.com) Received: from localhost (john@localhost) by athena.lightningone.net (8.9.3/8.9.3) with ESMTP id KAA28172; Mon, 17 Jul 2000 10:26:19 -0400 (EDT) (envelope-from john@essenz.com) X-Authentication-Warning: athena.lightningone.net: john owned process doing -bs Date: Mon, 17 Jul 2000 10:26:19 -0400 (EDT) From: Essenz Consulting X-Sender: john@athena.lightningone.net To: Graham Allen Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: FreeBSD 4.0-RELEASE and Adaptec AIC7892 In-Reply-To: <000401bfef47$8f6460e0$5aa2dec2@windows> 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 Graham, I have used the exact same boards, and have no problems with the onboard SCSI (aic-7892). I might suggest making sure all the SCSI stuff is setup right. i.e., using the right cables and pin settings, make sure you have the active terminator on the end of the chain, etc.,. But the current driver definitely supports those Supermicro PIIIDM3 AIC-7892 motherboards. Also, its not too outlandish for the motherboard to be BAD, I have had a few over the years from supermicro. -john v.e. On Sun, 16 Jul 2000, Graham Allen wrote: > I've been having trouble installing FreeBSD 4.0-RELEASE onto a dual PIII > 600Mhz system with a Supermicro PIIIDM3 Motherboard, and 2 x 128Mb non-ECC > DIMMs. The board has an Adaptec AIC-7892 Ultra160 onboard SCSI Controller. I > have searched through the mailing list archives, and noted that there is no > support for 160Mb/sec yet, however the problems still occur when we set the > speed to 80Mb/sec (or even 40Mb/sec) manually using the SCSISelect utility > with the card. I've tried using the latest -STABLE snapshot, but this doesnt > help. > > I'm assuming that the chip is actually supported, as AIC-789x chips are > listed in the supported hardware list. > > The installer gets as far as unpacking and installing the 'bin' set, and > sometimes a bit further, but then all disk activity stops, and the following > messages appear on the console: > > (da0:ahc0:0:0:0): SCB 0x1e - timed out while idle, SEQADDR == 0xc > (da0:ahc0:0:0:0): Queuing a BDR SCB > (da0:ahc0:0:0:0): SCB 0x1e - timed out while idle, SEQADDR == 0x9 > (da0:ahc0:0:0:0): no longer in timeout, status = 34b > ahc0: Issued Channel A Bus Reset. 125 SCBs aborted > ahc0:A:0: ahc_intr - referenced scb not valid during seqinit 0x71 scb(30) > ahc0: WARNING no command for scb 30 (cmdcmplt) > QOUTPOS = 0 > (da0:ahc0:0:0:0): SCB 0x1e - timed out while idle, SEQADDR == 0xb > (da0:ahc0:0:0:0): Queuing a BDR SCB > (da0:ahc0:0:0:0): SCB 0xe - timed out while idle, SEQADDR == 0x157 > (da0:ahc0:0:0:0): Queuing a BDR SCB > ahc0: WARNING no command for scb 30 (cmdcmplt) > QOUTPOS = 2 > (da0:ahc0:0:0:0): Bus Device Reset Message Sent > (da0:ahc0:0:0:0): no longer in timeout, status 34b > ahc0: Bus Device Reset on A:0. 73 SCBs aborted > (da0:ahc0:0:0:0): SCB 0xe - timed out while idle, SEQADDR == 0xb > ahc0: Issued Channel A Bus Reset. 0 SCBs aborted > > Any ideas on what may be causing this problem, or what we can do to fix it? > > Graham Allen > > > > > > 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 Jul 17 7:50:24 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by hub.freebsd.org (Postfix) with ESMTP id 19DD037B609 for ; Mon, 17 Jul 2000 07:50:19 -0700 (PDT) (envelope-from maillist@page-designer.co.uk) Received: from divinenature.demon.co.uk ([194.222.162.90] helo=cluck) by anchor-post-31.mail.demon.net with smtp (Exim 2.12 #1) id 13ECDm-000EHf-0V for freebsd-scsi@freebsd.org; Mon, 17 Jul 2000 15:50:14 +0100 Message-ID: <004601bfeffe$9147d9c0$1f00a8c0@cluck> From: "Graham Allen" To: Subject: Re: FreeBSD 4.0-RELEASE and Adaptec AIC7892 Date: Mon, 17 Jul 2000 15:52:01 +0100 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 >I have used the exact same boards, and have no problems with the onboard >SCSI (aic-7892). I might suggest making sure all the SCSI stuff is setup >right. i.e., using the right cables and pin settings, make sure you have >the active terminator on the end of the chain, etc.,. But the current >driver definitely supports those Supermicro PIIIDM3 AIC-7892 motherboards. >Also, its not too outlandish for the motherboard to be BAD, I have had a >few over the years from supermicro. I've considered that, so we did try it with Linux, OpenBSD and even Windows 2000, with no problems at all. This probably indicates that we've got the cabling and termination correct as well. Graham. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 17 8:12:25 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from sam.on-net.net (sam.on-net.net [204.117.190.8]) by hub.freebsd.org (Postfix) with ESMTP id 3600337B5CA for ; Mon, 17 Jul 2000 08:12:06 -0700 (PDT) (envelope-from jasomill@shaffstall.com) Received: from guildenstern.shaffstall.com (cisdn-2 [206.229.84.2]) by sam.on-net.net (8.9.3/8.9.3) with ESMTP id KAA23406 for ; Mon, 17 Jul 2000 10:09:53 -0500 (EST) Date: Mon, 17 Jul 2000 10:10:21 -0500 (EST) From: "Jason T. Miller" To: freebsd-scsi@freebsd.org Subject: Yamaha CDR100 and FreeBSD 4.0-STABLE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just recieved (for free), a Yamaha CDR100 4x CD burner. This is a great drive that (at work) has served me well for a couple years; it works fine with cdrecord and cdrdao. However, its cooperation with the FreeBSD SCSI CD-ROM driver is not as good. First of all, if there is no media loaded on boot, I get the messages "lost device" and "removing device entry." I haven't done much research on this particular problem yet; I'm just keeping a disc in the drive when I reboot. I have noticed, however, that the "removal" of the device entry is not complete; if I try to access /dev/cd0c, I get a kernel panic. The other problem is, initially, the drive would only mount CD-ROM mode 1 discs, and refuse both to mount CD-ROM XA mode 2 form 1 discs and to play CD-DA discs. After doing a little digging, I discovered that the CDR100 reports differing values for each disc type in response to the READ CAPACITY (0x25) command (i.e. 2048 for mode 1, 2352 for CD-DA, and 2340 for XA mode 2 form 1), and the code to open the device reads this; the disklabel code is married to the fact that the blocksize is a multiple of 512, and thus refuses permission to open the device with a console message "invalid block size nnnn." I solved the problem by hardcoding a return value of 2048 in the READ CAPACITY commands. Now everything works fine. This is an ugly, dumb hack, but not as drastic as it sounds. First of all, the SCSI-3 MMC standard (or at least the draft rev I have), the response of a CD-ROM type device to READ CAPACITY, insofar as block size is concerned, "shall be 2048;" obviously the CDR100 came about in the days of SCSI-2, who says that READ CD-ROM CAPACITY (0x25, but so named because the result is inexact, based on the TOC rather than the data). All data CD-ROM discs I've ever seen are recorded with a logical block size of 2048; there is, of course, XA mode 2 form 2, where the user data area consists of 2336 bytes, but it's not really used for data because it has no ECC. Besides, I don't think the driver would handle it anyway, set up as it is for 2048 byte blocks. So a 2048 byte block is a safe assumption, since anything else would result in an error anyway. Specific to the CDR100 (and many other drives, and MMC-3), 2340 is a valid block size, as are many other values, even though, for example, there are no CD-ROM modes or forms which provide for 2340 bytes of user data. Using MODE SELECT, one can select one of these block sizes, which then include various combinations of additional data, such as EDC, ECC, header and subheader information, sync, and padding. The default for all modes (except for mode 2 form 2, on most drives) is to return user data only. The current mode is determined, not by READ CAPACITY (which relates to the medium, not the drive's status), but by MODE SENSE. Since the drivers are already incapable of utilizing a block size which is not a multiple of 512, and all the other MODE SENSE option return such a block size, my dumb hack should not reduce functionality. It may allow a truncated mode 2 form 2 block to be transferred without error, though. The alternative would be to use MODE SENSE instead of READ CAPACITY. I don't know how that would affect other drives or functionality, however. The ideal situation, in fact, may be to do a MODE SELECT with a block size of 2048, return an error if this fails, otherwise assume the block size is 2048. This would reset the drive to send data only, and fail elegently with mode 2 form 2 discs, which, as I said above, would not work correctly anyway. Also, it should work for any drive, though I have to talk to my engineers about that. I'd like to get a working solution in the kernel, if possible, but want input before I write up the diffs. The simplest thing would be to use my "dumb hack" as a kernel DEFINE, since it shouldn't break anything that already works anyway. It could also be added as a new drive quirk. The most elegent solution, however, would be the above MODE SELECT solution, plus possibly a quirk entry if it turns out not to be compatible with all drives. Finally, I do realize that some OEM-modified CD-ROM drives allow a 512-byte block size, then do the deblocking of 2048-byte records in the drive. This was to maintain compatibility with hard drive code that was dependent on a 512-byte block size. Are these drives supported now, and is anyone using them? I don't think I have any, though I do have an old SunCD that may or may not do it; haven't checked yet. Jason T. Miller To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 17 17: 2:32 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from zeus.tassie.net.au (zeus.tassie.net.au [203.57.213.21]) by hub.freebsd.org (Postfix) with ESMTP id 59FEB37B705 for ; Mon, 17 Jul 2000 17:02:26 -0700 (PDT) (envelope-from Scott.Donovan@tassie.net.au) Received: from ante (ante.hbt.off.tassie.net.au [203.57.212.22]) by zeus.tassie.net.au (8.8.8/8.8.8) with SMTP id KAA25085; Tue, 18 Jul 2000 10:02:16 +1000 (EST) From: "Scott Donovan" To: "Karl Pielorz" Cc: Subject: RE: FW: Smart Cache VI and FBSD 4.0 Date: Tue, 18 Jul 2000 09:51:44 +1000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <3972CD18.76BD3B3@tdx.co.uk> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ahh righto.. Hmm I wonder if this is an area where the BSDi people could have an effect. Lately I am having to make a number of hardware choices am unhappy with to keep FreeBSD installed. In this case I changed my order to a mylex card, for which the support where I am is not great. Further to this is there any known comparisons for the the various raid products under FreeBSD anywhere? (Previously to this I have been using a transparent raid system). Hmm Perhaps someone needs to throw a LOT of money at simon to get the i2o card reintegrated into the -stable and -current branches! > > I have been trying to find unsuccessfully if very 4.0 (release) > or any other > > modern versino of freebsd supports the DPT SmartCache VI. > Closest we've got is FreeBSD 3.5-STABLE running with Simon's i2o > drivers (And > it is running very well)... > I believe he is working on a port to 4.0 - but AFAIK there were a > number of > internal changes in 3.X to 4.X which means moving it isn't the walk in the > park that keeping it on 3.X is :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 17 21: 4:59 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 19E9037B601 for ; Mon, 17 Jul 2000 21:04:51 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id WAA96465; Mon, 17 Jul 2000 22:04:36 -0600 (MDT) (envelope-from ken) Date: Mon, 17 Jul 2000 22:04:36 -0600 From: "Kenneth D. Merry" To: "Jason T. Miller" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Yamaha CDR100 and FreeBSD 4.0-STABLE Message-ID: <20000717220436.A96300@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from jasomill@shaffstall.com on Mon, Jul 17, 2000 at 10:10:21AM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jul 17, 2000 at 10:10:21 -0500, Jason T. Miller wrote: > I just recieved (for free), a Yamaha CDR100 4x CD burner. This is a great > drive that (at work) has served me well for a couple years; it works fine > with cdrecord and cdrdao. However, its cooperation with the FreeBSD SCSI > CD-ROM driver is not as good. First of all, if there is no media loaded on > boot, I get the messages "lost device" and "removing device entry." I > haven't done much research on this particular problem yet; I'm just > keeping a disc in the drive when I reboot. I have noticed, however, that > the "removal" of the device entry is not complete; if I try to access > /dev/cd0c, I get a kernel panic. Well, it might be interesting to see what exactly your drive returns in response to a read capacity when there is no CD in the drive. Here's an easy way to find out: # camcontrol cmd cd0 -v -c "25 0 0 0 0 0 0 0 0 0" -i 8 "i4 i4" 191854 2048 [ eject the CD ] # camcontrol cmd cd0 -v -c "25 0 0 0 0 0 0 0 0 0" -i 8 "i4 i4" camcontrol: error sending command (pass2:ahc0:0:4:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (pass2:ahc0:0:4:0): NOT READY asc:3a,0 (pass2:ahc0:0:4:0): Medium not present The cd(4) driver will attach to any CDROM or WORM device that returns a SCSI error for read capacity, as long as it isn't "logical unit not supported". If you get another type of error, like a selection timeout, it likely won't attach. So we need to figure out what sort of error your drive is returning to figure out whether there is a bug somewhere or not. As far as the panic, it would be nice if you could supply a stack trace for that. The FreeBSD Handbook covers crashdumps and kernel debugging: http://www.freebsd.org/handbook/kerneldebug.html [ Yamaha drive returns something other than 2048 for a blocksize ] > I'd like to get a working solution in the kernel, if possible, but want > input before I write up the diffs. The simplest thing would be to use my > "dumb hack" as a kernel DEFINE, since it shouldn't break anything that > already works anyway. It could also be added as a new drive quirk. The > most elegent solution, however, would be the above MODE SELECT solution, > plus possibly a quirk entry if it turns out not to be compatible with all > drives. Well, we've already solved that problem. You need a later version of -stable. Joerg Wunsch had a similar problem with an older Plasmon CD-R. The fix was to round any blocksize greater than 2048 and less than or equal to 2352 down to 2048. > Finally, I do realize that some OEM-modified CD-ROM drives allow a > 512-byte block size, then do the deblocking of 2048-byte records in the > drive. This was to maintain compatibility with hard drive code that was > dependent on a 512-byte block size. Are these drives supported now, and is > anyone using them? I don't think I have any, though I do have an old SunCD > that may or may not do it; haven't checked yet. Yes, they are supported by the driver, I'm not sure about the ISO9660 code. You can often use a dip switch or jumper to change the behavior back and forth, though. Usually you'll only want to use the drive in 512-byte block mode to access CDs created with a 512-byte blocksize. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 17 23:54:24 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 3BB1D37BB9E for ; Mon, 17 Jul 2000 23:54:18 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13ERGg-0005a2-00; Tue, 18 Jul 2000 06:54:14 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id IAA80708; Tue, 18 Jul 2000 08:43:47 +0200 (CEST) (envelope-from wkb) Date: Tue, 18 Jul 2000 08:43:47 +0200 From: Wilko Bulte To: "Kenneth D. Merry" Cc: "Jason T. Miller" , freebsd-scsi@freebsd.org Subject: Re: Yamaha CDR100 and FreeBSD 4.0-STABLE Message-ID: <20000718084347.A80690@freebie.demon.nl> Reply-To: wilko@freebsd.org References: <20000717220436.A96300@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000717220436.A96300@panzer.kdm.org>; from ken@kdm.org on Mon, Jul 17, 2000 at 10:04:36PM -0600 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Jul 17, 2000 at 10:04:36PM -0600, Kenneth D. Merry wrote: > On Mon, Jul 17, 2000 at 10:10:21 -0500, Jason T. Miller wrote: ... > > Finally, I do realize that some OEM-modified CD-ROM drives allow a > > 512-byte block size, then do the deblocking of 2048-byte records in the > > drive. This was to maintain compatibility with hard drive code that was > > dependent on a 512-byte block size. Are these drives supported now, and is > > anyone using them? I don't think I have any, though I do have an old SunCD > > that may or may not do it; haven't checked yet. The older Sun drives are 512, without jumpers. I have succesfully used the the Digital RRD4x series CDROM drives who are also 512 b/s (some have a 512/2048 jumper, but only the newer ones). The work just fine for me with 512 b/s selected. > Yes, they are supported by the driver, I'm not sure about the ISO9660 code. > You can often use a dip switch or jumper to change the behavior back and > forth, though. > > Usually you'll only want to use the drive in 512-byte block mode to access > CDs created with a 512-byte blocksize. -- Wilko Bulte http://www.freebsd.org wilko@freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 18 7:49:25 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from privatecube.privatelabs.com (privatecube.privatelabs.com [198.143.31.30]) by hub.freebsd.org (Postfix) with ESMTP id E865B37BE5F for ; Tue, 18 Jul 2000 07:49:21 -0700 (PDT) (envelope-from mi@privatelabs.com) Received: from misha.privatelabs.com (misha.privatelabs.com [198.143.31.6]) by privatecube.privatelabs.com (8.9.3/8.9.2) with ESMTP id JAA17744 for ; Tue, 18 Jul 2000 09:48:51 -0400 Received: (from mi@localhost) by misha.privatelabs.com (8.9.3/8.9.3) id KAA76520 for scsi@freebsd.org; Tue, 18 Jul 2000 10:46:59 -0400 (EDT) (envelope-from mi) From: Mikhail Teterin Message-Id: <200007181446.KAA76520@misha.privatelabs.com> Subject: slow tape behind fast drives on the chain To: scsi@freebsd.org Date: Tue, 18 Jul 2000 10:46:59 -0400 (EDT) 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 Hello! For a while we were happy with two external 45Gb drives hanging off of AdvanSys 3550 Ultra SCSI Adapter: da0 at adw0 bus 0 target 2 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number LF214132 da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 44884MB (91923356 512 byte sectors: 255H 63S/T 5721C) da1 at adw0 bus 0 target 3 lun 0 da1: Fixed Direct Access SCSI-2 device da1: Serial Number LF214978 da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 44884MB (91923356 512 byte sectors: 255H 63S/T 5721C) Yesterday, we added the tape drive: pass2: Removable Seq pass2: Serial Number GS0D9S5 pass2: 3.300MB/s transfers and the drives started to give all sorts of problems. This sounds like a bad cable/terminator, but I wonder if the combination is even suppoused to work -- the tape has the Tectronix connectors on the back, the drives have the 68pin. The short 68pin cables connect one of the drives to the adapter and to the second drive which used to have an active terminator on it's second 68pin jack. Now, there is a 68-50 cable there extending the chain to the tape, which has an active terminator. Would access to the drives be slower because of the tape's mere presense? Will it slow (noticable) when the tape is in use? It everything should work fine (it does not) -- what do I replace first -- the 68-50 cable connecting the tape to the second drive or the active terminator on the tape? Thanks a lot! -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 19 9:31:12 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.im.tku.edu.tw (im2.im.tku.edu.tw [163.13.200.193]) by hub.freebsd.org (Postfix) with ESMTP id 7B69137BF8E for ; Wed, 19 Jul 2000 09:31:08 -0700 (PDT) (envelope-from maverick@mail.im.tku.edu.tw) Received: (from maverick@localhost) by mail.im.tku.edu.tw (8.9.3/8.9.3) id AAA15547; Thu, 20 Jul 2000 00:28:41 +0800 Date: Thu, 20 Jul 2000 00:28:41 +0800 (CST) From: ³¢¬Õ§Ó To: freebsd-scsi@freebsd.org Subject: Compaq SmartRAID 4200 Install problem 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 Dear all: I test compaq 1600 Server with smart-raid 4200. bios & array rom refresh to the newest version today. but when i install freebsd, i get this error message "ida0: Can't Allocate Register Resource" and disk isn't found. when i do partion that show out "Disk Not Found", It Can't install continue.. Test Version is 5.0-20000710-current & 4.0-20000711-stable All the same error!! Please Please help me , Thanks a lot... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 19 14:42:41 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 493C337C06D for ; Wed, 19 Jul 2000 14:42:38 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id RAA80034; Wed, 19 Jul 2000 17:42:22 -0400 (EDT) Date: Wed, 19 Jul 2000 17:42:21 -0400 (EDT) From: "Matthew N. Dodd" To: =?X-UNKNOWN?B?s6Ks1afT?= Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Compaq SmartRAID 4200 Install problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 20 Jul 2000, ³¢¬Õ§Ó wrote: > I test compaq 1600 Server with smart-raid 4200. > bios & array rom refresh to the newest version today. > but when i install freebsd, i get this error message > > "ida0: Can't Allocate Register Resource" Make sure you don't have 'PnP' OS or some other silliness turned on in the BIOS. I'm fairly sure that there are some Compaq specific settings you'll want to change in general as Compaq likes doing stuff their own way and making non NT/Windows users crazy. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 19 16:39: 8 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 3870337B774 for ; Wed, 19 Jul 2000 16:39:05 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id QAA27895; Wed, 19 Jul 2000 16:47:46 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007192347.QAA27895@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Scott Donovan" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: FW: Smart Cache VI and FBSD 4.0 In-reply-to: Your message of "Tue, 18 Jul 2000 09:51:44 +1000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 19 Jul 2000 16:47:46 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Ahh righto.. Hmm I wonder if this is an area where the BSDi people could > have an effect. Lately I am having to make a number of hardware choices am > unhappy with to keep FreeBSD installed. In this case I changed my order to a > mylex card, for which the support where I am is not great. I don't know if "the BSDi people" will have an effect here; I'm not sure how easy it might be to migrate the BSD/OS DPT driver to FreeBSD, or if DPT would be happy with that (I think they would). > Further to this is there any known comparisons for the the various raid > products under FreeBSD anywhere? (Previously to this I have been using a > transparent raid system). I don't have any comparisons, just listings at http://people.freebsd.org/~msmith/RAID > Hmm Perhaps someone needs to throw a LOT of money at simon to get the i2o > card reintegrated into the -stable and -current branches! The last I heard, Simon was dealing with some health issues and a lot of workload. I'm not sure if he's going to get back to I2O or not. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 19 17:26:27 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.im.tku.edu.tw (im2.im.tku.edu.tw [163.13.200.193]) by hub.freebsd.org (Postfix) with ESMTP id 13DC637B816 for ; Wed, 19 Jul 2000 17:26:24 -0700 (PDT) (envelope-from maverick@mail.im.tku.edu.tw) Received: (from maverick@localhost) by mail.im.tku.edu.tw (8.9.3/8.9.3) id IAA18303; Thu, 20 Jul 2000 08:23:34 +0800 Date: Thu, 20 Jul 2000 08:23:34 +0800 (CST) From: ³¢¬Õ§Ó To: "Matthew N. Dodd" Cc: freebsd-scsi@freebsd.org Subject: Re: Compaq SmartRAID 4200 Install problem 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 hi Sorry i haven't saw any about PnP OS function in BIOS Can you tell me how to do this... thanks's To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 20 1:55:20 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by hub.freebsd.org (Postfix) with ESMTP id D474337BB93; Thu, 20 Jul 2000 01:55:14 -0700 (PDT) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id JAA50829; Thu, 20 Jul 2000 09:55:13 +0100 (BST) (envelope-from geoffb) Date: Thu, 20 Jul 2000 09:55:13 +0100 From: Geoff Buckingham To: hackers@freebsd.org Cc: scsi@freebsd.org Subject: Multiple ro mounts of vinum volume Message-ID: <20000720095513.A50799@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anybody with a knowledge of the vinum code have an opinion on the amount of work involved in getting vinum to the point that several JBODs in a FC switched fabric could be managed, as a vinum volume, by one machine, and mounted ro by that machine and several others on the switch fabric. (writing to that volume is obviously a fs issue) -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 20 2: 4: 3 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id A2C1637BAA5; Thu, 20 Jul 2000 02:03:54 -0700 (PDT) (envelope-from grog@wantadilla.lemis.com) Received: (from grog@localhost) by wantadilla.lemis.com (8.9.3/8.9.3) id SAA87185; Thu, 20 Jul 2000 18:33:42 +0930 (CST) (envelope-from grog) Date: Thu, 20 Jul 2000 18:33:42 +0930 From: Greg Lehey To: Geoff Buckingham Cc: hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: Multiple ro mounts of vinum volume Message-ID: <20000720183341.I30599@wantadilla.lemis.com> References: <20000720095513.A50799@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000720095513.A50799@chuggalug.clues.com> Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thursday, 20 July 2000 at 9:55:13 +0100, Geoff Buckingham wrote: > > Does anybody with a knowledge of the vinum code have an opinion on > the amount of work involved in getting vinum to the point that > several JBODs in a FC switched fabric could be managed, as a vinum > volume, by one machine, and mounted ro by that machine and several > others on the switch fabric. I'd say "no work at all" as far as Vinum is concerned. The real issue is getting the drivers to present the individual drives to the system. That's a device driver issue, and I don't know enough about the current state of FC drivers to make a sensible comment. But I'd certainly be interested to hear more. > (writing to that volume is obviously a fs issue) That depends if you want to put a file system on it. A thing that might bite you here is that ufs is currently limited to 1 TB per volume. Vinum doesn't have that restriction: if you want to create a 20 TB volume, and you know how to use the space, Vinum should work. The problem with ufs is that the block numbers in the inodes are 32 bit signed values. With 512 byte sectors, the only we can do it, that means a total address space of 2**9 * 2*31, or 1 TB. At some time I suspect we're going to need to fix that. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 20 2: 8:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id C43A337BD8D; Thu, 20 Jul 2000 02:08:24 -0700 (PDT) (envelope-from grog@wantadilla.lemis.com) Received: (from grog@localhost) by wantadilla.lemis.com (8.9.3/8.9.3) id SAA89230; Thu, 20 Jul 2000 18:38:13 +0930 (CST) (envelope-from grog) Date: Thu, 20 Jul 2000 18:38:13 +0930 From: Greg Lehey To: Geoff Buckingham Cc: hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: Multiple ro mounts of vinum volume Message-ID: <20000720183812.K30599@wantadilla.lemis.com> References: <20000720095513.A50799@chuggalug.clues.com> <20000720183341.I30599@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000720183341.I30599@wantadilla.lemis.com> Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thursday, 20 July 2000 at 18:33:42 +0930, Greg Lehey wrote: > On Thursday, 20 July 2000 at 9:55:13 +0100, Geoff Buckingham wrote: >> >> Does anybody with a knowledge of the vinum code have an opinion on >> the amount of work involved in getting vinum to the point that >> several JBODs in a FC switched fabric could be managed, as a vinum >> volume, by one machine, and mounted ro by that machine and several >> others on the switch fabric. > > I'd say "no work at all" as far as Vinum is concerned. The real issue > is getting the drivers to present the individual drives to the > system. That's a device driver issue, and I don't know enough about > the current state of FC drivers to make a sensible comment. But I'd > certainly be interested to hear more. > >> (writing to that volume is obviously a fs issue) Oops, I missed the point here. Yes, the multiple R/O issue would make it very difficult to write to it. I suspect that it would be almost impossible to write while other systems had the volume open R/O. I'll think about how that could be done, but it's not simple, if it's at all possible. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 20 2:32: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by hub.freebsd.org (Postfix) with ESMTP id 0714437B625; Thu, 20 Jul 2000 02:32:00 -0700 (PDT) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id KAA50932; Thu, 20 Jul 2000 10:31:50 +0100 (BST) (envelope-from geoffb) Date: Thu, 20 Jul 2000 10:31:50 +0100 From: Geoff Buckingham To: Greg Lehey Cc: hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: Multiple ro mounts of vinum volume Message-ID: <20000720103150.A50907@chuggalug.clues.com> References: <20000720095513.A50799@chuggalug.clues.com> <20000720183341.I30599@wantadilla.lemis.com> <20000720183812.K30599@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000720183812.K30599@wantadilla.lemis.com>; from Greg Lehey on Thu, Jul 20, 2000 at 06:38:13PM +0930 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jul 20, 2000 at 06:38:13PM +0930, Greg Lehey wrote: > On Thursday, 20 July 2000 at 18:33:42 +0930, Greg Lehey wrote: > > On Thursday, 20 July 2000 at 9:55:13 +0100, Geoff Buckingham wrote: > >> > >> Does anybody with a knowledge of the vinum code have an opinion on > >> the amount of work involved in getting vinum to the point that > >> several JBODs in a FC switched fabric could be managed, as a vinum > >> volume, by one machine, and mounted ro by that machine and several > >> others on the switch fabric. > > > > I'd say "no work at all" as far as Vinum is concerned. The real issue > > is getting the drivers to present the individual drives to the > > system. That's a device driver issue, and I don't know enough about > > the current state of FC drivers to make a sensible comment. But I'd > > certainly be interested to hear more. > > I believe all the disks should be visable to all the hosts, unless some aspect of your switch fabric has been configured to hide disks from NT4 boxes. > >> (writing to that volume is obviously a fs issue) > > Oops, I missed the point here. Yes, the multiple R/O issue would make > it very difficult to write to it. I suspect that it would be almost > impossible to write while other systems had the volume open R/O. I'll > think about how that could be done, but it's not simple, if it's at > all possible. > I would be happy with unmounting the FS everywhere mounting it rw on the 'management' machine , writing, then reversing back to having it mounted ro everywhere. I may have a play with this in a few months when I have a bit more kit, as I had imagined there would be more issues with multiple machines, each with an instance of vinum trying to manage the same single volume (particulary in degraded or repair situations) On the Fs front I must confess to having lost track of the XFS situation/ devate after the intial storm of interest when SGI first announced their interest. What happened? -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 21 2:14:41 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.im.tku.edu.tw (im2.im.tku.edu.tw [163.13.200.193]) by hub.freebsd.org (Postfix) with ESMTP id 053A437B6F3 for ; Fri, 21 Jul 2000 02:14:39 -0700 (PDT) (envelope-from maverick@mail.im.tku.edu.tw) Received: (from maverick@localhost) by mail.im.tku.edu.tw (8.9.3/8.9.3) id RAA01315; Fri, 21 Jul 2000 17:11:44 +0800 Date: Fri, 21 Jul 2000 17:11:44 +0800 (CST) From: ³¢¬Õ§Ó To: freebsd-scsi@freebsd.org Subject: Compaq Smart Raid drive ida's bug 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 Dear all: I test compaq 1600 Server with smart-raid 3500 & 4200. bios & array rom refresh to the newest version today. but when i install freebsd, i get this error message 3500 it's Ok :) 4200 it Can Find The Card But Cann't Find The Disk It show "ida0: Can't Allocate Register Resource" when i do partion that show out "Disk Not Found", It Can't install continue.. Test Version is 5.0-20000710-current & 4.0-20000711-stable All the same error!! Please Please help me , Thanks a lot... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 21 8:16:17 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from unix.megared.net.mx (megamail.megared.com.mx [200.52.207.52]) by hub.freebsd.org (Postfix) with ESMTP id B57D837BC06; Fri, 21 Jul 2000 08:16:05 -0700 (PDT) (envelope-from ales@megared.net.mx) Received: from ales (ales.corp.megared.net.mx [200.52.193.2]) by unix.megared.net.mx (8.9.3/8.9.3) with SMTP id KAA69847; Fri, 21 Jul 2000 10:13:09 -0500 (CDT) (envelope-from ales@megared.net.mx) Message-ID: <028401bff326$78f210e0$02c134c8@megared.net.mx> From: "Alejandro Ramirez" To: Cc: Subject: SCSI Bus Reset & Frozen System with ahc driver !!! Date: Fri, 21 Jul 2000 10:15:15 -0500 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I have a Netfinity 3500 server with FreeBSD 3.4-RELEASE and an Adaptec aic7895 Ultra SCSI adapter card, that has an IBM tape drive: sa0 at ahc0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8678MB (17774160 512 byte sectors: 255H 63S/T 1106C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 8678MB (17774160 512 byte sectors: 255H 63S/T 1106C) I have configured nightly backups in this server, suddenly the tape started to fail, and I were told by IBM to upgrade the firmware of this tape, I did it and its still failing, but the problem now its worst, because the system gets frozen when the backup starts, and the only way of get it out from this state its rebooting the server, this is the message that it gives after getting frozen: (sa0:ahc0:0:6:0): SCB 0x6b - timed out in command phase, SEQADDR == 0x152 (sa0:ahc0:0:6:0): BDR message in message buffer (sa0:ahc0:0:6:0): SCB 0x6b - timed out in command phase, SEQADDR == 0x152 (sa0:ahc0:0:6:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 5 SCBs aborted I know that I have to change the tape drive, and I also have eliminating the cron job from being executed, but in the mean time I really dont think that ist good to freebsd not to be able to recover it self from this state, resetting the SCSI bus where the disks also lives, and got frozen by this??? could this be a bug in the ahc driver??? Thanks for your help... Ales To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 21 21:47:35 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 57A0337B947; Fri, 21 Jul 2000 21:47:30 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id WAA34978; Fri, 21 Jul 2000 22:47:22 -0600 (MDT) (envelope-from ken) Date: Fri, 21 Jul 2000 22:47:22 -0600 From: "Kenneth D. Merry" To: Alejandro Ramirez Cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI Bus Reset & Frozen System with ahc driver !!! Message-ID: <20000721224722.A34948@panzer.kdm.org> References: <028401bff326$78f210e0$02c134c8@megared.net.mx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <028401bff326$78f210e0$02c134c8@megared.net.mx>; from ales@megared.net.mx on Fri, Jul 21, 2000 at 10:15:15AM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jul 21, 2000 at 10:15:15 -0500, Alejandro Ramirez wrote: > (sa0:ahc0:0:6:0): SCB 0x6b - timed out in command phase, SEQADDR == 0x152 > (sa0:ahc0:0:6:0): BDR message in message buffer > (sa0:ahc0:0:6:0): SCB 0x6b - timed out in command phase, SEQADDR == 0x152 > (sa0:ahc0:0:6:0): no longer in timeout, status = 34b > ahc0: Issued Channel A Bus Reset. 5 SCBs aborted > > I know that I have to change the tape drive, and I also have eliminating the > cron job from being executed, but in the mean time I really dont think that > ist good to freebsd not to be able to recover it self from this state, > resetting the SCSI bus where the disks also lives, and got frozen by this??? > could this be a bug in the ahc driver??? The 'timed out in command phase' message probably indicates that you have a cabling or termination problem. It means that the bus has probably gotten stuck in that phase, which isn't good. So check your cabling and termination. FreeBSD shouldn't freeze, and it's possible that the issue that causes the freezes has been fixed in a later version of FreeBSD, but I don't know for sure. In any case, the best way to fix your problem is to track down the cabling or termination problem in your system. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 21 21:52: 2 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 4057D37B84E for ; Fri, 21 Jul 2000 21:51:58 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id WAA35018; Fri, 21 Jul 2000 22:51:25 -0600 (MDT) (envelope-from ken) Date: Fri, 21 Jul 2000 22:51:25 -0600 From: "Kenneth D. Merry" To: Mikhail Teterin Cc: scsi@FreeBSD.ORG Subject: Re: slow tape behind fast drives on the chain Message-ID: <20000721225125.A34985@panzer.kdm.org> References: <200007181446.KAA76520@misha.privatelabs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007181446.KAA76520@misha.privatelabs.com>; from mi@privatelabs.com on Tue, Jul 18, 2000 at 10:46:59AM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Jul 18, 2000 at 10:46:59 -0400, Mikhail Teterin wrote: > Yesterday, we added the tape drive: > > pass2: Removable Seq > pass2: Serial Number GS0D9S5 > pass2: 3.300MB/s transfers > > and the drives started to give all sorts of problems. This sounds like a > bad cable/terminator, but I wonder if the combination is even suppoused > to work -- the tape has the Tectronix connectors on the back, the drives > have the 68pin. The short 68pin cables connect one of the drives to the > adapter and to the second drive which used to have an active terminator > on it's second 68pin jack. Now, there is a 68-50 cable there extending > the chain to the tape, which has an active terminator. > > Would access to the drives be slower because of the tape's mere > presense? Will it slow (noticable) when the tape is in use? It > everything should work fine (it does not) -- what do I replace first -- > the 68-50 cable connecting the tape to the second drive or the active > terminator on the tape? Well, one thing you'll want to check is whether your 68-50 pin cable is terminating the high byte of the SCSI bus, since that isn't passed through to the tape drive. Another thing that could cause problems is if the tape drive isn't disconnecting from the SCSI bus. Other than that, we might need to see some error messages to take a guess at what is going on. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 21 22: 2:23 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by hub.freebsd.org (Postfix) with ESMTP id BD84E37C1C5 for ; Fri, 21 Jul 2000 22:02:09 -0700 (PDT) (envelope-from gdinolt@pacbell.net) Received: from pacbell.net ([63.199.31.177]) by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FY3004PQ1XOTY@mta5.snfc21.pbi.net> for freebsd-scsi@freebsd.org; Fri, 21 Jul 2000 22:01:00 -0700 (PDT) Date: Fri, 21 Jul 2000 22:01:42 -0700 From: "George W. Dinolt" Subject: (noperiph:ahc0:0:-1:-1): ... error To: freebsd-scsi@freebsd.org Cc: mjacob@feral.com, rmtodd@servalan.servalan.com Message-id: <39792AB6.F4B7B1CB@pacbell.net> MIME-version: 1.0 X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.0-20000214-CURRENT i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I originally posted this on -current, but Matthew Jacob suggested that I post this on -scsi as well. I am trying to boot a recent kernel (as of yesterday) and am seeing the following pair of contiguous error messages when I try to boot:: (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. panic: Bogus resid sgptr value 0xbd68609 (I copied this from the console after the boot failure, there may be minor mistakes.) It appears that the probe for the ahc0 drive works. The probe message appears very early in the boot process. The above messages appear just before I would expect the messages about the scsi disk drives to appear. After the second message, of course, the system panics and halts and there is no information about the drives. This started happening when I started compiling kernels built from sources cvsuped around Jul 18. I am not sure what is causing these messages. The "noperiph" message appears to come from xpt_print_path in /usr/src/sys/cam/cam_xpt.c while the panic seems to be written by ahc_calc_residual in /usr/src/sys/dev/aic7xxx/aic7xxx.c. From a quick look at the code, the problem is not directly in the code pointed to by the messages. I have an Adaptec 2940UW. A much older kernel reports it as with aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs. The Bios on the board is version 2.20.0 I have 4 drives and a UMAX scanner connected to the bus. More details available if needed. I am using an IWILL XA100P motherboard I am hopeful that someone will recognize the problem. My config file looks as follows: machine i386 cpu I586_CPU cpu I686_CPU ident DINOLT1 maxusers 32 options CPU_WT_ALLOC # k6 support options NO_MEMORY_HOLE # k6 support options USER_LDT # wine support options EXT2FS # Linux file system support options PQ_CACHESIZE=512 # color for 512k/16k cache options INCLUDE_CONFIG_FILE # Include this file in kernel options INET #InterNETworking options INET6 #IPv6 communications protocols options IPSEC #IP security options IPSEC_ESP #IP security (crypto; define w/ IPSEC) options IPSEC_DEBUG #debug for IP security options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=6000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extentions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options RANDOMDEV #entropy device options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options SOFTUPDATES options NETGRAPH #netgraph(4) system options NETGRAPH_SOCKET options NETGRAPH_PPPOE options FFS_EXTATTR #Extended attributes for ACL Capabilities and MAC device isa device eisa options AUTO_EOI_1 options AUTO_EOI_2 device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID #Static device numbering options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # SCSI Controllers device ahc # AHA2940 and onboard AIC7xxx devices options AHC_ALLOW_MEMIO # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device cd # SCSI CD-ROMs #device pass # CAM passthrough driver # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc device atkbd device psm device vga # splash screen/screen saver device splash # syscons is the default console driver, resembling an SCO console device sc # Floating point support - do not disable. device npx # Serial (COM) ports device sio # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device ppi # Parallel port interface device options PPC_PROBE_CHIPSET # Pseudo devices - the number indicates how many units to allocated. device loop # Network loopback device ether # Ethernet support device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device vn # Vnode driver (turns a file into a device) device md # Memory "disks" device gif 4 # IPv6 and IPv4 tunneling #device faith 1 # IPv6-to-IPv4 relaying (translation) # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf #Berkeley packet filter # For PnP/PCI sound cards device pcm device sbc device midi device seq device joy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 22 6:53:37 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 04CBC37B7FF; Sat, 22 Jul 2000 06:53:30 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e6MDrCn19806 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Sat, 22 Jul 2000 15:53:15 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e6MDqhq59274; Sat, 22 Jul 2000 15:52:44 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id PAA27477; Sat, 22 Jul 2000 15:52:39 +0200 (CEST) (envelope-from ticso) Date: Sat, 22 Jul 2000 15:52:38 +0200 From: Bernd Walter To: Greg Lehey Cc: Geoff Buckingham , hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: Multiple ro mounts of vinum volume Message-ID: <20000722155238.A27452@cicely8.cicely.de> References: <20000720095513.A50799@chuggalug.clues.com> <20000720183341.I30599@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000720183341.I30599@wantadilla.lemis.com>; from grog@lemis.com on Thu, Jul 20, 2000 at 06:33:42PM +0930 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jul 20, 2000 at 06:33:42PM +0930, Greg Lehey wrote: > On Thursday, 20 July 2000 at 9:55:13 +0100, Geoff Buckingham wrote: > A thing that might bite you here is that ufs is currently limited to 1 > TB per volume. Vinum doesn't have that restriction: if you want to > create a 20 TB volume, and you know how to use the space, Vinum should > work. The problem with ufs is that the block numbers in the inodes > are 32 bit signed values. With 512 byte sectors, the only we can do > it, that means a total address space of 2**9 * 2*31, or 1 TB. At some > time I suspect we're going to need to fix that. Block numbers in inodes are not physical blocks (named sectorsize in UFS source) but logical which is equal to the size of an fragment and thus defaults to 1k. The problem is the driver and VM layer. If vinum would simulate 2k "physical" blocksize it may go up to 4TB if you set the fragment size to 4k. I don't know if any middle calculation might harm or VM is missbehaving. The point I never digged deeper here is because you already sugested changing the driver layer to 64bit byte numbers which was accepted if I remember right. Some of the systems I've setup are near this Limit so I spend some time to find out where the show stoppers are. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 22 7: 2:49 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id F412837B52F; Sat, 22 Jul 2000 07:02:44 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id QAA00262; Sat, 22 Jul 2000 16:01:59 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bernd Walter Cc: Greg Lehey , Geoff Buckingham , hackers@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: Multiple ro mounts of vinum volume In-reply-to: Your message of "Sat, 22 Jul 2000 15:52:38 +0200." <20000722155238.A27452@cicely8.cicely.de> Date: Sat, 22 Jul 2000 16:01:59 +0200 Message-ID: <260.964274519@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <20000722155238.A27452@cicely8.cicely.de>, Bernd Walter writes: >The point I never digged deeper here is because you already sugested >changing the driver layer to 64bit byte numbers which was accepted if >I remember right. Yes, I have this on my plate. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 22 9:46:59 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from unix.megared.net.mx (megamail.megared.com.mx [200.52.207.52]) by hub.freebsd.org (Postfix) with ESMTP id 1D17637B5C5; Sat, 22 Jul 2000 09:46:54 -0700 (PDT) (envelope-from ales@megared.net.mx) Received: from ales (ales.corp.megared.net.mx [200.52.193.2]) by unix.megared.net.mx (8.9.3/8.9.3) with SMTP id LAA89039; Sat, 22 Jul 2000 11:43:54 -0500 (CDT) (envelope-from ales@megared.net.mx) Message-ID: <01aa01bff3fc$4d59c460$02c134c8@megared.net.mx> From: "Alejandro Ramirez" To: "Kenneth D. Merry" Cc: , References: <028401bff326$78f210e0$02c134c8@megared.net.mx> <20000721224722.A34948@panzer.kdm.org> Subject: Re: SCSI Bus Reset & Frozen System with ahc driver !!! Date: Sat, 22 Jul 2000 11:45:54 -0500 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Fri, Jul 21, 2000 at 10:15:15 -0500, Alejandro Ramirez wrote: > > (sa0:ahc0:0:6:0): SCB 0x6b - timed out in command phase, SEQADDR == 0x152 > > (sa0:ahc0:0:6:0): BDR message in message buffer > > (sa0:ahc0:0:6:0): SCB 0x6b - timed out in command phase, SEQADDR == 0x152 > > (sa0:ahc0:0:6:0): no longer in timeout, status = 34b > > ahc0: Issued Channel A Bus Reset. 5 SCBs aborted > > > > I know that I have to change the tape drive, and I also have eliminating the > > cron job from being executed, but in the mean time I really dont think that > > ist good to freebsd not to be able to recover it self from this state, > > resetting the SCSI bus where the disks also lives, and got frozen by this??? > > could this be a bug in the ahc driver??? > > The 'timed out in command phase' message probably indicates that you have a > cabling or termination problem. Actually the cabling & termination are OK double checked that. > FreeBSD shouldn't freeze, and it's possible that the issue that causes the > freezes has been fixed in a later version of FreeBSD, but I don't know for > sure. Probably, I will upgrade to 3.5-STABLE, and I will let you know. Thanks Ales To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 22 9:52:40 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id E944F37B6C9; Sat, 22 Jul 2000 09:52:34 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA42592; Sat, 22 Jul 2000 10:52:25 -0600 (MDT) (envelope-from ken) Date: Sat, 22 Jul 2000 10:52:25 -0600 From: "Kenneth D. Merry" To: Alejandro Ramirez Cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI Bus Reset & Frozen System with ahc driver !!! Message-ID: <20000722105225.A42525@panzer.kdm.org> References: <028401bff326$78f210e0$02c134c8@megared.net.mx> <20000721224722.A34948@panzer.kdm.org> <01aa01bff3fc$4d59c460$02c134c8@megared.net.mx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <01aa01bff3fc$4d59c460$02c134c8@megared.net.mx>; from ales@megared.net.mx on Sat, Jul 22, 2000 at 11:45:54AM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Jul 22, 2000 at 11:45:54 -0500, Alejandro Ramirez wrote: > > FreeBSD shouldn't freeze, and it's possible that the issue that causes the > > freezes has been fixed in a later version of FreeBSD, but I don't know for > > sure. > > Probably, I will upgrade to 3.5-STABLE, and I will let you know. On second thought, since you've got everything on that SCSI bus, I'm not sure the system can avoid freezing if the bus locks up. I kinda doubt you'll be able to fix the problem by upgrading. Since you have a 7895, it might be worthwhile to put the tape drive on the second SCSI bus. That way the bus your system disk is on won't get locked up. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 22 9:57:34 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from unix.megared.net.mx (megamail.megared.com.mx [200.52.207.52]) by hub.freebsd.org (Postfix) with ESMTP id E08FB37B6C9; Sat, 22 Jul 2000 09:57:29 -0700 (PDT) (envelope-from ales@megared.net.mx) Received: from ales (ales.corp.megared.net.mx [200.52.193.2]) by unix.megared.net.mx (8.9.3/8.9.3) with SMTP id LAA91786; Sat, 22 Jul 2000 11:54:40 -0500 (CDT) (envelope-from ales@megared.net.mx) Message-ID: <029101bff3fd$ce40ec60$02c134c8@megared.net.mx> From: "Alejandro Ramirez" To: "Kenneth D. Merry" Cc: , References: <028401bff326$78f210e0$02c134c8@megared.net.mx> <20000721224722.A34948@panzer.kdm.org> <01aa01bff3fc$4d59c460$02c134c8@megared.net.mx> <20000722105225.A42525@panzer.kdm.org> Subject: Re: SCSI Bus Reset & Frozen System with ahc driver !!! Date: Sat, 22 Jul 2000 11:56:40 -0500 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Probably, I will upgrade to 3.5-STABLE, and I will let you know. > > On second thought, since you've got everything on that SCSI bus, I'm not > sure the system can avoid freezing if the bus locks up. > > I kinda doubt you'll be able to fix the problem by upgrading. > > Since you have a 7895, it might be worthwhile to put the tape drive on the > second SCSI bus. That way the bus your system disk is on won't get locked > up. That sounds good to me. Thanks Ales To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 22 18:26:42 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from amonduul.ecn.ou.edu (amonduul.ecn.ou.edu [129.15.119.201]) by hub.freebsd.org (Postfix) with ESMTP id 808E637B562 for ; Sat, 22 Jul 2000 18:26:36 -0700 (PDT) (envelope-from servalan!ichotolot.servalan.com!rmtodd@amonduul.ecn.ou.edu) Received: from servalan (3705 bytes) by amonduul.ecn.ou.edu via rmail with P:uucp/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) id for freebsd.org!freebsd-scsi; Sat, 22 Jul 2000 20:26:12 -0500 (CDT) (Smail-3.2.0.111 2000-Feb-17 #1 built 2000-Apr-4) Received: from ichotolot.servalan.com([127.0.0.1]) (3363 bytes) by servalan.servalan.com via sendmail with P:esmtp/R:smart_host/T:uux (sender: ) id for ; Sat, 22 Jul 2000 20:06:36 -0500 (CDT) (Smail-3.2.0.106 1999-Mar-31 #1 built 1999-Aug-10) Message-Id: To: "George W. Dinolt" Cc: freebsd-scsi@freebsd.org, rmtodd@servalan.servalan.com Subject: Re: (noperiph:ahc0:0:-1:-1): ... error In-Reply-To: Your message of "Fri, 21 Jul 2000 22:01:42 PDT." <39792AB6.F4B7B1CB@pacbell.net> Date: Sat, 22 Jul 2000 20:06:35 -0500 From: Richard Todd Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <39792AB6.F4B7B1CB@pacbell.net>, "George W. Dinolt" writes: >I originally posted this on -current, but Matthew Jacob > suggested that I post this on -scsi as well. Ditto. I'm seeing problems similar, but not identical, to those seen by George W. Dinolt. >I am trying to boot a recent kernel (as of yesterday) and am seeing the >following pair of contiguous error messages when I try to boot:: > >(noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. >panic: Bogus resid sgptr value 0xbd68609 > I saw the (noperiph...) message you saw. After that, the machine didn't panic, but it didn't work very well, either. It did, after a few seconds, detect the SCSI tape drive I had (sa0), but failed on detecting the SCSI disk and CDROM, repeatedly timing out and resetting the bus. Here are some of the messages, as best I could write them down (since the machine never got to the point where it acknowledged having its disks, there was no way it could dump on panic()). (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. (noperiph:ahc1:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. SMP: AP CPU #1 Launched! sa0 at ahc0 bus 0 target 0 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15) Mounting root from ufs:/dev/da0s2a (da0:ahc0:0:6:0) SCB 0x3 - timed out in Command phase, SEQADDR=0xa0 (da0:ahc0:0:6:0) Other SCB Timeout (cd0:ahc0:0:1:0) SCB 0x9 - timed out in Command phase, SEQADDR=0xa0 (cd0:ahc0:0:1:0) BDR message in message buffer (cd0:ahc0:0:1:0) SCB 0x9 - timed out in Command phase, SEQADDR=0x9f (cd0:ahc0:0:1:0) no longer in timeout, status=34b ahc0: Issued Channel A Bus Reset, 2 SCBs aborted and then the bus reset and it did more of the same; eventually it gave up and declared itself unable to attach da0 and cd0. This was on an SMP box (Tyan Thunder 100GX), with an aic7895 SCSI controller, and the following three SCSI devices: sa0 at ahc0 bus 0 target 0 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15) Mounting root from ufs:/dev/da0s2a da0 at ahc0 bus 0 target 6 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) cd0 at ahc0 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present A kernel built as of July 13th does not have this problem, so whatever caused this is presumably somewhere in the big CAM commit of the past week. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 22 21: 6:29 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.zuhause.org (www.zuhause.org [205.215.217.178]) by hub.freebsd.org (Postfix) with ESMTP id 9AF4837B757 for ; Sat, 22 Jul 2000 21:06:26 -0700 (PDT) (envelope-from bruce@zuhause.mn.org) Received: by mail.zuhause.org (Postfix, from userid 1001) id 38F7C7C18; Sat, 22 Jul 2000 23:06:25 -0500 (CDT) From: Bruce Albrecht MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14714.28481.138432.42784@celery.zuhause.org> Date: Sat, 22 Jul 2000 23:06:25 -0500 (CDT) To: freebsd-scsi@freebsd.org Subject: Transfer rate of LVD drives really 6.6 MB/s? X-Mailer: VM 6.72 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I recently bought a Tekram 390U2W controller and switched my IBM DDRS-39130 (68 pin) drive from SE to LVD, and also attached an IBM DRVS18D (SCA with a Corpsys LVD rated 80-68 converter), but instead of seeing 80 MB/s transfers, the output from dmesg and camcontrol say 6.6 MB/s. What's up with this? I'm using the supplied 68 pin cable and LVD/SE terminator supplied with the 390U2W controller. Even if I only have the DDRS-39130 connected, I still see it claim 6.6MB/s. I'm running 4.0-stable from early June, probably around June 10-12. Here's some of the messages from dmesg: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-STABLE #0: Mon Jun 12 21:55:18 CDT 2000 root@celery.zuhause.org:/usr/local/usr.src/src/sys/compile/celery Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (465.50-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbff real memory = 268369920 (262080K bytes) config> q avail memory = 257052672 (251028K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 IOAPIC #0 intpin 16 -> irq 11 IOAPIC #0 intpin 17 -> irq 5 IOAPIC #0 intpin 18 -> irq 9 IOAPIC #0 intpin 19 -> irq 10 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 sym0: <895> port 0xd400-0xd4ff mem 0xec001000-0xec001fff,0xec003000-0xec0030ff irq 11 at device 8.0 on pci0 sym0: Tekram NVRAM, ID 7, Fast-40, LVD, parity checking ahc0: port 0xe000-0xe0ff mem 0xec002000-0xec002fff irq 11 at device 12.0 on pci0 ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: port 0xe400-0xe4ff mem 0xec004000-0xec004fff irq 11 at device 12.1 on pci0 ahc1: aic7895 Wide Channel B, SCSI Id=7, 16/255 SCBs ahc1: Host Adapter Bios disabled. Using default SCSI device parameters Mounting root from ufs:/dev/da0a cd0 at ahc0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: cd present [116374 x 2048 byte records] da1 at sym0 bus 0 target 9 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 6.600MB/s transfers (16bit), Tagged Queueing Enabled da1: 17519MB (35879135 512 byte sectors: 255H 63S/T 2233C) da0 at sym0 bus 0 target 3 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 6.600MB/s transfers (16bit), Tagged Queueing Enabled da0: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message