From owner-freebsd-scsi@FreeBSD.ORG Sun Jun 13 09:32:49 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D22816A4CE; Sun, 13 Jun 2004 09:32:49 +0000 (GMT) Received: from kollerie.com (148-198.bbned.dsl.internl.net [217.149.198.148]) by mx1.FreeBSD.org (Postfix) with ESMTP id F261443D46; Sun, 13 Jun 2004 09:32:48 +0000 (GMT) (envelope-from gkoller@kollerie.com) Received: by kollerie.com (Postfix, from userid 1001) id AA45D2F8FE; Sun, 13 Jun 2004 11:32:03 +0200 (CEST) Date: Sun, 13 Jun 2004 11:32:03 +0200 From: Guido Kollerie To: "Simon L. Nielsen" Message-ID: <20040613093203.GA621@kollerie.com> References: <20040604085316.GA77766@kollerie.com> <20040609211940.GA829@zaphod.nitro.dk> <20040610065133.GA14542@kollerie.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PEIAKu/WMn1b1Hv9" Content-Disposition: inline In-Reply-To: <20040610065133.GA14542@kollerie.com> User-Agent: Mutt/1.5.6i cc: freebsd-scsi@freebsd.org Subject: Re: raidutil: Engine connect failed: Open X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jun 2004 09:32:49 -0000 --PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 10, 2004 at 08:51:33AM +0200, Guido Kollerie wrote: Simon, > > Check if you are running out of SysV shared memory... I have to stop > > PostgreSQL to run raidutil, since I haven't gotten around to bumping > > SysV memory in my kernel. >=20 > That did the trick. I happened to have installed PostgreSQL > recently but never made the link with raidutil failing. Stopping > PostgreSQL allows raidutil to run without any problems! Thank > you very much! And indeed, while upgrading to FreeBSD 4.10, I configured SysV shared memory according to: http://developer.postgresql.org/docs/postgres/kernel-resources.html which boils down to adding the following options or modify them in the kernel config to: options SYSVSHM options SHMMAXPGS=3D4096 options SHMSEG=3D256 options SYSVSEM options SEMMNI=3D256 options SEMMNS=3D512 options SEMMNU=3D256 options SEMMAP=3D256 Now I can run PostgreSQL and raidutil simultaneously. --=20 Guido --PEIAKu/WMn1b1Hv9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iEYEARECAAYFAkDMHxMACgkQC7vo05+GQSy73QCeLsEpir+NY504GqMveITaslXP nEsAnR5tB/cqABL4/C3UV7l8sqrqvAL+ =F0Gv -----END PGP SIGNATURE----- --PEIAKu/WMn1b1Hv9-- From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 15 06:24:34 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0778916A4EA for ; Tue, 15 Jun 2004 06:24:34 +0000 (GMT) Received: from usti.fccps.cz (usti.fccps.cz [194.108.74.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DD9443D46 for ; Tue, 15 Jun 2004 06:24:33 +0000 (GMT) (envelope-from Frantisek.Rysanek@post.cz) Received: from localhost (localhost [127.0.0.1]) by usti.fccps.cz (Postfix) with ESMTP id 3170E77C7D for ; Tue, 15 Jun 2004 08:24:23 +0200 (CEST) Received: from usti.fccps.cz ([127.0.0.1]) by localhost (usti [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16546-07 for ; Tue, 15 Jun 2004 08:24:21 +0200 (CEST) Received: from frr (unknown [10.0.0.238]) by usti.fccps.cz (Postfix) with ESMTP id 46FA877C7C for ; Tue, 15 Jun 2004 08:24:21 +0200 (CEST) From: "Frantisek Rysanek" To: freebsd-scsi@freebsd.org Date: Tue, 15 Jun 2004 08:26:07 +0200 MIME-Version: 1.0 Message-ID: <40CEB29F.29798.57E9A55@localhost> Priority: normal X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Virus-Scanned: by amavisd-new at fccps.cz Subject: Re: how to limit SCSI TCQ depth in FreeBSD? (SUMMARY) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jun 2004 06:24:34 -0000 Dear gentlemen, many thanks for everyone's responses - all of them helpful, all of them to the point. Let me reiterate a short summary of the responses: 1) "it's the firmware that is broken, try to get an update" -- exactly what I've tried in the first place. In the meantime, I've obtained a newer FW version from the manufacturer, and I'll try to flash it today. I did not disclose the name of the device deliberately, before I give an opportunity to the manufacturer's tech support. 2) "use `camcontrol tags da0 -N `" -- works like a charm. This is what I was looking for. Someone else has pointed out that this should be hooked up early into the rc scripts, before fsck starts up. That is, if the volume is mounted and auto-fsck'ed on startup - see /etc/fstab. 3) "try adding an entry to the xpt_quirk_table in sys/cam/cam_xpt.c for your disk" -- a good idea, didn't have the time to test it yet, I'm pretty sure it would work, though. If the firmware update doesn't help, this could be a proper long-term workaround. 4) "try this patch to aic79xx_osm.c" http://lists.freebsd.org/pipermail/freebsd-scsi/2003- August/000443.html -- I'm pretty sure this would work too. Didn't have the time to try it out, though. IMHO this solution is not as formally clean as adding an entry into the quirks table. To sum up, I have obtained several ways to work around my problem :) The one involving camcontrol is good enough for me. I understand that the OS-based workarounds won't help me to install FreeBSD on the faulty drive from the original installation media, but I guess I could manage that somehow "out of band" - and it's not my goal in the first place, the flawed drive is not my boot drive. With respect to booting off the culprit drive, it's my drive that is flawed, not FreeBSD. While I was testing the drive with Bonnie in Linux and FreeBSD, I got familiar with some aspects of the FreeBSD SCSI/CAM (compared to Linux) and I have to say I am impressed by FreeBSD's performance. Thanks for your care :-) Frank Rysanek From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 15 14:12:42 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 374A716A4CE; Tue, 15 Jun 2004 14:12:42 +0000 (GMT) Received: from out-mx1.crosswinds.net (out-mx1.crosswinds.net [216.18.117.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF8EE43D5C; Tue, 15 Jun 2004 14:12:41 +0000 (GMT) (envelope-from tony@crosswinds.net) Received: from admin.crosswinds.net (out-mx1.crosswinds.net [216.18.117.38]) by out-mx1.crosswinds.net (Postfix) with ESMTP id 8A15C2BA66; Tue, 15 Jun 2004 10:12:33 -0400 (EDT) Received: by admin.crosswinds.net (Postfix, from userid 1001) id 544C53F0B; Tue, 15 Jun 2004 10:12:33 -0400 (EDT) Date: Tue, 15 Jun 2004 10:12:33 -0400 From: Tony Holmes To: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org Message-ID: <20040615141233.GA41523@crosswinds.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: SCSI Probe Problem X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jun 2004 14:12:42 -0000 Hi! I have a server running 4.9-STABLE that I updated to 4.10 so that I could use a Promise TX-S150 to mirror a pair of SATA disks (seagate). The system currently has 4 SCSI drives on an Adaptec 19160 working flawlessly in them. Prior to the upgrade, the Promise controller and disks were installed, the disks configured in the promise controller and all was fine, except the kernel didn't recognize it, hence the reboot. Initially, I attempted an upgrade to a later 4.9-STABLE and on Friday, to 4.10-RELEASE. In both cases, the boot sequence hung at the SCSI reset (waiting for 15 sec) on the newer kernels. The new kernels were GENERIC with HZ set to 2000 and quotas turned on. Due to the fact that it is a production system, I could not debug further and reverted to the older kernel (with the new world) and it's running fine. Has anyone else experienced this? I noticed no details of any issues with the ahc driver or other issues in the UPDATING, so this perplexes me a litte. I assume that to aid I will have to eventually go in, install the new kernel and boot -v with a paste, but need to do it in the wee hours and warn my customers. -- Tony Holmes Founder and Senior Systems Architect Crosswinds Internet Communications Inc. From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 15 15:24:49 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F72716A4CE for ; Tue, 15 Jun 2004 15:24:49 +0000 (GMT) Received: from ida.interface-business.de (ida.interface-business.de [193.101.57.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33D7443D1D for ; Tue, 15 Jun 2004 15:24:49 +0000 (GMT) (envelope-from j@ida.interface-business.de) Received: by ida.interface-business.de (Postfix, from userid 107) id 257F27AC9; Tue, 15 Jun 2004 17:24:47 +0200 (MET DST) Date: Tue, 15 Jun 2004 17:24:47 +0200 From: Joerg Wunsch To: freebsd-scsi@freebsd.org Message-ID: <20040615172447.D47727@ida.interface-business.de> Mail-Followup-To: freebsd-scsi@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Phone: +49-351-31809-14 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Organization: interface systems GmbH, Dresden Subject: Drive statistics broken after replacing a drive? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joerg Wunsch List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jun 2004 15:24:49 -0000 I've got a Sun machine here where I've setup a vinum RAID-5 volume for /usr/ports, mainly in order to play a bit with the RAID-5 feature where I've never had an occasion before. So in order to get a feeling for what needs to be done to replace a failed drive of a RAID-5 plex, I started a "cvs update" on that /usr/ports directory, in order to get some heavy disk traffic. Then, I pulled one of the drives. The kernel properly announces the drive failure, vinum degrades the RAID-5 plex, the "cvs update" is continuing normally (not unexpectedly ;-). I then replaced the drive by another one, labelled it, and restarted the appropriate vinum structures in order to re-synchronize the RAID group. All worked out pretty well, the RAID-5 plex is up & running again -- but "iostat" no longer updates any statistics for that drive. While all the remaining disks participating in that RAID group display heavy traffic in iostat, and all the drive LEDs flicker as well, the disk's statistics for the new-born drive keep solid at 0: # iostat -d -w1 da3 da4 da5 da6 da3 da4 da5 da6 KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s 19.38 1 0.01 19.35 1 0.01 19.29 1 0.01 6.17 0 0.00 2.00 4 0.01 2.00 16 0.03 2.00 14 0.03 0.00 0 0.00 2.00 23 0.04 2.00 3 0.01 2.00 21 0.04 0.00 0 0.00 ^C (The first line is the accumulated statistics, it never changes again for da6.) -- J"org Wunsch Unix support engineer joerg_wunsch@interface-systems.de http://www.interface-systems.de/~j/ From owner-freebsd-scsi@FreeBSD.ORG Tue Jun 15 19:45:54 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2F3016A4CE for ; Tue, 15 Jun 2004 19:45:53 +0000 (GMT) Received: from elvis.bardenent.com (elvis.bardenent.com [216.90.241.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8098B43D49 for ; Tue, 15 Jun 2004 19:45:53 +0000 (GMT) (envelope-from meb@bardenent.com) Received: from meb (meb.bardenent.com [216.90.241.123]) by elvis.bardenent.com (8.12.9p2/8.12.9) with ESMTP id i5FJjBZQ081445 for ; Tue, 15 Jun 2004 15:45:11 -0400 (EDT) (envelope-from meb@bardenent.com) Message-Id: <200406151945.i5FJjBZQ081445@elvis.bardenent.com> From: "Matthew Bertrand" To: Date: Tue, 15 Jun 2004 15:45:11 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2096 Thread-Index: AcRTEUVkA72GgSncRES0Iw55HuRUIw== Subject: SCSI Tape problem after full write X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jun 2004 19:45:54 -0000 I am trying to use a Dell PV-122T LTO autoloader on FreeBSD 4.10-RELEASE, but am having some difficulties with it after writing a full tape. The tape drive is recognized properly and device entries are created. Here's the relevant information from my dmesg: sa0 at asr0 bus 0 target 6 lun 0 sa0: Removable Sequential Access SCSI-3 device ch0 at asr0 bus 0 target 5 lun 0 ch0: Removable Changer SCSI-2 device ch0: 8 slots, 1 drive, 1 picker, 0 portals (this is prior to having ch loaded into the kernel -- just trying to get the tape drive to work for right now) I'm attempting to use syutils/bacula to perform network backups, so following the instructions in the port, I used tapetest to write a full tape to verify I wouldn't lose any data after filling a tape. It took 2 hours and 11 minutes to fill up the 100GB tape, and it provided me this output: crazyeddie# c++ -g -O2 -Wall -pthread -c tapetest.c crazyeddie# c++ -g -O2 -Wall -pthread tapetest.o -o tapetest crazyeddie# ./tapetest /dev/nsa0 *rewind Rewound /dev/nsa0 *rawfill Begin writing blocks of 64512 bytes. +++++++ [...] weof_dev ioctl MTWEOF error on /dev/nsa0. ERR=Device not configured. Bad status from weof -1. ERR=Device not configured Write failed. Last block written=1656999. stat=-1 ERR=Input/output error *rewind Rewind error on /dev/nsa0. ERR=Device not configured. Bad status from rewind. ERR=Device not configured * After exiting out of that, it I would get the same Device not configured error trying anything else (mt, tar). Ran the following commands to try and get the tape drive back online: crazyeddie# camcontrol devlist at scbus0 target 1 lun 0 (pass0,da0) at scbus0 target 5 lun 0 (pass1) at scbus0 target 6 lun 0 (pass2,sa0) crazyeddie# camcontrol tur sa0 -v Unit is not ready CAM status is 0xa crazyeddie# camcontrol reset 0:6:0 Reset of 0:6:0 was successful crazyeddie# camcontrol devlist at scbus0 target 1 lun 0 (pass0,da0) at scbus0 target 5 lun 0 (pass1) crazyeddie# After that, the only way I could get the tape drive recognized again was to power cycle the autoloader and then restart FreeBSD. I've enabled CAMDEBUG in the kernel ( which is generic other than CAMDEBUG & ch), but the output from that doesn't seem to provide me with anything useful (I don't know what to look for). Does anyone have any suggestions for this problem or any tips on troubleshooting it further? Thanks, -Matthew Bertrand From owner-freebsd-scsi@FreeBSD.ORG Thu Jun 17 18:12:00 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3226B16A4CE; Thu, 17 Jun 2004 18:12:00 +0000 (GMT) Received: from shadow.wixb.com (shadow.wixb.com [65.43.82.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73DB843D41; Thu, 17 Jun 2004 18:11:59 +0000 (GMT) (envelope-from jbronson@wixb.com) Received: from dakota.wixb.com (shadow.wixb.com [10.43.82.173]) i5HIBe0S027451; Thu, 17 Jun 2004 13:11:40 -0500 (CDT) Organization: Aurora Health Care, Milwaukee WI USA Message-Id: <6.1.1.1.2.20040617130118.06dcd300@localhost> Date: Thu, 17 Jun 2004 13:12:01 -0500 To: freebsd-questions@freebsd.org From: "J.D. Bronson" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Miltered: at shadow.wixb.com with ID 40D1DEDC.000 by j-chkmail cc: freebsd-scsi@freebsd.org Subject: Adaptec 29160 Scsi card / camcontrol rescan X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jun 2004 18:12:00 -0000 I have a machine running 5.2.1 with DUAL Adaptec 29160LP scsi cards. In the machine there are 2 U160 LVD scsi drives...one attached to each drive... I have an external SE tape drive that I have a cable for that I can attach to the 'extra' 29160 card port. If I hook it up to the card and then boot the machine, it is detected and runs fine :) If I forget, I hook it up later and then run 'camcontrol rescan all' and the tape drive is immediately picked up and works fine :) My question is, since I start out w/o the tape drive connected, I am running LVD with u160 speeds. Then I hook up the tape drive (run the command) and then want to disconnect the tape drive. I know the bus will slow down with the tape drive attached, but will it come back to normal speeds once I remove the tape drive? - and/or do I have to run the camcontrol command again? Thanks in advance!! -- J.D. Bronson Aurora Health Care // Information Services // Milwaukee, WI USA Office: 414.978.8282 // Email: jd@aurora.org // Pager: 414.314.8282 From owner-freebsd-scsi@FreeBSD.ORG Thu Jun 17 18:19:12 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E14C516A4CE; Thu, 17 Jun 2004 18:19:12 +0000 (GMT) Received: from sift.mirapoint.com (sift.mirapoint.com [63.107.133.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAD3E43D5F; Thu, 17 Jun 2004 18:19:12 +0000 (GMT) (envelope-from cer@mirapoint.com) Received: from mirapoint.com (adsl-64-163-214-116.dsl.snfc21.pacbell.net [64.163.214.116]) by sift.mirapoint.com (MOS 3.4.6-GR) with ESMTP id AVC02233 (AUTH cer); Thu, 17 Jun 2004 11:19:01 -0700 (PDT) Message-ID: <40D1E094.4010803@mirapoint.com> Date: Thu, 17 Jun 2004 11:19:00 -0700 From: Carl Reisinger User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6) Gecko/20040509 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "J.D. Bronson" References: <6.1.1.1.2.20040617130118.06dcd300@localhost> In-Reply-To: <6.1.1.1.2.20040617130118.06dcd300@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-scsi@freebsd.org cc: freebsd-questions@freebsd.org Subject: Re: Adaptec 29160 Scsi card / camcontrol rescan X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: cer@mirapoint.com List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jun 2004 18:19:13 -0000 J.D. Bronson wrote: > > I know the bus will slow down with the tape drive attached, but will it > come back to normal speeds once I remove the tape drive? - and/or do I > have to run the camcontrol command again? Run the rescan again. Just removing the device from the bus does not cause the kernel or the hba to perform any action. From owner-freebsd-scsi@FreeBSD.ORG Thu Jun 17 18:29:42 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9E5A16A4CE; Thu, 17 Jun 2004 18:29:42 +0000 (GMT) Received: from shadow.wixb.com (shadow.wixb.com [65.43.82.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E66943D4C; Thu, 17 Jun 2004 18:29:42 +0000 (GMT) (envelope-from jbronson@wixb.com) Received: from dakota.wixb.com (shadow.wixb.com [10.43.82.173]) i5HITCkX027458; Thu, 17 Jun 2004 13:29:12 -0500 (CDT) Organization: Aurora Health Care, Milwaukee WI USA Message-Id: <6.1.1.1.2.20040617132320.06d5ca68@localhost> Date: Thu, 17 Jun 2004 13:29:33 -0500 To: cer@mirapoint.com From: "J.D. Bronson" In-Reply-To: <40D1E094.4010803@mirapoint.com> References: <6.1.1.1.2.20040617130118.06dcd300@localhost> <40D1E094.4010803@mirapoint.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Miltered: at shadow.wixb.com with ID 40D1E2F8.000 by j-chkmail cc: freebsd-scsi@freebsd.org cc: freebsd-questions@freebsd.org Subject: Re: Adaptec 29160 Scsi card / camcontrol rescan X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jun 2004 18:29:43 -0000 At 01:19 PM 06/17/2004, Carl Reisinger wrote: >J.D. Bronson wrote: > >>I know the bus will slow down with the tape drive attached, but will it >>come back to normal speeds once I remove the tape drive? - and/or do I >>have to run the camcontrol command again? > >Run the rescan again. > >Just removing the device from the bus does not cause the kernel or the hba >to perform any action. > Please excuse my ignorance here.... Once I disconnect my tape drive and run camcontrol rescan all, I should expect the bus speed to once again return to 160? thanks! -- J.D. Bronson Aurora Health Care // Information Services // Milwaukee, WI USA Office: 414.978.8282 // Email: jd@aurora.org // Pager: 414.314.8282 From owner-freebsd-scsi@FreeBSD.ORG Thu Jun 17 19:32:45 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24BD916A4CE for ; Thu, 17 Jun 2004 19:32:45 +0000 (GMT) Received: from vader.aacc.edu (vader.aacc.edu [12.167.138.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDB5043D1D for ; Thu, 17 Jun 2004 19:32:44 +0000 (GMT) (envelope-from fox@vader.aacc.edu) Received: from vader.aacc.edu (IDENT:r0QBb+BW85pPO7u0mypEqti/0HhQ8PhI@localhost [127.0.0.1]) by vader.aacc.edu (8.12.8/8.12.8) with ESMTP id i5HJWKuU021062 for ; Thu, 17 Jun 2004 15:32:25 -0400 Received: from localhost (fox@localhost) by vader.aacc.edu (8.12.8/8.12.8/Submit) with ESMTP id i5HJWEw1021058 for ; Thu, 17 Jun 2004 15:32:19 -0400 Date: Thu, 17 Jun 2004 15:32:14 -0400 (EDT) From: fox@vader.aacc.edu To: freebsd-scsi@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: -stable vs -current handling of SSD_KEY_MISCOMPARE SCSI sense data X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jun 2004 19:32:45 -0000 While trying to diagnose an unrelated hardware problem, I stumbled on the following code in RELENG_4 sys/cam/scsi/scsi_all.c (1.14.2.11): scsi_interpret_sense(...) { ... switch (error_code) { ... case SSD_CURRENT_ERROR: { switch (sense_key) { ... case SSD_KEY_MISCOMPARE: /* decrement the number of retries */ retry = ccb->ccb_h.retry_count > 0; if (retry) { error = ERESTART; ccb->ccb_h.retry_count--; } else { error = EIO; } case SSD_KEY_RECOVERED_ERROR: error = 0; /* not an error */ break; The lack of a break before "case SSD_KEY_RECOVERED_ERROR:" means that all assignments to error in case "SSD_KEY_MISCOMPARE:" are expensive comments, so I doubt that a /* FALLTHROUGH */ was intended. Also, this code was added as part of 1.18, then MFC'd in 1.14.2.3, so it was most likely deliberate. However, -current seems to ignore this error. sys/cam/scsi/scsi_all.c 1.44 has: const struct sense_key_table_entry sense_key_table[] = { ... { SSD_KEY_MISCOMPARE, SS_NOP, "MISCOMPARE" }, If I read the code in sys/cam/cam_periph.c correctly, this matches what -stable does, but should have s/SS_NOP/SS_RDEF/ to match what I suspect -stable was meant to do. OTOH, if -stable is really meant to do nothing in that case, perhaps it could do so in a more straightforward way, or have a comment added. OTGH, I may be missing something obvious. Perusal of cvs-all and freebsd-scsi archives from around the time scsi_all.c 1.21 was commited failed to elicit obvious clues. I eagerly await clue imparting, sarcasm, flamage, or LARTing. -- "I'd ask if you'd found the right sort of isolated wasteland for your citadel of dread yet, but that would be a silly question; you're in Utah, after all." --ESR to Darl McBride (Chief Excessive Ossifier of Squandered Clues Obstination), in http://www.catb.org/~esr/writings/mcbride.html From owner-freebsd-scsi@FreeBSD.ORG Fri Jun 18 01:06:27 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D1E616A4CE for ; Fri, 18 Jun 2004 01:06:27 +0000 (GMT) Received: from cmsrelay02.mx.net (cmsrelay02.mx.net [165.212.11.111]) by mx1.FreeBSD.org (Postfix) with SMTP id 2BE5043D39 for ; Fri, 18 Jun 2004 01:06:27 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: from uadvg129.cms.usa.net (165.212.11.129) by cmsoutbound.mx.net with SMTP; 18 Jun 2004 01:05:55 -0000 Received: from optimator.noacks.org [70.240.231.39] by uadvg129.cms.usa.net (ASMTP/noackjr@usa.net) via mtad (C8.MAIN.3.13N) with ESMTP id 761iFRBF10183M29; Fri, 18 Jun 2004 01:05:52 GMT X-USANET-Auth: 70.240.231.39 AUTH noackjr@usa.net optimator.noacks.org Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 8B8516166 for ; Thu, 17 Jun 2004 20:05:51 -0500 (CDT) Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 00649-03 for ; Thu, 17 Jun 2004 20:05:49 -0500 (CDT) Received: from compgeek.noacks.org (compgeek [192.168.1.10]) by optimator.noacks.org (Postfix) with ESMTP id A336A6140 for ; Thu, 17 Jun 2004 20:05:49 -0500 (CDT) Received: from [127.0.0.1] (localhost.noacks.org [127.0.0.1]) by compgeek.noacks.org (8.12.11/8.12.11) with ESMTP id i5I15m66001182 for ; Thu, 17 Jun 2004 20:05:48 -0500 (CDT) (envelope-from noackjr@alumni.rice.edu) Message-ID: <40D23FEC.9070409@alumni.rice.edu> Date: Thu, 17 Jun 2004 20:05:48 -0500 From: Jon Noack User-Agent: Mozilla Thunderbird 0.6 (X11/20040531) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at noacks.org Subject: ida(4) status X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jun 2004 01:06:27 -0000 I recently obtained a Compaq 6400R with a Smart Array 431 controller. The machine has 4 Pentium 3 550MHz w/ 2MB L2 cache processors, 1GB of RAM, and 4 18GB 10K rpm hard drives. I was wondering what was the current status of the ida(4) driver. It doesn't appear to be MPSAFE based on the busdma page. I was basically given this machine and would like to use it to test FreeBSD SMP. In any case, just wondering what I'm facing here. Thanks, Jon Noack From owner-freebsd-scsi@FreeBSD.ORG Fri Jun 18 13:32:45 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81D5716A4CE for ; Fri, 18 Jun 2004 13:32:45 +0000 (GMT) Received: from out-mx1.crosswinds.net (out-mx1.crosswinds.net [216.18.117.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 353E043D2F for ; Fri, 18 Jun 2004 13:32:45 +0000 (GMT) (envelope-from tony@crosswinds.net) Received: from admin.crosswinds.net (out-mx1.crosswinds.net [216.18.117.38]) by out-mx1.crosswinds.net (Postfix) with ESMTP id 1CE0B2CBE8 for ; Fri, 18 Jun 2004 09:32:26 -0400 (EDT) Received: by admin.crosswinds.net (Postfix, from userid 1001) id 0734F3F0B; Fri, 18 Jun 2004 09:32:26 -0400 (EDT) Date: Fri, 18 Jun 2004 09:32:25 -0400 From: Tony Holmes To: freebsd-scsi@freebsd.org Message-ID: <20040618133225.GA38427@crosswinds.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: 4.9 vs 4.10 SCSI Probe X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jun 2004 13:32:45 -0000 Well I had a bit of a chance to do a bit more investigation on the production system. Basic Specs. Adaptec 19160 controller 4 Seagate Disks 36GB Promise FastTrack S150 TX2plus 2 Seagate SATA 120 GB disks Intel FXP nic AMD 2800XP cpu Asus A7N-8X mobo 1GB Kingston ram Booting 4.9Release has no issues, except that the Promise is not recognized. No problem, upgraded via cvsup to 4.10, make world and kernel (same kernel config). When I rebooted into 4.10, (with -v) the SCSI reset is sent and the system hangs, dead. No timeout ever recovers (waited up to 1 hour). Tried all variations of bios options, and PCI positions with no luck at all. Has anyone else encountered this problem or any other issues with 4.10 and SCSI? -- Tony Holmes Founder and Senior Systems Architect Crosswinds Internet Communications Inc. From owner-freebsd-scsi@FreeBSD.ORG Sat Jun 19 13:26:06 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8366216A4CE for ; Sat, 19 Jun 2004 13:26:06 +0000 (GMT) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 236FB43D48 for ; Sat, 19 Jun 2004 13:26:06 +0000 (GMT) (envelope-from mdodd@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.12.11/8.12.9) with ESMTP id i5JDPjD6021104; Sat, 19 Jun 2004 09:25:45 -0400 (EDT) (envelope-from mdodd@FreeBSD.ORG) Date: Sat, 19 Jun 2004 09:25:45 -0400 (EDT) From: "Matthew N. Dodd" X-X-Sender: winter@sasami.jurai.net To: Jon Noack In-Reply-To: <40D23FEC.9070409@alumni.rice.edu> Message-ID: <20040619092317.W57156@sasami.jurai.net> References: <40D23FEC.9070409@alumni.rice.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ida(4) status X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jun 2004 13:26:06 -0000 On Thu, 17 Jun 2004, Jon Noack wrote: > I recently obtained a Compaq 6400R with a Smart Array 431 controller. > The machine has 4 Pentium 3 550MHz w/ 2MB L2 cache processors, 1GB of > RAM, and 4 18GB 10K rpm hard drives. I was wondering what was the > current status of the ida(4) driver. It doesn't appear to be MPSAFE > based on the busdma page. I was basically given this machine and would > like to use it to test FreeBSD SMP. In any case, just wondering what > I'm facing here. Its not locked down but other than that should work fine. I've received hardware from HPQ to allow me to do further work on the driver but have not had a chance to spend time working on it. -- 10 40 80 C0 00 FF FF FF FF C0 00 00 00 00 10 AA AA 03 00 00 00 08 00