From owner-freebsd-scsi@FreeBSD.ORG Mon Dec 5 11:02:23 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 510E216A41F for ; Mon, 5 Dec 2005 11:02:23 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAD5743D78 for ; Mon, 5 Dec 2005 11:02:09 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jB5B28t2024022 for ; Mon, 5 Dec 2005 11:02:08 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jB5B28dB024015 for freebsd-scsi@freebsd.org; Mon, 5 Dec 2005 11:02:08 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 5 Dec 2005 11:02:08 GMT Message-Id: <200512051102.jB5B28dB024015@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 11:02:23 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/05/03] kern/27059 scsi [sym] SCSI subsystem hangs under heavy lo o [2001/06/29] kern/28508 scsi problems with backup to Tandberg SLR40 st o [2002/06/17] kern/39388 scsi ncr/sym drivers fail with 53c810 and more o [2002/07/22] kern/40895 scsi wierd kernel / device driver bug o [2003/05/24] kern/52638 scsi [panic] SCSI U320 on SMP server won't run s [2003/09/30] kern/57398 scsi [mly] Current fails to install on mly(4) o [2003/12/26] kern/60598 scsi wire down of scsi devices conflicts with o [2003/12/27] kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C81 s [2004/01/10] kern/61165 scsi [panic] kernel page fault after calling c o [2004/12/02] kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5 o [2005/06/04] kern/81887 scsi [aac] Adaptec SCSI 2130S aac0: GetDeviceP 11 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/12/06] kern/23314 scsi aic driver fails to detect Adaptec 1520B o [2001/08/15] kern/29727 scsi [amr] [patch] amr_enquiry3 structure in a o [2002/02/23] kern/35234 scsi World access to /dev/pass? (for scanner) o [2002/06/02] kern/38828 scsi [feature request] DPT PM2012B/90 doesn't o [2002/10/29] kern/44587 scsi dev/dpt/dpt.h is missing defines required o [2003/10/01] kern/57469 scsi [scsi] [patch] Quirk for Conner CP3500 o [2005/01/12] kern/76178 scsi [ahd] Problem with ahd and large SCSI Rai 7 problems total. From owner-freebsd-scsi@FreeBSD.ORG Tue Dec 6 07:21:44 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 968E216A41F for ; Tue, 6 Dec 2005 07:21:44 +0000 (GMT) (envelope-from brunomiguel@dequim.ist.utl.pt) Received: from gecea.ist.utl.pt (gecea.ist.utl.pt [193.136.140.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E81C43D6E for ; Tue, 6 Dec 2005 07:21:39 +0000 (GMT) (envelope-from brunomiguel@dequim.ist.utl.pt) Received: from [192.168.0.100] (c-66-30-11-146.hsd1.ma.comcast.net [66.30.11.146]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gecea.ist.utl.pt (Postfix) with ESMTP id 2BFC74102 for ; Tue, 6 Dec 2005 07:21:36 +0000 (WET) Message-ID: <43953BFD.6040409@dequim.ist.utl.pt> Date: Tue, 06 Dec 2005 02:21:33 -0500 From: Bruno Afonso User-Agent: Thunderbird 1.5 (Macintosh/20051025) MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: mpt driver problem? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 07:21:44 -0000 Hi, I have a box that's running a scsi card that uses the mpt driver. This is now running 6.0: Dec 6 07:14:04 ribossoma kernel: mpt0: port 0xc400-0xc4ff mem 0xfea90000-0xfea9ffff,0xfea80000-0xfea8ffff irq 19 at device 3.0 on Dec 6 07:14:04 ribossoma kernel: mpt0: [GIANT-LOCKED] Dec 6 07:14:04 ribossoma kernel: mpt0: MPI Version=1.2.6.0 Dec 6 07:14:04 ribossoma kernel: mpt0: Unhandled Event Notify Frame. Event 0xa. Dec 6 07:14:04 ribossoma kernel: mpt0: Capabilities: ( RAID-1 SAFTE ) Dec 6 07:14:04 ribossoma kernel: mpt0: 0 Active Volumes (1 Max) Dec 6 07:14:04 ribossoma kernel: mpt0: 0 Hidden Drive Members (3 Max) Dec 6 07:14:04 ribossoma kernel: mpt1: port 0xc800-0xc8ff mem 0xfeaf0000-0xfeafffff,0xfeae0000-0xfeaeffff irq 18 at device 3.1 on Dec 6 07:14:04 ribossoma kernel: mpt1: [GIANT-LOCKED] Dec 6 07:14:04 ribossoma kernel: mpt1: MPI Version=1.2.6.0 Dec 6 07:14:04 ribossoma kernel: mpt1: Unhandled Event Notify Frame. Event 0xa. Dec 6 07:14:04 ribossoma kernel: mpt1: Capabilities: ( RAID-1 SAFTE ) Dec 6 07:14:04 ribossoma kernel: mpt1: 0 Active Volumes (1 Max) Dec 6 07:14:04 ribossoma kernel: mpt1: 0 Hidden Drive Members (3 Max) Dec 6 07:14:04 ribossoma kernel: da0 at mpt0 bus 0 target 0 lun 0 Dec 6 07:14:04 ribossoma kernel: da0: Fixed Direct Access SCSI-3 device Dec 6 07:14:04 ribossoma kernel: da0: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled Dec 6 07:14:04 ribossoma kernel: da0: 35003MB (71687372 512 byte sectors: 255H 63S/T 4462C) The problem appears randomly on boots, meaning that it does not show indeed on EVERY boot, but afterwards, every so often. This is what typically appears: Dec 6 07:14:27 ribossoma kernel: mpt0: Request 0xc24755a8 Timed out. Dec 6 07:14:27 ribossoma kernel: mpt0: Attempting to Abort Req 0xc24755a8 Dec 6 07:14:28 ribossoma kernel: (da0:mpt0:0:0:0): READ(10). CDB: 28 0 0 f0 88 87 0 0 48 0 Dec 6 07:14:28 ribossoma kernel: (da0:mpt0:0:0:0): CAM Status: SCSI Status Error Dec 6 07:14:28 ribossoma kernel: (da0:mpt0:0:0:0): SCSI Status: Check Condition Dec 6 07:14:28 ribossoma kernel: (da0:mpt0:0:0:0): UNIT ATTENTION asc:29,2 Dec 6 07:14:28 ribossoma kernel: (da0:mpt0:0:0:0): Scsi bus reset occurred field replaceable unit: 2 Dec 6 07:14:28 ribossoma kernel: (da0:mpt0:0:0:0): Retrying Command (per Sense Data) Dec 6 07:14:28 ribossoma kernel: mpt0: Request 0xc2475508 Timed out. Dec 6 07:14:28 ribossoma kernel: mpt0: Attempting to Abort Req 0xc2475508 Dec 6 07:14:29 ribossoma kernel: (da0:mpt0:0:0:0): READ(10). CDB: 28 0 0 f0 84 a7 0 0 28 0 Dec 6 07:14:29 ribossoma kernel: (da0:mpt0:0:0:0): CAM Status: SCSI Status Error Dec 6 07:14:29 ribossoma kernel: (da0:mpt0:0:0:0): SCSI Status: Check Condition Dec 6 07:14:29 ribossoma kernel: (da0:mpt0:0:0:0): UNIT ATTENTION asc:29,2 Dec 6 07:14:29 ribossoma kernel: (da0:mpt0:0:0:0): Scsi bus reset occurred field replaceable unit: 2 Dec 6 07:14:29 ribossoma kernel: (da0:mpt0:0:0:0): Retrying Command (per Sense Data) Dec 6 07:14:30 ribossoma kernel: mpt0: Request 0xc24756c0 Timed out. Dec 6 07:14:30 ribossoma kernel: mpt0: Attempting to Abort Req 0xc24756c0 Dec 6 07:14:30 ribossoma kernel: (da0:mpt0:0:0:0): READ(10). CDB: 28 0 0 ec cb af 0 0 40 0 Dec 6 07:14:30 ribossoma kernel: (da0:mpt0:0:0:0): CAM Status: SCSI Status Error Dec 6 07:14:30 ribossoma kernel: (da0:mpt0:0:0:0): SCSI Status: Check Condition Dec 6 07:14:30 ribossoma kernel: (da0:mpt0:0:0:0): UNIT ATTENTION asc:29,2 Dec 6 07:14:30 ribossoma kernel: (da0:mpt0:0:0:0): Scsi bus reset occurred field replaceable unit: 2 Dec 6 07:14:30 ribossoma kernel: (da0:mpt0:0:0:0): Retrying Command (per Sense Data) I'd like to know if this is a serious problem with hardware or the driver itself. Should I worry? I know that some work is being done on mpt but I cannot use -current as this is a production box. I have used a -stable and it didn't improve so now I'm back to 6.0. I'll provide more information if needed. Thanks Bruno Afonso From owner-freebsd-scsi@FreeBSD.ORG Tue Dec 6 08:55:25 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 33AFF16A41F for ; Tue, 6 Dec 2005 08:55:25 +0000 (GMT) (envelope-from brunomiguel@dequim.ist.utl.pt) Received: from gecea.ist.utl.pt (gecea.ist.utl.pt [193.136.140.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC76743D53 for ; Tue, 6 Dec 2005 08:55:24 +0000 (GMT) (envelope-from brunomiguel@dequim.ist.utl.pt) Received: from [192.168.0.100] (c-66-30-11-146.hsd1.ma.comcast.net [66.30.11.146]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gecea.ist.utl.pt (Postfix) with ESMTP id 3009840B9 for ; Tue, 6 Dec 2005 08:55:22 +0000 (WET) Message-ID: <439551F8.6090505@dequim.ist.utl.pt> Date: Tue, 06 Dec 2005 03:55:21 -0500 From: Bruno Afonso User-Agent: Thunderbird 1.5 (Macintosh/20051025) MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: more on the mpt problem X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 08:55:25 -0000 Turns out the machine completely blocks: mpt0: Request 0xc2475378 Timed out. mpt0: Timedout requests already complete. Interrupts may not be functioning. BA From owner-freebsd-scsi@FreeBSD.ORG Wed Dec 7 23:57:22 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 2665916A41F for ; Wed, 7 Dec 2005 23:57:22 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id B075243D75 for ; Wed, 7 Dec 2005 23:57:11 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (unknown [200.46.204.144]) by hub.org (Postfix) with ESMTP id 6F43462C88E for ; Wed, 7 Dec 2005 19:57:10 -0400 (AST) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 28592-03 for ; Wed, 7 Dec 2005 19:57:10 -0400 (AST) Received: from ganymede.hub.org (blk-222-82-85.eastlink.ca [24.222.82.85]) by hub.org (Postfix) with ESMTP id DD67462C850 for ; Wed, 7 Dec 2005 19:57:09 -0400 (AST) Received: by ganymede.hub.org (Postfix, from userid 1000) id E45B13BC1A; Wed, 7 Dec 2005 19:57:12 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id E08523AEFC for ; Wed, 7 Dec 2005 19:57:12 -0400 (AST) Date: Wed, 7 Dec 2005 19:57:12 -0400 (AST) From: "Marc G. Fournier" To: freebsd-scsi@freebsd.org Message-ID: <20051207194635.V1480@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org Subject: ICP driver with FreeBSD 4.x ... X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 23:57:22 -0000 I've been trying to get icpcon available at http://www.vortex.de/english/download/rz_neu/freebsd/frbsd_e.htm to work on my 4.x-STABLE server ... after talking to the techs, I've been told that I have to install the driver available on that web page, since the one in 4.x is outdated ... And it very much is: diff -r /sys/dev/iir/iir.c iir/iir.c 3c3,5 < * Copyright (c) 2000-01 Intel Corporation --- > * Copyright (c) 2000-04 ICP vortex GmbH > * Copyright (c) 2002-04 Intel Corporation > * Copyright (c) 2003-04 Adaptec Inc. I realized that 4.x was ancient, just didn't realize that it was *that* ancient ... Can someone comment on the safety of upgrading that driver to the one that they have on their web site on a live server? Are there any ramifications, or risks, with doing this? According to their web site, it was tested on 4.9 ... Comments / Opinions? Thanks ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664 From owner-freebsd-scsi@FreeBSD.ORG Thu Dec 8 23:47:18 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 0F0DA16A41F for ; Thu, 8 Dec 2005 23:47:18 +0000 (GMT) (envelope-from consummately@garrote.com) Received: from 202-151-70-255.dsl.teleguam.net (202-151-70-255.dsl.teleguam.net [202.151.70.255]) by mx1.FreeBSD.org (Postfix) with SMTP id EABBC43D4C for ; Thu, 8 Dec 2005 23:47:07 +0000 (GMT) (envelope-from consummately@garrote.com) Received: from unknown (HELO Chatham) (192.168.160.53) by 202-151-70-255.dsl.teleguam.net with SMTP; Fri, 9 Dec 2005 09:51:57 +1000 Content-Transfer-Encoding: 7bit Message-Id: <11032164515.12744852706@202-151-70-255.dsl.teleguam.net> Content-Type: text/plain; charset=us-ascii To: freebsd-scsi@freebsd.org From: Julian Perez Date: Thu, 8 Dec 2005 23:47:07 +0000 (GMT) Subject: No more penis enlarge ripoffs! X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 23:47:18 -0000 Bro check out this awesome new product http://www.kurevalw.net/pt/ Back of every noble life there are principles that have fashioned it. Punctuality is the virtue of the bored. It is not the position, but the disposition. Nice guys finish last, but we get to sleep in. I'm going to memorize your name and throw my head away. From owner-freebsd-scsi@FreeBSD.ORG Thu Dec 8 23:47:27 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 1066516A41F for ; Thu, 8 Dec 2005 23:47:27 +0000 (GMT) (envelope-from infinite1@despammed.com) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E2ED43D53 for ; Thu, 8 Dec 2005 23:47:10 +0000 (GMT) (envelope-from infinite1@despammed.com) Received: from [127.0.0.1] (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id jB8NwDA2046995; Thu, 8 Dec 2005 18:58:13 -0500 (EST) (envelope-from infinite1@despammed.com) Message-ID: <4398C60A.4050904@despammed.com> Date: Thu, 08 Dec 2005 18:47:22 -0500 From: Amit Rao User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: danny@cs.huji.ac.il X-Virus-Scanned: ClamAV devel-20050919/1206/Thu Dec 8 14:56:45 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-scsi@freebsd.org Subject: iSCSI status X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 23:47:27 -0000 Hi Danny, I saw your name listed for iSCSI on the list of ongoing freebsd projects. What is the current status of this project? Thanks, amit --------------------------------- Implement iSCSI Technical contact: Danny Braniss Danny Braniss has been working on an iSCSI stack for FreeBSD for some time now. His work is in Perforce, and he has posted several patch sets and had numerous discussions on the mailing lists. Requirements: Ability to read and understand foreign C code. Ability to write C code. Knowledge about (i)SCSI/CAM. ----------------------------------- From owner-freebsd-scsi@FreeBSD.ORG Fri Dec 9 19:23:15 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 5025D16A41F for ; Fri, 9 Dec 2005 19:23:15 +0000 (GMT) (envelope-from bmiele@ipnstock.com) Received: from ms-smtp-04.nyroc.rr.com (ms-smtp-04.nyroc.rr.com [24.24.2.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C60643D60 for ; Fri, 9 Dec 2005 19:23:14 +0000 (GMT) (envelope-from bmiele@ipnstock.com) Received: from [10.0.0.152] (cpe-69-207-238-239.maine.res.rr.com [69.207.238.239]) by ms-smtp-04.nyroc.rr.com (8.12.10/8.12.10) with ESMTP id jB9JNB95000166 for ; Fri, 9 Dec 2005 14:23:12 -0500 (EST) Date: Fri, 9 Dec 2005 14:23:10 -0500 (EST) From: Brad Miele To: freebsd-scsi@freebsd.org Message-ID: <20051209141608.W3172@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: isp errors with QLogic 2312 / DL380 / MSA 1500 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 19:23:15 -0000 Hello, I have recently moved from individual HP MS30 SCSI shelves to the HP MSA 1500 SAN with two MS30 SCSI shelves and two MS20 SATA shelves. I am seeing the following in messages: Dec 9 13:42:16 bwayipn04 kernel: isp0: command timed out for 0.125.4 Dec 9 13:49:58 bwayipn04 last message repeated 4 times Dec 9 13:55:48 bwayipn04 last message repeated 2 times Dec 9 13:59:44 bwayipn04 kernel: (da3:isp0:0:125:4): READ(10). CDB: 28 0 6a 54 85 bf 0 0 80 0 Dec 9 13:59:44 bwayipn04 kernel: (da3:isp0:0:125:4): CAM Status: SCSI Status Error Dec 9 13:59:44 bwayipn04 kernel: (da3:isp0:0:125:4): SCSI Status: Check Condition Dec 9 13:59:44 bwayipn04 kernel: (da3:isp0:0:125:4): UNIT ATTENTION asc:29,0 Dec 9 13:59:44 bwayipn04 kernel: (da3:isp0:0:125:4): Power on, reset, or bus device reset occurred Dec 9 13:59:44 bwayipn04 kernel: (da3:isp0:0:125:4): Retrying Command (per Sense Data) Dec 9 13:59:45 bwayipn04 kernel: (da1:isp0:0:125:2): WRITE(10). CDB: 2a 0 88 7a 71 9f 0 0 20 0 Dec 9 13:59:45 bwayipn04 kernel: (da1:isp0:0:125:2): CAM Status: SCSI Status Error Dec 9 13:59:45 bwayipn04 kernel: (da1:isp0:0:125:2): SCSI Status: Check Condition Dec 9 13:59:45 bwayipn04 kernel: (da1:isp0:0:125:2): UNIT ATTENTION asc:29,0 Dec 9 13:59:45 bwayipn04 kernel: (da1:isp0:0:125:2): Power on, reset, or bus device reset occurred Dec 9 13:59:45 bwayipn04 kernel: (da1:isp0:0:125:2): Retrying Command (per Sense Data) Dec 9 14:00:24 bwayipn04 kernel: (da2:isp0:0:125:3): READ(10). CDB: 28 0 1 21 13 ff 0 0 20 0 Dec 9 14:00:24 bwayipn04 kernel: (da2:isp0:0:125:3): CAM Status: SCSI Status Error Dec 9 14:00:24 bwayipn04 kernel: (da2:isp0:0:125:3): SCSI Status: Check Condition Dec 9 14:00:24 bwayipn04 kernel: (da2:isp0:0:125:3): UNIT ATTENTION asc:29,0 Dec 9 14:00:24 bwayipn04 kernel: (da2:isp0:0:125:3): Power on, reset, or bus device reset occurred Dec 9 14:00:24 bwayipn04 kernel: (da2:isp0:0:125:3): Retrying Command (per Sense Data) Dec 9 14:08:00 bwayipn04 kernel: isp0: command timed out for 0.125.4 Dec 9 14:08:00 bwayipn04 kernel: isp0: command timed out for 0.125.4 the time out errors occur more often, and while the device recovers (it seems), it does stop i/o while it works itself out. This is my first venture into the fiber waters, and coming off of really solid performance with the scsi shelves i am a bit worried. can anyone offer any pointers on where to start looking here? regards, Brad ------------------------------------------------------------ Brad Miele IPNStock bmiele@ipnstock.com From owner-freebsd-scsi@FreeBSD.ORG Fri Dec 9 20:00:37 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org 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 3C40716A41F for ; Fri, 9 Dec 2005 20:00:37 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67C9843D64 for ; Fri, 9 Dec 2005 20:00:31 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jB9K0UaP073205; Fri, 9 Dec 2005 13:00:30 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4399E25E.5010701@samsco.org> Date: Fri, 09 Dec 2005 13:00:30 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brad Miele References: <20051209141608.W3172@localhost> In-Reply-To: <20051209141608.W3172@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org Subject: Re: isp errors with QLogic 2312 / DL380 / MSA 1500 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 20:00:37 -0000 Brad Miele wrote: > Hello, > > I have recently moved from individual HP MS30 SCSI shelves to the HP MSA > 1500 SAN with two MS30 SCSI shelves and two MS20 SATA shelves. > > I am seeing the following in messages: > > Dec 9 13:42:16 bwayipn04 kernel: isp0: command timed out for 0.125.4 > Dec 9 13:49:58 bwayipn04 last message repeated 4 times > Dec 9 13:55:48 bwayipn04 last message repeated 2 times > Dec 9 13:59:44 bwayipn04 kernel: (da3:isp0:0:125:4): READ(10). CDB: 28 > 0 6a 54 85 bf 0 0 80 0 > Dec 9 13:59:44 bwayipn04 kernel: (da3:isp0:0:125:4): CAM Status: SCSI > Status Error > Dec 9 13:59:44 bwayipn04 kernel: (da3:isp0:0:125:4): SCSI Status: Check > Condition > Dec 9 13:59:44 bwayipn04 kernel: (da3:isp0:0:125:4): UNIT ATTENTION > asc:29,0 > Dec 9 13:59:44 bwayipn04 kernel: (da3:isp0:0:125:4): Power on, reset, > or bus device reset occurred > Dec 9 13:59:44 bwayipn04 kernel: (da3:isp0:0:125:4): Retrying Command > (per Sense Data) > Dec 9 13:59:45 bwayipn04 kernel: (da1:isp0:0:125:2): WRITE(10). CDB: 2a > 0 88 7a 71 9f 0 0 20 0 > Dec 9 13:59:45 bwayipn04 kernel: (da1:isp0:0:125:2): CAM Status: SCSI > Status Error > Dec 9 13:59:45 bwayipn04 kernel: (da1:isp0:0:125:2): SCSI Status: Check > Condition > Dec 9 13:59:45 bwayipn04 kernel: (da1:isp0:0:125:2): UNIT ATTENTION > asc:29,0 > Dec 9 13:59:45 bwayipn04 kernel: (da1:isp0:0:125:2): Power on, reset, > or bus device reset occurred > Dec 9 13:59:45 bwayipn04 kernel: (da1:isp0:0:125:2): Retrying Command > (per Sense Data) > Dec 9 14:00:24 bwayipn04 kernel: (da2:isp0:0:125:3): READ(10). CDB: 28 > 0 1 21 13 ff 0 0 20 0 > Dec 9 14:00:24 bwayipn04 kernel: (da2:isp0:0:125:3): CAM Status: SCSI > Status Error > Dec 9 14:00:24 bwayipn04 kernel: (da2:isp0:0:125:3): SCSI Status: Check > Condition > Dec 9 14:00:24 bwayipn04 kernel: (da2:isp0:0:125:3): UNIT ATTENTION > asc:29,0 > Dec 9 14:00:24 bwayipn04 kernel: (da2:isp0:0:125:3): Power on, reset, > or bus device reset occurred > Dec 9 14:00:24 bwayipn04 kernel: (da2:isp0:0:125:3): Retrying Command > (per Sense Data) > Dec 9 14:08:00 bwayipn04 kernel: isp0: command timed out for 0.125.4 > Dec 9 14:08:00 bwayipn04 kernel: isp0: command timed out for 0.125.4 > > the time out errors occur more often, and while the device recovers (it > seems), it does stop i/o while it works itself out. This is my first > venture into the fiber waters, and coming off of really solid > performance with the scsi shelves i am a bit worried. can anyone offer > any pointers on where to start looking here? > > regards, > > Brad This can mean that you have a bad power supply, or that the drive is having significant problems, or that an unexpected bus reset happened. The latter is the least likely. Scott