From owner-freebsd-scsi Sun Mar 8 03:54:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA17565 for freebsd-scsi-outgoing; Sun, 8 Mar 1998 03:54:15 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA17557; Sun, 8 Mar 1998 03:54:04 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA08262 (5.67b/IDA-1.5); Sun, 8 Mar 1998 12:53:58 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.7/8.6.12) id UAA27884; Sat, 7 Mar 1998 20:09:18 +0100 (MET) From: Wilko Bulte Message-Id: <199803071909.UAA27884@yedi.iaf.nl> Subject: Re: your mail In-Reply-To: <199803071731.JAA27263@hub.freebsd.org> from Julian Stacey at "Mar 7, 98 09:31:09 am" To: jhs@FreeBSD.ORG Date: Sat, 7 Mar 1998 20:09:18 +0100 (MET) Cc: scsi@FreeBSD.ORG, me@FreeBSD.ORG, gj@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL32 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Julian Stacey wrote... > Hi SCSI people, > Is it necessary to format a 4.3G SCSI disc on the same system + controller > ncr0 rev 18 int a irq 10 on pci0:10 > that the disc will later run FreeBSD on ? Not necessary. I assume you mean format as in 'sending it the SCSI command FORMAT UNIT' > BTW on my 2.2.5 system with the NCR controller, (with root on wd0) I did: > scsi -f /dev/rsd0c -m 1 -e -P 3 > AWRE (Auto Write Reallocation Enbld): 1 > ARRE (Auto Read Reallocation Enbld): 1 > [ so the disc _should_ be self correcting, > but obviously isn't, is running out of sectors ] If that is really the case this is normally the disc dying. Or overheating!!! > scsi -f /dev/rsd0c -c "4 0 0 0 0 0" > SCIOCCOMMAND ioctl: Command accepted. > return status 1 (Command Timeout) after 2000 msCommand out (6 of 6): > 04 00 00 00 00 00 > No sense sent. > [ Don't know what's wrong The format takes much longer than 2 seconds: man scsi ... -s sets the command timeout in seconds. The default is two seconds. ... It's more like a couple of hours for 4Gb. ;-) See also 'man scsiformat' Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko @ yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' --------------- Support your local daemons: run [Free,Net,Open]BSD Unix -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 8 05:47:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25818 for freebsd-scsi-outgoing; Sun, 8 Mar 1998 05:47:46 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns.frihet.com (root@frihet.bayarea.net [205.219.92.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA25806 for ; Sun, 8 Mar 1998 05:47:36 -0800 (PST) (envelope-from tweten@ns.frihet.com) Received: from ns.frihet.com (tweten@localhost [127.0.0.1]) by ns.frihet.com (8.8.8/8.8.8) with ESMTP id FAA15864; Sun, 8 Mar 1998 05:47:19 -0800 (PST) (envelope-from tweten@ns.frihet.com) Message-Id: <199803081347.FAA15864@ns.frihet.com> X-Mailer: exmh version 2.0.1 12/23/97 To: "Thomas F. Keefe" Cc: Julian Elischer , freebsd-scsi@FreeBSD.ORG Subject: Re: timeouts with adaptec 1742 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Mar 1998 05:47:18 -0800 From: "David E. Tweten" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Last October, you had a discussion on the FreeBSD SCSI list with Julian Elischer about your difficulties with an Adaptec 1742 and a Seagate ST32151N, under FreeBSD. You said that the combination worked under DOS. On Oct. 12, 1997, Thomas F. Keefe wrote: >During the commit step during the install, the system hangs (the activity LED >on the adaptec remains on) and after about 15sec. The message "Panic(adaptec >1742) for historical reasons" is displayed and after a short delay, the system >reboots. The e-mail thread in the FreeBSD data base petered out on the 30th of October, with no apparent resolution. Since I'm experiencing a similar problem with a 1742, FreeBSD 2.2.5, and a Seagate ST34571N, I'm hoping your problem actually was resolved. Was it? If so, what was the resolution? Thanks for any help you can provide. -- David E. Tweten | 2047-bit PGP fingerprint: | tweten@frihet.com 12141 Atrium Drive | E9 59 E7 5C 6B 88 B8 90 | tweten@and.com Saratoga, CA 95070-3162 | 65 30 2A A4 A0 BC 49 AE | (408) 446-4131 Those who make good products sell products; those who don't, sell solutions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 8 08:40:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13363 for freebsd-scsi-outgoing; Sun, 8 Mar 1998 08:40:51 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13358 for ; Sun, 8 Mar 1998 08:40:49 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id IAA26443; Sun, 8 Mar 1998 08:36:42 -0800 (PST) Message-Id: <199803081636.IAA26443@implode.root.com> To: "David E. Tweten" cc: "Thomas F. Keefe" , Julian Elischer , freebsd-scsi@FreeBSD.ORG Subject: Re: timeouts with adaptec 1742 In-reply-to: Your message of "Sun, 08 Mar 1998 05:47:18 PST." <199803081347.FAA15864@ns.frihet.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 08 Mar 1998 08:36:42 -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Last October, you had a discussion on the FreeBSD SCSI list with Julian >Elischer about your difficulties with an Adaptec 1742 and a Seagate ST32151N, >under FreeBSD. You said that the combination worked under DOS. ... >Since I'm experiencing a similar problem with a 1742, FreeBSD 2.2.5, and a >Seagate ST34571N, I'm hoping your problem actually was resolved. Was it? If >so, what was the resolution? That seems kind of strange, but I had problems using a 1742 with modern drives myself back in FreeBSD 1.x days - it simply refused to work reliably in fast (10MHz) mode with certain drives - actually resulting in corrupt data being written out(!). ...I don't know if this is at all related to your problem, however. You might try slowing things down to 5MHz though... -DG David Greenman Core-team/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 8 15:03:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25194 for freebsd-scsi-outgoing; Sun, 8 Mar 1998 15:03:13 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA25161 for ; Sun, 8 Mar 1998 15:03:04 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA03082 (5.67b/IDA-1.5 for freebsd-scsi@FreeBSD.ORG); Mon, 9 Mar 1998 00:02:13 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.7/8.6.12) id UAA03951; Sun, 8 Mar 1998 20:42:33 +0100 (MET) From: Wilko Bulte Message-Id: <199803081942.UAA03951@yedi.iaf.nl> Subject: Re: timeouts with adaptec 1742 In-Reply-To: <199803081636.IAA26443@implode.root.com> from David Greenman at "Mar 8, 98 08:36:42 am" To: dg@root.com Date: Sun, 8 Mar 1998 20:42:32 +0100 (MET) Cc: tweten@frihet.com, keefe@cse.psu.edu, julian@whistle.com, freebsd-scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL32 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As David Greenman wrote... > >Last October, you had a discussion on the FreeBSD SCSI list with Julian > >Elischer about your difficulties with an Adaptec 1742 and a Seagate ST32151N, > >under FreeBSD. You said that the combination worked under DOS. > ... > >Since I'm experiencing a similar problem with a 1742, FreeBSD 2.2.5, and a > >Seagate ST34571N, I'm hoping your problem actually was resolved. Was it? If > >so, what was the resolution? > > That seems kind of strange, but I had problems using a 1742 with modern > drives myself back in FreeBSD 1.x days - it simply refused to work reliably > in fast (10MHz) mode with certain drives - actually resulting in corrupt > data being written out(!). ...I don't know if this is at all related to > your problem, however. You might try slowing things down to 5MHz though... David is right: the 174x is a known pain in the b*tt for newer/faster drives. It is very sensitive to the 'cleanliness' of the SCSI bus, for instance you should not use an external and an internal cable on the same board at the same time. Some people get away with it, for others it is the kiss of death. I have FreeBSD 2.x running with 1740 successfully, but only with non-fast drives. 274x boards tend to be quite a bit better Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko @ yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' --------------- Support your local daemons: run [Free,Net,Open]BSD Unix -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 8 17:33:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15493 for freebsd-scsi-outgoing; Sun, 8 Mar 1998 17:33:18 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15476 for ; Sun, 8 Mar 1998 17:33:15 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id SAA04694 for ; Sun, 8 Mar 1998 18:33:14 -0700 (MST) Message-Id: <199803090133.SAA04694@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: scsi@FreeBSD.ORG Subject: New CAM snapshot available. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Mar 1998 18:30:05 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The 980308 CAM snapshot is now available at the following locations: ftp.FreeBSD.org:/pub/FreeBSD/cam ftp.kdm.org:/pub/FreeBSD/cam The README available at these sites is reproduced below. As always, your comments about CAM are greatly appreciated. Thanks, Justin Common Access Method SCSI Layer "What is CAM? and why would I want it?" CAM is an ANSI ratified spec that defines a software interface for talking to SCSI and ATAPI devices. This new SCSI layer for FreeBSD is not strictly CAM compliant, but follows many of the precepts of CAM. More importantly, this work addresses many of the short comings of the previous SCSI layer and should provide better performance, reliability, and ease the task of adding support for new controllers. "Who is working on CAM?" Justin T. Gibbs Kenneth D. Merry General discussion about CAM usually occurs on the FreeBSD-scsi@FreeBSD.org list. "What hardware is supported?" Controller Drivers: Aic7xxx driver (ahc): This driver supports all of the devices the original FreeBSD driver supports but with the following new features: Support for aic7890/91/95 based controllers. ULTRA2 speeds have not yet been tested. I'd be happy to do so if someone wants to send me a drive. 8-) The driver now uses the secondary DMA FIFO to DMA SCBs and SG lists on controllers that support it. Although some prefetching is performed now, there is still much room for improvement. Autotermination support for all cards that support it. SCB paging that allows up to 255 SCBs to be active on aic7770, aic7850, and aic7860 cards. Bug fixes to the multi-lun support. The beginnings of a target mode implementation. AdvanSys Driver (adv): This driver supports the entire line of AdvanSys narrow channel devices. Tagged queuing is also supported. NCR Driver (ncr): This driver supports all of the devices the original driver supports, but does not yet have truely robust error recovery features implemented. Supported Peripherals: Direct Access driver (da): 512 byte sectored disk drivers. Support for other sector sizes is planned, but further investigation on the "right" approach for this is needed. It probably belongs in the disk-slice code. CDROM driver (cd): This driver should support everything the old driver did. Sequential Access driver (sa): This driver should support most "newer" tape drives. It does not have the ability to change either the density or compression settings yet. This is the "greenest" component in CAM currently, having only been tested on an Archive Python. Look for additional enhancements to this driver in the near term. "What versions of FreeBSD can I use CAM with?" CAM is developed under FreeBSD-current so most patch sets apply to a "current" of the day the snapshot was released. The patches will likely apply to source trees synched near that date, but there are no guarantees. As soon as the merging activity for 2.2.6 into -stable dies down, we plan on releasing a version of CAM for 2.2. CAM greatly increases the stability of the SCSI system and is currently being run on Wcarchive (a 2.2 environment). If your environment does not require device support that CAM has yet to offer and you are encountering SCSI related instabilities, you may want to give it a try when the next 2.2 patch set becomes available. "How reliable is it?" Although "work in progress", this code has been through over six months of testing here at Pluto in a RAID application. We feel pretty good about the stability of the code. If you do have the facilities to experiment (you must be running current), please do. We welcome your feedback especially about the performance and reliability of the new system. "How do I install it?" BACKUP YOUR OLD SRC TREE AND KERNEL!!!! cp /kernel /kernel.works Get the code: ftp://ftp.FreeBSD.org/pub/FreeBSD/cam/cam-980308.diffs.gz On a FreeBSD-current system from ~980308 cd /usr/src zcat cam-980308.diffs.gz | patch -p1 cd usr.sbin/config make clean all install cd ../../sys/i386/conf vi MYKERNEL Comment out all unsupported SCSI devices, and substitute "da" for "sd" and "sa" for "st". Look in LINT or GENERIC for examples. config MYKERNEL cd ../../MYKERNEL make all make install "What are the features of CAM?" - Round-robin, per priority level scheduling of devices and their resources. - I/O Completion, error recovery, and processing queued I/O is performed in a separate software interrupt handler. The old system had the potential of blocking out hardware interrupts for lengthy periods as much of this processing occurred as the result of a call from the controller's interrupt handler. - The generic SCSI layer now understands tagged I/O and exports this functionality to the peripheral drivers. This allows drivers like the "direct access" driver to perform ordered tagged transactions for meta-data writes. Async, ordered, meta-data writes are now enabled in vfs_bio.c - The "direct access" driver prevents "tag starvation" from occurring by guaranteeing that at least one write in every 5 second period to a tagged queuing device has an ordered tag. This removes the need for individual controller drivers to worry about this problem. - Complete and controller independent handling of the "QUEUE FULL" and "BUSY" status codes. The number of tags that are queued to a device are dynamically adjusted by the generic layer. - Interrupt driven sub-device probing. At boot time, all buses are probed in parallel yielding a much faster boot. As probing occurs after all interrupt and timer services are available, no additional (and often error prone) "polling" code is needed in each controller driver. - Better error recovery. When an error occurs, the queue of transactions to the erring device is "frozen", full status is reported back to the peripheral driver, and the peripheral driver can recover the device without perturbing queued up I/O. As all transactions have an associated priority and generation count, after recovery is complete, transactions that are retried are automatically re-queued in their original order. - All error handling is performed based on a detected failure. The old code would often perform actions "just in case" before accessing a device as the error recovery mechanism was inadequate. Now, for example, if your disk spins down, the system will properly recover even if the device is already open. - Support for "high power" commands. Peripheral drivers can mark actions that may tax a power supply as "high powered". Only a certain number (default of 4, but configurable with the CAM_MAX_HIGHPOWER kernel option) of these commands are allowed to be active at a time. This allows a user to, for example, disable spin-up on the drives in an enclosure and let the system spin them up in a controlled fashion. - By default, all luns are scanned on devices during probe. In the old SCSI layer, this was often problematic as it performed a Test Unit Ready prior to performing an Identify. Many devices that properly handle the Identify will hang the bus if you attempt a different command to a high lun. - Transfer negotiations only occurs to devices that actually support negotiations (based on their inquiry information). This is performed in a controller independent fashion. - There is now a generic quirk mechanism that allows controllers, peripheral drivers, or the CAM transport layer to define their own quirks entries. Currently the CAM transport layer has quirk entries that allow for modulation of tags and disabling multi-lun probing. The AdvanSys driver uses quirk entries to control some of the "hardware bug fixes" in the driver that only apply to certain types of devices. - Hard-wiring of devices to specific unit numbers is supported as it was in the old system. - Userland "pass-through" commands are supported. The interface is different than from the old SCSI code, but sample code is provided (including patches to XMCD), and we also provide the beginnings of a "scsi.8" utility in the form of "camcontrol". Features added in the 971211 Snapshot: - Preliminary tape support. This has only been tested on a DDS2 drive and the driver is fairly green. - New device statistic code. A whole slew of information is now recorded on a per-device basis. The interface is generic and once we have systat converted to using this code, all other drivers using the old "dk" stat interface will be converted. The Iostat utility has already been converted to use the new stats. - Bus DMA based bounce buffer support. ISA AdvanSys support now works in all memory configurations. - aic7xxx driver improvements. The aic7895 is now supported. The command queing algorithm is now more efficient. Bug fixes include some problems with error recovery and target initiated sync/wide negotiation. - AdvanSys driver improvements. The driver has now been tested on almost every narrow SCSI card AdvanSys has produced. Many bugs in the device probe code have been fixed. - Table driven error handling. This greatly simplifies the task of enhancing or modifying how errors are handled. - Enhanced PCI conf support. Although this isn't really CAM related, you get it for free. Check out the pciconf utilty for details. - Numerous other bug fixes I've forgotten about. Features added in the 980103 Snapshot: - Preliminary NCR/Symbios adapter support. Regular operations should be fine, but the error recovery portions of this driver need work. - iostat is now fully functional. - Fixed an infinite retry bug in the Adaptec driver's error recovery code. - Fixed a bug that prevented disconnections and ultra speeds for target ids above 7 in the Adaptec driver. - Expanded the use of bowrite to other locations where synchronous writes were used only to maintain write ordering. - The disk drivers now perform the buffer elelevator sort even if the device supports tags. - The da driver will now only invalidate the media if it believes the media or device has changed. This means that errors like unrecoverable media errors will not prevent future reads and writes (e.g. to remap a sector). - Userconfig.c now compiles. - Correct ccd to initialize b_resid to 0 as all other buffer allocators in the kernel do so that low level driver code only needs to touch b_resid in the error case. - Transfer negotiation now occurs earlier in the probe sequence so that the messages output at boot time have the final and proper negotiation info in them. - When performing the mode sense during probe to retrieve the control page, we nolonger attempt to use the DBD bit. Some devices don't like that. Changes for the 980308 Snapshot: - Aic7xxx driver now supports the 7890/91 (AKA 2940U2W). This includes support for the new "bmov" instruction, and some utilization of the secondary DMA FIFO for S/G list prefetch on aic7890/91/95 chips. ULTRA2 speeds have not been tested as I do not have any ULTRA2 peripherals to test with. - CAM now differentiates between "user" transfer settings and "current" transfer settings. When a controller starts up, it's current settings should be async/narrow and it's user settings should reflect any configured settings for the card (e.g. SCSI-Select settings) or the defaults if configuration is not supported. During device probe, the XPT layer will querry for the user settings, filter them based on the capabilities of the device and use the result to set the current settings. The aic7xxx driver has been updated to deal with these changes including a new scheme for storing and handling negotiation settings in that driver. Updating the other drivers will follow shortly and is trivial to do. - Full kernel hot swap support. The kernel and all peripheral drivers can handle devices arriving and going away after boot up. - To determine whether any new devices have arrived, you must rescan a SCSI bus, or rescan a particular device by completely specifying it's bus/target/lun. This can be done with the new "camcontrol" utility. Although it would be possible to have the kernel "auto-detect" some new devices using Asynchronous Even Notifications (AEN), no controller driver currently supports AENs and device support for AENs is rare, so AEN support is low on the wish list. - The kernel can figure out that a device has gone away if it gets a selection timeout while talking to the device. In that case, the kernel will automatically invalidate the device and all attached peripheral drivers. You can also issue a rescan of a bus or a bus/target/lun and the kernel will notice if any devices have gone away. - Device removal goes in two stages: - The kernel notices (either through a rescan or a selection timeout) that a device has gone away. It marks the device as invalid, and prints out something like this: (cd5:ahc1:0:1:3): lost device At this point, the peripheral driver will still exists if it is open, although in a state where all new opens, ioctls and I/O requests are refused. This ensures that the system can gracefully handle final close of the device. - Once final close of the device occurs (all userland processes that have the device open issue a close), the kernel finishes removing that peripheral driver instance. The kernel then prints out something like this: (cd5:ahc1:0:1:3): removing device entry Then, and only then, can another peripheral driver with the same unit number take its place. The system enforces this behavior to ensure that all clients release the device, thereby acknowledging the error condition, before any new or old clients can access the new device instance. Be aware when removing a device that even though the "regular" peripheral driver (cd, sd, sa) for a device has gone away, the passthrough peripheral driver, if still open, will still be around. For instance, if you're playing a CD with xmcd, xmcd will only have the passthrough device open, not the cd device. If you unplug the CDROM drive from the SCSI bus, the cd device will go away on the next rescan or selection timeout since you don't have a CD filesystem mounted. The passthrough device will not release, though, until you exit XMCD. The passthrough device is normally "silent" about it's presense, and by default will not print any messages when it arrives or goes away. If you boot with -v, the passthrough driver will print out probe messages and arrival/departure messages. - Better CD changer support. The CAM CDROM driver now automatically detects lun-based CD changers and schedules run time for each lun. This greatly reduces the changer thrashing caused by multiple users or applications accessing multiple CDs on a changer at the same time. - Changer detection is rather simplistic -- if the CD driver sees a CDROM device with a LUN greater than 0, it assumes that that device is part of a changer. All luns of that target will be included in a changer meta-driver, and scheduled to run on a mutually exclusive basis. - Each lun on a changer gets a minimum and a maximum amount of run time. The compiled in defaults are 2 seconds and 10 seconds, respectively, but they can be changed easily by the end user. The maximum run time is only enforced if there is another lun on the changer with I/O waiting. The default minimum and maximum run time can be changed in the kernel config file. See LINT for details. They can also be changed on the fly via two new sysctl variables: kern.cam.cd.changer.min_busy_seconds kern.cam.cd.changer.max_busy_seconds So you can interactively tune your changer's performance to suit your changer and usage patterns. - If anyone actually has a CD tower or other peripheral with independant devices reported on each LUN (not target!), please send probe (i.e. boot) output to ken@plutotech.com. I'll put a quirk entry in the CD driver so that your device doesn't get recognized as a changer. Many thanks go to Lars Fredriksen for letting us borrow his changer to perform this work. - New camcontrol utility. There is no man page for it yet, but eventually this should be at least as useful as scsi(8). For now, it can: - list CAM peripherals attached to a given device - send a test unit ready to a given device - send a SCSI inquiry to a device (and yes, Satoshi, you can print out a drive serial number all by itself. :) ) - send a start/stop unit command to a device (and optionally load or eject media) - rescan a given bus for new/removed devices, or rescan a given bus/target/lun to see if it is present or has gone away - read the defect list (permanant or grown) for a given drive. - Tape driver enhancements. - The CAM tape driver now supports the retension, offline/rewoffl and erase mt(1) commands. - The tape driver also will reserve and release a tape drive on open and close, respectively. This insures mutually exclusive access to the tape drive in multiple initiator environments. - mt(1) has been updated with a number of new densities, and now prints out the bits per inch for each density. - Improved statistics support. Almost every SCSI command sent to a device is now recorded in the devstat facility. Before, some commands, especially non block I/O commands, fell through the cracks. - New transport layer device driver. This drive accepts CCB types that don't apply to a single device (e.g. bus rescanning CCBs). It also accepts the getpassthrough ioctl, and thus performs matching between peripheral drivers and their corresponding passthrough drivers. This change allows users to perform diagnostics on a device using the passthrough driver, even if the normal peripheral driver for the device can't be opened. For instance, you can issue a test unit ready to a CDROM device even when there is no media in the drive. - Updated userland CAM library. - The CAM library interface has been changed to take advantage of the new transport layer device. So, there is now a cam_open_spec_device() function. This allows you to individually specify the device name (e.g. "da", "cd", "sa") and unit number for the peripheral driver you want to open. cam_open_device() now just tries to derive the peripheral name and unit number from the passed in device path. It then passes those in to the real open function. - The CAM library now includes a number of tape-related CCB building functions. -- Justin T. Gibbs Kenneth D. Merry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 8 18:32:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26990 for freebsd-scsi-outgoing; Sun, 8 Mar 1998 18:32:36 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dt050ndd.san.rr.com (root@dt050ndd.san.rr.com [204.210.31.221]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26955 for ; Sun, 8 Mar 1998 18:32:32 -0800 (PST) (envelope-from Studded@dal.net) Received: from dal.net (dougdougdougdoug@localhost [127.0.0.1]) by dt050ndd.san.rr.com (8.8.8/8.8.8) with ESMTP id SAA05363; Sun, 8 Mar 1998 18:32:18 -0800 (PST) (envelope-from Studded@dal.net) Message-ID: <350354B2.1D12A068@dal.net> Date: Sun, 08 Mar 1998 18:32:18 -0800 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-STABLE-0308 i386) MIME-Version: 1.0 To: "Justin T. Gibbs" CC: scsi@FreeBSD.ORG Subject: Re: New CAM snapshot available. References: <199803090133.SAA04694@pluto.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T. Gibbs wrote: > As soon as the merging activity for 2.2.6 into -stable dies > down, we plan on releasing a version of CAM for 2.2. CAM > greatly increases the stability of the SCSI system and is > currently being run on Wcarchive (a 2.2 environment). If > your environment does not require device support that CAM > has yet to offer and you are encountering SCSI related > instabilities, you may want to give it a try when the next > 2.2 patch set becomes available. Once the base code beta period starts, there will be about two weeks before the ports collection freezes (per previous announcements). Would it be possible during that time period to make a port out of this? It seems that this would be the best solution, since committing the patches to -Stable is probably not a good idea. Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 5,328 clients and still growing. *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 8 18:49:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00468 for freebsd-scsi-outgoing; Sun, 8 Mar 1998 18:49:18 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00457 for ; Sun, 8 Mar 1998 18:49:14 -0800 (PST) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id VAA10750 for ; Sun, 8 Mar 1998 21:46:06 -0500 (EST) Date: Sun, 8 Mar 1998 21:49:13 -0500 (EST) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: scsi@FreeBSD.ORG Subject: Softupdates with new CAM snapshot 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 anyone know if the new CAM snapshot will now work with softupdates since softupdates is now in the tree? Before CAM's config didnt recognize softupdates in the kernel config. Do they both work together now? I hate having to choose one over the other. Chris -- "I am closed minded. It keeps the rain out." ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.5 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 8 19:17:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08690 for freebsd-scsi-outgoing; Sun, 8 Mar 1998 19:17:52 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08652 for ; Sun, 8 Mar 1998 19:17:47 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id WAA19657; Sun, 8 Mar 1998 22:16:33 -0500 (EST) Date: Sun, 8 Mar 1998 22:16:33 -0500 (EST) From: Chuck Robey X-Sender: chuckr@localhost To: Open Systems Networking cc: scsi@FreeBSD.ORG Subject: Re: Softupdates with new CAM snapshot 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, 8 Mar 1998, Open Systems Networking wrote: > > Does anyone know if the new CAM snapshot will now work with softupdates > since softupdates is now in the tree? > Before CAM's config didnt recognize softupdates in the kernel config. > Do they both work together now? > I hate having to choose one over the other. They shouldn't. A disk driver shouldn't know anything about a file sytem, should it? I'd be disappointed if it did, not in the loss of capability, but because that'd be unclean. > > Chris > > -- > "I am closed minded. It keeps the rain out." > > ===================================| Open Systems Networking And Consulting. > FreeBSD 2.2.5 is available now! | Phone: 316-326-6800 > -----------------------------------| 1402 N. Washington, Wellington, KS-67152 > FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net > http://www.freebsd.org | Consulting-Network Engineering-Security > ===================================| http://open-systems.net > > -----BEGIN PGP PUBLIC KEY BLOCK----- > Version: 2.6.2 > > mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te > gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC > foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z > d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb > NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv > CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 > b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= > =BBjp > -----END PGP PUBLIC KEY BLOCK----- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 8 19:19:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA09044 for freebsd-scsi-outgoing; Sun, 8 Mar 1998 19:19:47 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from TomQNX.tomqnx.com (ott-pm6-28.comnet.ca [206.75.140.188]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08872; Sun, 8 Mar 1998 19:19:08 -0800 (PST) (envelope-from freebsd@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m0yBt55-000833C; Sun, 8 Mar 1998 22:18:23 -0500 (EST) Message-Id: From: freebsd@tomqnx.com (Tom Torrance) Subject: Weird SCSI timeout problem To: freebsd-scsi@FreeBSD.ORG Date: Sun, 8 Mar 1998 22:18:22 -0500 (EST) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am quite concerned about a weird timeout problem I just had. Could it feasibly cause corruption of my ccd0? sd1, sd2 and sd3 comprise ccd0, interleave 32 and flag 0x02. I am using an adaptec 2740A controller in a 486DX2/66. It seems to work great, just installed it about 6 hours ago, except this just happened during a recursive copy of /usr/ports to ccd0. I am not signed on to the scsi list, so please include mail reply... Thanks in advance! Tom Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.5-STABLE #0: Sun Mar 8 17:19:20 EST 1998 tom@tomqnx.tomqnx.com:/usr/src/sys/compile/TOMQNX CPU: i486 DX2 (486-class CPU) Origin = "GenuineIntel" Id = 0x435 Stepping=5 Features=0x3 real memory = 50331648 (49152K bytes) avail memory = 46338048 (45252K bytes) eisa0: Probing for devices on the EISA bus ahc0: at 0x2c00-0x2cff irq 15 on eisa0 slot 2 ahc0: aic7770 >= Rev E, Single Channel, SCSI Id=7, 4 SCBs ahc0 waiting for scsi devices to settle ahc0: target 0 Tagged Queuing Device (ahc0:0:0): "QUANTUM FIREBALL_TM3200S 300N" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 3067MB (6281856 512 byte sectors) sd0(ahc0:0:0): with 6810 cyls, 5 heads, and an average 184 sectors/track (ahc0:1:0): "HP 2213A C938" type 0 fixed SCSI 1 sd1(ahc0:1:0): Direct-Access 633MB (1296512 512 byte sectors) sd1(ahc0:1:0): with 1457 cyls, 16 heads, and an average 55 sectors/track (ahc0:2:0): "HP 2213A C938" type 0 fixed SCSI 1 sd2(ahc0:2:0): Direct-Access 633MB (1296512 512 byte sectors) sd2(ahc0:2:0): with 1457 cyls, 16 heads, and an average 55 sectors/track (ahc0:3:0): "HP 2213A C938" type 0 fixed SCSI 1 sd3(ahc0:3:0): Direct-Access 633MB (1296512 512 byte sectors) sd3(ahc0:3:0): with 1457 cyls, 16 heads, and an average 55 sectors/track (ahc0:4:0): "HP CD-Writer 6020 1.07" type 5 removable SCSI 2 worm0(ahc0:4:0): Write-Once Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> pca0 on motherboard pca0: PC speaker audio driver sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 at 0x278-0x27f on isa psm0 not found at 0x60 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in fd1: 1.2MB 5.25in wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff on isa wdc0: unit 0 (wd0): , multi-block-64 wd0: 504MB (1032192 sectors), 1024 cyls, 16 heads, 63 S/T, 512 B/S wt0 at 0x300-0x301 irq 5 drq 1 on isa wt0: type 1 3C5x9 board(s) on ISA found at 0x210 ep0 at 0x210-0x21f irq 11 on isa ep0: aui/bnc[*BNC*] address 00:60:8c:de:bf:e1 joy0 at 0x201 on isa joy0: joystick npx0 msize 49152 on motherboard npx0: INT 16 interface sctarg0(noadapter::): Processor Target ccd0-3: Concatenated disk drivers pid 275 (mysqld), uid 0: exited on signal 11 sd2(ahc0:2:0): SCB 0x0 - timed out in message out phase, SCSISIGI == 0xa4 SEQADDR = 0x99 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0x2 sd2(ahc0:2:0): abort message in message buffer sd2(ahc0:2:0): SCB 0 - Abort Completed. sd2(ahc0:2:0): no longer in timeout sd1(ahc0:1:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x4 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa sd1(ahc0:1:0): Queueing an Abort SCB sd1(ahc0:1:0): Abort Message Sent sd1(ahc0:1:0): SCB 1 - Abort Completed. sd1(ahc0:1:0): no longer in timeout sd3(ahc0:3:0): SCB 0x3 - timed out in message out phase, SCSISIGI == 0xa4 SEQADDR = 0x99 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0x2 sd3(ahc0:3:0): abort message in message buffer sd3(ahc0:3:0): SCB 3 - Abort Completed. sd3(ahc0:3:0): no longer in timeout sd1(ahc0:1:0): SCB 0x2 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x7 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa sd1(ahc0:1:0): Queueing an Abort SCB sd1(ahc0:1:0): Abort Message Sent sd1(ahc0:1:0): SCB 2 - Abort Completed. sd1(ahc0:1:0): no longer in timeout To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 8 19:42:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13551 for freebsd-scsi-outgoing; Sun, 8 Mar 1998 19:42:30 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA13531 for ; Sun, 8 Mar 1998 19:42:25 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yBsol-00071b-00; Sun, 8 Mar 1998 19:01:31 -0800 Date: Sun, 8 Mar 1998 19:01:30 -0800 (PST) From: Tom To: Studded cc: scsi@FreeBSD.ORG Subject: Re: New CAM snapshot available. In-Reply-To: <350354B2.1D12A068@dal.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 8 Mar 1998, Studded wrote: > Once the base code beta period starts, there will be about two weeks > before the ports collection freezes (per previous announcements). Would > it be possible during that time period to make a port out of this? It > seems that this would be the best solution, since committing the patches > to -Stable is probably not a good idea. A port? CAM is a bunch of kernel patches. How are you going to make a port of it? > Doug Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 8 19:44:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13948 for freebsd-scsi-outgoing; Sun, 8 Mar 1998 19:44:20 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA13933 for ; Sun, 8 Mar 1998 19:44:17 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yBtC1-00072b-00; Sun, 8 Mar 1998 19:25:33 -0800 Date: Sun, 8 Mar 1998 19:25:28 -0800 (PST) From: Tom To: Chuck Robey cc: Open Systems Networking , scsi@FreeBSD.ORG Subject: Re: Softupdates with new CAM snapshot 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, 8 Mar 1998, Chuck Robey wrote: > On Sun, 8 Mar 1998, Open Systems Networking wrote: > > > Does anyone know if the new CAM snapshot will now work with softupdates > > since softupdates is now in the tree? > > Before CAM's config didnt recognize softupdates in the kernel config. > > Do they both work together now? > > I hate having to choose one over the other. > > They shouldn't. A disk driver shouldn't know anything about a file > sytem, should it? I'd be disappointed if it did, not in the loss of > capability, but because that'd be unclean. Since both CAM and Softupdates are distributed as patches, and both patches modify some of the same files, you can't install both without some fiddling. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 8 19:46:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14339 for freebsd-scsi-outgoing; Sun, 8 Mar 1998 19:46:19 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA14314 for ; Sun, 8 Mar 1998 19:46:13 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yBtEU-00072d-00; Sun, 8 Mar 1998 19:28:06 -0800 Date: Sun, 8 Mar 1998 19:28:04 -0800 (PST) From: Tom To: Tom Torrance cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Weird SCSI timeout problem In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Please don't CC to two lists... On Sun, 8 Mar 1998, Tom Torrance wrote: > I am quite concerned about a weird timeout problem I just had. > Could it feasibly cause corruption of my ccd0? Depends on whether your system recovers, or hangs. If it hangs, and you forced to do a reset, corruption is likely. "timed out while" idle is long standing issue (search archives for that phrase"). Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 8 19:59:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15582 for freebsd-scsi-outgoing; Sun, 8 Mar 1998 19:59:05 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.32]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA15576 for ; Sun, 8 Mar 1998 19:58:59 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0yBtQx-00073N-00; Sun, 8 Mar 1998 19:40:59 -0800 Date: Sun, 8 Mar 1998 19:40:59 -0800 (PST) From: Tom To: Open Systems Networking cc: scsi@FreeBSD.ORG Subject: Re: Softupdates with new CAM snapshot 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, 8 Mar 1998, Open Systems Networking wrote: > On Sun, 8 Mar 1998, Tom wrote: > > > Since both CAM and Softupdates are distributed as patches, and both > > patches modify some of the same files, you can't install both without some > > fiddling. > > Right. But as I said though, now that softupdates is IN the tree now, will > CAM work with the softupdates code? I agree that earlier, when they were > both patches yes it wouldn't work. But now softupdates is in the tree, so > does this fact change anything? Try the CAM patch and see. If it does fail, look at the reject files and you might be able to apply things manually. Its not that it won't work, it just that you haven't worked on it long enough yet :) > Chris > > -- > "I am closed minded. It keeps the rain out." Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 8 20:16:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18321 for freebsd-scsi-outgoing; Sun, 8 Mar 1998 20:16:41 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA18224 for ; Sun, 8 Mar 1998 20:16:21 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id VAA29005; Sun, 8 Mar 1998 21:13:05 -0700 (MST) Date: Sun, 8 Mar 1998 21:13:05 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199803090413.VAA29005@narnia.plutotech.com> To: Open Systems Networking cc: scsi@FreeBSD.ORG Subject: Re: Softupdates with new CAM snapshot Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > > Does anyone know if the new CAM snapshot will now work with softupdates > since softupdates is now in the tree? > Before CAM's config didnt recognize softupdates in the kernel config. > Do they both work together now? > I hate having to choose one over the other. This was most likeley due to a merging problem when you applied the older CAM patches to too new a source tree. CAM should not interfere with softupdates. > Chris -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Mar 8 20:44:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA23720 for freebsd-scsi-outgoing; Sun, 8 Mar 1998 20:44:34 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.webspan.net (root@mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA23647 for ; Sun, 8 Mar 1998 20:44:22 -0800 (PST) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id WAA22896; Sun, 8 Mar 1998 22:50:04 -0500 (EST) Date: Sun, 8 Mar 1998 22:53:11 -0500 (EST) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: Tom cc: scsi@FreeBSD.ORG Subject: Re: Softupdates with new CAM snapshot 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, 8 Mar 1998, Tom wrote: > Since both CAM and Softupdates are distributed as patches, and both > patches modify some of the same files, you can't install both without some > fiddling. Right. But as I said though, now that softupdates is IN the tree now, will CAM work with the softupdates code? I agree that earlier, when they were both patches yes it wouldn't work. But now softupdates is in the tree, so does this fact change anything? Chris -- "I am closed minded. It keeps the rain out." ===================================| Open Systems Networking And Consulting. FreeBSD 2.2.5 is available now! | Phone: 316-326-6800 -----------------------------------| 1402 N. Washington, Wellington, KS-67152 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting-Network Engineering-Security ===================================| http://open-systems.net -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQENAzPemUsAAAEH/06iF0BU8pMtdLJrxp/lLk3vg9QJCHajsd25gYtR8X1Px1Te gWU0C4EwMh4seDIgK9bzFmjjlZOEgS9zEgia28xDgeluQjuuMyUFJ58MzRlC2ONC foYIZsFyIqdjEOCBdfhH5bmgB5/+L5bjDK6lNdqD8OAhtC4Xnc1UxAKq3oUgVD/Z d5UJXU2xm+f08WwGZIUcbGcaonRC/6Z/5o8YpLVBpcFeLtKW5WwGhEMxl9WDZ3Kb NZH6bx15WiB2Q/gZQib3ZXhe1xEgRP+p6BnvF364I/To9kMduHpJKU97PH3dU7Mv CXk2NG3rtOgLTEwLyvtBPqLnbx35E0JnZc0k5YkABRO0JU9wZW4gU3lzdGVtcyA8 b3BzeXNAb3Blbi1zeXN0ZW1zLm5ldD4= =BBjp -----END PGP PUBLIC KEY BLOCK----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 9 19:40:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24490 for freebsd-scsi-outgoing; Mon, 9 Mar 1998 19:40:34 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from flint.cyweb.com (root@cyweb.com [209.83.135.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24477 for ; Mon, 9 Mar 1998 19:40:29 -0800 (PST) (envelope-from harry@visiontm.com) Received: from hp.harry.com (dial-16.r04.scbuft.InfoAve.Net [206.74.202.216]) by flint.cyweb.com (8.8.0/8.6.9) with ESMTP id WAA01855 for ; Mon, 9 Mar 1998 22:06:48 -0600 From: "Harry Patterson" To: "scsi freebsd" Subject: CTT8000-S Problems Date: Mon, 9 Mar 1998 22:39:12 -0500 Message-ID: <01bd4bd6$17b89820$d8ca4ace@hp.harry.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've seen several threads here on using the Conner SCSI CTT8000-S based tape drives. Some writers have indicated that they were able to get the HP version of the drives to work, and others had difficulty. I don't believe I saw a final recomendation on how to get these drives working under FreeBSD. If I missed it I appologize in advance. The last entry I saw in my search was the following (in excerpt) From: J Wunsch Subject: Re: BSD Tape Drive Drivers??? In-Reply-To: <19971231130425.44774@lemis.com>; from Greg Lehey on Wed, Dec 31, 1997 at 01:04:25PM +1030 >As Greg Lehey wrote: > > I need to find a driver for SCSI Tape drive for FreeBSD that will > > work with my Seagate Tapestore drive (most software recognizes it as > > a CTT8000-S drive). *snip* >Then you didn't follow this list very closely, Greg. ;-) >These drives aren't really SCSI, despite of their 50-pin connector >looking like SCSI. They violate the SCSI-2 specs. The violation >might be benign for you or not, but we've had several cases here. The >last i can remember is that it rejects the WRITE FILEMARKS command >which is mandatory per the standard. > > Has anyone found a driver that will work? >> Sure. It's part of the kernel. >Well, he's talking about the st(4) driver, most likely. Anyway, >without seeing the exact SCSI error message, it's indeed hard toguess. I just aquired this drive as a Seagate Tapestor (4 gig native) and I am using an Adaptec 1505 but have also used a 1510. When the system boots it probes with the following result: aic0 at 0x340-0x35f irq 11 on isa aic0 waiting for scsi devices to settle (aic0:2:0): "CONNER CTT8000-S 1.22" type 1 removable SCSI 2 st0(aic0:2:0): Sequential-Access density code 0x45, 512-byte blocks, write-enabled Everything looks pretty good at this point. However, no matter what command I try I get no response from the drive (no light, no activity, etc) and eventually get a "Timed out message". This happens with dump and just about any command, for example: mt rewind st0(aic0:2:0): timed out Since it probes, I'm assuming the driver is the problem although I've checked termination, scsi ID, different cables, no tape on boot and everything else this newbie can determine from the manuals, handbook and these lists, except debug. Are these drives supported under FreeBSD? Is there a patch I need to make to get them to work? Am I being dense and missing the obvious? Any help would be appreciated. Harry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Mar 9 23:12:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00189 for freebsd-scsi-outgoing; Mon, 9 Mar 1998 23:12:53 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from quark.ChrisBowman.com (207-172-239-109.s45.as2.rkv.erols.com [207.172.239.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00182 for ; Mon, 9 Mar 1998 23:12:48 -0800 (PST) (envelope-from crb@ChrisBowman.com) Received: from localhost (crb@localhost) by quark.ChrisBowman.com (8.8.8/8.8.7) with SMTP id CAA01248; Tue, 10 Mar 1998 02:14:40 -0500 (EST) (envelope-from crb@ChrisBowman.com) X-Authentication-Warning: quark.ChrisBowman.com: crb owned process doing -bs Date: Tue, 10 Mar 1998 02:14:40 -0500 (EST) From: "Christopher R. Bowman" To: Harry Patterson cc: scsi freebsd Subject: Re: CTT8000-S Problems In-Reply-To: <01bd4bd6$17b89820$d8ca4ace@hp.harry.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 9 Mar 1998, Harry Patterson wrote: >aic0 at 0x340-0x35f irq 11 on isa >aic0 waiting for scsi devices to settle >(aic0:2:0): "CONNER CTT8000-S 1.22" type 1 removable SCSI 2 >st0(aic0:2:0): Sequential-Access density code 0x45, 512-byte blocks, >write-enabled mine probes under 2.2.5 as: (ncr0:4:0): "CONNER CTT8000-S 1.17" type 1 removable SCSI 2 st0(ncr0:4:0): Sequential-Access st0(ncr0:4:0): 5.0 MB/s (200 ns, offset 15) density code 0x45, drive empty and works just fine. --------- Christopher R. Bowman crb@ChrisBowman.com My home page To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 10 03:31:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09056 for freebsd-scsi-outgoing; Tue, 10 Mar 1998 03:31:17 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.ruhrgebiet.individual.net (in-ruhr.ruhr.de [141.39.224.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA09047 for ; Tue, 10 Mar 1998 03:31:14 -0800 (PST) (envelope-from robsch@robkaos.ruhr.de) Received: from robkaos.ruhr.de (admin@localhost) by mail.ruhrgebiet.individual.net (8.8.5-r-beta/8.8.5) with UUCP id LAA20578 for freebsd.org!freebsd-scsi; Tue, 10 Mar 1998 11:10:43 +0100 (MET) Received: by robkaos.ruhr.de (Smail-3.2 1996-Jul-4 #1) id ; Tue, 10 Mar 1998 11:03:52 +0100 (CET) Message-Id: From: robsch@robkaos.ruhr.de (Robert Schien) Subject: Scanner support To: freebsd-scsi@FreeBSD.ORG Date: Tue, 10 Mar 1998 11:03:52 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have an UMAX Astro 1200 S scanner which I want to use under FreeBSD-current. Unfortunately, the SANE port does not compile properly. Something goes wrong with the Makefile, although I have installed gmake-3.75: >> Checksum OK for sane-0.65.tar.gz. ===> Building for sane-0.65 for subdir in lib sanei backend frontend doc; do \ target=`echo all-recursive | sed s/-recursive//`; \ echo making $target in $subdir; \ (cd $subdir && gmake $target) \ || case "" in *k*) fail=yes;; *) exit 1;; esac; \ done && test -z "$fail" making all in lib gmake[1]: Entering directory `/usr2/FreeBSD/robsch/sane/work/sane-0.65/lib' gmake[1]: Nothing to be done for `all'. gmake[1]: Leaving directory `/usr2/FreeBSD/robsch/sane/work/sane-0.65/lib' making all in sanei gmake[1]: Entering directory `/usr2/FreeBSD/robsch/sane/work/sane-0.65/sanei' gmake[1]: Nothing to be done for `all'. gmake[1]: Leaving directory `/usr2/FreeBSD/robsch/sane/work/sane-0.65/sanei' making all in backend gmake[1]: Entering directory `/usr2/FreeBSD/robsch/sane/work/sane-0.65/backend' rm -f .libs/libsane-epson.* -shared -o .libs/libsane-epson.so.0.65 epson.lo epson-s.lo sane_strstatus.lo ../sanei/sanei_init_debug.lo ../lib/alloca.lo ../lib/getopt.lo ../lib/getopt1.lo ../lib/snprintf.lo ../lib/strndup.lo ../lib/strsep.lo ../lib/usleep.lo ../sanei/sanei_constrain_value.lo ../sanei/sanei_scsi.lo -L/usr/X11R6/lib -shared: not found gmake[1]: *** [libsane-epson.la] Error 127 gmake[1]: Leaving directory `/usr2/FreeBSD/robsch/sane/work/sane-0.65/backend' gmake: *** [all-recursive] Error 1 *** Error code 2 Stop. *** Error code 1 Stop. *** Error code 1 Stop. How can I get it compiled and run? TIA Robert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 10 10:01:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10293 for freebsd-scsi-outgoing; Tue, 10 Mar 1998 10:01:12 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from friley585.res.iastate.edu (friley585.res.iastate.edu [129.186.167.85]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10262; Tue, 10 Mar 1998 10:01:00 -0800 (PST) (envelope-from ccsanady@friley585.res.iastate.edu) Received: from friley585.res.iastate.edu (loopback [127.0.0.1]) by friley585.res.iastate.edu (8.8.8/8.8.8) with ESMTP id LAA00353; Tue, 10 Mar 1998 11:59:39 -0600 (CST) (envelope-from ccsanady@friley585.res.iastate.edu) Message-Id: <199803101759.LAA00353@friley585.res.iastate.edu> X-Mailer: exmh version 2.0.1 12/23/97 To: "Justin T. Gibbs" cc: toor@dyson.iquest.net, freebsd-scsi@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Timedout SCBs In-reply-to: Your message of "Sun, 08 Mar 1998 16:40:09 MST." <199803082343.QAA00533@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Mar 1998 11:59:39 -0600 From: Chris Csanady Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>Yep.. Although, I will try it again with the rest of your changes >>as well. I have finally had this happen (I Think the same thing) >>running UP. Although I was not able to capture the exact messages, >>they seemed more scsi related. :\ These are by no means complete, >>or even in order, but should give somewhat of an idea. I think >>that the system just gets hung on a page in, and sits forever waiting >>for the scsi bus to timeout and retry again and again. >> >>Chris > >Can you try CAM? The latest snapshot is building right now (now that the >tree builds again...). Look for an announcement on current and scsi in a >little bit. Hmm.. It seems that it has not solved the problems either. :( Since this now seems as it may be scsi related, I'm inluding freebsd-scsi as well. These are the messages that I am getting with the CAM code--they seem very similar. Basically, the system gets so slow that it seems frozen. If you try to switch to the console from X, it will take a long time, but usually it works. :) /kernel.SMP: Timedout SCB handled by another timeout /kernel.SMP: Timedout SCB handled by another timeout ... /kernel.SMP: swap_pager: indefinate wait buffer: device 0x30411, blkno: 8688, size 8192 /kernel.SMP: swap_pager: indefinate wait buffer: device 0x30411, blkno: 8688, size 8192 ... Now that I have blown away my other disk.. I will try moving my swap there, and see if it makes any differenc. Is it likely it is hardware though? Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 10 10:01:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10490 for freebsd-scsi-outgoing; Tue, 10 Mar 1998 10:01:54 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.ruhrgebiet.individual.net (in-ruhr.ruhr.de [141.39.224.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10453 for ; Tue, 10 Mar 1998 10:01:50 -0800 (PST) (envelope-from robsch@robkaos.ruhr.de) Received: from robkaos.ruhr.de (admin@localhost) by mail.ruhrgebiet.individual.net (8.8.5-r-beta/8.8.5) with UUCP id SAA23341 for freebsd.org!freebsd-scsi; Tue, 10 Mar 1998 18:34:27 +0100 (MET) Received: by robkaos.ruhr.de (Smail-3.2 1996-Jul-4 #1) id ; Tue, 10 Mar 1998 18:31:09 +0100 (CET) Message-Id: From: robsch@robkaos.ruhr.de (Robert Schien) Subject: Re: Scanner support In-Reply-To: from Nick Hibma at "Mar 10, 98 01:44:39 pm" To: freebsd-scsi@FreeBSD.ORG Date: Tue, 10 Mar 1998 18:31:09 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > type > > env CC=gcc make > > instead of > > make > Yes, this did the job. But now I have problems with the configuration of the sane package: As I understand it SANE uses user-level-scsi in order to access the device. Therefore I enabled device uk0 in the kernel config file. I recompiled the kernel and rebooted: During boot the scanner appears as device uk0: Mar 10 18:18:31 robkaos /kernel: uk0 at scbus0 target 1 lun 0 Mar 10 18:18:31 robkaos /kernel: uk0: type 6 fixed SCSI 2 Mar 10 18:18:31 robkaos /kernel: uk0: Unknown I created a /dev entry for uk0: sh MAKEDEV uk0 I set the symlink ln -s uk0 scanner But when I invoke scanimage I get the following message: Mar 10 18:20:11 robkaos /kernel: uk0: physio split the request.. cannot proceed Mar 10 18:20:11 robkaos /kernel: uk0: physio split the request.. cannot proceed Did I anything wrong? There isn't much FreeBSD specific documentation in the sane package :-( TIA for further help Robert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 10 10:19:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15577 for freebsd-scsi-outgoing; Tue, 10 Mar 1998 10:19:21 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15342; Tue, 10 Mar 1998 10:18:39 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id LAA19486; Tue, 10 Mar 1998 11:17:18 -0700 (MST) Message-Id: <199803101817.LAA19486@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: Chris Csanady cc: "Justin T. Gibbs" , toor@dyson.iquest.net, freebsd-scsi@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: Timedout SCBs In-reply-to: Your message of "Tue, 10 Mar 1998 11:59:39 CST." <199803101759.LAA00353@friley585.res.iastate.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Mar 1998 11:14:09 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>Can you try CAM? The latest snapshot is building right now (now that the >>tree builds again...). Look for an announcement on current and scsi in a >>little bit. > >Hmm.. It seems that it has not solved the problems either. :( Since this >now seems as it may be scsi related, I'm inluding freebsd-scsi as well. > >These are the messages that I am getting with the CAM code--they seem very >similar. Basically, the system gets so slow that it seems frozen. If >you try to switch to the console from X, it will take a long time, but >usually it works. :) It looks like a locking or interrupt delivery problem most likely outside of the SCSI system. Can you see if you can reproduce this error using a UP kernel? >Chris -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 10 12:19:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15513 for freebsd-scsi-outgoing; Tue, 10 Mar 1998 12:19:41 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15444 for ; Tue, 10 Mar 1998 12:19:25 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id PAA22926; Tue, 10 Mar 1998 15:18:56 -0500 (EST) From: Peter Dufault Message-Id: <199803102018.PAA22926@hda.hda.com> Subject: Re: Scanner support In-Reply-To: from Robert Schien at "Mar 10, 98 06:31:09 pm" To: robsch@robkaos.ruhr.de (Robert Schien) Date: Tue, 10 Mar 1998 15:18:55 -0500 (EST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I set the symlink > ln -s uk0 scanner > > But when I invoke scanimage I get the following message: > Mar 10 18:20:11 robkaos /kernel: uk0: physio split the request.. cannot proceed > Mar 10 18:20:11 robkaos /kernel: uk0: physio split the request.. cannot proceed > > Did I anything wrong? There isn't much FreeBSD specific documentation > in the sane package :-( The user level commands don't know how to repackage a command when it is split up due to the memory not being physically contiguous - it doesn't know the details of the commands so it can't do the split properly. This makes it bad for data transfers. Options (if available) are to configure sane to use read/write transfers to some device instead for the data transfer, to set it to use smaller block sizes (4K will always work), or a questionable idea involving hackery to map a buffer to a contiguous address using mmap. I thought once about configuring the read/write details for the uk device - there aren't many flavors and a few "set transfer style 1", "set transfer style 2" calls would fix this so you could then have a read/write entry point, but I went no farther than thinking about it. The appropriate use for uk is IMHO for device setup, quirky commands, poking investigating how a device works, etc. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 10 14:33:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA17475 for freebsd-scsi-outgoing; Tue, 10 Mar 1998 14:33:38 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.ruhrgebiet.individual.net (in-ruhr.ruhr.de [141.39.224.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA17402 for ; Tue, 10 Mar 1998 14:33:13 -0800 (PST) (envelope-from robsch@robkaos.ruhr.de) Received: from robkaos.ruhr.de (admin@localhost) by mail.ruhrgebiet.individual.net (8.8.5-r-beta/8.8.5) with UUCP id XAA00235 for freebsd.org!freebsd-scsi; Tue, 10 Mar 1998 23:18:19 +0100 (MET) Received: by robkaos.ruhr.de (Smail-3.2 1996-Jul-4 #1) id ; Tue, 10 Mar 1998 23:16:23 +0100 (CET) Message-Id: From: robsch@robkaos.ruhr.de (Robert Schien) Subject: Re: Scanner support In-Reply-To: <199803102018.PAA22926@hda.hda.com> from Peter Dufault at "Mar 10, 98 03:18:55 pm" To: freebsd-scsi@FreeBSD.ORG Date: Tue, 10 Mar 1998 23:16:23 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The user level commands don't know how to repackage a command when > it is split up due to the memory not being physically contiguous > - it doesn't know the details of the commands so it can't do the > split properly. This makes it bad for data transfers. > > Options (if available) are to configure sane to use read/write > transfers to some device instead for the data transfer, to set it > to use smaller block sizes (4K will always work), or a questionable > idea involving hackery to map a buffer to a contiguous address > using mmap. > Thank you for your explanation. Unfortunately, this means that there is no possibility to use SCSI scanners with FreeBSD at the moment. :-(( It's quite disappointing. :-(( Robert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 10 15:03:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22733 for freebsd-scsi-outgoing; Tue, 10 Mar 1998 15:03:02 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22722 for ; Tue, 10 Mar 1998 15:02:55 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.8.7/8.6.12) id XAA05009; Tue, 10 Mar 1998 23:02:46 GMT Message-ID: <19980310150246.57452@nuxi.com> Date: Tue, 10 Mar 1998 15:02:46 -0800 From: "David E. O'Brien" To: Robert Schien Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Scanner support Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: ; from Robert Schien on Tue, Mar 10, 1998 at 06:31:09PM +0100 X-Warning: Mutt Bites! X-Operating-System: FreeBSD 2.2.5-STABLE Organization: The NUXI *BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > env CC=gcc make > > > > instead of > > > > make > > > Yes, this did the job. Why did this make a difference? Our `cc' is `gcc'. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@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 Mar 10 15:06:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23326 for freebsd-scsi-outgoing; Tue, 10 Mar 1998 15:06:29 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from garbo.lodgenet.com (garbo.lodgenet.com [204.124.122.252]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA23304 for ; Tue, 10 Mar 1998 15:06:24 -0800 (PST) (envelope-from erich@lodgenet.com) Received: from jake.lodgenet.com (jake.lodgenet.com [10.0.122.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id RAA28333; Tue, 10 Mar 1998 17:05:04 -0600 Received: from jake.lodgenet.com (localhost [127.0.0.1]) by jake.lodgenet.com (8.8.8/8.8.5) with ESMTP id RAA03015; Tue, 10 Mar 1998 17:04:47 -0600 (CST) Message-Id: <199803102304.RAA03015@jake.lodgenet.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Peter Dufault cc: robsch@robkaos.ruhr.de (Robert Schien), freebsd-scsi@FreeBSD.ORG Subject: Re: Scanner support In-reply-to: Your message of "Tue, 10 Mar 1998 15:18:55 EST." <199803102018.PAA22926@hda.hda.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Mar 1998 17:04:47 -0600 From: "Eric L. Hernes" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Dufault writes: >> I set the symlink >> ln -s uk0 scanner >> >> But when I invoke scanimage I get the following message: >> Mar 10 18:20:11 robkaos /kernel: uk0: physio split the request.. cannot proc >eed >> Mar 10 18:20:11 robkaos /kernel: uk0: physio split the request.. cannot proc >eed >> I saw almost the same thing with user level scsi commands to pt0, I traced it back to scsi_ioctl.c. around line 290, bp gets bzero()ed, so b_kvasize is forced to zero, regardless of what was passed, in. I patched as follows: Index: scsi_ioctl.c =================================================================== RCS file: /cvs/FreeBSD/src/sys/scsi/scsi_ioctl.c,v retrieving revision 1.29 diff -u -r1.29 scsi_ioctl.c --- scsi_ioctl.c 1998/02/01 18:09:46 1.29 +++ scsi_ioctl.c 1998/03/09 23:18:17 @@ -292,6 +292,7 @@ bp->b_bcount = len = screq->datalen; bp->b_screq = screq; bp->b_sc_link = sc_link; + bp->b_kvasize = len; if (len) { struct uio auio; struct iovec aiov; It's worked on an ncr 53860, and an adaptec 2940 with blocks of 64 bytes and 64k, maybe sizes too. I'd kind of liked to put some upper bound on len, rather than just using it, but this has worked. >Options (if available) are to configure sane to use read/write >transfers to some device instead for the data transfer, to set it >to use smaller block sizes (4K will always work), or a questionable >idea involving hackery to map a buffer to a contiguous address >using mmap. Is the contiguous memory for DMA? Have I just been lucky? >-- >Peter Dufault (dufault@hda.com) Realtime development, Machine control, >HD Associates, Inc. Safety critical systems, Agency approval > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-scsi" in the body of the message > Eric -- Eric L. Hernes erich@lodgenet.com erich@rrnet.com http://rrnet.com/~erich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 10 17:28:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20795 for freebsd-scsi-outgoing; Tue, 10 Mar 1998 17:28:33 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA20768 for ; Tue, 10 Mar 1998 17:28:26 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id UAA23857; Tue, 10 Mar 1998 20:28:04 -0500 (EST) From: Peter Dufault Message-Id: <199803110128.UAA23857@hda.hda.com> Subject: Re: Scanner support In-Reply-To: from Robert Schien at "Mar 10, 98 11:16:23 pm" To: robsch@robkaos.ruhr.de (Robert Schien) Date: Tue, 10 Mar 1998 20:28:04 -0500 (EST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Unfortunately, this means that there is no possibility to use > SCSI scanners with FreeBSD at the moment. :-(( > It's quite disappointing. :-(( I wrote that user level SCSI stuff in the first place when developing scanner support, and I did what isn't a good idea (transferring big chunks of data) without any trouble. It still may not work for the reasons I outlined - namely, that interface doesn't know a write transfer from a test unit ready or a hole in the wall, and so can't intelligently split up a transfer since it doesn't know things like where the number of bytes go etc. The same restriction applies to any "pass through" interface I know of that "sane" is using. I just saw the message about the "kvasize" structure member. I'm pretty sure that didn't exist in the old days - tomorrow I'll look and see what it does. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 10 17:30:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21263 for freebsd-scsi-outgoing; Tue, 10 Mar 1998 17:30:56 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21242 for ; Tue, 10 Mar 1998 17:30:50 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id MAA16949; Wed, 11 Mar 1998 12:26:58 +1100 Date: Wed, 11 Mar 1998 12:26:58 +1100 From: Bruce Evans Message-Id: <199803110126.MAA16949@godzilla.zeta.org.au> To: dufault@hda.com, erich@lodgenet.com Subject: Re: Scanner support Cc: freebsd-scsi@FreeBSD.ORG, robsch@robkaos.ruhr.de Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>> I set the symlink >>> ln -s uk0 scanner >>> >>> But when I invoke scanimage I get the following message: >>> Mar 10 18:20:11 robkaos /kernel: uk0: physio split the request.. cannot proc >>eed >>> Mar 10 18:20:11 robkaos /kernel: uk0: physio split the request.. cannot proc >>eed >>> > >I saw almost the same thing with user level scsi commands to pt0, I traced >it back to scsi_ioctl.c. around line 290, bp gets bzero()ed, so b_kvasize >is forced to zero, regardless of what was passed, in. I patched as follows: >Index: scsi_ioctl.c >=================================================================== >RCS file: /cvs/FreeBSD/src/sys/scsi/scsi_ioctl.c,v >retrieving revision 1.29 >diff -u -r1.29 scsi_ioctl.c >--- scsi_ioctl.c 1998/02/01 18:09:46 1.29 >+++ scsi_ioctl.c 1998/03/09 23:18:17 >@@ -292,6 +292,7 @@ > bp->b_bcount = len = screq->datalen; > bp->b_screq = screq; > bp->b_sc_link = sc_link; >+ bp->b_kvasize = len; > if (len) { > struct uio auio; > struct iovec aiov; > > >It's worked on an ncr 53860, and an adaptec 2940 with blocks of >64 bytes and 64k, maybe sizes too. I'd kind of liked to put >some upper bound on len, rather than just using it, but this has >worked. See PR 5846. b_kvasize should be 0, since the buffer doesn't have any kva. Setting it to a large value here probably works because the value is never used except in the broken maxphys(). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Mar 10 19:30:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06087 for freebsd-scsi-outgoing; Tue, 10 Mar 1998 19:30:34 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from flint.cyweb.com (root@cyweb.com [209.83.135.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06082 for ; Tue, 10 Mar 1998 19:30:32 -0800 (PST) (envelope-from harry@visiontm.com) Received: from hp.harry.com (dial-20.r03.scbuft.InfoAve.Net [206.74.202.150]) by flint.cyweb.com (8.8.0/8.6.9) with ESMTP id VAA12723 for ; Tue, 10 Mar 1998 21:57:25 -0600 From: "Harry Patterson" To: "scsi freebsd" Subject: Still having problems with CTT8000-S Date: Tue, 10 Mar 1998 22:26:13 -0500 Message-ID: <01bd4c9d$71b4e960$e96190cf@hp.harry.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am still having problems getting my Seagate Tapestor (4 gig native) to be accesible after boot. I have been using an Adaptec 1505 but have also used a 1510 + 1520 with the same results. When the system boots it probes with the following result: aic0 at 0x340-0x35f irq 11 on isa aic0 waiting for scsi devices to settle (aic0:2:0): "CONNER CTT8000-S 1.22" type 1 removable SCSI 2 st0(aic0:2:0): Sequential-Access density code 0x45, 512-byte blocks, write-enabled After boot I can't even get the light on the drive to light, let alone rewind or dump. Does anyone have any ideas on getting FreeBSD to work with this drive? I've put it in a Windows95 machine and it works fine as is (no jumper changes). Thanks for any help Harry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 11 04:13:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA01368 for freebsd-scsi-outgoing; Wed, 11 Mar 1998 04:13:11 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA01360 for ; Wed, 11 Mar 1998 04:13:08 -0800 (PST) (envelope-from dufault@hda.hda.com) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id HAA25156; Wed, 11 Mar 1998 07:12:33 -0500 (EST) From: Peter Dufault Message-Id: <199803111212.HAA25156@hda.hda.com> Subject: Re: Scanner support In-Reply-To: <199803110126.MAA16949@godzilla.zeta.org.au> from Bruce Evans at "Mar 11, 98 12:26:58 pm" To: bde@zeta.org.au (Bruce Evans) Date: Wed, 11 Mar 1998 07:12:32 -0500 (EST) Cc: dufault@hda.com, erich@lodgenet.com, freebsd-scsi@FreeBSD.ORG, robsch@robkaos.ruhr.de X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > See PR 5846. b_kvasize should be 0, since the buffer doesn't have > any kva. Setting it to a large value here probably works because > the value is never used except in the broken maxphys(). OK, so he can try something like (change to scsi_ioctl is good but won't fix things): Index: kern_physio.c =================================================================== RCS file: /hosts/hda/mnt2/cvs/src/sys/kern/kern_physio.c,v retrieving revision 1.23 diff -r1.23 kern_physio.c 181c181 < if (bp->b_kvasize < maxphys) --- > if (bp->b_kvasize && bp->b_kvasize < maxphys) Index: scsi_ioctl.c =================================================================== RCS file: /hosts/hda/mnt2/cvs/src/sys/scsi/scsi_ioctl.c,v retrieving revision 1.29 diff -r1.29 scsi_ioctl.c 289,290c289 < bp = malloc(sizeof (struct buf),M_TEMP,M_WAITOK); < bzero(bp,sizeof(struct buf)); --- > bp = getpbuf(); 324c323 < free(bp,M_TEMP); --- > relpbuf(bp) -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 11 05:36:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA10944 for freebsd-scsi-outgoing; Wed, 11 Mar 1998 05:36:21 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from garbo.lodgenet.com (garbo.lodgenet.com [204.124.122.252]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA10938 for ; Wed, 11 Mar 1998 05:36:19 -0800 (PST) (envelope-from erich@lodgenet.com) Received: from jake.lodgenet.com (jake.lodgenet.com [10.0.122.30]) by garbo.lodgenet.com (8.6.12/8.6.9) with ESMTP id HAA32104; Wed, 11 Mar 1998 07:35:00 -0600 Received: from jake.lodgenet.com (localhost [127.0.0.1]) by jake.lodgenet.com (8.8.8/8.8.5) with ESMTP id HAA00496; Wed, 11 Mar 1998 07:34:45 -0600 (CST) Message-Id: <199803111334.HAA00496@jake.lodgenet.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Bruce Evans cc: erich@lodgenet.com, freebsd-scsi@FreeBSD.ORG Subject: Re: Scanner support In-reply-to: Your message of "Wed, 11 Mar 1998 12:26:58 +1100." <199803110126.MAA16949@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Mar 1998 07:34:44 -0600 From: "Eric L. Hernes" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bruce Evans writes: >>It's worked on an ncr 53860, and an adaptec 2940 with blocks of >>64 bytes and 64k, maybe sizes too. I'd kind of liked to put >>some upper bound on len, rather than just using it, but this has >>worked. > >See PR 5846. b_kvasize should be 0, since the buffer doesn't have >any kva. Setting it to a large value here probably works because >the value is never used except in the broken maxphys(). That makes sense. I got to maxphys(), which checked b_kvasize, then choked. I (hackishly) set b_kvasize, where the rest of the structure was filled, without really thinking about it. Is it better to ignore b_kvasize in maxphys()? If so is it better form, or more robust, or both? > >Bruce > Eric -- Eric L. Hernes erich@lodgenet.com erich@rrnet.com http://rrnet.com/~erich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 11 10:03:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20515 for freebsd-scsi-outgoing; Wed, 11 Mar 1998 10:03:35 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20460 for ; Wed, 11 Mar 1998 10:03:19 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id LAA22227 for ; Wed, 11 Mar 1998 11:03:17 -0700 (MST) Message-Id: <199803111803.LAA22227@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: scsi@FreeBSD.ORG Subject: CAM testimonials? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Mar 1998 11:00:08 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I haven't gotten much feedback on the latest CAM snapshot. If you are running CAM, I'd appreciate a small note listing your configuration along with any other comments you have. Thanks! -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 11 10:04:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20973 for freebsd-scsi-outgoing; Wed, 11 Mar 1998 10:04:51 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gorillanet.gorilla.net (gorillanet.gorilla.net [208.128.8.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA20911 for ; Wed, 11 Mar 1998 10:04:34 -0800 (PST) (envelope-from tom@gorilla.net) Received: from [208.143.84.45] by gorillanet.gorilla.net (NTMail 3.03.0014/18.aaac) with ESMTP id na021593 for ; Wed, 11 Mar 1998 12:03:54 -0600 Received: (from tom@localhost) by gorilla.net (8.8.8/8.8.8) id MAA00351; Wed, 11 Mar 1998 12:04:06 -0600 (CST) (envelope-from tom) Message-ID: <19980311120326.41456@TOJ.org> Date: Wed, 11 Mar 1998 12:03:26 -0600 From: Tom Jackson To: scsi freebsd Subject: Re: Still having problems with CTT8000-S Mail-Followup-To: scsi freebsd References: <01bd4c9d$71b4e960$e96190cf@hp.harry.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <01bd4c9d$71b4e960$e96190cf@hp.harry.com>; from Harry Patterson on Tue, Mar 10, 1998 at 10:26:13PM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Mar 10, 1998 at 10:26:13PM -0500, Harry Patterson wrote: > I am still having problems getting my Seagate Tapestor (4 gig native) to be > accesible after boot. I have been using an Adaptec 1505 but have also used a > 1510 + 1520 with the same results. When the system boots it > probes with the following result: > > aic0 at 0x340-0x35f irq 11 on isa > aic0 waiting for scsi devices to settle > (aic0:2:0): "CONNER CTT8000-S 1.22" type 1 removable SCSI 2 > st0(aic0:2:0): Sequential-Access density code 0x45, 512-byte blocks, > write-enabled > > After boot I can't even get the light on the drive to light, let alone > rewind or dump. > > Does anyone have any ideas on getting FreeBSD to work with this drive? I've > put it in a Windows95 machine and it works fine as is (no jumper changes). > > Thanks for any help > > Harry > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message Mine works fine. Probes as:. The light only comes on when tape is winding. Put a tape in and reboot, you should see tape movement at probe time, if not, there is a problem. I'm using a 2940, not a 1505 (?). Have you got anything to run on the 1505? Also mine's external which makes it easy to fiddle with :) Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 11 10:22:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24778 for freebsd-scsi-outgoing; Wed, 11 Mar 1998 10:22:00 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sun.zipperup.org (root@sun.zipperup.org [142.154.6.148]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24769 for ; Wed, 11 Mar 1998 10:21:56 -0800 (PST) (envelope-from josh@sun.zipperup.org) Received: (from josh@localhost) by sun.zipperup.org (8.8.7/8.8.7) id NAA28887; Wed, 11 Mar 1998 13:21:48 -0500 (EST) Message-ID: <19980311132147.52937@sun.zipperup.org> Date: Wed, 11 Mar 1998 13:21:47 -0500 From: Josh Tiefenbach To: scsi@FreeBSD.ORG Cc: gibbs@narnia.plutotech.com Subject: Re: CAM Testimonials Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I havent been able to get the latest CAM snap to work on my machine. Specs: -current kernel ca 3/10/98, userland bits from ~ 1/27/98. Asus SC200 (53c810 based card) Micropolis Stinger 4gig HD (MICROP 4743 S150) SCSI CD-ROM (MATSHITA CD-ROM CR-506 8S05) The symptoms: Kernel boots up to the point where the CAM code would start scanning the bus. At this point, I get the following messages: Mar 10 23:12:00 asherah /kernel: ncr0: SCSI phase error fixup: CCB already dequeued (0xf085ac00) Mar 10 23:12:00 asherah /kernel: ncr0: timeout nccb=f085a800 (skip) Mar 10 23:12:00 asherah /kernel: ncr0: timeout nccb=f085c800 (skip) Followed by a lot more ncr timeouts. I've left it for ~5 minutes, with no change. Interestingly enough, when I boot with a `normal' kernel I get: sd0 at scbus0 target 0 lun 0 sd0: Direct-Access sd0: 10.0 MB/s (100 ns, offset 8) sd0: M_DISCONNECT received, but datapointer not saved: data=1e1b4 save=3226b0 goal=3226d4. I also get the odd Mar 10 13:24:24 asherah /kernel: ncr0: timeout ccb=f07c3400 (skip) >From time to time with the old code. I'm currently away from the machine right now, but if you want me to try any diagnostics, I can do it when I get home. josh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 11 11:33:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15902 for freebsd-scsi-outgoing; Wed, 11 Mar 1998 11:33:57 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA15872 for ; Wed, 11 Mar 1998 11:33:54 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id MAA27919; Wed, 11 Mar 1998 12:33:28 -0700 (MST) Message-Id: <199803111933.MAA27919@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: Josh Tiefenbach cc: scsi@FreeBSD.ORG, gibbs@plutotech.com Subject: Re: CAM Testimonials In-reply-to: Your message of "Wed, 11 Mar 1998 13:21:47 EST." <19980311132147.52937@sun.zipperup.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 11 Mar 1998 12:30:19 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I havent been able to get the latest CAM snap to work on my machine. > >Specs: > >-current kernel ca 3/10/98, userland bits from ~ 1/27/98. >Asus SC200 (53c810 based card) >Micropolis Stinger 4gig HD (MICROP 4743 S150) >SCSI CD-ROM (MATSHITA CD-ROM CR-506 8S05) Ah yes. An 810 controller. I know of this problem, but have no 810 to play with. I'll try to get my hands on one, but until I do, I'll work with Stefan to see if this can be resolved. >josh -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 11 15:14:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05062 for freebsd-scsi-outgoing; Wed, 11 Mar 1998 15:14:07 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from artorius.sunflower.com (artorius.sunflower.com [24.124.0.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04999; Wed, 11 Mar 1998 15:13:52 -0800 (PST) (envelope-from bsd-curr@artorius.sunflower.com) Received: from artorius.sunflower.com (artorius.sunflower.com [24.124.0.6]) by artorius.sunflower.com (8.8.8/8.8.7) with SMTP id RAA04553; Wed, 11 Mar 1998 17:12:56 -0600 (CST) (envelope-from bsd-curr@artorius.sunflower.com) Date: Wed, 11 Mar 1998 17:12:55 -0600 (CST) From: "Stephen D. Spencer" To: "Justin T. Gibbs" cc: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: CAM testimonials? In-Reply-To: <199803111803.LAA22230@pluto.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 11 Mar 1998, Justin T. Gibbs wrote: > > I haven't gotten much feedback on the latest CAM snapshot. If you are > running CAM, I'd appreciate a small note listing your configuration along > with any other comments you have. > rev 0x00 int a irq 11 on pci0.11.0 da3: Fixed Direct Access SCSI2 device da2: Fixed Direct Access SCSI2 device da1: Fixed Direct Access SCSI2 device da0: Fixed Direct Access SCSI2 device cd0: Removable CD-ROM SCSI2 device motherboard is an Asus TX w/ 64 Mb SDRAM DIMM, AMD-200MMX, 4Mb s3/virge, gus-pnp, blah blah blah... Um... it flies? ;) No problems whatsoever. As with the last snapshot, performance improvements are extremely noticable. I will be borrowing an HP DAT to test on that system in a couple days. Thanks for the fantastic work! Regards, Stephen --------------------------------------------------------------------- - Stephen Spencer finger gladiatr@artorius.sunflower.com for - - administrator PGP key. - - Sunflower Datavision http://www.sunflower.com - --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 11 15:29:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08231 for freebsd-scsi-outgoing; Wed, 11 Mar 1998 15:29:44 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08092; Wed, 11 Mar 1998 15:28:42 -0800 (PST) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE (8.8.7/8.8.7) with ESMTP id AAA11956; Thu, 12 Mar 1998 00:28:34 +0100 (MET) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id XAA02680; Wed, 11 Mar 1998 23:47:30 +0100 (CET) X-Face: " Date: Wed, 11 Mar 1998 23:47:30 +0100 From: Stefan Esser To: Josh Tiefenbach , scsi@FreeBSD.ORG Cc: gibbs@narnia.plutotech.com, Stefan Esser Subject: Re: CAM Testimonials References: <19980311132147.52937@sun.zipperup.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980311132147.52937@sun.zipperup.org>; from Josh Tiefenbach on Wed, Mar 11, 1998 at 01:21:47PM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1998-03-11 13:21 -0500, Josh Tiefenbach wrote: > I havent been able to get the latest CAM snap to work on my machine. > > Specs: > > -current kernel ca 3/10/98, userland bits from ~ 1/27/98. > Asus SC200 (53c810 based card) > Micropolis Stinger 4gig HD (MICROP 4743 S150) > SCSI CD-ROM (MATSHITA CD-ROM CR-506 8S05) > > The symptoms: > > Kernel boots up to the point where the CAM code would start scanning the bus. > At this point, I get the following messages: > > Mar 10 23:12:00 asherah /kernel: ncr0: SCSI phase error fixup: CCB already > dequeued (0xf085ac00) > Mar 10 23:12:00 asherah /kernel: ncr0: timeout nccb=f085a800 (skip) > Mar 10 23:12:00 asherah /kernel: ncr0: timeout nccb=f085c800 (skip) > > Followed by a lot more ncr timeouts. I've left it for ~5 minutes, with no > change. Can't really tell what's wrong. Are these the only SCSI and NCR messages ? > Interestingly enough, when I boot with a `normal' kernel I get: > > sd0 at scbus0 target 0 lun 0 > sd0: Direct-Access > sd0: 10.0 MB/s (100 ns, offset 8) > > sd0: M_DISCONNECT received, but datapointer not saved: > data=1e1b4 save=3226b0 goal=3226d4. This is most likely caused by the drive sending back less than 36 bytes as response to an INQUIRE command. > I also get the odd > > Mar 10 13:24:24 asherah /kernel: ncr0: timeout ccb=f07c3400 (skip) > > >From time to time with the old code. Shouldn't happen, but this message is not sufficient to tell what's wrong. > I'm currently away from the machine right now, but if you want me to try any > diagnostics, I can do it when I get home. It would be interesting to know, which SCSI command fails. I guess, that the NCR driver does not correctly interoperate with the CAM layer, if a short read (less than 36 bytes) has occured. I'll try building a kernel with the latest CAM code and will let you know, what I find. Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 11 15:29:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08264 for freebsd-scsi-outgoing; Wed, 11 Mar 1998 15:29:52 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08101; Wed, 11 Mar 1998 15:28:49 -0800 (PST) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE (8.8.7/8.8.7) with ESMTP id AAA11962; Thu, 12 Mar 1998 00:28:46 +0100 (MET) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id XAA02667; Wed, 11 Mar 1998 23:41:07 +0100 (CET) X-Face: " Date: Wed, 11 Mar 1998 23:41:06 +0100 From: Stefan Esser To: "Justin T. Gibbs" , Josh Tiefenbach Cc: scsi@FreeBSD.ORG, Stefan Esser Subject: Re: CAM Testimonials References: <19980311132147.52937@sun.zipperup.org> <199803111933.MAA27919@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199803111933.MAA27919@pluto.plutotech.com>; from Justin T. Gibbs on Wed, Mar 11, 1998 at 12:30:19PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1998-03-11 12:30 -0700, "Justin T. Gibbs" wrote: > >I havent been able to get the latest CAM snap to work on my machine. > > > >Specs: > > > >-current kernel ca 3/10/98, userland bits from ~ 1/27/98. > >Asus SC200 (53c810 based card) > >Micropolis Stinger 4gig HD (MICROP 4743 S150) > >SCSI CD-ROM (MATSHITA CD-ROM CR-506 8S05) > > Ah yes. An 810 controller. I know of this problem, but have no 810 > to play with. I'll try to get my hands on one, but until I do, I'll > work with Stefan to see if this can be resolved. I had trouble downloading the CAM patches, but finally got them via UUENCODED mail (direct FTP transfers from KDM.Org and FreeBSD.Org failed for some reason still unknown to me ...) Since I already had a previous version applied, and have other local modifications which might conflict with those patches, I'll need some spare time (possibly tomorrow night) to apply them and test the kernel. The last set of CAM patches worked for me, but the system started to freeze after minutes to hours of heavy use. But this may have been caused by the VM and VFS changes, that went into current at the same time ... I never was able to get a kernel dump, since the system just became non-responsive (incl. the keyboard LEDs !). My system (53c810 with Quantum Atlas, HP 1533 DAT, Toshiba CD-ROM and a 53c875 with an IBM DORS) was probed correctly (I did not try to actually use the tape or CD-ROM drives) and worked just fine until lockup ... Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 11 15:30:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08536 for freebsd-scsi-outgoing; Wed, 11 Mar 1998 15:30:30 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ziplink.net (relay-0.ziplink.net [206.15.168.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08434 for ; Wed, 11 Mar 1998 15:30:12 -0800 (PST) (envelope-from mi@xxx.video-collage.com) Received: from xxx.video-collage.com (xxx.video-collage.com [199.232.254.68]) by ziplink.net (8.8.7/8.8.7) with ESMTP id SAA03945 for ; Wed, 11 Mar 1998 18:30:07 -0500 (EST) Received: (from mi@localhost) by xxx.video-collage.com (8.8.8/8.8.7) id SAA18515; Wed, 11 Mar 1998 18:28:37 -0500 (EST) (envelope-from mi) From: Mikhail Teterin Message-Id: <199803112328.SAA18515@xxx.video-collage.com> Subject: seeking advise on FS tuning To: freebsd-scsi@FreeBSD.ORG Date: Wed, 11 Mar 1998 18:28:37 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"