From owner-freebsd-scsi@FreeBSD.ORG Mon Sep 29 11:06:57 2008 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 86AA91065691 for ; Mon, 29 Sep 2008 11:06:57 +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 75ACC8FC30 for ; Mon, 29 Sep 2008 11:06:57 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m8TB6vmk040933 for ; Mon, 29 Sep 2008 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m8TB6u1a040929 for freebsd-scsi@FreeBSD.org; Mon, 29 Sep 2008 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 29 Sep 2008 11:06:56 GMT Message-Id: <200809291106.m8TB6u1a040929@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, 29 Sep 2008 11:06:57 -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/126866 scsi [isp] [panic] kernel panic on card initialization o kern/124667 scsi [amd] [panic] FreeBSD-7 kernel page faults at amd-scsi o kern/123674 scsi [ahc] ahc driver dumping o 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/38828 scsi [dpt] [request] DPT PM2012B/90 doesn't work o kern/35234 scsi World access to /dev/pass? (for scanner) requires acce 26 problems total. From owner-freebsd-scsi@FreeBSD.ORG Tue Sep 30 15:11:49 2008 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 3FB951065686 for ; Tue, 30 Sep 2008 15:11:49 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from core.stromnet.se (core.stromnet.se [83.218.84.131]) by mx1.freebsd.org (Postfix) with ESMTP id EEE6E8FC21 for ; Tue, 30 Sep 2008 15:11:48 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from localhost (core.stromnet.se [83.218.84.131]) by core.stromnet.se (Postfix) with ESMTP id 409D0FB2F1F for ; Tue, 30 Sep 2008 16:55:37 +0200 (CEST) X-Virus-Scanned: amavisd-new at stromnet.se X-Spam-Flag: NO X-Spam-Score: -1.135 X-Spam-Level: X-Spam-Status: No, score=-1.135 tagged_above=-1000 required=6.2 tests=[AWL=0.671, BAYES_00=-2.599, RDNS_DYNAMIC=0.1, SPF_FAIL=0.693] Received: from core.stromnet.se ([83.218.84.131]) by localhost (core.stromnet.se [83.218.84.131]) (amavisd-new, port 10024) with ESMTP id fyConwSbAK7C for ; Tue, 30 Sep 2008 16:55:31 +0200 (CEST) Received: from johan-mp.stromnet.se (78-69-139-60-no129.tbcn.telia.com [78.69.139.60]) by core.stromnet.se (Postfix) with ESMTP id F338FFB2F1E for ; Tue, 30 Sep 2008 16:55:30 +0200 (CEST) Message-Id: <35FAB782-F576-4FB7-8633-67CFB63D9389@stromnet.se> From: =?ISO-8859-1?Q?Johan_Str=F6m?= To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Tue, 30 Sep 2008 16:55:30 +0200 X-Mailer: Apple Mail (2.929.2) Subject: state of iscsi_initiator? 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, 30 Sep 2008 15:11:49 -0000 Hi list, I'm looking into FreeBSDs iSCSI initiator capabilities, and I'm wondering how stable/used this is? Judging from the commits (http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/iscsi/initiator/ ) there haven't been very much (iSCSI specific) activity since imported 14 months ago. Either nobody is using it thus not reporting bugs, or it is working very well ;) So, what I'm wondering is, how stable is this? Anyone using it successfully in production? Checking this list's archive I've seen some people with deadlock problems, but are there anyone using it without these problems? Or is the userbase that small? How about performance? Thanks! -- Johan From owner-freebsd-scsi@FreeBSD.ORG Tue Sep 30 21:16:40 2008 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 E52251065678 for ; Tue, 30 Sep 2008 21:16:40 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.233]) by mx1.freebsd.org (Postfix) with ESMTP id B6FD68FC1A for ; Tue, 30 Sep 2008 21:16:40 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so192435rvf.43 for ; Tue, 30 Sep 2008 14:16:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=XJmjs5ZFCrPotmY7SiSGvg9a8S1zNEzs8wNWRQ8M39w=; b=xTUBFoSwV+lbRnZcjPm2DGxFrBihzsX4Ah77AVLhOU0OGUaVmyZfOgFH4Ll8evdmZP tsJgGlLm74kYsumGWe5KyS9QuetxiIsixv823Ljk+QJ+EncZkSIrXajFSxqxcEuNXSFy 6tsZhkhq9z82iF6mP4tx+I45uuAOrsffhmmwo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=F590cTixyUShawPYQk2USqm9OoIeqR8ivreUVdi3RvVUBfGf0iMD/WZ6hT2f/M0baz FIoT8AYFGMWBqlifQp0ohKXhJYF9e6F6/g2d+qpJETVZnKIo4d4UYhWqWGc9ma956Rvk GEfbbNYltpfJnA4fYMYL7YqPBTk5M0RN2lVzA= Received: by 10.141.13.16 with SMTP id q16mr3883381rvi.99.1222809400251; Tue, 30 Sep 2008 14:16:40 -0700 (PDT) Received: by 10.141.136.21 with HTTP; Tue, 30 Sep 2008 14:16:39 -0700 (PDT) Message-ID: <3c0b01820809301416v416460e5gc0b4689febcf0905@mail.gmail.com> Date: Tue, 30 Sep 2008 17:16:39 -0400 From: "Alexander Sack" To: "Paul A. Procacci" In-Reply-To: <3c0b01820809251051q34a33fa5od5ec9fe9d853612@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200809250910.m8P9A4MY047099@freefall.freebsd.org> <835218108.20080925113214@connection.ca> <3c0b01820809251051q34a33fa5od5ec9fe9d853612@mail.gmail.com> Cc: freebsd-scsi@freebsd.org Subject: Re: Re[2]: kern/126866: [isp] [panic] kernel panic on card initialization 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, 30 Sep 2008 21:16:41 -0000 On Thu, Sep 25, 2008 at 1:51 PM, Alexander Sack wrote: > On Thu, Sep 25, 2008 at 11:32 AM, Ross wrote: >> >> PAP> I am having the same exact problem you were having using the same >> PAP> device. I started receiving this error on FBSD7-RELEASE and thought it >> PAP> was specific to that version. Naturally I upgraded to FBSD7-Stable as >> PAP> of today (9/25/2008), but still haven't been able to resolve this error, >> PAP> even with the patch presented here. Like you had mentioned on >> PAP> freebsd-scsi, the machine panic's roughly 50% of the time during boot. >> >> Actually, going over the trap output, it looks different than the >> output I had, so it might be a different issue in the end. >> >> Which kernel are you running? (i386/amd64), and is it possible to get >> the output of a dmesg, so we know what chipset the driver thinks it is? >> (Are you running an HP Blade w QHM6432 like I am?) >> >> Also, if you can set 'hint.isp.[01].debug=0x11F' in your >> /boot/device.hints file, it'll hopefully give some additional output >> to help track the problem down. >> >> Obviously the best is to compile in the kernel debugger as that'll >> give the exact place it crashes. > > > Yea totally. If you can get a stack trace that would be great (just > compile in the debugger support, reboot, and when you hit the panic do > a trace and just give us the function output (again exact addresses > not so much)). Paul do you have any update with this issue? I have my patches ready and I want to try to resolve yours if it indeed turns out to be a similar bug. Please let me know, -aps From owner-freebsd-scsi@FreeBSD.ORG Wed Oct 1 02:31:43 2008 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 ADFB41065692 for ; Wed, 1 Oct 2008 02:31:43 +0000 (UTC) (envelope-from klapperzhu@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.174]) by mx1.freebsd.org (Postfix) with ESMTP id 851828FC14 for ; Wed, 1 Oct 2008 02:31:43 +0000 (UTC) (envelope-from klapperzhu@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so340319wfg.7 for ; Tue, 30 Sep 2008 19:31:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=+UC/Ta+k+8J2AKzB5hSURsuCeQfHNhSGc2oLjl+OX6c=; b=RQnk0jqQiEVYejdSfPFncYihD0+BGPqrCIsU2VPU0BgE/wYXxUZlJMSy+eJRpDVA+N GFMmpnJZQXl8Lukk+pNPFwhF60grTUtz15NxG59zxYQwZTmEg/byVrnvqQrt8mVvrps4 FdJJUXIqIDuFurQcMOLJtlCaFY+0qnddV1yis= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=ofsUZnZH1tJv3BGcKSznotHjlNB6MWuqAQ1Hc4f9ATAhbKe987mqnvz3IwUK5iYRKA k8nl48OyPJ+a3jbJXH6TEAF3g5idQXV7gLSoJJYLN2cftQg06N3cJxrTV/ekEky/FuiY amWfMMqNQyLHc2tPB4ghp1F48RiIxxs+CHSwo= Received: by 10.142.251.15 with SMTP id y15mr3132545wfh.39.1222828302370; Tue, 30 Sep 2008 19:31:42 -0700 (PDT) Received: by 10.142.179.1 with HTTP; Tue, 30 Sep 2008 19:31:42 -0700 (PDT) Message-ID: Date: Tue, 30 Sep 2008 22:31:42 -0400 From: "Klapper Zhu" To: freebsd-scsi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: [ISP] QLA2432 Target Mode Broken 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, 01 Oct 2008 02:31:43 -0000 I also found in 24XX documentation that Enable/Modify LUN iocbs are not listed. They are listed in 23XX documentation. Should I assume that there is no need to register LUNs for target mode firmware for QLA24XX ? Sean Bruno sbruno at miralink.com Wrote Thu Aug 28 17:34:19 UTC 2008 >I tried putting a 2432 into target mode this week and noted that the >system threw a pretty nice panic and thought I would post the output >here. Reviewing the 4G documentation from Qlogic, it looks like they've >substantially changed the target mode interface, so I'm not surprised >that there's some work to do. If anyone has any patches they'd like me >to test, I'm open to integration: From owner-freebsd-scsi@FreeBSD.ORG Wed Oct 1 05:06:40 2008 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 898461065889 for ; Wed, 1 Oct 2008 05:06:27 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (host-122-100-2-232.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id 4AEAC8FC17 for ; Wed, 1 Oct 2008 05:06:27 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id 380AD17DA7; Wed, 1 Oct 2008 14:48:05 +1000 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.1.50.60] (142.19.96.58.exetel.com.au [58.96.19.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id 50E581737D; Wed, 1 Oct 2008 14:48:00 +1000 (EST) Message-ID: <48E300CB.8070808@modulus.org> Date: Wed, 01 Oct 2008 14:47:07 +1000 From: Andrew Snow User-Agent: Thunderbird 2.0.0.14 (X11/20080523) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Johan_Str=F6m?= References: <35FAB782-F576-4FB7-8633-67CFB63D9389@stromnet.se> In-Reply-To: <35FAB782-F576-4FB7-8633-67CFB63D9389@stromnet.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-scsi@freebsd.org Subject: Re: state of iscsi_initiator? 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, 01 Oct 2008 05:06:40 -0000 I'm just playing with iSCSI now, on a fresh 7.1-STABLE machine connected to another FreeBSD box running ports/net/iscsi-target. I am using the latest version 2.1 Initiator from: ftp://ftp.cs.huji.ac.il/users/danny/freebsd/ It seems alot better now than when I last tried it. The speed is constant at around 50MB/s for a single sequential read or write. It also reconnected very quickly when I restarted the target. I was even able to reboot the target box and I/O resumed perfectly once it finished booting! The speed increased to 80mb/s when I ran two threads, which is close to the max performance for the network cards in this machine. A couple of minor issues: 1. Trouble shutting down iscontrol - after I kill -9 it stays around for a minute or more until it finally goes away. 2. Under very heavy multi-threaded load, the client machine gets sluggish to respond, even to keystrokes on the console. And if I shutdown the target, even local disk accesses on the client computer stop working after a while. (I don't think this is a problem with iSCSI initiator. I suspect there's something in FreeBSD which pauses all disk I/O if the length of outstanding requests is too high, can anyone shed some light on this?) Overall, a pleasant experience and shows how much good work has been done on iSCSI. Congratulations Danny :-) - Andrew From owner-freebsd-scsi@FreeBSD.ORG Wed Oct 1 05:35:55 2008 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 A07B31065694 for ; Wed, 1 Oct 2008 05:35:55 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id 586858FC29 for ; Wed, 1 Oct 2008 05:35:55 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1KkuNM-0005Kr-PX; Wed, 01 Oct 2008 08:35:52 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Andrew Snow In-reply-to: <48E300CB.8070808@modulus.org> References: <35FAB782-F576-4FB7-8633-67CFB63D9389@stromnet.se> <48E300CB.8070808@modulus.org> Comments: In-reply-to Andrew Snow message dated "Wed, 01 Oct 2008 14:47:07 +1000." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Oct 2008 08:35:52 +0300 From: Danny Braniss Message-ID: Cc: freebsd-scsi@freebsd.org Subject: Re: state of iscsi_initiator? 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, 01 Oct 2008 05:35:55 -0000 > > I'm just playing with iSCSI now, on a fresh 7.1-STABLE machine connected > to another FreeBSD box running ports/net/iscsi-target. > > I am using the latest version 2.1 Initiator from: > ftp://ftp.cs.huji.ac.il/users/danny/freebsd/ > > It seems alot better now than when I last tried it. The speed is > constant at around 50MB/s for a single sequential read or write. It > also reconnected very quickly when I restarted the target. I was even > able to reboot the target box and I/O resumed perfectly once it finished > booting! > > The speed increased to 80mb/s when I ran two threads, which is close to > the max performance for the network cards in this machine. > > > A couple of minor issues: > > 1. Trouble shutting down iscontrol - after I kill -9 it stays around > for a minute or more until it finally goes away. > you should kill -1, this does an orderly shutdown of the connection. I guess an update to the manual is needed. > 2. Under very heavy multi-threaded load, the client machine gets > sluggish to respond, even to keystrokes on the console. And if I > shutdown the target, even local disk accesses on the client computer > stop working after a while. > > (I don't think this is a problem with iSCSI initiator. I suspect > there's something in FreeBSD which pauses all disk I/O if the length of > outstanding requests is too high, can anyone shed some light on this?) > I've noticed slugishness when a heavy fsck is running in the background - not iscsi related, so it seems that heavy disk IO is using up resources, but then again, the CPU is working :-) > > Overall, a pleasant experience and shows how much good work has been > done on iSCSI. Congratulations Danny :-) > thanks, danny From owner-freebsd-scsi@FreeBSD.ORG Wed Oct 1 11:02:20 2008 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 8C5A41065693 for ; Wed, 1 Oct 2008 11:02:20 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from core.stromnet.se (core.stromnet.se [83.218.84.131]) by mx1.freebsd.org (Postfix) with ESMTP id 19A8A8FC5D for ; Wed, 1 Oct 2008 11:02:20 +0000 (UTC) (envelope-from johan@stromnet.se) Received: from localhost (core.stromnet.se [83.218.84.131]) by core.stromnet.se (Postfix) with ESMTP id E25AEFB31EE; Wed, 1 Oct 2008 13:02:14 +0200 (CEST) X-Virus-Scanned: amavisd-new at stromnet.se X-Spam-Flag: NO X-Spam-Score: -1.136 X-Spam-Level: X-Spam-Status: No, score=-1.136 tagged_above=-1000 required=6.2 tests=[AWL=0.670, BAYES_00=-2.599, RDNS_DYNAMIC=0.1, SPF_FAIL=0.693] Received: from core.stromnet.se ([83.218.84.131]) by localhost (core.stromnet.se [83.218.84.131]) (amavisd-new, port 10024) with ESMTP id jnGdkEg8sE15; Wed, 1 Oct 2008 13:02:12 +0200 (CEST) Received: from johan-mp.stromnet.se (78-69-139-60-no129.tbcn.telia.com [78.69.139.60]) by core.stromnet.se (Postfix) with ESMTP id 482CCFB31E6; Wed, 1 Oct 2008 13:02:12 +0200 (CEST) Message-Id: From: =?ISO-8859-1?Q?Johan_Str=F6m?= To: Danny Braniss In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Wed, 1 Oct 2008 13:02:11 +0200 References: <35FAB782-F576-4FB7-8633-67CFB63D9389@stromnet.se> <48E300CB.8070808@modulus.org> X-Mailer: Apple Mail (2.929.2) Cc: freebsd-scsi@freebsd.org Subject: Re: state of iscsi_initiator? 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, 01 Oct 2008 11:02:20 -0000 On Oct 1, 2008, at 7:35 AM, Danny Braniss wrote: >> >> I'm just playing with iSCSI now, on a fresh 7.1-STABLE machine >> connected >> to another FreeBSD box running ports/net/iscsi-target. >> >> I am using the latest version 2.1 Initiator from: >> ftp://ftp.cs.huji.ac.il/users/danny/freebsd/ >> >> It seems alot better now than when I last tried it. The speed is >> constant at around 50MB/s for a single sequential read or write. It >> also reconnected very quickly when I restarted the target. I was >> even >> able to reboot the target box and I/O resumed perfectly once it >> finished >> booting! >> >> >> The speed increased to 80mb/s when I ran two threads, which is >> close to >> the max performance for the network cards in this machine. Nice, I guess. Wonder how much one can get up to with 1GBit.. Altough then I guess thats when the disks will be the limiting factor. As for recovery, that have been working pretty nice for me to, I've been running 2 VMWare machines here (on the same physcal box), one with OpenFiler and one with 7.0-STABLE (and 2.0.99 iscsi). I've been running iozone for a couple of hours, without any crashes or so at least. I also tried rebooting the openfiler in the middle of the iozone process with the following results (where the numbers are iozone output): 2048 128 2111 3961 2547261 2190626 2048 256 4405 4363 2443638 2233342 2048 512iscontrol[3687]: trapped signal 30 trapped signal 30 iscontrol: supervise going down iscontrol[3687]: sess flags=2000040d iscontrol[3687]: Reconnect errno=61 connect: Connection refused iscontrol[3687]: Reconnect iscontrol: supervise starting main loop 21 4271 1391257 2098062 2048 1024 4053 4151 2389263 4113514 2048 2048 3634 5330 2233342 3475985 4096 4 2860 3947 1648862 1836000 Yes iscontrol was started from the same console earlier. Regarding that, I noticed that the 2.1 version had a daemonized version. is there any changelog for 2.1? >> >> >> >> A couple of minor issues: >> >> 1. Trouble shutting down iscontrol - after I kill -9 it stays >> around >> for a minute or more until it finally goes away. >> > > you should kill -1, this does an orderly shutdown of the connection. > I guess an update to the manual is needed. > >> 2. Under very heavy multi-threaded load, the client machine gets >> sluggish to respond, even to keystrokes on the console. And if I >> shutdown the target, even local disk accesses on the client computer >> stop working after a while. If you take the target back up, does it wake up again? >> >> >> (I don't think this is a problem with iSCSI initiator. I suspect >> there's something in FreeBSD which pauses all disk I/O if the >> length of >> outstanding requests is too high, can anyone shed some light on >> this?) >> > I've noticed slugishness when a heavy fsck is running in the > background - not > iscsi related, so it seems that heavy disk IO is using up resources, > but > then again, the CPU is working :-) Thanks for your input :) From owner-freebsd-scsi@FreeBSD.ORG Fri Oct 3 19:20:10 2008 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 151D91065699 for ; Fri, 3 Oct 2008 19:20:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8E21D8FC0C for ; Fri, 3 Oct 2008 19:20:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m93JK9YQ008180 for ; Fri, 3 Oct 2008 19:20:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m93JK9L5008179; Fri, 3 Oct 2008 19:20:09 GMT (envelope-from gnats) Date: Fri, 3 Oct 2008 19:20:09 GMT Message-Id: <200810031920.m93JK9L5008179@freefall.freebsd.org> To: freebsd-scsi@FreeBSD.org From: Alexander Sack Cc: Subject: Re: kern/126866: [isp] [panic] kernel panic on card initialization X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alexander Sack List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Oct 2008 19:20:10 -0000 The following reply was made to PR kern/126866; it has been noted by GNATS. From: Alexander Sack To: bug-followup@FreeBSD.org, westr@connection.ca Cc: Subject: Re: kern/126866: [isp] [panic] kernel panic on card initialization Date: Fri, 3 Oct 2008 14:39:14 -0400 --Apple-Mail-13--61181355 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit The main problem is if you issue a firmware MAILBOX command before you quiesce the ISP then you will wound up handling async events to early at attach time. I've moved checking for the reset signature further down the isp_reset() path as well as remove checking OUTMAILBOX3 (OUTMAILBOX3 is really isp->isp_type (but its a string), if you see the 'ISP' characters in OUTMAILBOX1 and 2 then we assume the soft reset sequence worked and we can move on). Note the ABOUT FIRMWARE command seems to fail on ISP24xx after a reset until the EXEC occurs. We might want to rehash this sequence at some point but for now, we either load via dodnld or we don't via loader.conf parameter., i.e. we are still not checking which firmware is newer the one on the card or the one shipped with the driver. I also removed putting the ISP24xx into PAUSE mode - I don't see the reason for this since we only touch SXP and FPM/FBM registers for non- ISP24xx cards. Note I have another patch to fix some firmware related issues as well which I will coordinate with this fix... -aps --Apple-Mail-13--61181355 Content-Disposition: attachment; filename=isp.c.patch Content-Type: application/octet-stream; x-unix-mode=0644; name="isp.c.patch" Content-Transfer-Encoding: 7bit --- isp.c Tue Sep 30 18:09:42 2008 +++ isp.c.fix Fri Oct 3 14:27:48 2008 @@ -171,60 +171,6 @@ isp->isp_state = ISP_NILSTATE; - /* - * Basic types (SCSI, FibreChannel and PCI or SBus) - * have been set in the MD code. We figure out more - * here. Possibly more refined types based upon PCI - * identification. Chip revision has been gathered. - * - * After we've fired this chip up, zero out the conf1 register - * for SCSI adapters and do other settings for the 2100. - */ - - /* - * Get the current running firmware revision out of the - * chip before we hit it over the head (if this is our - * first time through). Note that we store this as the - * 'ROM' firmware revision- which it may not be. In any - * case, we don't really use this yet, but we may in - * the future. - */ - if (isp->isp_touched == 0) { - /* - * First see whether or not we're sitting in the ISP PROM. - * If we've just been reset, we'll have the string "ISP " - * spread through outgoing mailbox registers 1-3. We do - * this for PCI cards because otherwise we really don't - * know what state the card is in and we could hang if - * we try this command otherwise. - * - * For SBus cards, we just do this because they almost - * certainly will be running firmware by now. - */ - if (ISP_READ(isp, OUTMAILBOX1) != 0x4953 || - ISP_READ(isp, OUTMAILBOX2) != 0x5020 || - ISP_READ(isp, OUTMAILBOX3) != 0x2020) { - /* - * Just in case it was paused... - */ - if (IS_24XX(isp)) { - ISP_WRITE(isp, BIU2400_HCCR, - HCCR_2400_CMD_RELEASE); - } else { - ISP_WRITE(isp, HCCR, HCCR_CMD_RELEASE); - } - MEMZERO(&mbs, sizeof (mbs)); - mbs.param[0] = MBOX_ABOUT_FIRMWARE; - mbs.logval = MBLOGNONE; - isp_mboxcmd(isp, &mbs); - if (mbs.param[0] == MBOX_COMMAND_COMPLETE) { - isp->isp_romfw_rev[0] = mbs.param[1]; - isp->isp_romfw_rev[1] = mbs.param[2]; - isp->isp_romfw_rev[2] = mbs.param[3]; - } - } - isp->isp_touched = 1; - } ISP_DISABLE_INTS(isp); @@ -279,13 +225,13 @@ } /* - * Put the board into PAUSE mode (so we can read the SXP registers + * XXX: For 23xx and earlier, put the board into + * PAUSE mode (so we can read the SXP registers * or write FPM/FBM registers). */ if (IS_24XX(isp)) { ISP_WRITE(isp, BIU2400_HCCR, HCCR_2400_CMD_CLEAR_HOST_INT); ISP_WRITE(isp, BIU2400_HCCR, HCCR_2400_CMD_CLEAR_RISC_INT); - ISP_WRITE(isp, BIU2400_HCCR, HCCR_2400_CMD_PAUSE); } else { ISP_WRITE(isp, HCCR, HCCR_CMD_PAUSE); } @@ -675,6 +621,61 @@ ISP_WRITE(isp, HCCR, HCCR_CMD_RELEASE); } + /* + * Basic types (SCSI, FibreChannel and PCI or SBus) + * have been set in the MD code. We figure out more + * here. Possibly more refined types based upon PCI + * identification. Chip revision has been gathered. + * + * After we've fired this chip up, zero out the conf1 register + * for SCSI adapters and do other settings for the 2100. + */ + + /* + * Get the current running firmware revision out of the + * chip before we hit it over the head (if this is our + * first time through). Note that we store this as the + * 'ROM' firmware revision- which it may not be. In any + * case, we don't really use this yet, but we may in + * the future. + */ + if (isp->isp_touched == 0) { + /* + * First see whether or not we're sitting in the ISP PROM. + * If we've just been reset, we'll have the string "ISP " + * spread through outgoing mailbox registers 1-3. We do + * this for PCI cards because otherwise we really don't + * know what state the card is in and we could hang if + * we try this command otherwise. + * + * For SBus cards, we just do this because they almost + * certainly will be running firmware by now. + */ + if (ISP_READ(isp, OUTMAILBOX1) != 0x4953 || + ISP_READ(isp, OUTMAILBOX2) != 0x5020) { + isp_prt(isp, ISP_LOGERR, "reset signature was invalid, RISC maybe paused"); + /* + * Just in case it was paused... + */ + if (IS_24XX(isp)) { + ISP_WRITE(isp, BIU2400_HCCR, + HCCR_2400_CMD_RELEASE); + } else { + ISP_WRITE(isp, HCCR, HCCR_CMD_RELEASE); + MEMZERO(&mbs, sizeof (mbs)); + mbs.param[0] = MBOX_ABOUT_FIRMWARE; + mbs.logval = MBLOGNONE; + isp_mboxcmd(isp, &mbs); + if (mbs.param[0] == MBOX_COMMAND_COMPLETE) { + isp->isp_romfw_rev[0] = mbs.param[1]; + isp->isp_romfw_rev[1] = mbs.param[2]; + isp->isp_romfw_rev[2] = mbs.param[3]; + } + } + } + isp->isp_touched = 1; + } + ISP_WRITE(isp, isp->isp_rqstinrp, 0); ISP_WRITE(isp, isp->isp_rqstoutrp, 0); ISP_WRITE(isp, isp->isp_respinrp, 0); @@ -738,6 +739,7 @@ mbs.logval = MBLOGALL; isp_mboxcmd(isp, &mbs); if (mbs.param[0] != MBOX_COMMAND_COMPLETE) { + isp_prt(isp, ISP_LOGERR, "Mailbox Register Test mailbox command failed to complete"); ISP_RESET0(isp); return; } @@ -1832,7 +1834,6 @@ mbs.logval = MBLOGALL; isp_mboxcmd(isp, &mbs); if (mbs.param[0] != MBOX_COMMAND_COMPLETE) { - isp_prt(isp, ISP_LOGERR, "setting firmware options failed"); return; } @@ -2056,7 +2057,6 @@ isp_mboxcmd(isp, &mbs); FC_SCRATCH_RELEASE(isp); if (mbs.param[0] != MBOX_COMMAND_COMPLETE) { - isp_prt(isp, ISP_LOGERR, "initialization of firmware fails"); return; } isp->isp_reqidx = 0; --Apple-Mail-13--61181355 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit --Apple-Mail-13--61181355--