From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 15 11:07:09 2010 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5EB5E106566C for ; Mon, 15 Feb 2010 11:07:09 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 436BE8FC15 for ; Mon, 15 Feb 2010 11:07:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id o1FB79xB070439 for ; Mon, 15 Feb 2010 11:07:09 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id o1FB788i070437 for freebsd-scsi@FreeBSD.org; Mon, 15 Feb 2010 11:07:08 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 15 Feb 2010 11:07:08 GMT Message-Id: <201002151107.o1FB788i070437@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-scsi@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org 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, 15 Feb 2010 11:07:09 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/142351 scsi [mpt] LSILogic driver performance problems o kern/141934 scsi [cam] [patch] add support for SEAGATE DAT Scopion 130 o kern/140091 scsi [da] [patch] allow for da(4) large block transfer than o kern/138789 scsi [cam] [patch] cd(4) patch for drives/discs failing the o kern/134488 scsi [mpt] MPT SCSI driver probes max. 8 LUNs per device o kern/132250 scsi [ciss] ciss driver does not support more then 15 drive o kern/132206 scsi [mpt] system panics on boot when mirroring and 2nd dri p kern/130735 scsi [cam] [patch] pass M_NOWAIT to the malloc() call insid o kern/130621 scsi [mpt] tranfer rate is inscrutable slow when use lsi213 o kern/129602 scsi [ahd] ahd(4) gets confused and wedges SCSI bus o kern/128452 scsi [sa] [panic] Accessing SCSI tape drive randomly crashe o kern/128245 scsi [scsi] "inquiry data fails comparison at DV1 step" [re o kern/127927 scsi [isp] isp(4) target driver crashes kernel when set up o kern/124667 scsi [amd] [panic] FreeBSD-7 kernel page faults at amd-scsi o kern/123674 scsi [ahc] ahc driver dumping f kern/123666 scsi [aac] attach fails with Adaptec SAS RAID 3805 controll o sparc/121676 scsi [iscsi] iscontrol do not connect iscsi-target on sparc o kern/120487 scsi [sg] scsi_sg incompatible with scanners o kern/120247 scsi [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s o kern/119668 scsi [cam] [patch] certain errors are too verbose comparing o kern/114597 scsi [sym] System hangs at SCSI bus reset with dual HBAs o kern/110847 scsi [ahd] Tyan U320 onboard problem with more than 3 disks o kern/99954 scsi [ahc] reading from DVD failes on 6.x [regression] o kern/94838 scsi Kernel panic while mounting SD card with lock switch o o kern/92798 scsi [ahc] SCSI problem with timeouts o kern/90282 scsi [sym] SCSI bus resets cause loss of ch device o kern/76178 scsi [ahd] Problem with ahd and large SCSI Raid system o kern/74627 scsi [ahc] [hang] Adaptec 2940U2W Can't boot 5.3 s kern/61165 scsi [panic] kernel page fault after calling cam_send_ccb o kern/60641 scsi [sym] Sporadic SCSI bus resets with 53C810 under load o kern/60598 scsi wire down of scsi devices conflicts with config s kern/57398 scsi [mly] Current fails to install on mly(4) based RAID di o kern/52638 scsi [panic] SCSI U320 on SMP server won't run faster than o kern/44587 scsi dev/dpt/dpt.h is missing defines required for DPT_HAND o kern/40895 scsi wierd kernel / device driver bug o kern/39388 scsi ncr/sym drivers fail with 53c810 and more than 256MB m o kern/35234 scsi World access to /dev/pass? (for scanner) requires acce 37 problems total. From owner-freebsd-scsi@FreeBSD.ORG Mon Feb 15 23:45:44 2010 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E9171065697; Mon, 15 Feb 2010 23:45:44 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id 1E3BB8FC18; Mon, 15 Feb 2010 23:45:43 +0000 (UTC) Received: from elsa.codelab.cz (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id B6F2B19E023; Tue, 16 Feb 2010 00:45:41 +0100 (CET) Received: from [192.168.1.2] (r5bb235.net.upc.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 6D03219E019; Tue, 16 Feb 2010 00:45:39 +0100 (CET) Message-ID: <4B79DCA2.1070005@quip.cz> Date: Tue, 16 Feb 2010 00:45:38 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.7) Gecko/20100104 SeaMonkey/2.0.2 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: 4B5F1553.4070709@quip.cz Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: ivoras@freebsd.org Subject: performance tuning of iSCSI and Dell MD3000i / gjournal 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: Mon, 15 Feb 2010 23:45:44 -0000 I am sorry for my late reply, I am not subscribed to this list and I was busy by my other work. Please CC me next time. >> >> Just a note, I am still having performance problems with iSCSI and Dell >> MD3000i. >> I tried it with ZFS, but writing performance was even worse - about >> 3-5MB/s! Copying 33GB from local UFS partition do iSCSI ZFS partition >> takes almost 5 hours: > > You've written a lot of information here. Firstly, is your problem > related to iSCSI performance, ZFS performance or UFS performance? As it > looks to me, you are mostly complaining about iSCSI performance, right? I am complaining about iSCSI performance in general. I think it should give some better results on gigabit link with underlying RAID5 of 4 SATA 7200rpm drives. The performance is much below one physical SATA drive. Then I use 3 different setups to test if it is just iSCSI problem, or UFS+SU. UFS+SU have much lower write performance than UFS+Gjournal, but gjournal doesn't work well with iSCSI at boot time. And ZFS on iSCSI is the worst case with 5MB/s write performance! (I have much better experiences with ZFS on RAIDZ pool of 4 SATA drives) The mentioned iSCSI storage (Dell MD3000i) is now in production serving about 200Mbits (350Mbits in peaks) through Lighttpd, using UFS+SU. It is used almost read only, so write performance doesn't matter at this time, but if there will be any disaster and I will need to restore backups, it will take more than 2 days to copy 1TB of data! Miroslav Lachman From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 16 01:40:38 2010 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2DFEC106566B for ; Tue, 16 Feb 2010 01:40:38 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from portcityhosting.com (bayringfw.portcityweb.com [64.140.243.92]) by mx1.freebsd.org (Postfix) with ESMTP id D1FCC8FC16 for ; Tue, 16 Feb 2010 01:40:37 +0000 (UTC) Received: from [127.0.0.1] ([173.14.128.81]) by portcityhosting.com with MailEnable ESMTP; Mon, 15 Feb 2010 20:00:38 -0500 Message-ID: <4B79EF45.5070904@greatbaysoftware.com> Date: Mon, 15 Feb 2010 20:05:09 -0500 From: Charles Owens MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: <4B75AB2D.2090306@greatbaysoftware.com> In-Reply-To: <4B75AB2D.2090306@greatbaysoftware.com> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit X-WatchGuard-AntiVirus: part scanned. clean action=allow X-ME-Bayesian: 0.000000 Subject: bin/143972: mptutil(8) segfault 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, 16 Feb 2010 01:40:38 -0000 I've posted about this previously on -hardware... maybe this is the more appropriate list? I'd appreciate any and all input. Please see below and PR at http://www.freebsd.org/cgi/query-pr.cgi?pr=143972 As noted in PR, this is with a controller based on the LSI 1068E processor. Thank much Charles Owens Great Bay Software, Inc. Charles Owens wrote: > Howdy, > > We're working with IBM hardware (xSeries 3550) that has an > mpt-based RAID controller... after initial success with testing the > mptutil utility, now operations other than "show adapter" and "show > volume" are resulting in segfaults. > > While it was working properly we created and removed volumes several > times, force-failed drives, and just generally put it through its > paces... and all seemed fine. Then, after a reboot, it suddenly started > failing with segfault as described, and nothing we do has helped to get > it out of this state (including trying to use the LSI in-BIOS manager to > create/delete volumes -- which in and of itself works fine). > > We found recent thread > http://docs.freebsd.org/cgi/mid.cgi?4B56CD4C.80503 and hoped that it > might somehow relate... and even tried the patch that John Baldwin > posted, but to no avail. > > Has anyone seen this behavior and/or have a suggested fix or workaround? > > > Here's the output of "mptutil show adapter": > > mpt0 Adapter: > Board Name: SR-BR10i > Board Assembly: L3-25116-01H > Chip Name: C1068E > Chip Revision: UNUSED > RAID Levels: RAID0, RAID1, RAID1E > RAID0 Stripes: 64K > RAID1E Stripes: 64K > RAID0 Drives/Vol: 1-10 > RAID1 Drives/Vol: 2 > RAID1E Drives/Vol: 3-10 > > > This work is being done using FreeBSD 8.0-RELEASE-p2 + PAE. > > Thank very much, > > Charles > > > _______________________________________________ freebsd-hardware@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 16 10:02:58 2010 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 58229106566B for ; Tue, 16 Feb 2010 10:02:58 +0000 (UTC) (envelope-from osharoiko@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26]) by mx1.freebsd.org (Postfix) with ESMTP id B69ED8FC13 for ; Tue, 16 Feb 2010 10:02:57 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id 9so730726eyd.9 for ; Tue, 16 Feb 2010 02:02:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:content-type :date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=Ainzcc6JLQBH+3gCC5vVsbc5GFblWncUAzgBo4B5IZ0=; b=i5IAOk6N4t5SaZLDrxIVC9eQwNTe1VH+R6cYC6ez5CtFyrp4d4sc5MVJeN6+/G0+Zn 5gMHa4lDsh8NzKKjGk6q//6e7nIvhnNAuf1yEX4cfVSpXdHom1B9EGPDzfq5943FQ9lb tVIcJRQ9kyQZ0KtuK9ykKSZyIIGyAAREI4Ogs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; b=i+WgAoGRExWPSBCtAOUnQFNHaqeUCTDZPI46E6tOE7KPcLKUkmwyuCEqtEgBWiFfWt Y2XYphjAFEpu3huE5dAUX61pW9YZBIbJmUFr2rGIo7H9XFOAukyaqcjVdq+7px6bX33o Y9s4ubcQHVBr7YAcheruP3g+TWyCjW+tekJPA= Received: by 10.213.0.212 with SMTP id 20mr3861804ebc.41.1266314576487; Tue, 16 Feb 2010 02:02:56 -0800 (PST) Received: from ?195.208.252.154? (brain.cc.rsu.ru [195.208.252.154]) by mx.google.com with ESMTPS id 5sm10505207eyf.0.2010.02.16.02.02.55 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 16 Feb 2010 02:02:55 -0800 (PST) From: Oleg Sharoyko To: freebsd-scsi@freebsd.org, freebsd-hackers@freebsd.org Content-Type: text/plain; charset="UTF-8" Date: Tue, 16 Feb 2010 13:02:50 +0300 Message-ID: <1266314570.73716.42.camel@brain.cc.rsu.ru> Mime-Version: 1.0 X-Mailer: Evolution 2.28.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Subject: Qlogic (isp) cannot login into fabric after link loss 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, 16 Feb 2010 10:02:58 -0000 Hi! I'm sorry for cross-posting, but I'm in trouble with isp driver and I really need your help. Here we have IBM blade with Qlogic (seems to be 2462s card) and EMC CX3-40 both connected to Brocade DS4900. Everything seems to be ok, until FC link between switch and server fails. When it later restores isp cannot anymore log into fabric. I have a complete debug log of isp output. Here is small excerpt from it which I think is relevant to my problem: isp0: Chan 0 got 3 ports back from name server isp0: Chan 0 skip ourselves on @ PortID 0x011500 isp0: Chan 0 Checking Fabric Port 0x010e00 isp0: IN mbox 0 = 0x0064 isp0: IN mbox 1 = 0x0003 isp0: IN mbox 2 = 0x05e8 isp0: IN mbox 3 = 0xd000 isp0: IN mbox 6 = 0x0000 isp0: IN mbox 7 = 0x0000 isp0: IN mbox 9 = 0x0000 isp0: IN mbox 10 = 0x0000 isp0: RISC2HOST ISR 0x40000010 isp0: RISC2HOST ISR 0x40068011 isp0: OUT mbox 0 = 0x4006 isp0: IOCB LOGX: isp0: 0x00000000: 52 01 00 00 ff ff ff ff 00 00 03 00 00 00 00 00 isp0: 0x00000010: 00 0e 01 00 00 00 00 00 00 00 00 00 00 00 00 00 isp0: 0x00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 isp0: 0x00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 isp0: IN mbox 0 = 0x0054 isp0: IN mbox 1 = 0x0040 isp0: IN mbox 2 = 0x05e8 isp0: IN mbox 3 = 0xd000 isp0: IN mbox 6 = 0x0000 isp0: IN mbox 7 = 0x0000 isp0: RISC2HOST ISR 0x40060011 isp0: RISC2HOST ISR 0x40060011 isp0: RISC2HOST ISR 0x40060011 isp0: RISC2HOST ISR 0x40008010 isp0: OUT mbox 0 = 0x4000 isp0: IOCB LOGX response: isp0: 0x00000000: 52 01 00 00 ff ff ff ff 31 00 03 00 00 00 00 00 isp0: 0x00000010: 00 0e 01 02 1a 00 00 00 01 00 00 00 00 00 00 00 isp0: 0x00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 isp0: 0x00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 isp0: Chan 0 PLOGX PortID 0x010e00 to N-Port handle 0x3: already logged in with N-Port handle 0x1 isp0: IN mbox 0 = 0x0064 isp0: IN mbox 1 = 0x0001 isp0: IN mbox 2 = 0x05e8 isp0: IN mbox 3 = 0xd000 isp0: IN mbox 6 = 0x0000 isp0: IN mbox 7 = 0x0000 isp0: IN mbox 9 = 0x0000 isp0: IN mbox 10 = 0x0000 isp0: RISC2HOST ISR 0x40000010 isp0: RISC2HOST ISR 0x40008010 isp0: OUT mbox 0 = 0x4000 isp0: Chan 0 Port 0x010e00 flags 0x0 curstate 7 isp0: Chan 0 new device 0x010e00@0x1 disappeared As far as I can tell from this log and isp.c things are happening in the following order: 1. Get the list of devices on fabric 2. Try to log into each device (excluding self) 3. The result is failure with code "already logged in" and old login handle 4. Try to login with that handle and expect that to work, but it fails with code PDB2400_STATE_PORT_UNAVAIL. Bear in mind, that I'm not anywhere close to FC expert, so I may be totally wrong here. So who is wrong and would it be possible to do resolve this issue? I have an access to all the components (blade, fc switch and storage system) and can provide additional information if it's needed. I'm really stuck and would greatly appreciate any help! Thanks in advance. -- Oleg Sharoyko From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 16 15:38:54 2010 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57427106566B for ; Tue, 16 Feb 2010 15:38:54 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 2E4CA8FC08 for ; Tue, 16 Feb 2010 15:38:53 +0000 (UTC) Received: from [192.168.0.101] (m206-63.dsl.tsoft.com [198.144.206.63]) by ns1.feral.com (8.14.3/8.14.3) with ESMTP id o1GFcrgR004329 for ; Tue, 16 Feb 2010 07:38:53 -0800 (PST) (envelope-from mj@feral.com) Message-ID: <4B7ABC10.5060004@feral.com> Date: Tue, 16 Feb 2010 07:38:56 -0800 From: Matthew Jacob User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: <1266314570.73716.42.camel@brain.cc.rsu.ru> In-Reply-To: <1266314570.73716.42.camel@brain.cc.rsu.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.2.3 (ns1.feral.com [192.67.166.1]); Tue, 16 Feb 2010 07:38:53 -0800 (PST) Subject: Re: Qlogic (isp) cannot login into fabric after link loss 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, 16 Feb 2010 15:38:54 -0000 On 2/16/2010 2:02 AM, Oleg Sharoyko wrote: > Hi! > > I'm sorry for cross-posting, but I'm in trouble with isp driver and I > really need your help. > > Hmm. You haven't given details of what you're running here (OS rev, whether you're loading ispfw from the OS or running it from the BIOS). That would help. But this seems to happen with the latest anyway sometimes. I don't suppose you have a FC trace of this happening? It's probably step 4 below that there is a logic problem on. I need to work on this. > Here we have IBM blade with Qlogic (seems to be 2462s card) and EMC > CX3-40 both connected to Brocade DS4900. Everything seems to be ok, > until FC link between switch and server fails. When it later restores > isp cannot anymore log into fabric. I have a complete debug log of isp > output. Here is small excerpt from it which I think is relevant to my > problem: > > isp0: Chan 0 got 3 ports back from name server > isp0: Chan 0 skip ourselves on @ PortID 0x011500 > isp0: Chan 0 Checking Fabric Port 0x010e00 > isp0: IN mbox 0 = 0x0064 > isp0: IN mbox 1 = 0x0003 > isp0: IN mbox 2 = 0x05e8 > isp0: IN mbox 3 = 0xd000 > isp0: IN mbox 6 = 0x0000 > isp0: IN mbox 7 = 0x0000 > isp0: IN mbox 9 = 0x0000 > isp0: IN mbox 10 = 0x0000 > isp0: RISC2HOST ISR 0x40000010 > isp0: RISC2HOST ISR 0x40068011 > isp0: OUT mbox 0 = 0x4006 > isp0: IOCB LOGX: > isp0: 0x00000000: 52 01 00 00 ff ff ff ff 00 00 03 00 00 00 00 00 > isp0: 0x00000010: 00 0e 01 00 00 00 00 00 00 00 00 00 00 00 00 00 > isp0: 0x00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > isp0: 0x00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > isp0: IN mbox 0 = 0x0054 > isp0: IN mbox 1 = 0x0040 > isp0: IN mbox 2 = 0x05e8 > isp0: IN mbox 3 = 0xd000 > isp0: IN mbox 6 = 0x0000 > isp0: IN mbox 7 = 0x0000 > isp0: RISC2HOST ISR 0x40060011 > isp0: RISC2HOST ISR 0x40060011 > isp0: RISC2HOST ISR 0x40060011 > isp0: RISC2HOST ISR 0x40008010 > isp0: OUT mbox 0 = 0x4000 > isp0: IOCB LOGX response: > isp0: 0x00000000: 52 01 00 00 ff ff ff ff 31 00 03 00 00 00 00 00 > isp0: 0x00000010: 00 0e 01 02 1a 00 00 00 01 00 00 00 00 00 00 00 > isp0: 0x00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > isp0: 0x00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > isp0: Chan 0 PLOGX PortID 0x010e00 to N-Port handle 0x3: already logged > in with N-Port handle 0x1 > isp0: IN mbox 0 = 0x0064 > isp0: IN mbox 1 = 0x0001 > isp0: IN mbox 2 = 0x05e8 > isp0: IN mbox 3 = 0xd000 > isp0: IN mbox 6 = 0x0000 > isp0: IN mbox 7 = 0x0000 > isp0: IN mbox 9 = 0x0000 > isp0: IN mbox 10 = 0x0000 > isp0: RISC2HOST ISR 0x40000010 > isp0: RISC2HOST ISR 0x40008010 > isp0: OUT mbox 0 = 0x4000 > isp0: Chan 0 Port 0x010e00 flags 0x0 curstate 7 > isp0: Chan 0 new device 0x010e00@0x1 disappeared > > As far as I can tell from this log and isp.c things are happening in the > following order: > > 1. Get the list of devices on fabric > 2. Try to log into each device (excluding self) > 3. The result is failure with code "already logged in" and old login > handle > 4. Try to login with that handle and expect that to work, but it fails > with code PDB2400_STATE_PORT_UNAVAIL. > > Bear in mind, that I'm not anywhere close to FC expert, so I may be > totally wrong here. > > So who is wrong and would it be possible to do resolve this issue? I > have an access to all the components (blade, fc switch and storage > system) and can provide additional information if it's needed. > > I'm really stuck and would greatly appreciate any help! Thanks in > advance. > > From owner-freebsd-scsi@FreeBSD.ORG Tue Feb 16 18:48:44 2010 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86EEE1065670 for ; Tue, 16 Feb 2010 18:48:44 +0000 (UTC) (envelope-from osharoiko@gmail.com) Received: from mail.r61.net (mail.r61.net [195.208.245.249]) by mx1.freebsd.org (Postfix) with ESMTP id E0CE48FC0A for ; Tue, 16 Feb 2010 18:48:43 +0000 (UTC) Received: from mind.local (os.adsl.r61.net [195.208.243.95]) (authenticated bits=0) by mail.r61.net (8.14.3/8.14.1) with ESMTP id o1GIG8ns089560 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 16 Feb 2010 21:16:10 +0300 (MSK) (envelope-from osharoiko@gmail.com) X-Authentication-Warning: asterix.r61.net: Host os.adsl.r61.net [195.208.243.95] claimed to be mind.local Message-ID: <4B7AE0DE.9070700@gmail.com> Date: Tue, 16 Feb 2010 21:15:58 +0300 From: Oleg Sharoyko User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-GB; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: Matthew Jacob References: <1266314570.73716.42.camel@brain.cc.rsu.ru> <4B7ABC10.5060004@feral.com> In-Reply-To: <4B7ABC10.5060004@feral.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-scsi@freebsd.org Subject: Re: Qlogic (isp) cannot login into fabric after link loss 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, 16 Feb 2010 18:48:44 -0000 Hi! On 16.02.10 18:38, Matthew Jacob wrote: > Hmm. You haven't given details of what you're running here (OS rev, > whether you're loading ispfw from the OS or running it from the BIOS). > That would help. But this seems to happen with the latest anyway sometimes. Ups. Sorry, I was fighting with this for a couple of days and forgot that people can't read my mind (though that wouldn't be a good thing). The kernel is RELENG_8 checked out on 2010-02-12. The world is a bit older, but that shouldn't matter. I have tried both ispfw and BIOS firmware without any difference. > I don't suppose you have a FC trace of this happening? I think I could try to make one. I have to check the switch manual. I'll let you know if I have one. > It's probably step 4 below that there is a logic problem on. I need to > work on this. If you need access to this box - it's possible, just let me know. -- Oleg Sharoyko From owner-freebsd-scsi@FreeBSD.ORG Wed Feb 17 01:37:30 2010 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8630D106566B for ; Wed, 17 Feb 2010 01:37:30 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 4DC578FC18 for ; Wed, 17 Feb 2010 01:37:30 +0000 (UTC) Received: from [10.8.0.2] (remotevpn [10.8.0.2]) by ns1.feral.com (8.14.3/8.14.3) with ESMTP id o1H1bTOV011007 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Feb 2010 17:37:29 -0800 (PST) (envelope-from mj@feral.com) Message-ID: <4B7B4854.7020206@feral.com> Date: Tue, 16 Feb 2010 17:37:24 -0800 From: Matthew Jacob Organization: Feral Software User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Oleg Sharoyko References: <1266314570.73716.42.camel@brain.cc.rsu.ru> In-Reply-To: <1266314570.73716.42.camel@brain.cc.rsu.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.2.3 (ns1.feral.com [10.8.0.1]); Tue, 16 Feb 2010 17:37:30 -0800 (PST) Cc: freebsd-scsi@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Qlogic (isp) cannot login into fabric after link loss 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, 17 Feb 2010 01:37:30 -0000 Oleg Sharoyko wrote: > Hi! > > I I've reproduced the problem and I think I know what's going on. I've filed a PR which I'll put you on the CC list for as soon as I find it. From owner-freebsd-scsi@FreeBSD.ORG Wed Feb 17 06:25:28 2010 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 43D801065695 for ; Wed, 17 Feb 2010 06:25:28 +0000 (UTC) (envelope-from j@uriah.heep.sax.de) Received: from uriah.heep.sax.de (uriah.heep.sax.de [213.240.137.9]) by mx1.freebsd.org (Postfix) with ESMTP id E24558FC27 for ; Wed, 17 Feb 2010 06:25:27 +0000 (UTC) Received: by uriah.heep.sax.de (Postfix, from userid 107) id DBB3786; Wed, 17 Feb 2010 07:25:26 +0100 (MET) Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <4B53C505.7050608@langille.org> In-Reply-To: <4B53C505.7050608@langille.org> From: j@uriah.heep.sax.de (Joerg Wunsch) X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii Message-Id: <20100217062526.DBB3786@uriah.heep.sax.de> Date: Wed, 17 Feb 2010 07:25:26 +0100 (MET) Cc: Subject: Re: device.hints isn't setting what I want X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joerg Wunsch List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Feb 2010 06:25:28 -0000 Dan Langille wrote: > In /boot/devices, I have added these entries: > > hint.scbus.1.at="ahc0" > hint.scbus.0.at="ahc1" > hint.scbus.2.at="acd0" > hint.scbus.5.at="umass0" > The second two lines aren't doing as expected. They look "upside down" to me. You are trying to connect a SCSI bus to a particular device? Run a "camcontrol devlist -v" to see the HBA names. You can only wire a bus onto an HBA, and then a device onto a bus. I think you want something like hint.scbus.2.at="ata0" The umass controller might be more difficult. Mine is called "umass-sim0", I guess there could be many of them, no idea whether they honor device hints at all. But perhaps you don't need those. For your pass device, I don't know whether it can be wired down at all. If so, try hint.pass.3.at="scbus1" hint.pass.3.target="0" I used to do something like that by the time I had multiple tape drives and multiple CD-{R,ROM} drives, but I don't wire my devices down anymore these days. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi@FreeBSD.ORG Wed Feb 17 06:37:02 2010 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 458C71065676 for ; Wed, 17 Feb 2010 06:37:02 +0000 (UTC) (envelope-from j@uriah.heep.sax.de) Received: from uriah.heep.sax.de (uriah.heep.sax.de [213.240.137.9]) by mx1.freebsd.org (Postfix) with ESMTP id E40118FC12 for ; Wed, 17 Feb 2010 06:37:01 +0000 (UTC) Received: by uriah.heep.sax.de (Postfix, from userid 107) id 6332D26; Wed, 17 Feb 2010 07:37:00 +0100 (MET) Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <4B53C505.7050608@langille.org> In-Reply-To: <4B53C505.7050608@langille.org> From: j@uriah.heep.sax.de (Joerg Wunsch) X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii Message-Id: <20100217063700.6332D26@uriah.heep.sax.de> Date: Wed, 17 Feb 2010 07:37:00 +0100 (MET) Cc: Subject: Re: device.hints isn't setting what I want X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joerg Wunsch List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Feb 2010 06:37:02 -0000 Dan Langille wrote: > I have an external tape library and an external tape drive. They > are not always powered up. Btw., a word of a warning as I'm running a similar setup to yours: when powered down, do run a "camcontrol rescan 1" so the device nodes will disappear. At least under FreeBSD 7.x (don't know whether that has been fixed later), CAM gets totally upset if you try accessing /dev/nsa0 when its underlying hardware disappeared. This leaves CAM in a state where the sa0 device is partially removed ("lost device"), but since you just opened it, parts will remain in the kernel. If you reattach it to the bus, and run another "camcontrol rescan 1", you'll no longer get your sa0 device back but something else, and sooner or later, your kernel will crash. If you ever run into that situation, reboot volunteerily before it crashes... -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi@FreeBSD.ORG Wed Feb 17 06:40:54 2010 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 767251065670 for ; Wed, 17 Feb 2010 06:40:54 +0000 (UTC) (envelope-from j@uriah.heep.sax.de) Received: from uriah.heep.sax.de (uriah.heep.sax.de [213.240.137.9]) by mx1.freebsd.org (Postfix) with ESMTP id 257E38FC08 for ; Wed, 17 Feb 2010 06:40:54 +0000 (UTC) Received: by uriah.heep.sax.de (Postfix, from userid 107) id 24BE447; Wed, 17 Feb 2010 07:13:44 +0100 (MET) Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <4B53C4DA.9080008@langille.org> In-Reply-To: <4B53C4DA.9080008@langille.org> From: j@uriah.heep.sax.de (Joerg Wunsch) X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii Message-Id: <20100217061344.24BE447@uriah.heep.sax.de> Date: Wed, 17 Feb 2010 07:13:44 +0100 (MET) Cc: Subject: Re: do I want ch0 or pass1? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joerg Wunsch List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Feb 2010 06:40:54 -0000 Dan Langille wrote: > My understanding: chio(1) will with ch0, whereas mtx(1) will work > with pass1. Is this correct? Yes, it is. I've also got a changer device here, and it works fine with ch(4). -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi@FreeBSD.ORG Sat Feb 20 02:31:14 2010 Return-Path: Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FC171065672; Sat, 20 Feb 2010 02:31:14 +0000 (UTC) (envelope-from jmg@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2FF478FC1E; Sat, 20 Feb 2010 02:31:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id o1K2VE0w094661; Sat, 20 Feb 2010 02:31:14 GMT (envelope-from jmg@freefall.freebsd.org) Received: (from jmg@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id o1K2VDaj094657; Sat, 20 Feb 2010 02:31:13 GMT (envelope-from jmg) Date: Sat, 20 Feb 2010 02:31:13 GMT Message-Id: <201002200231.o1K2VDaj094657@freefall.freebsd.org> To: nox@jelal.kn-bremen.de, jmg@FreeBSD.org, freebsd-scsi@FreeBSD.org, jmg@FreeBSD.org From: jmg@FreeBSD.org Cc: Subject: Re: kern/138789: [cam] [patch] cd(4) patch for drives/discs failing the 'read toc' command 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: Sat, 20 Feb 2010 02:31:14 -0000 Synopsis: [cam] [patch] cd(4) patch for drives/discs failing the 'read toc' command State-Changed-From-To: open->analyzed State-Changed-By: jmg State-Changed-When: Sat Feb 20 02:26:32 UTC 2010 State-Changed-Why: I will take over this PR... The problem is that the scsi-cd.c driver attempts to read the LEADOUT track of the disc, and if it can't, assumes the disc is not valid.. For some Blu-Ray drives, they, per the spec, do not allow reading of the LEADOUT track... I also have a drive that fails.. I am currently working on a patch to not read the LEADOUT track, but keep the original behavior as a sysctl incase it breaks older cd-rom drives. Responsible-Changed-From-To: freebsd-scsi->jmg Responsible-Changed-By: jmg Responsible-Changed-When: Sat Feb 20 02:26:32 UTC 2010 Responsible-Changed-Why: I will take over this PR... The problem is that the scsi-cd.c driver attempts to read the LEADOUT track of the disc, and if it can't, assumes the disc is not valid.. For some Blu-Ray drives, they, per the spec, do not allow reading of the LEADOUT track... I also have a drive that fails.. I am currently working on a patch to not read the LEADOUT track, but keep the original behavior as a sysctl incase it breaks older cd-rom drives. http://www.freebsd.org/cgi/query-pr.cgi?pr=138789