From owner-freebsd-scsi Sun Nov 19 18:13: 9 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from hotmail.com (f113.pav1.hotmail.com [64.4.31.113]) by hub.freebsd.org (Postfix) with ESMTP id 43F2237B479 for ; Sun, 19 Nov 2000 18:13:07 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 19 Nov 2000 18:13:07 -0800 Received: from 61.151.174.97 by pv1fd.pav1.hotmail.msn.com with HTTP; Mon, 20 Nov 2000 02:13:06 GMT X-Originating-IP: [61.151.174.97] From: "bsdnewbie bsdnewbie" To: freebsd-scsi@FreeBSD.org Subject: _ioctl with scsi drivers? Date: Mon, 20 Nov 2000 10:13:06 CST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 20 Nov 2000 02:13:07.0054 (UTC) FILETIME=[6BEBF8E0:01C05297] Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I wanna to talk with scsi drivers, how to modify them? Is there any examples? I have not see any ioctl in aha or aic7xxx. Or I have to make a device file and then talk with scsi drivers via the device file? Thanks in advance best regards, bsdewbie Nov 20, 2k _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 20 2:56:20 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-178-138.dsl.snfc21.pacbell.net [63.202.178.138]) by hub.freebsd.org (Postfix) with ESMTP id E84DE37B479 for ; Mon, 20 Nov 2000 02:56:18 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAKB39F12392; Mon, 20 Nov 2000 03:03:09 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011201103.eAKB39F12392@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "bsdnewbie bsdnewbie" Cc: freebsd-scsi@FreeBSD.org Subject: Re: _ioctl with scsi drivers? In-reply-to: Your message of "Mon, 20 Nov 2000 10:13:06 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 20 Nov 2000 03:03:09 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi, > I wanna to talk with scsi drivers, how to modify them? Is there any > examples? I have not see any ioctl in aha or aic7xxx. Or I have to make a > device file and then talk with scsi drivers via the device file? This depends a lot on what you're trying to achieve by doing this. Are you trying to write your own SCSI driver, or modify an existing one? In many cases, you may find that using a sysctl node is the easiest way to go. -- ... 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] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 20 3:26:41 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from hotmail.com (f151.pav1.hotmail.com [64.4.31.151]) by hub.freebsd.org (Postfix) with ESMTP id 82EA137B479; Mon, 20 Nov 2000 03:26:38 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 20 Nov 2000 03:26:38 -0800 Received: from 202.109.0.100 by pv1fd.pav1.hotmail.msn.com with HTTP; Mon, 20 Nov 2000 11:26:38 GMT X-Originating-IP: [202.109.0.100] From: "bsdnewbie bsdnewbie" To: msmith@freebsd.org Cc: freebsd-scsi@FreeBSD.org Subject: Re: _ioctl with scsi drivers? Date: Mon, 20 Nov 2000 19:26:38 CST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 20 Nov 2000 11:26:38.0324 (UTC) FILETIME=[BF619B40:01C052E4] Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >From: Mike Smith >To: "bsdnewbie bsdnewbie" >CC: freebsd-scsi@FreeBSD.org >Subject: Re: _ioctl with scsi drivers? >Date: Mon, 20 Nov 2000 03:03:09 -0800 > > > Hi, > > I wanna to talk with scsi drivers, how to modify them? Is there any > > examples? I have not see any ioctl in aha or aic7xxx. Or I have to >make a > > device file and then talk with scsi drivers via the device file? > >This depends a lot on what you're trying to achieve by doing this. Are >you trying to write your own SCSI driver, or modify an existing one? > >In many cases, you may find that using a sysctl node is the easiest way >to go. > >-- >... 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] > V I C T O R Y N O T V E N G E A N C E > > Thanks a alot. I'm writing my own scsi driver and want to inspect the status of the card, so I need a ioctl. And I also need to set the parameters of my card. Therefore, I need a function like ioctl. Thank you best regards bsdnewbie, Nov 20, 2k _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 21 5:19:32 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id EE7AA37B667 for ; Tue, 21 Nov 2000 05:19:03 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id 0C88957311; Tue, 21 Nov 2000 07:19:29 -0600 (CST) Date: Tue, 21 Nov 2000 07:19:28 -0600 From: "Michael C . Wu" To: freebsd-scsi@freebsd.org Subject: Sym0 not autodetecting Ultra160 Message-ID: <20001121071928.A75565@peorth.iteration.net> Reply-To: "Michael C . Wu" Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="vtzGhvizbBRQ85DL" Content-Disposition: inline User-Agent: Mutt/1.2.5i X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --vtzGhvizbBRQ85DL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi all, I have recently bought a Tekram Ultra160 U3W controller along with a couple IBM DDYS Ultra160 harddrives. However, I am puzzled by the dmesg output. It seems to say that the harddrives can only do 3.300MB/S transfers, when it should be saying 160.000MB/S The cd0 and cd1 devices both autodetect their speed correctly da0 at sym1 bus 0 target 2 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 3.300MB/s transfers, Tagged Queueing Enabled da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da1 at sym1 bus 0 target 4 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 3.300MB/s transfers, Tagged Queueing Enabled da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) cd0 at sym1 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed Searching the archives, I find that someone had a similiary trouble with the ahc0 driver. He fixed it by setting the harddrive speed in the SCSI BIOS to the lowest possible, boot, move the speed setting higher, boot, until it displays 160MB/S. (i.e. 10MB/S 20M/S 40MB/s and so on to 160MB/S) I tried this, and the highest I could make it go is 40MB/S. After that, the kernel stays dmesg'ing at 40MB/S when I set the BIOS to 80MB/S or 160MB/S. I also tried messing with camcontrol negotiate da0 -R XXX to no avail. Is this just an display error? or is it really only 3.3MB/S? Thanks, (Attached is my dmesg) -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ --vtzGhvizbBRQ85DL Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dmesg.txt" 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-20001119-CURRENT #0: Sun Nov 19 14:07:24 GMT 2000 root@usw2.freebsd.org:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 598625041 Hz CPU: Pentium III/Pentium III Xeon/Celeron (598.63-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x383f9ff real memory = 402653184 (393216K bytes) config> di sn0 config> di lnc0 config> di le0 config> di ie0 config> di fe0 config> di ed0 config> di cs0 config> di bt0 config> di aic0 config> di aha0 config> di adv0 config> q avail memory = 386682880 (377620K bytes) Preloaded elf kernel "kernel" at 0xc04eb000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc04eb09c. Preloaded elf module "linprocfs.ko" at 0xc04eb0ec. Pentium Pro MTRR support enabled md0: Malloc disk WARNING: Driver mistake: destroy_dev on 154/0 Using $PIR table, 10 entries at 0xc00fdf20 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 11 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1860-0x186f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 uhci0: port 0x1800-0x181f irq 9 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ulpt0: Xerox Corporation Xerox DocuPrint P1202, rev 1.00/1.00, addr 2, iclass 7/1 pci0: at 7.3 fxp0: port 0x1820-0x183f mem 0xf4100000-0xf41fffff,0xf4015000-0xf4015fff irq 11 at device 13.0 on pci0 fxp0: Ethernet address 00:08:c7:3a:24:c2 pci0: (vendor=0x109e, dev=0x036e) at 14.0 irq 10 pci0: (vendor=0x109e, dev=0x0878) at 14.1 irq 10 sym0: <1010-33> port 0x1000-0x10ff mem 0xf4010000-0xf4011fff,0xf4014000-0xf40143ff irq 3 at device 15.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS. sym1: <1010-33> port 0x1400-0x14ff mem 0xf4012000-0xf4013fff,0xf4014400-0xf40147ff irq 3 at device 15.1 on pci0 sym1: Symbios NVRAM, ID 7, Fast-80, SE, parity checking sym1: open drain IRQ line driver, using on-chip SRAM sym1: using LOAD/STORE-based firmware. sym1: handling phase mismatch from SCRIPTS. pci0: (vendor=0x14f1, dev=0x1033) at 16.0 irq 9 pcm0: port 0x1840-0x185f irq 3 at device 17.0 on pci0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources ad0: 13042MB [26500/16/63] at ata0-master UDMA33 ad1: 4126MB [8944/15/63] at ata0-slave UDMA33 Waiting 15 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. (noperiph:sym1:0:-1:-1): SCSI BUS reset delivered. (probe17:sym1:0:2:0): M_REJECT to send for : 1-6-4-c-0-3e-1-0. (probe19:sym1:0:4:0): M_REJECT to send for : 1-6-4-c-0-3e-1-0. Mounting root from ufs:/dev/da0s1a da0 at sym1 bus 0 target 2 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 3.300MB/s transfers, Tagged Queueing Enabled da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da1 at sym1 bus 0 target 4 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 3.300MB/s transfers, Tagged Queueing Enabled da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) cd0 at sym1 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed --vtzGhvizbBRQ85DL-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 21 11:58:26 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from peorth.iteration.net (peorth.iteration.net [208.190.180.178]) by hub.freebsd.org (Postfix) with ESMTP id 519BB37B4F9 for ; Tue, 21 Nov 2000 11:58:24 -0800 (PST) Received: by peorth.iteration.net (Postfix, from userid 1001) id 3FC8857325; Tue, 21 Nov 2000 13:24:20 -0600 (CST) Date: Tue, 21 Nov 2000 13:24:20 -0600 From: "Michael C . Wu" To: scsi@freebsd.org Subject: Re: Sym0 not autodetecting Ultra160 Message-ID: <20001121132420.A79669@peorth.iteration.net> Reply-To: "Michael C . Wu" References: <20001121071928.A75565@peorth.iteration.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001121071928.A75565@peorth.iteration.net>; from keichii@iteration.net on Tue, Nov 21, 2000 at 07:19:28AM -0600 X-PGP-Fingerprint: 5025 F691 F943 8128 48A8 5025 77CE 29C5 8FA1 2E20 X-PGP-Key-ID: 0x8FA12E20 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Nov 21, 2000 at 07:19:28AM -0600, Michael C . Wu scribbled: Sorry guys, I was stupid and did not read the manual. Plugged in the wrong slot on the controller. Everything works well now. -- +------------------------------------------------------------------+ | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 21 14:21: 4 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front5.grolier.fr (front5.grolier.fr [194.158.96.55]) by hub.freebsd.org (Postfix) with ESMTP id 7ACE737B4C5 for ; Tue, 21 Nov 2000 14:21:00 -0800 (PST) Received: from nas23-136.vlt.club-internet.fr (nas23-136.vlt.club-internet.fr [195.36.173.136]) by front5.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id XAA28016; Tue, 21 Nov 2000 23:15:29 +0100 (MET) Date: Tue, 21 Nov 2000 22:15:43 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: "Michael C . Wu" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Sym0 not autodetecting Ultra160 In-Reply-To: <20001121071928.A75565@peorth.iteration.net> 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 On Tue, 21 Nov 2000, Michael C . Wu wrote: > Hi all, >=20 > I have recently bought a Tekram Ultra160 U3W controller along > with a couple IBM DDYS Ultra160 harddrives. However, I am puzzled > by the dmesg output. It seems to say that the harddrives > can only do 3.300MB/S transfers, when it should be saying 160.000MB/S > The cd0 and cd1 devices both autodetect their speed correctly >=20 > da0 at sym1 bus 0 target 2 lun 0 > da0: Fixed Direct Access SCSI-3 device > da0: 3.300MB/s transfers, Tagged Queueing Enabled > da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) > da1 at sym1 bus 0 target 4 lun 0 > da1: Fixed Direct Access SCSI-3 device > da1: 3.300MB/s transfers, Tagged Queueing Enabled > da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) > cd0 at sym1 bus 0 target 1 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 20.000MB/s transfers (20.000MHz, offset 15) > cd0: Attempt to query device size failed: NOT READY, Medium not present -= tray closed >=20 > Searching the archives, I find that someone had a similiary trouble > with the ahc0 driver. He fixed it by setting the harddrive speed > in the SCSI BIOS to the lowest possible, boot, move the speed setting > higher, boot, until it displays 160MB/S. (i.e. 10MB/S 20M/S 40MB/s > and so on to 160MB/S) >=20 > I tried this, and the highest I could make it go is 40MB/S. > After that, the kernel stays dmesg'ing at 40MB/S when I set > the BIOS to 80MB/S or 160MB/S. >=20 > I also tried messing with camcontrol negotiate da0 -R XXX to no avail. >=20 > Is this just an display error? or is it really only 3.3MB/S? All your devices are connected to the same SCSI BUS (name `sym1 bus0'). Given that the PLEXTOR CD-ROM is very unlikely to be LVD, then _all_ the=20 devices on the BUS are using SE =3D Single Ended signaling. As a result, the maximum speed allowed is FAST-20 Wide-16 synchronous data transfers that cannot exceed 20MB/s * 2 =3D 40 MB/s. The Tekram U3W has 2 SCSI BUSes. One is LVD capable, allowing up to 160MB/s with Ultra-3 devices if _all_ the devices on the BUS are using LVD signaling. The other one is only SE capable. In result: 1) Only put LVD devices on the LVD capable channel of your controller,=20 using a LVD conformant cable with a LVD/SE terminateur at its end. 2) Connect SE devices on the other channel (BUS) which is only SE capable. 3) Configure the devices to their highest possible speed and to their real width in the controller NVRAM for each channel (control/c at boot). Let me know if this fixes. G=E9rard. PS: I have no quite sure explanation about the 3.3MB/s async speed for your hard disks. May-be the drive refused the negotiation for some=20 reason, or the driver tried a PPR nego. the drive disliked a lot. Btw, in my opinion, 3.3 MB/s is the real speed. :-)=20 > Thanks, >=20 > (Attached is my dmesg) > -- > +------------------------------------------------------------------+ > | keichii@peorth.iteration.net | keichii@bsdconspiracy.net | > | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | > +------------------------------------------------------------------+ >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 21 15:48: 1 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from isp.mabna.net (unknown [194.165.22.75]) by hub.freebsd.org (Postfix) with ESMTP id B370237B479 for ; Tue, 21 Nov 2000 15:47:53 -0800 (PST) Received: from Z9H5K9 ([192.168.11.111]) by isp.mabna.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id XKSTHBT1; Wed, 22 Nov 2000 03:03:11 +0330 MIME-Version: 1.0 To: "PUBLIC" <> From: znc@mabna.org Subject: TRADING Content-Type: multipart/mixed; boundary="divider" Message-Id: <20001121234753.B370237B479@hub.freebsd.org> Date: Tue, 21 Nov 2000 15:47:53 -0800 (PST) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --divider Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Dear Sir or Madam If you are producer or exporter & importer, please let me know the field of your activity. If you have any catalog, please send me one. My address: P.O.Box 14155 - 5841 Tehran, Iran Tel & Fax: +98 21 742 4714 E-mail: znc@mabna.org Yours sincerely, F.Shahbazi --divider-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 22 6:57:40 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from ichor.miseria.org (ichor.miseria.org [12.2.86.250]) by hub.freebsd.org (Postfix) with ESMTP id 29FA837B4CF for ; Wed, 22 Nov 2000 06:57:37 -0800 (PST) Received: by ichor.miseria.org (Postfix, from userid 1000) id A8794318F; Wed, 22 Nov 2000 14:59:40 +0000 (GMT) Received: from localhost (localhost [127.0.0.1]) by ichor.miseria.org (Postfix) with ESMTP id 6D3E34A7F for ; Wed, 22 Nov 2000 14:59:40 +0000 (GMT) Date: Wed, 22 Nov 2000 14:59:40 +0000 (GMT) From: justin To: scsi@freebsd.org Subject: Root mount failed; question 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 Since 4.1.1, i have been having a problem with FreeBSD being unable to mount in the final stages of booting. i get: Root mount failed: 22 when it gets to the UFS section of mounting the filesystems. originally i thought that it was due to 4.1.1's non-official support of the adaptec 29160N scsi card. now that 4.2 has come out and the same thing has happened, i'm wondering if it is my setup? the disk is "dangerously dedicated", and the hardware and filesystems are detailed below. my question is this: has anyone else seen this happen? is there something in the scsi setup itself (hardware, etc) that i should look at? many thanks, justin Filesystem Size Used Avail Capacity Mounted on /dev/da0s1a 992M 37M 876M 4% / /dev/da0s1e 15G 857M 13G 6% /usr /dev/ad0s1e 25G 807M 22G 3% /usr/home /dev/da0s1f 485M 1.9M 444M 0% /var procfs 4.0K 4.0K 0B 100% /proc FreeBSD 4.1-STABLE #0: Thu Nov 2 13:45:07 GMT 2000 root@baltazar.ef.uni-lj.si:/usr/src/sys/compile/ELEND Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 801820954 Hz CPU: Pentium III/Pentium III Xeon/Celeron (801.82-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 536858624 (524276K bytes) avail memory = 520257536 (508064K bytes) Preloaded elf kernel "kernel.old" at 0xc0286000. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 4.2 irq 10 chip1: port 0xe800-0xe80f at device 4.3 on pci0 fxp0: port 0xd000-0xd01f mem 0xe1000000-0xe10fffff,0xe3800000-0xe3800fff irq 11 at device 7.0 on pci0 fxp0: Ethernet address 00:e0:18:99:03:89 pci0: at 9.0 irq 10 ahc0: port 0xb400-0xb4ff mem 0xe0000000-0xe0000fff irq 11 at device 10.0 on pci0 ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppi0: on ppbus0 IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to accept, logging limited to 100 packets/entry by default ad0: 26105MB [53040/16/63] at ata0-master using UDMA33 acd0: CDROM at ata1-master using PIO4 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s1a da0 at ahc0 bus 0 target 6 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 23 19: 5:53 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from aplcenMP.apl.jhu.edu (apl.jhu.edu [128.220.101.100]) by hub.freebsd.org (Postfix) with ESMTP id 16F7137B4D7 for ; Thu, 23 Nov 2000 19:05:52 -0800 (PST) Received: from apl.jhu.edu (kslip21.apl.jhu.edu [128.220.108.31]) by aplcenMP.apl.jhu.edu (8.9.3+Sun/8.9.3) with ESMTP id WAA18641 for ; Thu, 23 Nov 2000 22:05:50 -0500 (EST) Message-ID: <3A1DE6E4.C38854C8@apl.jhu.edu> Date: Thu, 23 Nov 2000 22:56:20 -0500 From: Chuck McCrobie X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: RFC 2143 (IP over SCSI) Support in FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org RFC 2143 - Encapsulating IP with SCSI Is there planned FreeBSD support for this RFC? What SCSI controllers are capable of target mode? I have a NCR 875 IntraServer card, but the sym_hipd.c does not mention anything about putting it into target mode. Thanks, Chuck McCrobie mccrobi@apl.jhu.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 23 19:16:56 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 6E7C537B4D7 for ; Thu, 23 Nov 2000 19:16:53 -0800 (PST) Received: from aslan (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id eAO3Go489714; Thu, 23 Nov 2000 20:16:50 -0700 (MST) (envelope-from gibbs@aslan.scsiguy.com) Message-Id: <200011240316.eAO3Go489714@aslan.scsiguy.com> To: Chuck McCrobie Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: RFC 2143 (IP over SCSI) Support in FreeBSD In-Reply-To: Your message of "Thu, 23 Nov 2000 22:56:20 EST." <3A1DE6E4.C38854C8@apl.jhu.edu> Date: Thu, 23 Nov 2000 20:16:50 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >RFC 2143 - Encapsulating IP with SCSI > >Is there planned FreeBSD support for this RFC? > >What SCSI controllers are capable of target mode? I have a NCR 875 >IntraServer card, but the sym_hipd.c does not mention anything about >putting it into target mode. I haven't looked to see how hard RFC2143 would be to implement, but both the isp (Qlogic controllers) and aic7xxx (Adaptec controllers) drivers have support for target mode. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 23 21:46:55 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id 4E31237B479 for ; Thu, 23 Nov 2000 21:46:52 -0800 (PST) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 13zB1W-0001lY-00; Thu, 23 Nov 2000 21:03:46 -0800 Date: Thu, 23 Nov 2000 21:03:44 -0800 (PST) From: Tom Samplonius To: Chuck McCrobie Cc: freebsd-scsi@freebsd.org Subject: Re: RFC 2143 (IP over SCSI) Support in FreeBSD In-Reply-To: <3A1DE6E4.C38854C8@apl.jhu.edu> 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 Thu, 23 Nov 2000, Chuck McCrobie wrote: > RFC 2143 - Encapsulating IP with SCSI > > Is there planned FreeBSD support for this RFC? > > What SCSI controllers are capable of target mode? I have a NCR 875 > IntraServer card, but the sym_hipd.c does not mention anything about > putting it into target mode. > > Thanks, Is there planned support for SCSI over IP? I've just seen a storage server that uses SCSI over IP. The reasoning is that gigabit ethernet is just as fast as fibrechannel, and much more standard. They have drivers for Linux and NT, and have announced that a driver will be released for FreeBSD in early 2001? Apparently the driver simply probes the LAN for SCSI devices and attaches each discovered storage server as a LUN. For some reason the name of this product escapes me. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 23 23:59:15 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id C70E437B4CF for ; Thu, 23 Nov 2000 23:59:09 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13zDlB-000P4f-00; Fri, 24 Nov 2000 07:59:05 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.0) id eAO7iPt27254; Fri, 24 Nov 2000 08:44:25 +0100 (CET) (envelope-from wkb) Date: Fri, 24 Nov 2000 08:44:25 +0100 From: Wilko Bulte To: "Justin T. Gibbs" Cc: Chuck McCrobie , freebsd-scsi@freebsd.org Subject: Re: RFC 2143 (IP over SCSI) Support in FreeBSD Message-ID: <20001124084425.A27240@freebie.demon.nl> References: <3A1DE6E4.C38854C8@apl.jhu.edu> <200011240316.eAO3Go489714@aslan.scsiguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200011240316.eAO3Go489714@aslan.scsiguy.com>; from gibbs@scsiguy.com on Thu, Nov 23, 2000 at 08:16:50PM -0700 X-OS: FreeBSD 4.2-RELEASE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Nov 23, 2000 at 08:16:50PM -0700, Justin T. Gibbs wrote: > >RFC 2143 - Encapsulating IP with SCSI > > > >Is there planned FreeBSD support for this RFC? > > > >What SCSI controllers are capable of target mode? I have a NCR 875 > >IntraServer card, but the sym_hipd.c does not mention anything about > >putting it into target mode. > > I haven't looked to see how hard RFC2143 would be to implement, > but both the isp (Qlogic controllers) and aic7xxx (Adaptec > controllers) drivers have support for target mode. Matt once told me that isp target mode is not really well tested. Would be interesting to have for things like shared disk - SCSI clusters as well. -- Wilko Bulte Arnhem, the Netherlands wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 24 10: 4: 0 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from locust.etext.org (locust.etext.org [216.93.75.148]) by hub.freebsd.org (Postfix) with ESMTP id 3CAE837B4CF; Fri, 24 Nov 2000 10:03:50 -0800 (PST) Received: from localhost (pauls@localhost) by locust.etext.org (8.11.0/8.11.0) with ESMTP id eAOI3hT31200; Fri, 24 Nov 2000 13:03:49 -0500 (EST) (envelope-from pauls@etext.org) Date: Fri, 24 Nov 2000 13:03:43 -0500 (EST) From: Paul Southworth To: Greg Lehey Cc: "Eric S. Nooden" , Michael Hughes , freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: Mounting a SCSI tape drive In-Reply-To: <19991202195345.47886@mojave.sitaranetworks.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 [About a year ago there was a thread on freebsd-questions about Exabyte 8200 drives which I would like to revive with the hope that someone found a solution.] On Thu, 2 Dec 1999, Greg Lehey wrote: :On Thursday, 2 December 1999 at 15:17:47 -0600, Eric S. Nooden wrote: :> At 02:29 PM 12/2/99 -0600, Michael Hughes wrote: :>> Eric S. Nooden said in email to me: :>>> :>>> I am running into some problems trying to mount a tape drive. When I run: :>>> :>>> mt -f /dev/nrsa0 rewind (or any command i.e. status) :>>> :>>> I get the following error message: :>>> :>>> (sa0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 :>>> (sa0:ahc0:0:4:0): ILLEGAL REQUEST :>>> :>>> ***I did notice that when the command ran, the light on the tape drive did :>>> flash. :>>> :>>> The file /var/log/messages reports the following about sa0: :>>> :>>> sa0: at ahc0 bus 0 target 4 lun 0 :>>> sa0: Removable Sequential Access SCSI-CCS device :>>> sa0: 3.300MB/s transfers I have what appears to be an almost identical drive. Mine is reported as " Removable Sequential Access SCSI-CCS device". This was a drive Exabyte made OEM for IBM and was sold in RS/6000s ten years ago, white faceplate and round blue eject button. I am aware that it is a piece of crap - if I can make it work this whole machine is going to a charitable cause, otherwise the drive goes to the dumpster. I have it attached to a SCSI bus with a hard drive attached (id #0). The tape is id #1. The host adapter is an Adaptec 2930C at id #7. I have verified no SCSI ID conflicts by removing each device and probing. I get the exact same error message when I 'mt -f /dev/rsa0 status'. I am running a 4.1.1 GENERIC kernel (freshly installed OS). :>>> Any help in mounting this beast and get backups done would be appreciated. :>> :>> Type changing dup switch 4 to on, on the MX Card. :> :> Thanks for replying. I unfortunately must show my ignorance and ask "What :> is an MX Card?" Are you referring to the SCCI controller or a card :> physically attached to the tape drive. : :I believe the MX board is the second from the back ot the unit. You :should see an 8-position DIP switch on the right (looking from the :front). Unfortunately, the units I have have special screws for which :I don't have any screwdrivers available here. I'll see if I can :arrange something tomorrow. The small screws are Torx T-8 and the large are T-10. Examining the MX 2 card DIP block, factory settings were different from what I find on Exabyte's web site. They say default is all switches "off". http://www.exabyte.com/suppserv/techsupp/8mm/fullhigh/in0011.html On mine, switches 2, 3, 4, 5, and 8 were on by default (ie, for use in an RS/6000). I tried moving all switches to off, and all switches off but 4 on. When switch 4 is _off_ the drive returns an error immediately after an 'mt -f /dev/rsa0 status'. If switch 4 is _on_ it takes about 10 seconds and then returns the same error, after blinking the drive lights and making it's little Exabyte tape tensioning noises. I realize that Exabyte shipped drives with insane firmware variations (especially OEM) but this drive previously worked (a while ago) in a Linux box (Intel hardware) with a 1.2 kernel, which seems like a good sign. If anyone has the dirt on this drive, please drop me a note. --Paul 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 4.1.1-RELEASE #0: Tue Sep 26 00:46:59 GMT 2000 jkh@narf.osd.bsdi.com:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P54C (99.87-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x526 Stepping = 6 Features=0x1bf real memory = 33488896 (32704K bytes) config> di sn0 config> di lnc0 config> di le0 config> di ie0 config> di fe0 config> di ed0 config> di cs0 config> di bt0 config> di ata1 config> di ata0 config> di aic0 config> di aha0 config> di adv0 config> q avail memory = 28614656 (27944K bytes) Preloaded elf kernel "kernel" at 0xc0416000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc041609c. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 atapci0: Busmastering DMA not enabled uhci0: port 0xef80-0xef9f irq 11 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered chip1: port 0xfcb0-0xfcbf at device 7.3 on pci0 ahc0: port 0xec00-0xecff mem 0xfebef000-0xfebeffff irq 9 at device 18.0 on pci0 aic7850: Single Channel A, SCSI Id=7, 3/255 SCBs pci0: at 20.0 irq 11 ep0: <3Com 3C509-Combo EtherLink III> at port 0x300-0x30f irq 10 on isa0 ep0: Ethernet address 00:a0:24:4d:35:5f fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 1 lun 0 sa0: Removable Sequential Access SCSI-CCS device sa0: 3.300MB/s transfers da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15) da0: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) Mounting root from ufs:/dev/da0s1a (sa0:ahc0:0:1:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 (sa0:ahc0:0:1:0): ILLEGAL REQUEST (sa0:ahc0:0:1:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 (sa0:ahc0:0:1:0): ILLEGAL REQUEST (sa0:ahc0:0:1:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 (sa0:ahc0:0:1:0): ILLEGAL REQUEST (sa0:ahc0:0:1:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 (sa0:ahc0:0:1:0): ILLEGAL REQUEST (sa0:ahc0:0:1:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 (sa0:ahc0:0:1:0): ILLEGAL REQUEST (sa0:ahc0:0:1:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 (sa0:ahc0:0:1:0): ILLEGAL REQUEST To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 24 10:18:57 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from hurlame.pdl.cs.cmu.edu (HURLAME.PDL.CS.CMU.EDU [128.2.189.78]) by hub.freebsd.org (Postfix) with ESMTP id 6703737B4C5 for ; Fri, 24 Nov 2000 10:18:54 -0800 (PST) Received: (from magus@localhost) by hurlame.pdl.cs.cmu.edu (8.11.1/8.11.1) id eAOIIjA65517; Fri, 24 Nov 2000 13:18:45 -0500 (EST) (envelope-from magus) To: Tom Samplonius Cc: Chuck McCrobie , freebsd-scsi@freebsd.org Subject: Re: RFC 2143 (IP over SCSI) Support in FreeBSD References: From: Nat Lanza Date: 24 Nov 2000 13:18:45 -0500 In-Reply-To: Tom Samplonius's message of "Thu, 23 Nov 2000 21:03:44 -0800 (PST)" Message-ID: Lines: 50 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Tom Samplonius writes: > Is there planned support for SCSI over IP? I've just seen a storage > server that uses SCSI over IP. The reasoning is that gigabit ethernet is > just as fast as fibrechannel, and much more standard. They have drivers > for Linux and NT, and have announced that a driver will be released for > FreeBSD in early 2001? Apparently the driver simply probes the LAN for > SCSI devices and attaches each discovered storage server as a LUN. For > some reason the name of this product escapes me. Please keep in mind that SCSI-over-IP is currently the topic of an active IETF working group, and the protocol development is not finished. It would probably be best to wait for the standard to actually be finalized before adding support, since having support that doesn't interoperate is not much better than having no support. The current timeline has the standard proposal being submitted next May. If you're interested in following the progress of the standard, the IP Storage working group's charter is here: http://www.ietf.org/html.charters/ips-charter.html Additionally, there is a public mailing list archived here: http://ips.pdl.cs.cmu.edu/mail/maillist.html Subscription information for the list is available on the charter page. Our lab is working on SCSI-over-IP, and our target platforms are FreeBSD and Linux. We would most likely be interested in contributing our code to the FreeBSD community when we're done, but it's far too early to make any promises. Also, discussion at the SCSI panel at BSDCon indicated that the FreeBSD SCSI developers are certainly interested in providing a framework in which SCSI-over-IP can be supported well. Our initial results show that it's possible to build a system with decent performance over 100bT and gigabit links without any modifications to the OS -- the driver builds as a self-contained KLD, and acts much like any other SCSI HBA driver. --nat -- nat lanza --------------------- research programmer, parallel data lab, cmu scs magus@cs.cmu.edu -------------------------------- http://www.cs.cmu.edu/~magus/ there are no whole truths; all truths are half-truths -- alfred north whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 24 12:46:58 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from front1.grolier.fr (front1.grolier.fr [194.158.96.51]) by hub.freebsd.org (Postfix) with ESMTP id B8B8937B4D7 for ; Fri, 24 Nov 2000 12:46:55 -0800 (PST) Received: from nas1-195.mea.club-internet.fr (nas1-195.mea.club-internet.fr [195.36.139.195]) by front1.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id VAA17068; Fri, 24 Nov 2000 21:46:43 +0100 (MET) Date: Fri, 24 Nov 2000 20:46:55 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Chuck McCrobie Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: RFC 2143 (IP over SCSI) Support in FreeBSD In-Reply-To: <3A1DE6E4.C38854C8@apl.jhu.edu> 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 On Thu, 23 Nov 2000, Chuck McCrobie wrote: > RFC 2143 - Encapsulating IP with SCSI >=20 > Is there planned FreeBSD support for this RFC? >=20 > What SCSI controllers are capable of target mode? I have a NCR 875 > IntraServer card, but the sym_hipd.c does not mention anything about > putting it into target mode. Reason is that the driver does not support this mode (yet). I guess you already have been told that the aic7xxx and isp drivers are providing some host target mode through FreeBSD-CAM, but, btw, there is nothing for now related to IP over SCSI in FreeBSD-CAM. I have target mode for the sym driver on my todo list and even have some prelimary code ready since September, but due to limited time (and probably too limited brain :) ) I am very late on that development. At the moment, I am working on an unified SYM driver (nothing to do with UDI at all, but just a portable driver based on cpp features) for Linux and FreeBSD. It is based on FreeBSD sym and will (does, since I already use it) replace the 3 drivers I currently maintain (2 under Linux and `sym' under FreeBSD). I cannot announce any date of availability for target mode support in `sym'. I wanted to have it before end-2K, but I will probably be weeks or months late. Regards, G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Nov 25 6:26: 6 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from relay.flashnet.it (ems.flashnet.it [194.247.160.44]) by hub.freebsd.org (Postfix) with ESMTP id D300037B4CF for ; Sat, 25 Nov 2000 06:25:58 -0800 (PST) Received: from smtp.flashnet.it (ip046.pool-173.cyb.it [195.191.181.47]) by relay.flashnet.it (EMS-RELAY/8.10.0) with SMTP id eAPEPmi24483 for ; Sat, 25 Nov 2000 15:25:50 +0100 Message-Id: <200011251425.eAPEPmi24483@relay.flashnet.it> To: freebsd-scsi@freebsd.org X-Mailer: Post Road Mailer for OS/2 (Green Edition Ver 3.0) Date: Sat, 25 Nov 2000 16:25:40 EST From: Andrea Venturoli Reply-To: Andrea Venturoli Subject: Zip Zoom Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello. I've got a problem with a FreeBSD 4.1.1-RELEASE system (although I also tried 4.0-R, which behaves just the same. The machine is an IBM PS VP with a 486DX2, 20MB of RAM, ISA bus, an IDE HD, a 3Com EtherLink III, a modem and an Elsa QuickStep 1000pro ISDN card. Now I had a spare SCSI HD along with a Zip Zoom SCSI adapter (which is actually an Adaptec AVA-1502): ok, it can't boot, it will probably be very slow, but it's fine for what I have to do. I plugged in the adapter and connected the Disk (with another OS it works fine, so I don't think it's an hardware problem). I configured my kernel with the following lines (but it's the same with the generic kernel): > device aic0 at isa? > device scbus > device da Then I rebooted, but I got the following: > Waiting 15 seconds for SCSI devices to settle > (probe0:aic0:0:0:0) ccb 0xc04dbc00 - timed out, phase 0xb6, state 4 > (probe0:aic0:0:0:0) ccb 0xc04dbc00 - timed out, phase 0xb6, state 4 > (probe0:aic0:0:0:0) ccb 0xc04dbc00 - timed out, phase 0xb6, state 1 > (probe0:aic0:0:0:0) ccb 0xc04dbc00 - timed out, phase 0xb6, state 1 > ... After the first line, the others appear very slowly (even one per minute); every device is probed a few times times up to device 7 (it's a narrow bus), sometimes the number after "ccb" changes. I tried every IRQ the card could handle (i.e. from 9 to 12), the kernel will always default to 12, so I "userconfig"ured it in the other cases; I also tried using the "alternate" jumper which moves the card from i/o ports 0x140 to 0x340, and here the kernel is smart enough to detect it. Anyway I could not get it to work. I double-checked and I should have no IRQ conflicts, since from 9 to 12 there is no legacy card, only the two plug and play ones, which get whichever ones are free. Any hint/suggestion? Bye & Thanks av. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Nov 25 14:25:44 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from funkthat.com (mg128-054.ricochet.net [204.179.128.54]) by hub.freebsd.org (Postfix) with ESMTP id F32DD37B479 for ; Sat, 25 Nov 2000 14:25:31 -0800 (PST) Received: (from jmg@localhost) by funkthat.com (8.9.3/8.8.7) id OAA01714; Sat, 25 Nov 2000 14:26:13 -0800 (PST) Message-ID: <20001125142603.14261@hydrogen.funkthat.com> Date: Sat, 25 Nov 2000 14:26:03 -0800 From: John-Mark Gurney To: freebsd-scsi@freebsd.org Subject: ncr problems (and amd) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.4-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I reciently bought a couple Tekram SCSI cards. One was a DC-390T, and the other was a DC-390U. ncr0: rev 0x26 int a irq 10 on pci0.8.0 tekram_amd0: rev 0x10 int a irq 12 on pci0.9.0 and yes, I'm running an old version of FreeBSD, 3.4-R to be exact, but there hasn't been any major changes to the code as far as I can tell from CVS. I'm having problems with the ncr going out to lunch: ncr0: timeout nccb=0xc0d92000 (skip) swap_pager: indefinite wait buffer: device: 0x411, blkno: 6912, size: 32768 ncr0: timeout nccb=0xc10dfc00 (skip) ncr0: timeout nccb=0xc0d92400 (skip) ncr0: timeout nccb=0xc0d92800 (skip) [timeout messages repeate a few hundred times with swap_pager mixed in] ncr0: timeout nccb=0xc0d91800 (skip) swap_pager: I/O error - pagein failed; blkno 27248, size 8192, error 5 vm_fault: pager read error, pid 1432 (dnsserver) pid 1432 (dnsserver), uid 65534: exited on signal 11 (core dumped) swap_pager: I/O error - pagein failed; blkno 27120, size 8192, error 5 vm_fault: pager read error, pid 1433 (dnsserver) pid 1433 (dnsserver), uid 65534: exited on signal 11 (core dumped) swap_pager: I/O error - pagein failed; blkno 7376, size 4096, error 5 panic: pmap_swapin_proc: cannot get upages for proc: 1435 syncing disks... ncr0: timeout nccb=0xc0d92400 (skip) [with another few hundred (over 350) timeout messages] ncr0: timeout nccb=0xc0d8f000 (skip) ncr0: timeout nccb=0xc0d8f200 (skip) 286 286 286 286 286 286 286 286 286 286 286 286 286 286 286 286 286 286 286 286 giving up finally it decides to sync disks (without any reason, I was myself out grabbing lunch) w/o any reason, and left 286 unwritten... I did reduce the tags on one of the four drives attached to the ncr down to 32, and the remaining drives auto dropped themselves to 32.. Any suggestsions? I tried the tekram ncr driver, but that just crashed shortly after it go to multiuser mode.. will I need to upgrade to 4.2-R to get any decient support? Thanks for the help. I would of cc'd who ever is maintaining the ncr driver, but it doesn't look like any specific person is from the cvs logs.. -- John-Mark Gurney Voice: +1 408 975 9651 Cu Networking "Thank God I'm an atheist, that'd just be confusing." -- cmc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message