From owner-freebsd-scsi@FreeBSD.ORG Mon Aug 20 11:08:02 2012 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 52E8B106567A for ; Mon, 20 Aug 2012 11:08:02 +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 3BD8B8FC1D for ; Mon, 20 Aug 2012 11:08:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7KB826E048063 for ; Mon, 20 Aug 2012 11:08:02 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7KB81PF048050 for freebsd-scsi@FreeBSD.org; Mon, 20 Aug 2012 11:08:01 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 20 Aug 2012 11:08:01 GMT Message-Id: <201208201108.q7KB81PF048050@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, 20 Aug 2012 11:08:02 -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/169976 scsi [cam] [patch] make scsi_da use sysctl values where app o kern/169974 scsi [cam] [patch] add Quirks for SSD that are 4k optimised o kern/169835 scsi [patch] remove some unused variables from scsi_da prob o kern/169801 scsi [cam] [patc] make changes to delete_method in scsi_da o kern/169403 scsi [cam] [patch] CAM layer, I/O starvation, no fairness o kern/165982 scsi [mpt] mpt instability, drive resets, and losses on Fre o kern/165740 scsi [cam] SCSI code must drain callbacks before free o kern/163713 scsi [aic7xxx] [patch] Add Adaptec29329LPE to aic79xx_pci.c o kern/162256 scsi [mpt] QUEUE FULL EVENT and 'mpt_cam_event: 0x0' o kern/161809 scsi [cam] [patch] set kern.cam.boot_delay via build option o kern/159412 scsi [ciss] 7.3 RELEASE: ciss0 ADAPTER HEARTBEAT FAILED err o kern/157770 scsi [iscsi] [panic] iscsi_initiator panic o kern/154432 scsi [xpt] run_interrupt_driven_hooks: still waiting after o kern/153514 scsi [cam] [panic] CAM related panic o kern/153361 scsi [ciss] Smart Array 5300 boot/detect drive problem o kern/152250 scsi [ciss] [patch] Kernel panic when hw.ciss.expose_hidden o kern/151564 scsi [ciss] ciss(4) should increase CISS_MAX_LOGICAL to 10 o docs/151336 scsi Missing documentation of scsi_ and ata_ functions in c s kern/149927 scsi [cam] hard drive not stopped before removing power dur o kern/148083 scsi [aac] Strange device reporting o kern/147704 scsi [mpt] sys/dev/mpt: new chip revision, partially unsupp o kern/146287 scsi [ciss] ciss(4) cannot see more than one SmartArray con o kern/145768 scsi [mpt] can't perform I/O on SAS based SAN disk in freeb o kern/144648 scsi [aac] Strange values of speed and bus width in dmesg o kern/144301 scsi [ciss] [hang] HP proliant server locks when using ciss o kern/142351 scsi [mpt] LSILogic driver performance problems 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 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/127717 scsi [ata] [patch] [request] - support write cache toggling o kern/123674 scsi [ahc] ahc driver dumping o kern/123520 scsi [ahd] unable to boot from net while using ahd 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/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/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/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 55 problems total. From owner-freebsd-scsi@FreeBSD.ORG Tue Aug 21 10:33:47 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C81F11065670; Tue, 21 Aug 2012 10:33:47 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id 5B4968FC12; Tue, 21 Aug 2012 10:33:47 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.4/8.14.4/ALCHEMY.FRANKEN.DE) with ESMTP id q7LAXW1c089839; Tue, 21 Aug 2012 12:33:32 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.4/8.14.4/Submit) id q7LAXWCt089838; Tue, 21 Aug 2012 12:33:32 +0200 (CEST) (envelope-from marius) Date: Tue, 21 Aug 2012 12:33:32 +0200 From: Marius Strobl To: Alexander Motin Message-ID: <20120821103332.GA89798@alchemy.franken.de> References: <20120717151311.GA62358@mech-cluster241.men.bris.ac.uk> <500AD584.1020505@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <500AD584.1020505@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-scsi@freebsd.org Subject: Re: can't use cdrecord on -current - lots of warnigs, possible ATA_CAM issue? 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, 21 Aug 2012 10:33:47 -0000 On Sat, Jul 21, 2012 at 07:15:00PM +0300, Alexander Motin wrote: > On 17.07.2012 18:13, Anton Shterenlikht wrote: > >I thought this was a sparc64 issue, > >but marius@ advised to ask for help > >in this list. > > > >I've rebuild sysutils/cdrecord (I also tried sysutils/cdrecord-devel) > >multiple times. > > > >Thanks > > > >----- Forwarded message from Anton Shterenlikht ----- > > > > > ># uname -a > >FreeBSD mech-anton240.men.bris.ac.uk 10.0-CURRENT FreeBSD 10.0-CURRENT #6 > >r235474: Tue Jul 17 13:52:07 BST 2012 > >root@mech-anton240.men.bris.ac.uk:/usr/obj/usr/src/sys/QOF sparc64 > ># > > > >After updating to ATA_CAM framework > >I cannot use cdrecord: > > > ># cdrecord -dev=1,0,0 -sao /home/mexas/FreeBSD-8.1-RELEASE-ia64-livefs.iso > >Cdrecord-ProDVD-ProBD-Clone 3.01a07 (sparc64-unknown-freebsd10.0) > >Copyright (C) > >1995-2012 Joerg Schilling > >scsidev: '1,0,0' > >scsibus: 1 target: 0 lun: 0 > >Using libscg version 'schily-0.9'. > >Device type : Removable CD-ROM > >Version : 0 > >Response Format: 2 > >Capabilities : > >Vendor_info : 'TSSTcorp' > >Identifikation : 'CDW/DVD TS-H492C' > >Revision : 'SI00' > >Device seems to be: Generic mmc2 DVD-ROM. > >cdrecord: Warning: controller returns zero sized CD write parameter page. > >cdrecord: Warning: controller returns wrong size for CD write parameter > >page. > >cdrecord: Warning: controller returns wrong page 0 for CD write parameter > >page ( > >5). > >Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). > >Driver flags : MMC-3 SWABAUDIO BURNFREE > >Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R > >cdrecord: Warning: Cannot read drive buffer. > >cdrecord: Warning: The DMA speed test has been skipped. > >resid: 2 > >resid: 24 > >DMA overrun, resid: -24 > >resid: 30 > >cdrecord: Warning: controller returns zero sized CD write parameter page. > >cdrecord: Warning: controller returns wrong size for CD write parameter > >page. > >cdrecord: Warning: controller returns wrong page 0 for CD write parameter > >page ( > >5). > >cdrecord: Warning: controller returns zero sized CD write parameter page. > >cdrecord: Warning: controller returns wrong size for CD write parameter > >page. > >cdrecord: Warning: controller returns wrong page 0 for CD write parameter > >page ( > >5). > >cdrecord: Cannot init drive. > ># > > > > > >while on the console: > > > > > >ata3: unknown transfer phase > >ata3: WARNING - MODE_SENSE_BIG read data overrun 2>0 > >ata3: WARNING - MODE_SENSE_BIG read data overrun 2>0 > >ata3: WARNING - MODE_SENSE_BIG read data overrun 2>0 > >ata3: WARNING - MODE_SENSE_BIG read data overrun 2>0 > >ata3: WARNING - MODE_SENSE_BIG read data overrun 2>0 > >ata3: WARNING - MODE_SENSE_BIG read data overrun 2>0 > >ata3: WARNING - MODE_SENSE_BIG read data overrun 2>0 > >ata3: WARNING - MODE_SENSE_BIG read data overrun 2>0 > >ata3: WARNING - TEST_UNIT_READY read data overrun 2>0 > >ata3: WARNING - TEST_UNIT_READY read data overrun 60>0 > >ata3: WARNING - TEST_UNIT_READY read data overrun 10>0 > >ata3: WARNING - READ_BUFFER read data overrun 4>0 > >ata3: WARNING - START_STOP read data overrun 18>0 > >ata3: WARNING - TEST_UNIT_READY read data overrun 16>0 > >ata3: WARNING - READ_CAPACITY read data overrun 8>0 > >ata3: WARNING - READ_TOC read data overrun 4>0 > >ata3: WARNING - READ_TOC read data overrun 2>0 > >ata3: WARNING - READ_DISK_INFO read data overrun 4>0 > >ata3: WARNING - READ_DISK_INFO read data overrun 4>0 > >ata3: WARNING - READ_DISK_INFO read data overrun 4>0 > >ata3: WARNING - READ_DISK_INFO read data overrun 4>0 > >ata3: WARNING - READ_DISK_INFO read data overrun 4>0 > >ata3: WARNING - READ_DISK_INFO read data overrun 4>0 > >ata3: WARNING - TEST_UNIT_READY read data overrun 34>0 > >ata3: WARNING - TEST_UNIT_READY read data overrun 2>0 > >ata3: WARNING - TEST_UNIT_READY read data overrun 2>0 > >ata3: WARNING - TEST_UNIT_READY read data overrun 10>0 > >ata3: WARNING - TEST_UNIT_READY read data overrun 2>0 > >ata3: WARNING - TEST_UNIT_READY read data overrun 2>0 > >ata3: WARNING - TEST_UNIT_READY read data overrun 2>0 > >ata3: WARNING - TEST_UNIT_READY read data overrun 10>0 > >ata3: WARNING - SYNCHRONIZE_CACHE read data overrun 2>0 > > > > > ># dmesg|grep cd0 > >cd0 at ata3 bus 0 scbus1 target 0 lun 0 > >cd0: Removable CD-ROM SCSI-0 device > >cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) > >cd0: Attempt to query device size failed: NOT READY, Medium not present - > >tray c > >losed > ># > > I can't reproduce your problem on my Sun Blade 100. I've fixed two other > problems in ata(4) I've found in process (r238666 and r238673) and now I > can successfully record CD with both cdrtools and cdrtools-devel. > Thanks a lot! Could you please MFC these fixes to 8/9/9.1 as apparently r238666 affects all and r238673 at least all !x86 architectures and not just sparc64? Also, could you please look into why ATA_CAM breaks ATAPI CAM/ causes data corruption for/with certain controllers driven by ata(4)? At least the the ALi ATA controller in Blade 100, which AFAIK you own one of, is affected, but again, this problem is also seen with ITE ones on x86. Marius From owner-freebsd-scsi@FreeBSD.ORG Wed Aug 22 05:44:13 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 726D41065675; Wed, 22 Aug 2012 05:44:13 +0000 (UTC) (envelope-from aoyama@peach.ne.jp) Received: from moon.peach.ne.jp (moon.peach.ne.jp [203.141.148.98]) by mx1.freebsd.org (Postfix) with ESMTP id 97FF48FC14; Wed, 22 Aug 2012 05:44:12 +0000 (UTC) Received: from moon.peach.ne.jp (localhost [127.0.0.1]) by moon.peach.ne.jp (Postfix) with ESMTP id 930EF39D4E; Wed, 22 Aug 2012 14:44:04 +0900 (JST) Received: from artemis (unknown [172.18.0.20]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by moon.peach.ne.jp (Postfix) with ESMTPSA id 7FDCF39D4A; Wed, 22 Aug 2012 14:44:04 +0900 (JST) Message-ID: From: "Daisuke Aoyama" To: Date: Wed, 22 Aug 2012 14:43:50 +0900 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-2022-jp"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-stable@freebsd.org Subject: iSCSI boot driver 0.2.5 (isboot.ko) has been released. 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, 22 Aug 2012 05:44:13 -0000 You can download the source file from: http://www.peach.ne.jp/archives/isboot/isboot-0.2.5.tar.gz Also, you can download a demo version of 9.1-BETA1. http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-9.1-BETA1-amd64-memstick-isboot-0.2.5.img This demo version is added isboot.txz which includes isboot.ko and loader.conf and a syscons patched kernel for DN2800MT. You can use it as istgt's LUN extent like this: ---------------------------------------------------------------------- [LogicalUnit2800] TargetName "iqn.2007-09.jp.ne.peach:aria:dn2800mt-boot" Mapping PortalGroup4 InitiatorGroup2800 UnitType Disk QueueDepth 32 LUN0 Storage /tank/iscsi/istgt-DN2800MT.vdi Auto LUN1 Storage /tank/iscsi/FreeBSD-9.1-BETA1-amd64-memstick-isboot-0.2.5.img Auto ---------------------------------------------------------------------- Then, boot FreeBSD installer from LUN1 and install FreeBSD by normal way to LUN0. After installation, you have an iSCSI based diskless machine. I have tested it with iPXE(USB boot) and Intel Desktop Board DN2800MT without using SATA ports. For example, booting LUN1 by iPXE(just use :::1:): sanboot iscsi:172.18.0.26:::1:iqn.2007-09.jp.ne.peach:aria:dn2800mt-boot For more info of Japanese is here: http://shell.peach.ne.jp/aoyama/archives/2097 http://shell.peach.ne.jp/aoyama/archives/2100 Have fun! Daisuke Aoyama From owner-freebsd-scsi@FreeBSD.ORG Thu Aug 23 05:31:24 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 54625106566B; Thu, 23 Aug 2012 05:31:24 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (secure.freebsdsolutions.net [69.55.234.48]) by mx1.freebsd.org (Postfix) with ESMTP id 348F58FC16; Thu, 23 Aug 2012 05:31:23 +0000 (UTC) Received: from [192.168.2.82] (jn@c-67-182-217-170.hsd1.ut.comcast.net [67.182.217.170]) (authenticated bits=0) by ns1.jnielsen.net (8.14.4/8.14.4) with ESMTP id q7N5OJQx068596 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 23 Aug 2012 01:24:20 -0400 (EDT) (envelope-from lists@jnielsen.net) Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\)) Content-Type: text/plain; charset=iso-2022-jp From: John Nielsen X-Priority: 3 In-Reply-To: Date: Wed, 22 Aug 2012 23:24:37 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <02E5BFB9-901B-4AA3-9594-160C3259AE66@jnielsen.net> References: To: Daisuke Aoyama X-Mailer: Apple Mail (2.1485) X-DCC-sonic.net-Metrics: ns1.jnielsen.net 1117; Body=3 Fuz1=3 Fuz2=3 X-Virus-Scanned: clamav-milter 0.97.5 at ns1.jnielsen.net X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org Subject: Re: iSCSI boot driver 0.2.5 (isboot.ko) has been released. 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, 23 Aug 2012 05:31:24 -0000 On Aug 21, 2012, at 11:43 PM, Daisuke Aoyama wrote: > You can download the source file from: > http://www.peach.ne.jp/archives/isboot/isboot-0.2.5.tar.gz > ... Daisuke-san- Thank you for this great work! I can see a lot of potential applications = for it. I set up a test machine and got as far as booting the FreeBSD = 10-CURRENT kernel from an istgt LUN, but it failed to find the root = device--the isboot.ko module loaded fine but the iBFT handoff didn't = happen so the network was not configured early enough. This machine has = an sk(4) NIC, and I am chain-loading gPXE using the "undionly.kpxe" = image. I have a few questions for you (or other knowledgeable people on the = list): 1) Does iBFT require hardware support in the NIC? 2) Does iBFT require NIC driver support? 3) Is anything required in loader.conf besides = isboot_load=3D"YES"? 3) How hard would it be to get this working with sk(4)? 4) Is it likely to work (better) if I find an em(4) card = instead? Thanks, JN From owner-freebsd-scsi@FreeBSD.ORG Fri Aug 24 00:25:31 2012 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 AA863106566B; Fri, 24 Aug 2012 00:25:31 +0000 (UTC) (envelope-from aoyama@peach.ne.jp) Received: from moon.peach.ne.jp (moon.peach.ne.jp [203.141.148.98]) by mx1.freebsd.org (Postfix) with ESMTP id 494D38FC08; Fri, 24 Aug 2012 00:25:30 +0000 (UTC) Received: from moon.peach.ne.jp (localhost [127.0.0.1]) by moon.peach.ne.jp (Postfix) with ESMTP id 12CF539D4F; Fri, 24 Aug 2012 09:25:24 +0900 (JST) Received: from artemis (unknown [172.18.0.20]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by moon.peach.ne.jp (Postfix) with ESMTPSA id 0EB1D39D4E; Fri, 24 Aug 2012 09:25:24 +0900 (JST) Message-ID: <143B56D7A14648EF98B8FE876080D497@ad.peach.ne.jp> From: "Daisuke Aoyama" To: "John Nielsen" References: <02E5BFB9-901B-4AA3-9594-160C3259AE66@jnielsen.net> In-Reply-To: <02E5BFB9-901B-4AA3-9594-160C3259AE66@jnielsen.net> Date: Fri, 24 Aug 2012 09:25:16 +0900 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-2022-jp"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org Subject: Updated isboot 0.2.6 and FreeBSD 9.1-RC1 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, 24 Aug 2012 00:25:31 -0000 Hi, Thank you for reporting. It seems a bug of isboot. Your NIC is link down, but isboot never retry on first connection. Because of this, it failed to find the boot device. I have updated isboot and created 9.1-RC based image. Please try it: http://www.peach.ne.jp/archives/isboot/isboot-0.2.6.tar.gz http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-9.1-RC1-amd64-memstick-isboot-0.2.6.img > I have a few questions for you (or other knowledgeable people on the > list): > 1) Does iBFT require hardware support in the NIC? > 2) Does iBFT require NIC driver support? NO. You can use both iBFT software like gPXE and NIC's rom like Intel iSCSI boot agent. The isboot should work with any NIC supported by FreeBSD. > 3) Is anything required in loader.conf besides isboot_load="YES"? If your NIC driver is within the kernel, you need only isboot_load="YES". > 4) Is it likely to work (better) if I find an em(4) card instead? I have tested with Intel cards/onboard. If you want the maximum performance, I recommend you to use Intel card, but other cards should work with isboot. This is my log of ASRock E350M1/USB3(re(4) + gPXE): ---------------------------------------------------------------------- iSCSI boot driver version 0.2.6 IS: Initiator name: iqn.2000-09.org.etherboot:e350m1 NIC0: IP address: 172.18.0.131 NIC0: Prefix: 16 NIC0: Gateway: 172.18.0.1 NIC0: MAC address: 00:25:22:b3:b7:a7 TGT0: Target IP address: 172.18.0.26 TGT0: Target Port: 3260 TGT0: Target LUN: 0 TGT0: Target name: iqn.2007-09.jp.ne.peach:aria:e350m1-boot Boot NIC: re0 Configure IPv4 by NIC0 (snip) da1 at isboot0 bus 0 scbus8 target 0 lun 0 da1: Fixed Direct Access SCSI-5 device da1: 300.000MB/s transfers da1: 20480MB (41943040 512 byte sectors: 255H 63S/T 2610C) da0 at umass-sim0 bus 0 scbus7 target 0 lun 0 da0: < USB Reader 0001> Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 1882MB (3854336 512 byte sectors: 255H 63S/T 239C) da2 at isboot0 bus 0 scbus8 target 0 lun 1 da2: Fixed Direct Access SCSI-5 device da2: 300.000MB/s transfers da2: 681MB (1395264 512 byte sectors: 64H 32S/T 681C) Boot device: da1 SMP: AP CPU #1 Launched! Timecounter "TSC-low" frequency 12500234 Hz quality 800 GEOM: da0: the primary GPT table is corrupt or invalid. GEOM: da0: using the secondary instead -- recovery strongly advised. GEOM: da2: geometry does not match label (32h,63s != 64h,32s). GEOM: ufsid/5029dbce6b8b4567: geometry does not match label (32h,63s != 64h,32s). GEOM: ufs/FreeBSD_Install: geometry does not match label (32h,63s != 64h,32s). Trying to mount root from ufs:/dev/da1p2 [rw]... ---------------------------------------------------------------------- Thanks, Daisuke Aoyama From owner-freebsd-scsi@FreeBSD.ORG Fri Aug 24 02:08:31 2012 Return-Path: Delivered-To: freebsd-scsi@FreeBSD.org Received: by hub.freebsd.org (Postfix, from userid 821) id D87A5106566B; Fri, 24 Aug 2012 02:08:31 +0000 (UTC) Date: Fri, 24 Aug 2012 02:08:31 +0000 From: John To: FreeBSD SCSI Message-ID: <20120824020831.GA72562@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: 9.1-PRERELEASE Performance slowdown with gmultipath Active/Active 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, 24 Aug 2012 02:08:31 -0000 Hi Folks, A colleague was setting up a system and noticed some performance differences. After poking around for a while, we found that gmultipath in active/active mode is slower than active/passive: #gmultipath configure -A Z181 #gmultipath status Z181 Name Status Components multipath/Z181 OPTIMAL da180 (ACTIVE) da372 (ACTIVE) #dd if=/dev/da180 of=/dev/null bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 0.690743 secs (151804079 bytes/sec) #dd if=/dev/da372 of=/dev/null bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 0.681540 secs (153853916 bytes/sec) #dd if=/dev/multipath/Z181 of=/dev/null bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 1.531437 secs (68470064 bytes/sec) Above, note the multipath device is 2x slower. #gmultipath configure -P Z181 #gmultipath status Z181 Name Status Components multipath/Z181 OPTIMAL da180 (ACTIVE) da372 (PASSIVE) #dd if=/dev/da180 of=/dev/null bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 0.691087 secs (151728507 bytes/sec) #dd if=/dev/da372 of=/dev/null bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 0.681589 secs (153842830 bytes/sec) #dd if=/dev/multipath/Z181 of=/dev/null bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 0.681605 secs (153839278 bytes/sec) In A/P mode, the performance is equal. #gmultipath rotate Z181 #gmultipath status Z181 Name Status Components multipath/Z181 OPTIMAL da180 (PASSIVE) da372 (ACTIVE) #dd if=/dev/da180 of=/dev/null bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 0.685385 secs (152990803 bytes/sec) #dd if=/dev/da372 of=/dev/null bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 0.681613 secs (153837395 bytes/sec) #dd if=/dev/multipath/Z181 of=/dev/null bs=1m count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 0.681614 secs (153837233 bytes/sec) Using the other path the performance is also the same. The drives: # camcontrol inquiry da180 pass190: Fixed Direct Access SCSI-5 device pass190: Serial Number EA01PB70SKG41128 pass190: 600.000MB/s transfers, Command Queueing Enabled # camcontrol inquiry da372 pass390: Fixed Direct Access SCSI-5 device pass390: Serial Number EA01PB70SKG41128 pass390: 600.000MB/s transfers, Command Queueing Enabled A complete dmesg from the system - a 9.1-prerelease FreeBSD 9.1-PRERELEASE #0 r239482M: Tue Aug 21 22:49:16 EDT 2012 here: http://people.freebsd.org/~jwd/dmesg.boot.txt Any thoughts on what this might be or the best way to debug it? Thanks, John From owner-freebsd-scsi@FreeBSD.ORG Sat Aug 25 02:47:53 2012 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 CE8271065673; Sat, 25 Aug 2012 02:47:53 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (secure.freebsdsolutions.net [69.55.234.48]) by mx1.freebsd.org (Postfix) with ESMTP id AD1C58FC0C; Sat, 25 Aug 2012 02:47:53 +0000 (UTC) Received: from [192.168.2.82] (jn@c-67-182-217-170.hsd1.ut.comcast.net [67.182.217.170]) (authenticated bits=0) by ns1.jnielsen.net (8.14.4/8.14.4) with ESMTP id q7P2liI6098049 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 24 Aug 2012 22:47:44 -0400 (EDT) (envelope-from lists@jnielsen.net) Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\)) Content-Type: text/plain; charset=iso-2022-jp From: John Nielsen X-Priority: 3 In-Reply-To: <143B56D7A14648EF98B8FE876080D497@ad.peach.ne.jp> Date: Fri, 24 Aug 2012 20:48:01 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <02E5BFB9-901B-4AA3-9594-160C3259AE66@jnielsen.net> <143B56D7A14648EF98B8FE876080D497@ad.peach.ne.jp> To: Daisuke Aoyama X-Mailer: Apple Mail (2.1485) X-DCC-sonic.net-Metrics: ns1.jnielsen.net 1117; Body=3 Fuz1=3 Fuz2=3 X-Virus-Scanned: clamav-milter 0.97.5 at ns1.jnielsen.net X-Virus-Status: Clean Cc: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Updated isboot 0.2.6 and FreeBSD 9.1-RC1 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, 25 Aug 2012 02:47:54 -0000 Thank you for the quick response! On Aug 23, 2012, at 6:25 PM, Daisuke Aoyama wrote: > It seems a bug of isboot. Your NIC is link down, but isboot never = retry > on first connection. Because of this, it failed to find the boot = device. >=20 > I have updated isboot and created 9.1-RC based image. > Please try it: >=20 > http://www.peach.ne.jp/archives/isboot/isboot-0.2.6.tar.gz Working great with the new version of the module. It retries 3-4 times = until the link comes up then continues. Performing pretty well, = too--this is over a 1Gbps LAN on somewhat dated consumer hardware, with = istgt and a ZFS zvol on the other end. > = http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-9.1-RC1-amd64-memstick= -isboot-0.2.6.img >=20 >> I have a few questions for you (or other knowledgeable people on the = list): >> 1) Does iBFT require hardware support in the NIC? >> 2) Does iBFT require NIC driver support? >=20 > NO. You can use both iBFT software like gPXE and NIC's rom like Intel = iSCSI boot agent. > The isboot should work with any NIC supported by FreeBSD. Fantastic. >> 3) Is anything required in loader.conf besides isboot_load=3D"YES"? >=20 > If your NIC driver is within the kernel, you need only = isboot_load=3D"YES". >=20 >> 4) Is it likely to work (better) if I find an em(4) card instead? >=20 > I have tested with Intel cards/onboard. If you want the maximum = performance, > I recommend you to use Intel card, but other cards should work with = isboot. I'll stick with what I have for this machine since it's working. In case = you're interested, here is the dmesg output from the machine: mptable_probe: MP Config Table has bad signature: 4\^C\^_ Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights = reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-CURRENT #2 r239337M: Fri Aug 24 12:58:51 EDT 2012 root@stealth.jnielsen.net:/usr/obj/i386.i386/usr/src/sys/BUFF i386 CPU: AMD Athlon(tm) XP 2800+ (2079.60-MHz 686-class CPU) Origin =3D "AuthenticAMD" Id =3D 0x6a0 Family =3D 6 Model =3D a = Stepping =3D 0 = Features=3D0x383fbff AMD Features=3D0xc0400800 real memory =3D 1342177280 (1280 MB) avail memory =3D 1300516864 (1240 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 4fef0000 (3) failed cpu0: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x73 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 Correcting nForce2 C1 CPU disconnect hangs agp0: on hostb0 pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 0.5 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 nfsmb0: port 0xd800-0xd81f irq 23 at = device 1.1 on pci0 smbus0: on nfsmb0 nfsmb1: on nfsmb0 smbus1: on nfsmb1 ohci0: mem 0xe5085000-0xe5085fff irq 20 = at device 2.0 on pci0 usbus0 on ohci0 ohci1: mem 0xe5081000-0xe5081fff irq 21 = at device 2.1 on pci0 usbus1 on ohci1 ehci0: mem 0xe5082000-0xe50820ff irq = 22 at device 2.2 on pci0 usbus2: EHCI version 1.0 usbus2 on ehci0 pci0: at device 5.0 (no driver attached) pcm0: port 0xdc00-0xdcff,0xe000-0xe07f mem = 0xe5086000-0xe5086fff irq 21 at device 6.0 on pci0 pcm0: pcib1: at device 8.0 on pci0 pci1: on pcib1 skc0: port 0x9000-0x90ff mem = 0xe4020000-0xe4023fff irq 17 at device 4.0 on pci1 skc0: Marvell Yukon Lite Gigabit Ethernet rev. A3(0x7) sk0: on skc0 sk0: Ethernet address: 00:11:2f:57:f4:bf miibus0: on sk0 e1000phy0: PHY 0 on miibus0 e1000phy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, = 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto pci1: at device 7.0 (no driver attached) ath0: mem 0xe4010000-0xe401ffff irq 18 at device 8.0 on = pci1 [ath] enabling AN_TOP2_FIXUP ath0: DMA setup: legacy ath0: [HT] enabling HT modes ath0: [HT] 2 RX streams; 2 TX streams ath0: AR9220 mac 128.2 RF5133 phy 13.0 ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 atapci0: port = 0x9400-0x9407,0x9800-0x9803,0x9c00-0x9c07,0xa000-0xa003,0xa400-0xa40f = mem 0xe4024000-0xe40241ff irq 18 at device 11.0 on pci1 ata2: at channel 0 on atapci0 ata3: at channel 1 on atapci0 atapci1: port = 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 9.0 on pci0 ata0: at channel 0 on atapci1 ata1: at channel 1 on atapci1 fwohci0: <1394 Open Host Controller Interface> mem = 0xe5083000-0xe50837ff,0xe5084000-0xe508403f irq 22 at device 13.0 on = pci0 fwohci0: OHCI version 1.10 (ROM=3D0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:e0:18:00:00:8e:25:12 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwohci0: Initiate bus reset fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=3D0x00000000, SelfID Count=3D1, = CYCLEMASTER mode pcib2: at device 30.0 on pci0 pci3: on pcib2 vgapci0: port 0xc000-0xc0ff mem = 0xd8000000-0xdfffffff,0xe2000000-0xe207ffff irq 19 at device 0.0 on pci3 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on = acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] orm0: at iomem = 0xc0000-0xcbfff,0xcc000-0xcffff,0xd0000-0xd0fff pnpid ORM0000 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on = isa0 fdc0: No FDOUT register! ctl: CAM Target Layer loaded fwohci0: fwohci_intr_core: BUS reset firewire0: 1 nodes, maxhop <=3D 0 cable IRM irm(0) (me)=20 firewire0: bus manager 0=20 Timecounters tick every 1.000 msec iSCSI boot driver version 0.2.6 IS: Initiator name: iqn.2000-09.org.etherboot:UNKNOWN NIC0: IP address: 192.168.2.8 NIC0: Prefix: 24 NIC0: Gateway: 192.168.2.10 NIC0: MAC address: 00:11:2f:57:f4:bf TGT0: Target IP address: 192.168.2.10 TGT0: Target Port: 3260 TGT0: Target LUN: 0 TGT0: Target name: iqn.2007-09.jp.ne.peach.istgt:bsdvol Boot NIC: sk0 Configure IPv4 by NIC0 Attempting to login to iSCSI target and scan all LUNs. usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 480Mbps High Speed USB v2.0 connect error connect failed ugen0.1: at usbus0 uhub0: on = usbus0 ugen1.1: at usbus1 uhub1: on = usbus1 ugen2.1: at usbus2 uhub2: on = usbus2 uhub0: 3 ports with 3 removable, self powered uhub1: 3 ports with 3 removable, self powered connect error connect failed connect error connect failed uhub2: 6 ports with 6 removable, self powered fwohci0: fwohci_intr_core: BUS reset connect error connect failed ugen1.2: at usbus1 ukbd0: on usbus1 kbd2 at ukbd0 ada0 at ata0 bus 0 scbus2 target 0 lun 0 cd0 at ata1 bus 0 scbus3 target 0 lun 0 cd0: <_NEC DVD_RW ND-3550A 1.05> Removable CD-ROM SCSI-0 device=20 cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at isboot0 bus 0 scbus5 target 0 lun 0 da0: Fixed Direct Access SCSI-5 device=20 da0: 300.000MB/s transfers da0: 12288MB (25165824 512 byte sectors: 255H 63S/T 1566C) ada0: ATA-7 device ada0: 133.000MB/s transfers (UDMA6, PIO 8192bytes) ada0: 78167MB (160086528 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad0 ada1 at ata1 bus 0 scbus3 target 1 lun 0 ada1: ATA-7 device ada1: 133.000MB/s transfers (UDMA6, PIO 8192bytes) ada1: 78167MB (160086528 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad3 Boot device: da0 Timecounter "TSC" frequency 2079598782 Hz quality 800 Trying to mount root from ufs:/dev/gpt/bsdroot [rw]... uhid0: on usbus1 JN