From owner-freebsd-scsi Sun Jul 23 0:13:44 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front4m.grolier.fr (front4m.grolier.fr [195.36.216.54]) by hub.freebsd.org (Postfix) with ESMTP id 35F1937B984 for ; Sun, 23 Jul 2000 00:13:40 -0700 (PDT) (envelope-from groudier@club-internet.fr) Received: from nas1-32.cgy.club-internet.fr (nas1-32.cgy.club-internet.fr [195.36.197.32]) by front4m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id JAA19661; Sun, 23 Jul 2000 09:07:59 +0200 (MET DST) Date: Sun, 23 Jul 2000 08:53:19 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Bruce Albrecht Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Transfer rate of LVD drives really 6.6 MB/s? In-Reply-To: <14714.28481.138432.42784@celery.zuhause.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This looks like a problem that has been fixed. You can perform a renego for FAST-40 after boot (using camcontrol) with the kernel you are using, but updating the driver files to lastest ones should fix the problem: You just have to replace src/sys/dev/sym/* by the latest driver files from RELENG4 or HEAD and rebuild your kernel. You may let me know if this actually fixes the problem. Regards, G=E9rard. On Sat, 22 Jul 2000, Bruce Albrecht wrote: > 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=20 > seeing 80 MB/s transfers, the output from dmesg and camcontrol say 6.6=20 > 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=20 > 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=20 > the messages from dmesg:=20 >=20 > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > =09The 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 =3D "GenuineIntel" Id =3D 0x665 Stepping =3D 5 > Features=3D0x183fbff > real memory =3D 268369920 (262080K bytes) > config> q > avail memory =3D 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 pci= 0 > pci1: on pcib1 > sym0: <895> port 0xd400-0xd4ff mem 0xec001000-0xec001fff,0xec003000-0xec0= 030ff irq 11 at device 8.0 on pci0 > sym0: Tekram NVRAM, ID 7, Fast-40, LVD, parity checking > ahc0: port 0xe000-0xe0ff mem 0xec002= 000-0xec002fff irq 11 at device 12.0 on pci0 > ahc0: aic7895 Wide Channel A, SCSI Id=3D7, 16/255 SCBs > ahc1: port 0xe400-0xe4ff mem 0xec004= 000-0xec004fff irq 11 at device 12.1 on pci0 > ahc1: aic7895 Wide Channel B, SCSI Id=3D7, 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=20 > 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=20 > 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=20 > da0: 6.600MB/s transfers (16bit), Tagged Queueing Enabled > da0: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) >=20 >=20 > 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 Jul 23 12:26:41 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from garm.bart.nl (garm.bart.nl [194.158.170.13]) by hub.freebsd.org (Postfix) with ESMTP id 315CB37B58F; Sun, 23 Jul 2000 12:26:30 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org (root@daemon.ninth-circle.org [195.38.210.81]) by garm.bart.nl (8.10.1/8.10.1) with ESMTP id e6NJQMo24688; Sun, 23 Jul 2000 21:26:23 +0200 (CEST) Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id VAA97188; Sun, 23 Jul 2000 21:26:21 +0200 (CEST) (envelope-from asmodai) Date: Sun, 23 Jul 2000 21:26:21 +0200 From: Jeroen Ruigrok/Asmodai To: scsi@freebsd.org Cc: sos@freebsd.org Subject: CAM layer Message-ID: <20000723212621.P49169@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is there anybody working on getting the CAM layer a bit less SCSI-specific in order to easily fold ATA under it so that we have a common access method, which CAM should be? -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Any road leads to the end of the world... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jul 23 12:34: 7 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id BD9D437B56D; Sun, 23 Jul 2000 12:34:03 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA14095; Sun, 23 Jul 2000 21:34:00 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200007231934.VAA14095@freebsd.dk> Subject: Re: CAM layer In-Reply-To: <20000723212621.P49169@daemon.ninth-circle.org> from Jeroen Ruigrok/Asmodai at "Jul 23, 2000 09:26:21 pm" To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai) Date: Sun, 23 Jul 2000 21:34:00 +0200 (CEST) Cc: scsi@freebsd.org, sos@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Jeroen Ruigrok/Asmodai wrote: > Is there anybody working on getting the CAM layer a bit less > SCSI-specific in order to easily fold ATA under it so that we have a > common access method, which CAM should be? I've played a bit with having the ATAPI part use CAM, but the results was not encouraging, having ATA devices use CAM is a different animal and would probably require significant changes to CAM. Another thing is the binary bloat CAM would add to an ATA/ATAPI only system, and that is probably the most significant issue in the projects I work on currently... So, thats some of the reasons this falls further and further down on my TODO list... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jul 23 13:36:42 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from njord.bart.nl (njord.bart.nl [194.158.170.15]) by hub.freebsd.org (Postfix) with ESMTP id D940837BAFB; Sun, 23 Jul 2000 13:36:38 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org (root@daemon.ninth-circle.org [195.38.210.81]) by njord.bart.nl (8.10.1/8.10.1) with ESMTP id e6NKa5C13633; Sun, 23 Jul 2000 22:36:10 +0200 (CEST) Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id WAA99102; Sun, 23 Jul 2000 22:31:50 +0200 (CEST) (envelope-from asmodai) Date: Sun, 23 Jul 2000 22:31:49 +0200 From: Jeroen Ruigrok/Asmodai To: Soren Schmidt Cc: scsi@freebsd.org, sos@freebsd.org Subject: Re: CAM layer Message-ID: <20000723223149.R49169@daemon.ninth-circle.org> References: <20000723212621.P49169@daemon.ninth-circle.org> <200007231934.VAA14095@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007231934.VAA14095@freebsd.dk>; from sos@freebsd.dk on Sun, Jul 23, 2000 at 09:34:00PM +0200 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -On [20000723 22:03], Soren Schmidt (sos@freebsd.dk) wrote: >It seems Jeroen Ruigrok/Asmodai wrote: >> Is there anybody working on getting the CAM layer a bit less >> SCSI-specific in order to easily fold ATA under it so that we have a >> common access method, which CAM should be? > >I've played a bit with having the ATAPI part use CAM, but the results >was not encouraging, having ATA devices use CAM is a different animal >and would probably require significant changes to CAM. Well, CAM should be what the name implies, so we need to start working towards that end. >Another thing is the binary bloat CAM would add to an ATA/ATAPI >only system, and that is probably the most significant issue in >the projects I work on currently... Would you care to substantiate this more? I come from a background where I do know ATA and SCSI on an average-good hardware level, but I don't know too much about the programming issues and thus am a bit left in the darkness when you say binary bloat. Or so you mean that adding the abstraction layer will mean simply larger drivers due to compiling/linking them in? I could envision that in this case you could make the interfacing layer a bit more abstract and less tied in, so that the drivers itself are still small (getting smaller mayhaps) and there is just one interface method with its SCSI/ATA backend to solve things. But its late and my mind races a bit too fast for me to really get this picture straight in my head. Explanations, ideas and such all welcome, since I really want to understand the whole she-bang. >So, thats some of the reasons this falls further and further down >on my TODO list... Any other reasons, other than time, social life (hah!) and such? =) -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Black as coal, my sunken Soul, will it ever be saved? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jul 23 13:55: 9 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CDCAC37BAFB; Sun, 23 Jul 2000 13:55:05 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA22074; Sun, 23 Jul 2000 13:55:02 -0700 Date: Sun, 23 Jul 2000 13:55:05 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jeroen Ruigrok/Asmodai Cc: scsi@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: CAM layer In-Reply-To: <20000723212621.P49169@daemon.ninth-circle.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've thought about it some, but since sos has such a lock on the current ATA stuff I've not thought very far- sos and I don't get along very well which has hampered taking the thinking very far. The NetBSD midlayer has a good example of SCSI/ATAPI in one layer. It probably wouldn't be *too* hard to add this all to CAM. It's really less of a CAM issue than finding the right glue hooks so that an ATAPI sim interface happens. I suspect that Justin's thought about this a bit more. In another context I've been fooling around with some of the newer ATA spec thingies, and it would be to *BSD's advantage to have a unified ATAPI/SCSI handler as there are many places of complete overlap. But since I consider sos essenitally the complete owner of any of the ATA stuff now, it's really up to him. We have a prettyu reasonably working i386 implementation. I think about a half day's work could dma-busify it (with no real performance penalty) so I'd feel more comfortable about the alpha platform support being solid. But whether or not there is a net benefit to merged support such that da && sa && cd drive ATAPI devices is open to question, and not just on a purely technical level. > Is there anybody working on getting the CAM layer a bit less > SCSI-specific in order to easily fold ATA under it so that we have a > common access method, which CAM should be? > > -- > Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] > Documentation nutter/C-rated Coder BSD: Technical excellence at its best > The BSD Programmer's Documentation Project > Any road leads to the end of the world... > > > 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 Jul 23 13:55:56 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id C42F237B8E7 for ; Sun, 23 Jul 2000 13:55:53 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA22078; Sun, 23 Jul 2000 13:55:46 -0700 Date: Sun, 23 Jul 2000 13:55:48 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Soren Schmidt Cc: Jeroen Ruigrok/Asmodai , scsi@FreeBSD.ORG Subject: Re: CAM layer In-Reply-To: <200007231934.VAA14095@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 23 Jul 2000, Soren Schmidt wrote: > It seems Jeroen Ruigrok/Asmodai wrote: > > Is there anybody working on getting the CAM layer a bit less > > SCSI-specific in order to easily fold ATA under it so that we have a > > common access method, which CAM should be? >=20 > I've played a bit with having the ATAPI part use CAM, but the results > was not encouraging, having ATA devices use CAM is a different animal > and would probably require significant changes to CAM. What do you feel needs to change with FreeBSD's CAM implementation? > Another thing is the binary bloat CAM would add to an ATA/ATAPI > only system, and that is probably the most significant issue in > the projects I work on currently... >=20 > So, thats some of the reasons this falls further and further down > on my TODO list... >=20 >=20 > -S=F8ren >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jul 23 17:56:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from guru.mired.org (zoom0-048.telepath.com [216.14.0.48]) by hub.freebsd.org (Postfix) with SMTP id 1284237B7A6 for ; Sun, 23 Jul 2000 17:56:06 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 5385 invoked by uid 100); 24 Jul 2000 00:55:38 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14715.37898.771990.675489@guru.mired.org> Date: Sun, 23 Jul 2000 19:55:38 -0500 (CDT) To: scsi@freebsd.org Subject: forwarded message from Mike Meyer X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On the advice of a couple of people on -current, I'm resending this to -scsi. The responses there include at least one other person having problems with recent changes (on a 7895), and comments that others are having problems as well. Thanx, at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 1 lun 0 (pass1,da1) at scbus0 target 3 lun 0 (pass2,da2) at scbus0 target 4 lun 0 (pass3,cd0) at scbus0 target 5 lun 0 (pass4,cd1) at scbus0 target 6 lun 0 (pass5) Target 0 is the system disk: /, /var, /usr, swap and some scratch space. Target 1 is data: /home, more scratch space (/usr/obj lives there) and more swap. The SCSI bus is: AM12S(6) -- AIC(7) -- da(1) -- da(0) -- jazz(3) -- cd(4) -- cd(5) -- term plug I'm a bit leary of the external scanner, so I unplugged it, made sure the AIC had termination set properly, and rebooted single user. Mounted /usr read-only, mounted the scratch space on da1, and did a cp -r of /usr to the scratch space. The system locked up in the same state as described above. Trying the same test - except I left the scanner plugged in - with a kernel built with the old version of the ahc driver worked fine. In fact, building the world with /usr/src and /usr/obj on different disks has been working fine for a while now. I'm hoping to get some guidance from someone who's familiar with the code before I start digging into it. If more information would be useful (dmesg output? config file? other?), let me know. If there's somne specific testing to do - including, if needed, borrowing a 2940 and moving the drives to that to try things on - let me know. Thanx, ; Sun, 23 Jul 2000 22:59:29 -0700 (PDT) (envelope-from gdinolt@pacbell.net) Received: from pacbell.net ([63.201.59.169]) by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FY600MV1T0DGT@mta5.snfc21.pbi.net> for scsi@freebsd.org; Sun, 23 Jul 2000 22:38:38 -0700 (PDT) Date: Sun, 23 Jul 2000 22:39:20 -0700 From: "George W. Dinolt" Subject: (noperiph:ahc0:0:-1:-1) & forwarded message ... To: scsi@freebsd.org Cc: rmtodd@servalan.servalan.com, mjacob@feral.com, Gemorga2@vt.edu, mwm@mired.org Message-id: <397BD688.983DCD97@pacbell.net> MIME-version: 1.0 X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 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 Last week I reported on a pair of errors I have had trying to boot my 5.0-current system using the new (July 18 and later) ahc code. Specifically (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. panic: Bogus resid sgptr value 0xbd68609 I have done a little more investigation. My scsi chain normally contains the following (taken from a dmesg from a kernel.GENERIC from July 16) ----------------- Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-20000716-CURRENT #0: Sun Jul 16 12:24:18 GMT 2000 root@usw2.freebsd.org:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (451.02-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 ... ahc0: port 0xe000-0xe0ff mem 0xe0200000-0xe0200fff irq 9 at device 14.0 on pci0 ... pass3 at ahc0 bus 0 target 5 lun 0 pass3: Fixed Scanner SCSI-2 device pass3: 3.300MB/s transfers Mounting root from ufs:/dev/ad0s2a cd0 at ahc0 bus 0 target 3 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 - tray closed da2 at ahc0 bus 0 target 6 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) da2: 2048MB (4194304 512 byte sectors: 255H 63S/T 261C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) da4 at ahc0 bus 0 target 9 lun 0 da4: Fixed Direct Access SCSI-2 device da4: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da4: 8683MB (17783112 512 byte sectors: 255H 63S/T 1106C) da3 at ahc0 bus 0 target 8 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 8683MB (17783112 512 byte sectors: 255H 63S/T 1106C) da1 at ahc0 bus 0 target 4 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) ... ---------------- Note the pass3 device, the UMAX astra 1220s V1.3 scanner I have one disk and the cdrw on the "internel" end of the SCSI chain off my 2940 UW. The other four disks are in a separate box (with cooling) on a 68 pin bus. The scanner is attached via a 68pin to 25pin "cable/adapter" from the other external 68 pin connector on the external box. If I have the scanner attached, then the two errors from above appear and the system refuses to boot. This happens whether I put the terminator on the scanner or not. If I remove the scanner from the chain, then the new kernel (after July 18) yields the error message (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. still appears, but the system continues to boot and works fine afterwords as far as I can tell. I still would like to check all my disks for correct termination conditions. But, since the system worked before, I am hopeful that it will work again in its current state, with scanner attached. If someone can give me further pointers, I would appreciate it. Many thanks. George Dinolt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 24 11:43:28 2000 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 0186E37B6C2 for ; Mon, 24 Jul 2000 11:43:22 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from caspian.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id MAA17178; Mon, 24 Jul 2000 12:43:13 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <200007241843.MAA17178@pluto.plutotech.com> To: "George W. Dinolt" Cc: scsi@FreeBSD.org Subject: Re: (noperiph:ahc0:0:-1:-1): ... error Date: Mon, 24 Jul 2000 12:43:59 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. > panic: Bogus resid sgptr value 0xbd68609 ^^^^^^^^^<==== Is this value correct? Please double check the value printed out by the panic line. The panic checks the last three bits of the value printed out, and having bit one set should have prevented the routine from progressing this far (bit one is SG_LIST_NULL). So, either the value wass not written down correctly, the compiler is generating bad code, or something is corrupting the kernel text image in memory. Can you also provide a full dmesg listing for your system based on an earlier kernel? I'm most interested in what chipset your computer uses. Thanks, Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 24 11:48:16 2000 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 55ECE37BCB5 for ; Mon, 24 Jul 2000 11:48:10 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from caspian.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id MAA17284; Mon, 24 Jul 2000 12:47:54 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <200007241847.MAA17284@pluto.plutotech.com> To: "NandaKumar P.K." Cc: scsi@FreeBSD.org Subject: Re: System panic with new HBA driver Date: Mon, 24 Jul 2000 12:48:40 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <20000629120911.22792.qmail@web1904.mail.yahoo.com> you wrote: > Hi, > > I am in the process of testing all the error > conditions of my FreeBSD 3.4 driver for the HBA. I > have 4 partitions on the Fibre Channel disk and a copy > is done from one partition to other. Now if remove > the disk when this is going on the firmware reports > timeout error and i report back the CAM_CMD_TIMEOUT > status. Now after sometime system comes with a sync > cache command and i report the same status > CAM_CMD_TIMEOUT for this command also. After this > system panic. Is there any way to avoid this condition > ? Since the disks are hot swapable this may be > condition i can expect in the real situation. If a device goes completely away, you should return CAM_SEL_TIMEOUT. That doesn't explain the panic in the sync cache code. Have you bothered to debug why the system panics? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 24 12: 0:57 2000 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 D1D6737BD9F for ; Mon, 24 Jul 2000 12:00:47 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from caspian.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id NAA17859; Mon, 24 Jul 2000 13:00:39 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <200007241900.NAA17859@pluto.plutotech.com> To: mjacob@feral.com Cc: scsi@FreeBSD.org Subject: Re: CAM layer Date: Mon, 24 Jul 2000 13:01:24 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > On Sun, 23 Jul 2000, Soren Schmidt wrote: > >> It seems Jeroen Ruigrok/Asmodai wrote: >> > Is there anybody working on getting the CAM layer a bit less >> > SCSI-specific in order to easily fold ATA under it so that we have a >> > common access method, which CAM should be? >> >> I've played a bit with having the ATAPI part use CAM, but the results >> was not encouraging, having ATA devices use CAM is a different animal >> and would probably require significant changes to CAM. > > What do you feel needs to change with FreeBSD's CAM implementation? It needs to be made less SCSI centric. e.g. cam/scsi/cam_xpt_scsi.c with cam/cam_xpt.c offering only common glue. It has been on my list of things to do for a long time, but I just haven't gotten around to it. I think that a large part of the CAM/ATA/ATAPI issue is that the barrier to entry for new subsystems is too high... Someone has to do the "split it out" work first. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 24 12: 9:31 2000 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 D90C837B90C for ; Mon, 24 Jul 2000 12:09:21 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from caspian.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id NAA18106; Mon, 24 Jul 2000 13:09:06 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <200007241909.NAA18106@pluto.plutotech.com> To: "George W. Dinolt" Cc: scsi@FreeBSD.org Subject: Re: (noperiph:ahc0:0:-1:-1) & forwarded message ... In-Reply-To: <397BD688.983DCD97@pacbell.net> Date: Mon, 24 Jul 2000 13:09:52 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <397BD688.983DCD97@pacbell.net> you wrote: > Last week I reported on a pair of errors I have had trying to boot my > 5.0-current system using the new (July 18 and later) ahc code. Sorry for the late reply. I had a mail configuration problem. My original message to you should be there now, but based on this message, I have some more ideas. > If I have the scanner attached, then the two errors from above appear > and the system refuses to boot. This happens whether I put the > terminator on the scanner or not. > > If I remove the scanner from the chain, then the new kernel (after July > 18) yields the error message > > (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. > > still appears, but the system continues to boot and works fine > afterwords as far as I can tell. It does indeed sound like the termination settings have changed in the latest code drop although they shouldn't have for your card type. Can you boot your system with -v and note the message the driver displays regarding termination on your card? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 24 12:16:41 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 3402D37BC4B for ; Mon, 24 Jul 2000 12:16:37 -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 OAA29520 for ; Mon, 24 Jul 2000 14:14:24 -0500 (EST) Date: Mon, 24 Jul 2000 14:14:48 -0500 (EST) From: "Jason T. Miller" To: freebsd-scsi@freebsd.org Subject: Re: CAM layer In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 23 Jul 2000, Matthew Jacob wrote: > platform support being solid. But whether or not there is a net benefit to > merged support such that da && sa && cd drive ATAPI devices is open to > question, and not just on a purely technical level. I don't see much benefit there, except not having to maintain separate drivers. What I want to do, personally, is shoot random CDBs at ATAPI devices; that is, an ATAPI passthrough device. Linux does it with the IDE-SCSI emulation layer; this allows one to use cdrecord, cdrdao, etc, on supported IDE devices, amongst other neat things. Yes, I know, ATAPI CD-R support is present in the kernel, but it doesn't work with all drives (with the proliferation of weird CD-R command sets, SCSI-3 MMC or no, it probably never will); in all honesty, I'd rather see kernel bloat from a clean architectural model than from application-specific stuff like CD burning; this process does not (and will never) fit the UNIX device model, and is therefore hopelessly tied to IOCTLs (or a so-called "funky character device interface" with command packets etc); most of these IOCTLs are more-or-less directly tied to SCSI (or ATAPI) commands (and to support most older, pre-MMC drives, vendor-unique commands; even with MMC, we have different media types and drive capabilities). Furthermore, if we're talking anything more complicated than "one-off" CD mastering, we more or less need full control of the bus, to deal with things such as drives that fail to disconnect from the bus for a few ms when the write process is beginning (that is, after the buffer is full but before the write laser "gets its groove"), etc. Again, I don't want to deal with this in the kernel. Now that I think about it, I don't want to do multi-CD duplication over an ATA bus; this, however, is not my point. Support for packet-written CD-Rs and CD-RWs, multisession support, R-W subchannel control, ISRCs, etc. would be nice; again, this would add significant kernel bloat with little gain. Also, in its current incarnation, the CD driver will never support block sizes that aren't a multiple of 512; therefore, reading CD-ROM XA form 2 discs and non-XA mode 2 discs (although such discs are rare outside of CD-I; I'm not sure about Photo CD -- do we handle these?) is impossible through the device driver. ATAPI tape drives would also benefit from a CAM interface: how, through the tape device driver, could one set mode pages or retrieve diagnostic information via LOG SENSE? Very nice features indeed in a high-end system; it's nice to be able to control the drive's error-handling and get retry counts and such. Finally, a passthrough device is always nice when prototyping new device code. ATAPI (but not ATA), like 1394 or fibre channel, can be thought of as just another SCSI command transport (that is, a physical layer in the SCSI-3 architecture model), therefore, support for it can and should be worked into CAM. All this from someone who would use SCSI for all of the above, though I do admit to owning one old 2x ATAPI CD-R (which doesn't work with the 4.0 kernel-level CD-R code). -jtm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 24 17:55:58 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 8BC3237B51C for ; Mon, 24 Jul 2000 17:55:53 -0700 (PDT) (envelope-from dgilbert@office.tor.velocet.net) Received: from office.tor.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 7E094138019 for ; Mon, 24 Jul 2000 20:55:46 -0400 (EDT) Received: (from dgilbert@localhost) by office.tor.velocet.net (8.9.3/8.9.3) id UAA70200; Mon, 24 Jul 2000 20:55:46 -0400 (EDT) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14716.58769.839776.66400@trooper.velocet.net> Date: Mon, 24 Jul 2000 20:55:45 -0400 (EDT) X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid To: freebsd-scsi@freebsd.org Subject: Advansys SCSI controllers. Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (This is a copy of my post to -stable some days ago...) I have found that the Advansys controller which probes as: adw0: port 0xe800-0xe83f mem 0xe6820000-0xe68200ff irq 11 at device 9.0 on pci0 adw0: SCSI ID 7, High & Low SE Term Enabled, Queue Depth 253 with drives: da0 at adw0 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: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) da1 at adw0 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: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) will under heavy usage spit out the message: Jul 22 19:00:27 mortar /kernel: (da0:adw0:0:0:0): Invalidating pack After which, the machine will respond to incoming telnet requests, but never print login. I assume this to be because the drive is no longer available. This is a server hosted at "rackspace.com". They report that this definately does not happen under 3.4 (which they consider a standard FreeBSD install), but I've found that it does happen with 4.0 and it appears to happen more often under 4.1-RC2. The message itself comes from CAM (scsi_da.c) in response to an ENXIO return code from the lower driver. A number of ENXIO returns were recently removed from the advansys driver, but they were all in a section dealing with attaching the device, etc. Anyhow, there appear to be several places were ENXIO can happen, and CAM appears to consider this unrecoverable. The server at rackspace.com will likely get IDE drives or a different scsi controller, so this is unfortunately a report without much ability to try patches. Rackspace.com aparently knows of this ... they've had this problem come up before with 4.0 installed customers. Replicating the problem is simple: make buildworld exercises it quite quickly. I will likely create a PR unless someone knows of a fix for this. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 25 11:56:20 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from guru.mired.org (zoom2-187.telepath.com [216.14.2.187]) by hub.freebsd.org (Postfix) with SMTP id C9B9C37B625 for ; Tue, 25 Jul 2000 11:56:15 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 478 invoked by uid 100); 25 Jul 2000 18:55:38 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14717.58026.117126.568975@guru.mired.org> Date: Tue, 25 Jul 2000 13:55:38 -0500 (CDT) To: "Justin T. Gibbs" Cc: scsi@freebsd.org Subject: Re: (noperiph:ahc0:0:-1:-1) & forwarded message ... X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ In-Reply-To: <200007241909.NAA18106@pluto.plutotech.com> Referemces: <200007241909.NAA18106@pluto.plutotech.com>, <397BD688.983DCD97@pacbell.net> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry 'bout the subject on my message - I sometimes forget to fix that in this mailer :-(. > It does indeed sound like the termination settings have changed > in the latest code drop although they shouldn't have for your > card type. Can you boot your system with -v and note the message > the driver displays regarding termination on your card? Sure. This was done using the new ahc drivers. Given that most of the ahc boot message is about termination, here's all of it: ahc0: port 0xe800-0xe8ff mem 0xffaff000-0xffafffff irq 11 at device 14.0 on pci0 ahc0: Reading SEEPROM...done. ahc0: Manual LVD Termination ahc0: BIOS eeprom is present ahc0: Secondary High byte termination Enabled ahc0: Secondary Low byte termination Enabled ahc0: Primary Low Byte termination Enabled ahc0: Primary High Byte termination Enabled ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 32/255 SCBs ahc0: Downloading Sequencer Program... 430 instructions downloaded Thanx, ; Tue, 25 Jul 2000 12:12:49 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id QAA50146 for ; Tue, 25 Jul 2000 16:10:43 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 25 Jul 2000 16:10:43 -0300 (ADT) From: The Hermit Hacker To: freebsd-scsi@freebsd.org Subject: 4.1RC read/write speeds ... 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 Does this look right for a Dual-PIII, no load other then the operating system, idle disk *only* being used for the tests ... just seems low to me: Writing the 232 Megabyte file, 'iozone.tmp'...14.273438 seconds Reading the file...3.328125 seconds IOZONE performance measurements: 17043521 bytes/second for writing the file 73095100 bytes/second for reading the file ============== full configuration fo that machine can be seen at http://atelier.acadiau.ca, but the basics are: ========= ahc0: port 0xa800-0xa8ff mem 0xe0000000-0xe0000fff irq 10 at device 11.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs =========== da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) da1: 8727MB (17873040 512 byte sectors: 255H 63S/T 1112C) Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 25 12:33:19 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 5CDBD37B864 for ; Tue, 25 Jul 2000 12:33:15 -0700 (PDT) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id B40539B3F; Tue, 25 Jul 2000 15:33:11 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id A79ECBA11; Tue, 25 Jul 2000 15:33:11 -0400 (EDT) Date: Tue, 25 Jul 2000 15:33:11 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: The Hermit Hacker Cc: freebsd-scsi@freebsd.org Subject: Re: 4.1RC read/write speeds ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 25 Jul 2000, The Hermit Hacker wrote: > > Does this look right for a Dual-PIII, no load other then the operating > system, idle disk *only* being used for the tests ... just seems low to > me: > > > Writing the 232 Megabyte file, 'iozone.tmp'...14.273438 seconds > Reading the file...3.328125 seconds > > IOZONE performance measurements: > 17043521 bytes/second for writing the file > 73095100 bytes/second for reading the file > > ============== > > full configuration fo that machine can be seen at > http://atelier.acadiau.ca, but the basics are: > > ========= > ahc0: port 0xa800-0xa8ff mem 0xe0000000-0xe0000fff irq 10 at device 11.0 on pci0 > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > =========== > > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) > da1: 8727MB (17873040 512 byte sectors: 255H 63S/T 1112C) > > You may want to try without the quirk entry. From /sys/cam/cam_xpt.c: { /* * Slow when tagged queueing is enabled. (1.5MB/sec versus * 8MB/sec.) * Submitted by: Andrew Gallatin * Best performance with these drives is achieved with * tagged queueing turned off, and write caching turned on. */ { T_DIRECT, SIP_MEDIA_FIXED, west_digital, "WDE*", "*" }, /*quirks*/0, /*mintags*/0, /*maxtags*/0 }, ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 25 12:39:33 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 4917237B8DF for ; Tue, 25 Jul 2000 12:39:29 -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 MAA31740; Tue, 25 Jul 2000 12:48:52 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007251948.MAA31740@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: The Hermit Hacker Cc: freebsd-scsi@freebsd.org Subject: Re: 4.1RC read/write speeds ... In-reply-to: Your message of "Tue, 25 Jul 2000 16:10:43 -0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Jul 2000 12:48:52 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Does this look right for a Dual-PIII, no load other then the operating > system, idle disk *only* being used for the tests ... just seems low to > me: > > > Writing the 232 Megabyte file, 'iozone.tmp'...14.273438 seconds > Reading the file...3.328125 seconds > > IOZONE performance measurements: > 17043521 bytes/second for writing the file > 73095100 bytes/second for reading the file The test is meaningless; you probably have a good portion of the 232MB file in the buffer cache. 17MB/sec is far too fast for one of these lame-duck WD SCSI disks, let alone 73MB/sec. -- ... 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 Tue Jul 25 12:39:38 2000 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 5547A37B927 for ; Tue, 25 Jul 2000 12:39:35 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from caspian.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id NAA48431; Tue, 25 Jul 2000 13:38:39 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <200007251938.NAA48431@pluto.plutotech.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Meyer Cc: "Justin T. Gibbs" , scsi@freebsd.org Subject: Re: (noperiph:ahc0:0:-1:-1) & forwarded message ... In-Reply-To: Your message of "Tue, 25 Jul 2000 13:55:38 CDT." <14717.58026.117126.568975@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Jul 2000 13:39:25 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Sure. This was done using the new ahc drivers. Given that most of the >ahc boot message is about termination, here's all of it: > >ahc0: port 0xe800-0xe8ff mem 0xffaff0 >00-0xffafffff irq 11 at device 14.0 on pci0 >ahc0: Reading SEEPROM...done. >ahc0: Manual LVD Termination >ahc0: BIOS eeprom is present >ahc0: Secondary High byte termination Enabled >ahc0: Secondary Low byte termination Enabled >ahc0: Primary Low Byte termination Enabled >ahc0: Primary High Byte termination Enabled >ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 32/255 SCBs >ahc0: Downloading Sequencer Program... 430 instructions downloaded It seems that your manual LVD Termination is not correct given the picture you drew in your earlier message. Don't you have an external device on this thing? Also, your picture seemed to show that all devices live on the same (LVD?) segment. It that true? When the system hangs, if you are at the console, can you drop into the debugger. You must have options DDB in your kernel to try this. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 25 13: 0:24 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from guru.mired.org (zoom0-223.telepath.com [216.14.0.223]) by hub.freebsd.org (Postfix) with SMTP id F273637BA30 for ; Tue, 25 Jul 2000 13:00:18 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 2118 invoked by uid 100); 25 Jul 2000 19:59:59 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14717.61887.241374.229647@guru.mired.org> Date: Tue, 25 Jul 2000 14:59:59 -0500 (CDT) To: "Justin T. Gibbs" Cc: scsi@freebsd.org Subject: Re: (noperiph:ahc0:0:-1:-1) & forwarded message ... In-Reply-To: <200007251938.NAA48431@pluto.plutotech.com> References: <14717.58026.117126.568975@guru.mired.org> <200007251938.NAA48431@pluto.plutotech.com> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T. Gibbs writes: > >Sure. This was done using the new ahc drivers. Given that most of the > >ahc boot message is about termination, here's all of it: > > > >ahc0: port 0xe800-0xe8ff mem 0xffaff0 > >00-0xffafffff irq 11 at device 14.0 on pci0 > >ahc0: Reading SEEPROM...done. > >ahc0: Manual LVD Termination > >ahc0: BIOS eeprom is present > >ahc0: Secondary High byte termination Enabled > >ahc0: Secondary Low byte termination Enabled > >ahc0: Primary Low Byte termination Enabled > >ahc0: Primary High Byte termination Enabled > >ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 32/255 SCBs > >ahc0: Downloading Sequencer Program... 430 instructions downloaded > > It seems that your manual LVD Termination is not correct given > the picture you drew in your earlier message. Don't you have > an external device on this thing? > > Also, your picture seemed to show that all devices live on the > same (LVD?) segment. It that true? There are two segments. All the drives live on one, and yes, that one is plugged into the LVD socket on the motherboard. The other end of that cable is plugged into an active terminator. The slower devices are on socket adapters to go from 68 to 50 pins. The second is on the 50 pin socket on the motherboard, and runs to an expansion socket (50pin HD), and then to an external scanner. > When the system hangs, if you are at the console, can you drop > into the debugger. You must have options DDB in your kernel > to try this. Are you just curious about whether or not I can, or is there something specific you'd like to know? If the former, the system is still responding to interrupts - it echos characters and answers to pings. Does that answer the question? Thanx, ; Tue, 25 Jul 2000 13:22:04 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from caspian.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id OAA50400; Tue, 25 Jul 2000 14:21:11 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <200007252021.OAA50400@pluto.plutotech.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Meyer Cc: "Justin T. Gibbs" , scsi@freebsd.org Subject: Re: (noperiph:ahc0:0:-1:-1) & forwarded message ... In-Reply-To: Your message of "Tue, 25 Jul 2000 14:59:59 CDT." <14717.61887.241374.229647@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Jul 2000 14:21:57 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> Also, your picture seemed to show that all devices live on the >> same (LVD?) segment. It that true? > >There are two segments. All the drives live on one, and yes, that one >is plugged into the LVD socket on the motherboard. The other end of >that cable is plugged into an active terminator. The slower devices >are on socket adapters to go from 68 to 50 pins. > >The second is on the 50 pin socket on the motherboard, and runs to an >expansion socket (50pin HD), and then to an external >scanner. So the bus is not "T-ed" at the motherboard's 50pin connector? Just wanted to make sure that having the single ended bus terminated, as the driver reported, is correct. >> When the system hangs, if you are at the console, can you drop >> into the debugger. You must have options DDB in your kernel >> to try this. > >Are you just curious about whether or not I can, or is there something >specific you'd like to know? If the former, the system is still >responding to interrupts - it echos characters and answers to >pings. Does that answer the question? A stack trace from the hung system would be useful. db> trace -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 25 13:55:33 2000 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 56BEC37B6DD for ; Tue, 25 Jul 2000 13:55:30 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from caspian.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id OAA51488; Tue, 25 Jul 2000 14:55:22 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <200007252055.OAA51488@pluto.plutotech.com> To: David Gilbert Cc: scsi@FreeBSD.org Subject: Re: Advansys SCSI controllers. X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <14716.58769.839776.66400@trooper.velocet.net> Date: Tue, 25 Jul 2000 14:56:08 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <14716.58769.839776.66400@trooper.velocet.net> you wrote: ... > da0 at adw0 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 Enable d > da0: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) > da1 at adw0 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 Enable d > da1: 17522MB (35885168 512 byte sectors: 255H 63S/T 2233C) > > will under heavy usage spit out the message: > > Jul 22 19:00:27 mortar /kernel: (da0:adw0:0:0:0): Invalidating pack You need to talk to Seagate about updating the firmware on your drives. Just recently I reproduced this problem under 3.4, 4.0-stable, and -current using an adaptec controller on a Cheetah 18XL. After upgrading the firmware on the device, the problems disappeared. It seems that several Seagate U2/U160 devices have inherited a write cache problem that will cause the disk to simply fall off the bus with selection timeouts. With the drives I tested, the disk failed to respond to selection and after several retries by CAM, the system had no choice but to drop the device. Perhaps 3.4 is not as efficient as 4.X in terms of I/O delivery, but you can make it happen there too, if you are persistent. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 25 16: 1:32 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from thelab.hub.org (nat193.142.mpoweredpc.net [142.177.193.142]) by hub.freebsd.org (Postfix) with ESMTP id 44E0F37B712; Tue, 25 Jul 2000 16:01:26 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id TAA93276; Tue, 25 Jul 2000 19:59:27 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 25 Jul 2000 19:59:26 -0300 (ADT) From: The Hermit Hacker To: Mike Smith Cc: freebsd-scsi@freebsd.org Subject: Re: 4.1RC read/write speeds ... In-Reply-To: <200007251948.MAA31740@mass.osd.bsdi.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, 25 Jul 2000, Mike Smith wrote: > > > > Does this look right for a Dual-PIII, no load other then the operating > > system, idle disk *only* being used for the tests ... just seems low to > > me: > > > > > > Writing the 232 Megabyte file, 'iozone.tmp'...14.273438 seconds > > Reading the file...3.328125 seconds > > > > IOZONE performance measurements: > > 17043521 bytes/second for writing the file > > 73095100 bytes/second for reading the file > > The test is meaningless; you probably have a good portion of the 232MB > file in the buffer cache. 17MB/sec is far too fast for one of these > lame-duck WD SCSI disks, let alone 73MB/sec. d'oh ... I wasn't reading it right :( I was reading 1.7/7.3 ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 25 20:33:40 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from guru.mired.org (zoom0-163.telepath.com [216.14.0.163]) by hub.freebsd.org (Postfix) with SMTP id 08C1637BDD4 for ; Tue, 25 Jul 2000 20:33:35 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 760 invoked by uid 100); 26 Jul 2000 02:33:30 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14718.19962.177709.777148@guru.mired.org> Date: Tue, 25 Jul 2000 21:33:30 -0500 (CDT) To: "Justin T. Gibbs" Cc: Mike Meyer , scsi@freebsd.org Subject: Re: (noperiph:ahc0:0:-1:-1) & forwarded message ... In-Reply-To: <200007252021.OAA50400@pluto.plutotech.com> References: <14717.61887.241374.229647@guru.mired.org> <200007252021.OAA50400@pluto.plutotech.com> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T. Gibbs writes: > >The second is on the 50 pin socket on the motherboard, and runs to an > >expansion socket (50pin HD), and then to an external > >scanner. > So the bus is not "T-ed" at the motherboard's 50pin connector? Not unless I've badly misunderstood the SCSI spec. There are two cables connected to the motherboard, which should mean I've got a straight bus. The old SCSI-1 stuff is on the 68-pin cable because routing a cable past those and then to the external expanion would nearly double the length of the internal cables. > Just wanted to make sure that having the single ended bus terminated, > as the driver reported, is correct. Sounds right. The devices on the cable plugged into the LVD socket are reported as SSE by the BIOS boot message, and that cable is indeed terminated. It came from the system integrators that way. Is that wrong? > >> When the system hangs, if you are at the console, can you drop > >> into the debugger. You must have options DDB in your kernel > >> to try this. > >Are you just curious about whether or not I can, or is there something > >specific you'd like to know? If the former, the system is still > >responding to interrupts - it echos characters and answers to > >pings. Does that answer the question? > A stack trace from the hung system would be useful. > > db> trace Well, I couldn't get it into the debugger, but I'm not familiar with the DDB. Ctrl-Alt-Esc does nothing - which is what it does at the single-user shell prompt as well. Do I need to go multi-user to enable this? Also, this time (I rebuilt with sources I supped today), I got a series of error messages I'd not seen before: (da1:ahc0:0:1:0) SCB 0x6 - timed out in Data-in phase, seqadr == 0x85 (da1:ahc0:0:1:0) other SCB Timeout (da1:ahc0:0:0:0) SCB 0x3 - timed out in Data-in phase, seqadr == 0x85 (da1:ahc0:0:0:0) BDR message in message buffer (da1:ahc0:0:0:0) SCB 0x3 - timed out in Data-in phase, seqadr == 0x85 (da1:ahc0:0:0:0) no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted This sequence (with minor variations in the SCB and seqadr numbers, but not the final status) repeated three or four times while I was trying to get it into the debugger. Thanx, ; Tue, 25 Jul 2000 23:04:41 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 13HJyz-0002Vf-00; Tue, 25 Jul 2000 22:43:53 -0700 Date: Tue, 25 Jul 2000 22:43:31 -0700 (PDT) From: Tom Samplonius To: "Chris D. Faulhaber" Cc: The Hermit Hacker , freebsd-scsi@freebsd.org Subject: Re: 4.1RC read/write speeds ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 25 Jul 2000, Chris D. Faulhaber wrote: > > Writing the 232 Megabyte file, 'iozone.tmp'...14.273438 seconds > > Reading the file...3.328125 seconds ... > You may want to try without the quirk entry. ... > * Best performance with these drives is achieved with > * tagged queueing turned off, and write caching turned ... Tagged command queueing isn't a factor if you are only doing one IO at a time, which is exactly what a single iozone process does. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 26 9:13:32 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by hub.freebsd.org (Postfix) with ESMTP id 37C4337BC05 for ; Wed, 26 Jul 2000 09:13:24 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer goliath.siemens.de) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by goliath.siemens.de (8.10.1/8.10.1) with ESMTP id e6QGD6H06196; Wed, 26 Jul 2000 18:13:06 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail2.siemens.de (8.10.1/8.10.1) with ESMTP id e6QGD6F09899; Wed, 26 Jul 2000 18:13:06 +0200 (MET DST) Received: (from localhost) by curry.mchp.siemens.de (8.10.2/8.10.2) id e6QGD6a84218; Date: Wed, 26 Jul 2000 18:13:05 +0200 From: Andre Albsmeier To: "Justin T. Gibbs" Cc: Mike Meyer , scsi@FreeBSD.ORG Subject: Re: (noperiph:ahc0:0:-1:-1) & forwarded message ... Message-ID: <20000726181305.A99461@curry.mchp.siemens.de> References: <14717.58026.117126.568975@guru.mired.org> <200007251938.NAA48431@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200007251938.NAA48431@pluto.plutotech.com>; from gibbs@plutotech.com on Tue, Jul 25, 2000 at 01:39:25PM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 25-Jul-2000 at 13:39:25 -0600, Justin T. Gibbs wrote: > >Sure. This was done using the new ahc drivers. Given that most of the > >ahc boot message is about termination, here's all of it: > > > >ahc0: port 0xe800-0xe8ff mem 0xffaff0 > >00-0xffafffff irq 11 at device 14.0 on pci0 > >ahc0: Reading SEEPROM...done. > >ahc0: Manual LVD Termination > >ahc0: BIOS eeprom is present > >ahc0: Secondary High byte termination Enabled > >ahc0: Secondary Low byte termination Enabled > >ahc0: Primary Low Byte termination Enabled > >ahc0: Primary High Byte termination Enabled > >ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 32/255 SCBs > >ahc0: Downloading Sequencer Program... 430 instructions downloaded > > It seems that your manual LVD Termination is not correct given > the picture you drew in your earlier message. Don't you have > an external device on this thing? > > Also, your picture seemed to show that all devices live on the > same (LVD?) segment. It that true? > > When the system hangs, if you are at the console, can you drop > into the debugger. You must have options DDB in your kernel > to try this. Hi Justin, I didn't follow this thread completely but might we have a problem here that is similar to the one we were talking about a while ago? It was the thing with the 2940U2W not working with a manually terminated LVD bus (automatically worked). -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 26 10:38:35 2000 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 86BB737C16F for ; Wed, 26 Jul 2000 10:38:26 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from caspian.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id LAA75236; Wed, 26 Jul 2000 11:38:04 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <200007261738.LAA75236@pluto.plutotech.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andre Albsmeier Cc: "Justin T. Gibbs" , Mike Meyer , scsi@FreeBSD.ORG Subject: Re: (noperiph:ahc0:0:-1:-1) & forwarded message ... In-Reply-To: Your message of "Wed, 26 Jul 2000 18:13:05 +0200." <20000726181305.A99461@curry.mchp.siemens.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Jul 2000 11:38:52 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Hi Justin, > >I didn't follow this thread completely but might we have a problem >here that is similar to the one we were talking about a while ago? >It was the thing with the 2940U2W not working with a manually >terminated LVD bus (automatically worked). The 5.0-current driver should have that problem corrected. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 26 11: 2: 8 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (Postfix) with ESMTP id 11F7737BD1C for ; Wed, 26 Jul 2000 11:02:05 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by david.siemens.de (8.10.1/8.10.1) with ESMTP id e6QI1vR12222; Wed, 26 Jul 2000 20:01:57 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail1.siemens.de (8.10.1/8.10.1) with ESMTP id e6QI1tM27482; Wed, 26 Jul 2000 20:01:55 +0200 (MET DST) Received: (from localhost) by curry.mchp.siemens.de (8.10.2/8.10.2) id e6QI1ta84949; Date: Wed, 26 Jul 2000 20:01:55 +0200 From: Andre Albsmeier To: "Justin T. Gibbs" Cc: Andre Albsmeier , Mike Meyer , scsi@FreeBSD.ORG Subject: Re: (noperiph:ahc0:0:-1:-1) & forwarded message ... Message-ID: <20000726200155.A7262@curry.mchp.siemens.de> References: <20000726181305.A99461@curry.mchp.siemens.de> <200007261738.LAA75236@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200007261738.LAA75236@pluto.plutotech.com>; from gibbs@plutotech.com on Wed, Jul 26, 2000 at 11:38:52AM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 26-Jul-2000 at 11:38:52 -0600, Justin T. Gibbs wrote: > >Hi Justin, > > > >I didn't follow this thread completely but might we have a problem > >here that is similar to the one we were talking about a while ago? > >It was the thing with the 2940U2W not working with a manually > >terminated LVD bus (automatically worked). > > The 5.0-current driver should have that problem corrected. Can you please tell me which files I have to check? I like to try it on 3.5-STABLE. Maybe I can figure out what changed and manually import it into 3.5-STABLE... Thanks a lot, -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 26 11: 9:57 2000 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 3A5A237B790 for ; Wed, 26 Jul 2000 11:09:53 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from caspian.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id MAA76493; Wed, 26 Jul 2000 12:08:20 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <200007261808.MAA76493@pluto.plutotech.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andre Albsmeier Cc: "Justin T. Gibbs" , Mike Meyer , scsi@FreeBSD.ORG Subject: Re: (noperiph:ahc0:0:-1:-1) & forwarded message ... In-Reply-To: Your message of "Wed, 26 Jul 2000 20:01:55 +0200." <20000726200155.A7262@curry.mchp.siemens.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Jul 2000 12:09:08 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Can you please tell me which files I have to check? I like >to try it on 3.5-STABLE. Maybe I can figure out what changed >and manually import it into 3.5-STABLE... Everything in sys/dev/aic7xxx. A few things in sys/cam/scsi/scsi_message.h A few things in sys/cam/cam_xpt.c See CVSWeb for details. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 26 11:17: 3 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by hub.freebsd.org (Postfix) with ESMTP id 1821F37BD95 for ; Wed, 26 Jul 2000 11:16:54 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer goliath.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by goliath.siemens.de (8.10.1/8.10.1) with ESMTP id e6QID2H15640; Wed, 26 Jul 2000 20:13:02 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail1.siemens.de (8.10.1/8.10.1) with ESMTP id e6QID1M05328; Wed, 26 Jul 2000 20:13:01 +0200 (MET DST) Received: (from localhost) by curry.mchp.siemens.de (8.10.2/8.10.2) id e6QID1a85062; Date: Wed, 26 Jul 2000 20:13:01 +0200 From: Andre Albsmeier To: "Justin T. Gibbs" Cc: Andre Albsmeier , Mike Meyer , scsi@FreeBSD.ORG Subject: Re: (noperiph:ahc0:0:-1:-1) & forwarded message ... Message-ID: <20000726201301.A7548@curry.mchp.siemens.de> References: <20000726200155.A7262@curry.mchp.siemens.de> <200007261808.MAA76493@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200007261808.MAA76493@pluto.plutotech.com>; from gibbs@plutotech.com on Wed, Jul 26, 2000 at 12:09:08PM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 26-Jul-2000 at 12:09:08 -0600, Justin T. Gibbs wrote: > >Can you please tell me which files I have to check? I like > >to try it on 3.5-STABLE. Maybe I can figure out what changed > >and manually import it into 3.5-STABLE... > > Everything in sys/dev/aic7xxx. > > A few things in sys/cam/scsi/scsi_message.h > > A few things in sys/cam/cam_xpt.c Not to forget sys/dev/aic7xxx/ahc_pci.c, I think. > > See CVSWeb for details. Thanks. I will try to figure it out. Is there any chance that at least the termination fixes can make it into 3.5-STABLE? If not, will it be safe to stick with the automatic termination enabled in the BIOS? Thanks a gain, -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 26 11:36:42 2000 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 05BB037B982 for ; Wed, 26 Jul 2000 11:36:39 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from caspian.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id MAA77295; Wed, 26 Jul 2000 12:36:15 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <200007261836.MAA77295@pluto.plutotech.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andre Albsmeier Cc: "Justin T. Gibbs" , Mike Meyer , scsi@FreeBSD.ORG Subject: Re: (noperiph:ahc0:0:-1:-1) & forwarded message ... In-Reply-To: Your message of "Wed, 26 Jul 2000 20:13:01 +0200." <20000726201301.A7548@curry.mchp.siemens.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Jul 2000 12:37:00 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> Everything in sys/dev/aic7xxx. >> >> A few things in sys/cam/scsi/scsi_message.h >> >> A few things in sys/cam/cam_xpt.c > >Not to forget sys/dev/aic7xxx/ahc_pci.c, I think. Which, last I checked, resides in sys/dev/aic7xxx 8-) >Thanks. I will try to figure it out. Is there any chance >that at least the termination fixes can make it into 3.5-STABLE? Perhaps when I have more time. >If not, will it be safe to stick with the automatic termination >enabled in the BIOS? Yes. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 26 22: 9:22 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by hub.freebsd.org (Postfix) with ESMTP id B7AC437B82C for ; Wed, 26 Jul 2000 22:09:15 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer goliath.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by goliath.siemens.de (8.10.1/8.10.1) with ESMTP id e6R596H00106; Thu, 27 Jul 2000 07:09:06 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail1.siemens.de (8.10.1/8.10.1) with ESMTP id e6R58iN13240; Thu, 27 Jul 2000 07:08:44 +0200 (MET DST) Received: (from localhost) by curry.mchp.siemens.de (8.10.2/8.10.2) id e6R58ia88213; Date: Thu, 27 Jul 2000 07:08:43 +0200 From: Andre Albsmeier To: "Justin T. Gibbs" Cc: Andre Albsmeier , Mike Meyer , scsi@FreeBSD.ORG Subject: Re: (noperiph:ahc0:0:-1:-1) & forwarded message ... Message-ID: <20000727070843.A9125@curry.mchp.siemens.de> References: <20000726201301.A7548@curry.mchp.siemens.de> <200007261836.MAA77295@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200007261836.MAA77295@pluto.plutotech.com>; from gibbs@plutotech.com on Wed, Jul 26, 2000 at 12:37:00PM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 26-Jul-2000 at 12:37:00 -0600, Justin T. Gibbs wrote: > >> Everything in sys/dev/aic7xxx. > >> > >> A few things in sys/cam/scsi/scsi_message.h > >> > >> A few things in sys/cam/cam_xpt.c > > > >Not to forget sys/dev/aic7xxx/ahc_pci.c, I think. > > Which, last I checked, resides in sys/dev/aic7xxx 8-) Well, /sys/pci/ahc_pci.c more or less :-) > > >Thanks. I will try to figure it out. Is there any chance > >that at least the termination fixes can make it into 3.5-STABLE? > > Perhaps when I have more time. > > >If not, will it be safe to stick with the automatic termination > >enabled in the BIOS? > > Yes. OK, that's good news. Meanwhile, I will see if I can backport the changes myself... Thanks again, -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 26 22:56:11 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by hub.freebsd.org (Postfix) with ESMTP id C572937C031 for ; Wed, 26 Jul 2000 22:56:06 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer goliath.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by goliath.siemens.de (8.10.1/8.10.1) with ESMTP id e6R5u2H10123; Thu, 27 Jul 2000 07:56:02 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail1.siemens.de (8.10.1/8.10.1) with ESMTP id e6R5ttN12633; Thu, 27 Jul 2000 07:55:56 +0200 (MET DST) Received: (from localhost) by curry.mchp.siemens.de (8.10.2/8.10.2) id e6R5tta88637; Date: Thu, 27 Jul 2000 07:55:55 +0200 From: Andre Albsmeier To: "Justin T. Gibbs" Cc: Andre Albsmeier , scsi@FreeBSD.ORG Subject: Re: (noperiph:ahc0:0:-1:-1) & forwarded message ... Message-ID: <20000727075555.A62166@curry.mchp.siemens.de> References: <20000726201301.A7548@curry.mchp.siemens.de> <200007261836.MAA77295@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200007261836.MAA77295@pluto.plutotech.com>; from gibbs@plutotech.com on Wed, Jul 26, 2000 at 12:37:00PM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 26-Jul-2000 at 12:37:00 -0600, Justin T. Gibbs wrote: > >> Everything in sys/dev/aic7xxx. > >> > >> A few things in sys/cam/scsi/scsi_message.h > >> > >> A few things in sys/cam/cam_xpt.c > > > >Not to forget sys/dev/aic7xxx/ahc_pci.c, I think. > > Which, last I checked, resides in sys/dev/aic7xxx 8-) > > >Thanks. I will try to figure it out. Is there any chance > >that at least the termination fixes can make it into 3.5-STABLE? This might fix just the termination problems in a 3.5-STABLE tree. Can you please just give it a quick look if I might miss something? The kernel compiles... --- sys/dev/aic7xxx/aic7xxx.h.ORI Thu Jul 27 07:41:12 2000 +++ sys/dev/aic7xxx/aic7xxx.h Thu Jul 27 07:44:15 2000 @@ -373,9 +373,9 @@ #define CF284XSTERM 0x0020 /* SCSI low byte term (284x cards) */ #define CFRESETB 0x0040 /* reset SCSI bus at boot */ #define CFCHNLBPRIMARY 0x0100 /* aic7895 probe B channel first */ -#define CFSEAUTOTERM 0x0400 /* aic7890 Perform SE Auto Termination*/ -#define CFLVDSTERM 0x0800 /* aic7890 LVD Termination */ -/* UNUSED 0xf080 */ +#define CFSEAUTOTERM 0x0400 /* Ultra2 Perform secondary Auto Term*/ +#define CFSELOWTERM 0x0800 /* Ultra2 secondary low term */ +#define CFSEHIGHTERM 0x1000 /* Ultra2 secondary high term */ /* * Bus Release, Host Adapter ID --- sys/pci/ahc_pci.c.ORI Thu Jul 27 07:20:14 2000 +++ sys/pci/ahc_pci.c Thu Jul 27 07:37:20 2000 @@ -1128,15 +1128,15 @@ if (bootverbose) printf("%s: Manual SE Termination\n", ahc_name(ahc)); - enableSEC_low = (adapter_control & CFSTERM); - enableSEC_high = (adapter_control & CFWSTERM); + enableSEC_low = (adapter_control & CFSELOWTERM); + enableSEC_high = (adapter_control & CFSEHIGHTERM); } if ((adapter_control & CFAUTOTERM) == 0) { if (bootverbose) printf("%s: Manual LVD Termination\n", ahc_name(ahc)); - enablePRI_low = enablePRI_high = - (adapter_control & CFLVDSTERM); + enablePRI_low = (adapter_control & CFSTERM); + enablePRI_high = (adapter_control & CFWSTERM); } /* Make the table calculations below happy */ internal50_present = 0; Thanks for your help, -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 27 10:32: 7 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from thelab.hub.org (nat193.142.mpoweredpc.net [142.177.193.142]) by hub.freebsd.org (Postfix) with ESMTP id EAE0137BC82 for ; Thu, 27 Jul 2000 10:32:04 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id OAA66576 for ; Thu, 27 Jul 2000 14:30:03 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 27 Jul 2000 14:30:03 -0300 (ADT) From: The Hermit Hacker To: freebsd-scsi@freebsd.org Subject: FreeBSD I/O vs Solaris ... iozone 3.x Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can someone give me recommendations on a good set of args for iozone3.x to use on a machine with 1gig of RAM, FreeBSD 4.1, an adaptec 2940 controller with an empty 4 gig drive for running the test on? thanks ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 27 11:29:45 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from rigel.pucrs.br (rigel.pucrs.br [200.132.10.13]) by hub.freebsd.org (Postfix) with ESMTP id D90D637B68A; Thu, 27 Jul 2000 11:29:30 -0700 (PDT) (envelope-from mwp@pucrs.br) Received: from pucrs.br (kernel.pucrs.br [200.132.13.17]) by rigel.pucrs.br (8.9.3/8.9.3) with ESMTP id PAA43550; Thu, 27 Jul 2000 15:29:16 -0300 (EST) (envelope-from mwp@pucrs.br) Message-ID: <39807F9C.31D06E15@pucrs.br> Date: Thu, 27 Jul 2000 15:29:48 -0300 From: MauricioWP Organization: PUCRS - Brasil X-Mailer: Mozilla 4.74 [en] (X11; U; FreeBSD 4.0-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-questions@FreeBSD.ORG" , freebsd-scsi@FreeBSD.ORG Subject: SCSI Problem/Error Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi. I had a *little* problem in my SCSI devices that halted my 4.0-stable box today. The console messages follows: (da1:ahc0:0:12:0): SCB 0x3b - timed out in Data-out phase, SEQADDR == 0x115 (da1:ahc0:0:12:0): BDR message in message buffer (da1:ahc0:0:12:0): SCB 0x47 - timed out in Data-out phase, SEQADDR == 0x115 These messages were in highlight, so I think they're important messages :). The SCSI devices of the box follows: ahc0: port 0xb800-0xb8ff mem 0xe2000000-0xe2000fff irq 5 at device 13.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s1a da1 at ahc0 bus 0 target 12 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) da0 at ahc0 bus 0 target 6 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 4136MB (8471232 512 byte sectors: 255H 63S/T 527C) I also have a Sony DDS3 external tape drive, which is off at the moment. Sometimes when I connect the tape to system some strange SCSi errors appear in the console (I don't have any know, the tape was off in this boot...). What I'd like to know is what these error messages mean. I don't know much about SCSI. A month ago this machine lost a disk (which I changed). The two disks (da1 and da0) are in different SCSI channels (as you can see in the informations above). Am I playing dumb and there something I should do to not happen these errors. Or there is some evil in my hardware? Maybe there is some evil Spirit of Bytes who is playing with my machine (then I should call some kind of hardware exorcist). Thanks for your help. MaurícioWP. PS.: answers from FreeBSD-SCSI please reply directly to my e-mail too. ------------------------------ Maurício Westendorff Pegoraro CPD - PUCRS - Brasil Unix & Security Team To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 27 12:46:53 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from cx587235-a.chnd1.az.home.com (cx587235-a.chnd1.az.home.com [24.11.88.170]) by hub.freebsd.org (Postfix) with ESMTP id CC91637B69C; Thu, 27 Jul 2000 12:46:48 -0700 (PDT) (envelope-from jjreynold@home.com) Received: from whale.home-net (whale [192.168.1.2]) by cx587235-a.chnd1.az.home.com (8.9.3/8.9.3) with ESMTP id MAA13000; Thu, 27 Jul 2000 12:46:48 -0700 (MST) (envelope-from jjreynold@home.com) Received: (from jjreynold@localhost) by whale.home-net (8.9.3/8.9.3) id MAA49438; Thu, 27 Jul 2000 12:46:48 -0700 (MST) (envelope-from jjreynold@home.com) From: John Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14720.37288.299262.35678@whale.home-net> Date: Thu, 27 Jul 2000 12:46:48 -0700 (MST) To: emulation@freebsd.org Subject: more VMware quirks/questions - scsi CD-ROM -> emulated ATAPI X-Mailer: VM 6.75 under Emacs 20.7.1 Cc: scsi@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ cc'ing to -scsi because somebody there might have some insight into the behavior I'm seeing from VMware ] OK, I have nailed down some behavior that I saw last night after having success in installing the VMware tools, etc. I am currently using a SCSI CD-ROM (cd0) as the /dev/cdrom device (link to /dev/cd0c) for VMware's emulated ATAPI CD-ROM. Everything works wonderfully if I "power on" the virtual machine with a disc sitting in the CD-ROM. However, if the tray is empty then VMware comes back with a dialog box saying CDROM: Unable to open '/dev/cdrom' Device not configured Error connecting the CDROM device. (another dialog box) Device ide1:0 will start disconnected This smacks of the "troubles" one might have when installing from SCSI CD-ROM if you don't boot with a disc in the drive (sysinstall can't find the drive when you choose CDROM as the media type if there wasn't a disc in the drive during boot). Is this something we can work-around in our vmmon module or is this an unavoidable CAM thing? Do other people using SCSI CD-ROM's notice the same thing? For now, I will happily insert any ol' disc into the machine as I power up the VM, but just wondering how this can be fixed in software ultimately (or if it's just a "VMware thing + scsi" thing and we're stuck with it). Thanks, -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jjreynold@home.com FreeBSD 4.1-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 27 15:53: 5 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 35AD337C10E; Thu, 27 Jul 2000 15:52:52 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA87146; Thu, 27 Jul 2000 16:52:16 -0600 (MDT) (envelope-from ken) Date: Thu, 27 Jul 2000 16:52:16 -0600 From: "Kenneth D. Merry" To: MauricioWP Cc: "freebsd-questions@FreeBSD.ORG" , freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI Problem/Error Message-ID: <20000727165216.A87100@panzer.kdm.org> References: <39807F9C.31D06E15@pucrs.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <39807F9C.31D06E15@pucrs.br>; from mwp@pucrs.br on Thu, Jul 27, 2000 at 03:29:48PM -0300 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jul 27, 2000 at 15:29:48 -0300, MauricioWP wrote: > Hi. > > I had a *little* problem in my SCSI devices that halted my 4.0-stable > box today. The console messages follows: > > (da1:ahc0:0:12:0): SCB 0x3b - timed out in Data-out phase, SEQADDR == > 0x115 > (da1:ahc0:0:12:0): BDR message in message buffer > (da1:ahc0:0:12:0): SCB 0x47 - timed out in Data-out phase, SEQADDR == > 0x115 > > These messages were in highlight, so I think they're important messages > :). Yes. This generally means that you have a cabling or termination problem. Timed out in data-out phase usually means that the bus is stuck in a particular phase. Since the error is coming from the da(4) driver, it has probably been stuck in data-out phase for 60 seconds. > I also have a Sony DDS3 external tape drive, which is off at the moment. > Sometimes when I connect the tape to system some strange SCSi errors > appear in the console (I don't have any know, the tape was off in this > boot...). Well, in order to diagnose those errors, we'd have to see what they are. :) > What I'd like to know is what these error messages mean. I don't know > much about SCSI. A month ago this machine lost a disk (which I changed). > The two disks (da1 and da0) are in different SCSI channels (as you can > see in the informations above). Am I playing dumb and there something I > should do to not happen these errors. Or there is some evil in my > hardware? Maybe there is some evil Spirit of Bytes who is playing with > my machine (then I should call some kind of hardware exorcist). Actually, your disks are on the same SCSI bus, just different cables. You should check for a cabling or termination problem. 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 Thu Jul 27 16: 2:33 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 AC70037C11D; Thu, 27 Jul 2000 16:02:24 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA87247; Thu, 27 Jul 2000 17:01:01 -0600 (MDT) (envelope-from ken) Date: Thu, 27 Jul 2000 17:01:01 -0600 From: "Kenneth D. Merry" To: John Reynolds Cc: emulation@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: more VMware quirks/questions - scsi CD-ROM -> emulated ATAPI Message-ID: <20000727170101.B87100@panzer.kdm.org> References: <14720.37288.299262.35678@whale.home-net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <14720.37288.299262.35678@whale.home-net>; from jjreynold@home.com on Thu, Jul 27, 2000 at 12:46:48PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jul 27, 2000 at 12:46:48 -0700, John Reynolds wrote: > > [ cc'ing to -scsi because somebody there might have some insight into the > behavior I'm seeing from VMware ] > > OK, I have nailed down some behavior that I saw last night after having success > in installing the VMware tools, etc. > > I am currently using a SCSI CD-ROM (cd0) as the /dev/cdrom device (link to > /dev/cd0c) for VMware's emulated ATAPI CD-ROM. > > Everything works wonderfully if I "power on" the virtual machine with a disc > sitting in the CD-ROM. However, if the tray is empty then VMware comes back > with a dialog box saying > > CDROM: Unable to open '/dev/cdrom' > Device not configured > > Error connecting the CDROM device. > > (another dialog box) > > Device ide1:0 will start disconnected > > This smacks of the "troubles" one might have when installing from SCSI CD-ROM > if you don't boot with a disc in the drive (sysinstall can't find the drive > when you choose CDROM as the media type if there wasn't a disc in the drive > during boot). Yes, it's pretty much the same problem -- sysinstall thinks the device isn't there if it can't open it. In fact, the problem is just that you don't have a disk in it. > Is this something we can work-around in our vmmon module or is this an > unavoidable CAM thing? Do other people using SCSI CD-ROM's notice the same > thing? I'm sure other people have the same problem, since the cd(4) driver acts the same way for any drive when there is no media present. > For now, I will happily insert any ol' disc into the machine as I power up the > VM, but just wondering how this can be fixed in software ultimately (or if it's > just a "VMware thing + scsi" thing and we're stuck with it). There may be a way to do something different, but you'd have to look into the 'vmmon' module to figure it out. What is the vmmon module, anyway? Where is the source? (I don't know much about vmware.) 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 Thu Jul 27 16:23: 7 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from melete.ch.intel.com (melete.ch.intel.com [143.182.246.25]) by hub.freebsd.org (Postfix) with ESMTP id 9DFF937C14C; Thu, 27 Jul 2000 16:23:02 -0700 (PDT) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by melete.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.30 2000/06/08 18:25:35 dmccart Exp $) with ESMTP id XAA05866; Thu, 27 Jul 2000 23:22:45 GMT Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id QAA17970; Thu, 27 Jul 2000 16:23:02 -0700 (MST) X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id TAA13652; Thu, 27 Jul 2000 19:23:01 -0400 (EDT) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14720.50260.568637.275395@hip186.ch.intel.com> Date: Thu, 27 Jul 2000 16:23:00 -0700 (MST) To: emulation@freebsd.org, scsi@freebsd.org Subject: Re: more VMware quirks/questions - scsi CD-ROM -> emulated ATAPI In-Reply-To: <20000727170101.B87100@panzer.kdm.org> References: <14720.37288.299262.35678@whale.home-net> <20000727170101.B87100@panzer.kdm.org> X-Mailer: VM 6.75 under Emacs 20.6.3 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ On Thursday, July 27, Kenneth D. Merry wrote: ] > > Yes, it's pretty much the same problem -- sysinstall thinks the device > isn't there if it can't open it. In fact, the problem is just that you > don't have a disk in it. > > I'm sure other people have the same problem, since the cd(4) driver acts > the same way for any drive when there is no media present. could this be changed maybe with a sysctl variable or something, or is there a fundamental reason why it "should" work this way? > There may be a way to do something different, but you'd have to look into > the 'vmmon' module to figure it out. > > What is the vmmon module, anyway? Where is the source? (I don't know much > about vmware.) http://www.mindspring.com/~vsilyaev/vmware/files/ vmmon-freebsd-0.97-b1.tar.gz is the "latest" that the port fetches. This is freebsd-only code plus a patch for the vmmon code from VMware. So far, I'm pretty happy with it--I need to squash a few more bugs and figure a few more things out about it, but they might actually get my $$$ for this one ;-) -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 27 16:40:17 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 7C19337BB6B; Thu, 27 Jul 2000 16:40:04 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA87686; Thu, 27 Jul 2000 17:38:39 -0600 (MDT) (envelope-from ken) Date: Thu, 27 Jul 2000 17:38:39 -0600 From: "Kenneth D. Merry" To: John Reynolds~ Cc: emulation@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: more VMware quirks/questions - scsi CD-ROM -> emulated ATAPI Message-ID: <20000727173838.A87609@panzer.kdm.org> References: <14720.37288.299262.35678@whale.home-net> <20000727170101.B87100@panzer.kdm.org> <14720.50260.568637.275395@hip186.ch.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <14720.50260.568637.275395@hip186.ch.intel.com>; from jreynold@sedona.ch.intel.com on Thu, Jul 27, 2000 at 04:23:00PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jul 27, 2000 at 16:23:00 -0700, John Reynolds~ wrote: > [ On Thursday, July 27, Kenneth D. Merry wrote: ] > > > > Yes, it's pretty much the same problem -- sysinstall thinks the device > > isn't there if it can't open it. In fact, the problem is just that you > > don't have a disk in it. > > > > I'm sure other people have the same problem, since the cd(4) driver acts > > the same way for any drive when there is no media present. > > could this be changed maybe with a sysctl variable or something, or is there a > fundamental reason why it "should" work this way? Well, we have to have the CD size and blocksize in order to complete the open call. (That information goes into the faked-up disklabel that allows the device to be mounted.) We can't get that information without a CD in the drive. (The SCSI READ CAPACITY command won't succeed without a CD in the drive.) > > There may be a way to do something different, but you'd have to look into > > the 'vmmon' module to figure it out. > > > > What is the vmmon module, anyway? Where is the source? (I don't know much > > about vmware.) > > http://www.mindspring.com/~vsilyaev/vmware/files/ > > vmmon-freebsd-0.97-b1.tar.gz is the "latest" that the port fetches. This is > freebsd-only code plus a patch for the vmmon code from VMware. > > So far, I'm pretty happy with it--I need to squash a few more bugs and figure > a few more things out about it, but they might actually get my $$$ for this > one ;-) I looked through the source briefly, and I found some code in linux_emu.c that translates Linux CD ioctls to FreeBSD CD ioctls, but I didn't find any wrappers for open(2). You'll probably need to find someone familiar with vmware to fix the problem. 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 Thu Jul 27 18:56: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from dirty.research.bell-labs.com (dirty.research.bell-labs.com [204.178.16.6]) by hub.freebsd.org (Postfix) with SMTP id 38EF437C193 for ; Thu, 27 Jul 2000 18:56:02 -0700 (PDT) (envelope-from weeteck@aura.research.bell-labs.com) Received: from grubby.research.bell-labs.com ([135.104.2.9]) by dirty; Thu Jul 27 21:55:39 EDT 2000 Received: from aura.research.bell-labs.com ([135.104.46.10]) by grubby; Thu Jul 27 21:55:39 EDT 2000 Received: (from weeteck@localhost) by aura.research.bell-labs.com (8.9.1/8.9.1) id VAA28839 for freebsd-scsi@freebsd.org; Thu, 27 Jul 2000 21:55:38 -0400 (EDT) From: Wee Teck Ng Message-Id: <200007280155.VAA28839@aura.research.bell-labs.com> Subject: max SCB on Adaptec 2940U2W To: freebsd-scsi@freebsd.org Date: Thu, 27 Jul 2000 21:55:38 -0400 (EDT) X-Mailer: ELM [version 2.5 PL2] 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 Adaptec 2940U2W is supposed to be able to handle 255 concurrent tasks, but i noticed that freebsd reported the max number of SCB as 16: ahc0: aic7896/97 Wide Channel A, SCSI Id=7, 16/255 SCBs this number appears to be probed by ahc_probe(). my question is: does the card supports more than 16 concurrent SCBs? thanks! wee teck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 29 0: 6:36 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from guru.mired.org (zoom0-097.telepath.com [216.14.0.97]) by hub.freebsd.org (Postfix) with SMTP id 773FA37B698 for ; Sat, 29 Jul 2000 00:06:31 -0700 (PDT) (envelope-from mwm@mired.org) Received: (qmail 29629 invoked by uid 100); 29 Jul 2000 07:06:27 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14722.33395.136915.927338@guru.mired.org> Date: Sat, 29 Jul 2000 02:06:27 -0500 (CDT) To: scsi@FreeBSD.ORG Subject: Re: (noperiph:ahc0:0:-1:-1) & forwarded message ... In-Reply-To: <20000726181305.A99461@curry.mchp.siemens.de> References: <14717.58026.117126.568975@guru.mired.org> <200007251938.NAA48431@pluto.plutotech.com> <20000726181305.A99461@curry.mchp.siemens.de> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just a note to let you know that the current version of the ahc driver has solved this problem for me, and to say thanks to Justin et. al. for the quick response. Thanx, To: "Justin T. Gibbs" Cc: mjacob@feral.com, scsi@freebsd.org, sos@freebsd.org Subject: Re: CAM layer Message-ID: <20000729212605.A27295@daemon.ninth-circle.org> References: <200007241900.NAA17859@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2i In-Reply-To: <200007241900.NAA17859@pluto.plutotech.com>; from gibbs@plutotech.com on Mon, Jul 24, 2000 at 01:01:24PM -0600 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -On [20000724 22:00], Justin T. Gibbs (gibbs@plutotech.com) wrote: >In article you wrote: [you being Matthew Jacob] >> What do you feel needs to change with FreeBSD's CAM implementation? [Matt to Søren] >It needs to be made less SCSI centric. e.g. cam/scsi/cam_xpt_scsi.c >with cam/cam_xpt.c offering only common glue. It has been on my >list of things to do for a long time, but I just haven't gotten >around to it. I think that a large part of the CAM/ATA/ATAPI >issue is that the barrier to entry for new subsystems is too high... >Someone has to do the "split it out" work first. Ok, so we need to get the following at least: /usr/src/sys/cam/ ata/ common/ scsi/ for the directories. I see that, for example, cam_xpt.c contains the quirk table, perhaps we want to put this in a seperate file for each disksystem. Of course, all SCSI functions would need to move towards scsi/ with scsi_xpt.c being a more consistent name when it comes to that directory, or when given the names in cam/ cam_xpt_scsi.c like Justin says. Going by the scsi word in the files, we have at least these files to clean up: [asmodai@celestial] (15) $ grep -i scsi * | sed 's/\:.*//' | uniq cam.c cam.h cam_ccb.h cam_debug.h cam_periph.c cam_sim.c cam_sim.h cam_xpt.c I can only help with the splitting of the files, I am SCSI/ATA clueless when it comes to programming those systems. -- Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/C-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Abandon hope, all ye who enter here... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 29 12:51:21 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7CAE937B554; Sat, 29 Jul 2000 12:51:15 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA14400; Sat, 29 Jul 2000 12:50:58 -0700 Date: Sat, 29 Jul 2000 12:51:01 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jeroen Ruigrok/Asmodai Cc: "Justin T. Gibbs" , scsi@freebsd.org, sos@freebsd.org Subject: Re: CAM layer In-Reply-To: <20000729212605.A27295@daemon.ninth-circle.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, the 'needs' was Justin's take on things. I'm not sure I agree. I tend= to see ATA like I implement SAF-TE inside SES- SCSI/CAM is a superset of what = ATA uses, although there are things in ANSI t13 committee that are not well represented within t10 (SCSI) yet but can be shoehorned in pretty easily. I still fail to see why the ATA chip hardware, which is admittedly where a = lot of Sos' good work lives, can't just be a SIM layer thing for CAM. There are= a couple of ATA specific properties that might have to be tunnelled from sa o= r da, but I'm not really sure I see a need for the large splitup. I was present at a lot of discussions at Sun in 1998 where, once again, the= y tried to resolve with the Solaris/Intel folks' cmdk driver (joins ATA && SC= SI with one disk driver- there was also, briefly, a cmtp driver) could be shot and the new ata stuff could be driven by the sd && st drivers. They didn't kill cmdk, but the Sparc/Solaris ATA stuff is not driven as it should be-= =20 but that was due to the same lack of initiative being shown here. I've comapers both the atapi && scsi midlayer source for Solaris 2.8- they're structured almost *exactly* the same. All of this indicates to me that ATA *drives* are not all that different fr= om SCSI drives. There are some differences, of course, but 95% of which are within control of the SIM to inform the XPT layer about what to do. There a= re probably a few extra things so that the periph drivers don't do something stupid, but that's the rest of what I see as a fairly small change. Would somebody (Jusgin? Sos?) please tell me I'm wrong, and if so, give specifics? -matt On Sat, 29 Jul 2000, Jeroen Ruigrok/Asmodai wrote: > -On [20000724 22:00], Justin T. Gibbs (gibbs@plutotech.com) wrote: > >In article y= ou wrote: > [you being Matthew Jacob] >=20 > >> What do you feel needs to change with FreeBSD's CAM implementation? > [Matt to S=F8ren] >=20 > >It needs to be made less SCSI centric. e.g. cam/scsi/cam_xpt_scsi.c > >with cam/cam_xpt.c offering only common glue. It has been on my > >list of things to do for a long time, but I just haven't gotten > >around to it. I think that a large part of the CAM/ATA/ATAPI > >issue is that the barrier to entry for new subsystems is too high... > >Someone has to do the "split it out" work first. >=20 > Ok, >=20 > so we need to get the following at least: >=20 > /usr/src/sys/cam/ > =09=09=09ata/ > =09=09=09common/ > =09=09=09scsi/ >=20 > for the directories. >=20 > I see that, for example, cam_xpt.c contains the quirk table, perhaps we > want to put this in a seperate file for each disksystem. >=20 > Of course, all SCSI functions would need to move towards scsi/ with > scsi_xpt.c being a more consistent name when it comes to that directory, > or when given the names in cam/ cam_xpt_scsi.c like Justin says. >=20 > Going by the scsi word in the files, we have at least these files to > clean up: >=20 > [asmodai@celestial] (15) $ grep -i scsi * | sed 's/\:.*//' | uniq > cam.c > cam.h > cam_ccb.h > cam_debug.h > cam_periph.c > cam_sim.c > cam_sim.h > cam_xpt.c >=20 > I can only help with the splitting of the files, I am SCSI/ATA clueless > when it comes to programming those systems. >=20 > --=20 > Jeroen Ruigrok vd Werven/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] > Documentation nutter/C-rated Coder BSD: Technical excellence at its best = =20 > The BSD Programmer's Documentation Project > Abandon hope, all ye who enter here... >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 29 13: 2:23 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from web217.mail.yahoo.com (web217.mail.yahoo.com [128.11.68.117]) by hub.freebsd.org (Postfix) with SMTP id F1F6E37B728 for ; Sat, 29 Jul 2000 13:02:20 -0700 (PDT) (envelope-from fjrm@yahoo.com) Received: (qmail 25760 invoked by uid 60001); 29 Jul 2000 20:02:20 -0000 Message-ID: <20000729200220.25759.qmail@web217.mail.yahoo.com> Received: from [208.139.165.5] by web217.mail.yahoo.com; Sat, 29 Jul 2000 13:02:20 PDT Date: Sat, 29 Jul 2000 13:02:20 -0700 (PDT) From: Francisco Reyes Subject: Sharing external RAID with FreeBSD To: scsi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What would it take for FreeBSD to be able to share an external SCSI RAID system? I recently got some quotes from BSDI for some hardware and one of the things which I was told was that I would be able to connect two FreeBSD computers to the same RAID system, but that only one system will be able to see the RADI. It would take a setting change on the RAID and a reboot to have the second computer use the RAID (which in turn will not let the first computer have access). Would this be an issue for the "filesystem" list or the SCSI list? I originally tried to mail the "cluster" list, but I am getting the feeling this list is not active. __________________________________________________ Do You Yahoo!? Kick off your party with Yahoo! Invites. http://invites.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 29 13:14:44 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 8CCA537B79F for ; Sat, 29 Jul 2000 13:14:41 -0700 (PDT) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id NAA11764; Sat, 29 Jul 2000 13:00:32 -0700 (PDT) Message-Id: <200007292000.NAA11764@implode.root.com> To: Francisco Reyes Cc: scsi@FreeBSD.ORG Subject: Re: Sharing external RAID with FreeBSD In-reply-to: Your message of "Sat, 29 Jul 2000 13:02:20 PDT." <20000729200220.25759.qmail@web217.mail.yahoo.com> From: David Greenman Reply-To: dg@root.com Date: Sat, 29 Jul 2000 13:00:32 -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >What would it take for FreeBSD to be able to share an >external SCSI RAID system? If the servers are accessing different LUNs (and thus different filesystems), then it should work already. If you want the servers to have shared access to the same filesystem, then that's a whole different thing that requires a new type of filesystem. Basically the servers need to coordinate accesses to the filesystem via a lock protocol, and they need to have a way of handling cache coherency. The closest thing to meeting these goals that I've seen so far is the "Global File System", and last I heard, someone was working on porting it to FreeBSD. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org Manufacturer of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 29 13:19:19 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id BF38D37B728 for ; Sat, 29 Jul 2000 13:18:41 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA14504; Sat, 29 Jul 2000 13:18:28 -0700 Date: Sat, 29 Jul 2000 13:18:31 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: David Greenman Cc: Francisco Reyes , scsi@FreeBSD.ORG Subject: Re: Sharing external RAID with FreeBSD In-Reply-To: <200007292000.NAA11764@implode.root.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 You can also share spindles (luns) if you use a FreeBSD disk label, or a disklabel that FreeBSD will understand, and you use different partitions. You can also share read-only filesystems. On Sat, 29 Jul 2000, David Greenman wrote: > >What would it take for FreeBSD to be able to share an > >external SCSI RAID system? > > If the servers are accessing different LUNs (and thus different > filesystems), then it should work already. If you want the servers to > have shared access to the same filesystem, then that's a whole different > thing that requires a new type of filesystem. Basically the servers need > to coordinate accesses to the filesystem via a lock protocol, and they > need to have a way of handling cache coherency. The closest thing to > meeting these goals that I've seen so far is the "Global File System", > and last I heard, someone was working on porting it to FreeBSD. > > -DG > > David Greenman > Co-founder, The FreeBSD Project - http://www.freebsd.org > Manufacturer of high-performance Internet servers - http://www.terasolutions.com > Pave the road of life with opportunities. > > > 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 Sat Jul 29 13:24:26 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from web214.mail.yahoo.com (web214.mail.yahoo.com [128.11.68.114]) by hub.freebsd.org (Postfix) with SMTP id 4222B37B86F for ; Sat, 29 Jul 2000 13:24:20 -0700 (PDT) (envelope-from fjrm@yahoo.com) Received: (qmail 1615 invoked by uid 60001); 29 Jul 2000 20:24:20 -0000 Message-ID: <20000729202420.1614.qmail@web214.mail.yahoo.com> Received: from [208.139.165.5] by web214.mail.yahoo.com; Sat, 29 Jul 2000 13:24:20 PDT Date: Sat, 29 Jul 2000 13:24:20 -0700 (PDT) From: Francisco Reyes Subject: Re: Sharing external RAID with FreeBSD To: dg@root.com Cc: scsi@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --- David Greenman wrote: >>What would it take for FreeBSD to be able to share >> an external SCSI RAID system? >If you want the servers to have shared access >to the same filesystem, then that's a whole different > thing that requires a new type of filesystem. Yes this is what I am looking for. This in conjunction with something like Understudy Polyserve would allow a couple of FreeBSD computers to operate as a "fail over cluster". >"Global File System", and last I heard, someone >was working on porting it to FreeBSD. Any clues who Or any pointers where this was last discussed? Just searched deja with no luck. __________________________________________________ Do You Yahoo!? Kick off your party with Yahoo! Invites. http://invites.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 29 15:30: 4 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2978D37B76A for ; Sat, 29 Jul 2000 15:30:01 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA14742; Sat, 29 Jul 2000 15:29:06 -0700 Date: Sat, 29 Jul 2000 15:29:09 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: scsi@freebsd.org Cc: Alexander Leidinger Subject: Re: Panic in xpt_setup_ccb (cam_xpt.c) (fwd) 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 Proper discussion are for this.... stack trace was..?? I tossed the mail - Alexander, can you repost to -scsi? It's weird to me why syncing prior to a reboot would blow up with xpt_setup_ccb with a released devq.... ---------- Forwarded message ---------- Date: Sat, 29 Jul 2000 23:14:09 +0200 (CEST) From: Alexander Leidinger To: mjacob@feral.com Cc: current@FreeBSD.ORG Subject: Re: Panic in xpt_setup_ccb (cam_xpt.c) On 29 Jul, Matthew Jacob wrote: > > What hardware? ahc0: port 0xb000-0xb0ff mem 0xd9800000-0xd9800fff irq 9 at device 6.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs cd0 at ahc0 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd1 at ahc0 bus 0 target 2 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 20.000MB/s transfers (20.000MHz, offset 15) The panic was with cd0. Bye, Alexander. -- ...and that is how we know the Earth to be banana-shaped. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 29 18: 8:55 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from hotmail.com (f125.law4.hotmail.com [216.33.149.125]) by hub.freebsd.org (Postfix) with ESMTP id 9778637B5C8 for ; Sat, 29 Jul 2000 18:08:52 -0700 (PDT) (envelope-from wahyudi@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 29 Jul 2000 18:08:52 -0700 Received: from 192.135.249.2 by lw4fd.law4.hotmail.msn.com with HTTP; Sun, 30 Jul 2000 GMT X-Originating-IP: [192.135.249.2] From: "Wahyudi Gunawan" To: scsi@freebsd.org Subject: ahc0 for Ultra160 Date: Sat, 29 Jul 2000 21:08:51 EDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 30 Jul 2000 01:08:52.0093 (UTC) FILETIME=[B981DAD0:01BFF9C2] Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have a problem when installing FreeBSD 4.0 or 4.1 to my machine. I did my installation from an FTP server. The installation will run for sometime and suddenly it freeze in the middle Here are the message that I got: No active SCB for reconnecting target-issuing BUS DEVICE RESET saved TCL=0x10 ARG_1=0x48, SEQ_FLAG=0x0 ahc0: Interrupted 0x0 ahc0: Warning no command for SCB 72 (cmdcmplt) QOUTPOST=65 (da0:ahc0:0:0:1:0):SCB 0x48-timeout while idle SEQ_ADDR=0xa (da0:ahc0:0:0:1:0):Queueing a BDR SCB QOUTPOST=2 (da0:ahc0:0:0:1:0):SCB 0x48-timeout while idle, SEQ_ADDR=0xa (da0:ahc0:0:0:1:0):no longer timeout, status=34B ahc0: Issued channel A Bus reset, 1 SCB aborted ahc0:A:1: ahc_intr_ referenced SCB not valid during segint 0x71 scb (72) My machine is: Kayak XU800, 9.1G Quantum Ultra 160, adaptec 7892. I already set the speed to 80M. Can somebody help about this? I already don't know what to do Thanks in advance -WG ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message