From owner-freebsd-scsi@FreeBSD.ORG Mon Aug 27 11:07:22 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 95EF21065673 for ; Mon, 27 Aug 2012 11:07:22 +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 7F70C8FC22 for ; Mon, 27 Aug 2012 11:07:22 +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 q7RB7MBG085982 for ; Mon, 27 Aug 2012 11:07:22 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7RB7LMS085980 for freebsd-scsi@FreeBSD.org; Mon, 27 Aug 2012 11:07:21 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 27 Aug 2012 11:07:21 GMT Message-Id: <201208271107.q7RB7LMS085980@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, 27 Aug 2012 11:07:22 -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 28 12:59:58 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 0752E1065675 for ; Tue, 28 Aug 2012 12:59:58 +0000 (UTC) (envelope-from mikea@mikea.ath.cx) Received: from mikea.ath.cx (mikea.ath.cx [70.164.65.62]) by mx1.freebsd.org (Postfix) with ESMTP id 7E5748FC15 for ; Tue, 28 Aug 2012 12:59:57 +0000 (UTC) Received: from mikea.ath.cx (localhost [127.0.0.1]) by mikea.ath.cx (8.14.5/8.14.5) with ESMTP id q7SCxunE064982 for ; Tue, 28 Aug 2012 07:59:56 -0500 (CDT) (envelope-from mikea@mikea.ath.cx) Received: (from mikea@localhost) by mikea.ath.cx (8.14.5/8.14.5/Submit) id q7SCxuhO064981 for freebsd-scsi@freebsd.org; Tue, 28 Aug 2012 07:59:56 -0500 (CDT) (envelope-from mikea) Date: Tue, 28 Aug 2012 07:59:56 -0500 From: Mike A To: freebsd-scsi@freebsd.org Message-ID: <20120828125956.GA64922@mikea.ath.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): install fails with NMI 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, 28 Aug 2012 12:59:58 -0000 Hi. I'm posting this bug report here at the suggestion of Andriy Gapon, of the freebsd-amd64 list. The machine is, as stated in the Subject header, a shiny new IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e) I just got handed 4 of the subject boxes with instructions "put 'em to work". Naturally I tried FreeBSD first, on one of the machines. Boot from the 9.0 AMD64 boot-only install CD fails. Things look fine until the last several lines of the (verbose enabled) boot sequence, which (from an insufficiently-wide phone camera capture) are: " mpt0: port 0x3000-0x[lost off right edge of phone] xc5d00000-0xc5deffff irq 34 at device 0.0 on pci[lost] mpt0: attempting to allocate 1 MSI vectors (1 su[lost] msi: routing MSI IRQ 256 to local APIC 0 vector [lost] mpt0: using IRQ 256 for MSI mpt0: soft reset failed, device not running NMI ISA 2c, EISA 0 NMI ... going to debugger mpt0: hard reset failed " after which the firmware reinitializes the system and the sequence starts over, totally repeatable. The IBM literature says the RAID adapter is an IBM ServeRaid M5110e, the RAID configuration firmware calls it a MegaRaid, and FreeBSD identifies it as an LSILogic SAS/SATA Adapter. I don't know what it really is, but it's getting in the way and not playing nicely. I'd really like to add these to the stable, and particularly want to run them in 64-bit mode; 32-bit just isn't roomy enough. This isn't my first rodeo. If this is an appropriate venue, then what do you need from me? What can I do to help get this set of problems solved? Or have I just got incompatible, unsupported hardware? If it's not the right venue, then a (flameless) pointer to the appropriate venue will be greatly appreciated. Many thanks, from -- Mike Andrews, W5EGO mikea@mikea.ath.cx Tired old sysadmin From owner-freebsd-scsi@FreeBSD.ORG Tue Aug 28 16:41:21 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 B3CB510658CB for ; Tue, 28 Aug 2012 16:41:21 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by mx1.freebsd.org (Postfix) with ESMTP id 7B5138FC1A for ; Tue, 28 Aug 2012 16:41:21 +0000 (UTC) Received: from [IPv6:::1] (proxy7.corp.yahoo.com [216.145.48.98]) by mrout1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id q7SGV8Dl024805; Tue, 28 Aug 2012 09:31:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1346171469; bh=X+D1rn/2IKBe4GKzCVO4WZp5GCqD/i1pDjQNv+3xHZ8=; h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version:Content-Transfer-Encoding; b=WVFmMXj/5Zgxj5Ra6uFyvD0UmAxkaKuSwmbBVJWLHkKgqZzf1TPgQwO2jwgxPOvNl veQNl4x5+YLReQd/d8r9XrQelKD78t8hC/S1ybuPATaAgQduqwlhZGMRRgHt42QsmP zDSXiadnOFZzhNBIJkWR/ppO0Nie5gz/Ad1S0Bhk= From: Sean Bruno To: Mike A In-Reply-To: <20120828125956.GA64922@mikea.ath.cx> References: <20120828125956.GA64922@mikea.ath.cx> Content-Type: text/plain; charset="UTF-8" Date: Tue, 28 Aug 2012 09:31:08 -0700 Message-ID: <1346171468.3526.2.camel@powernoodle.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Milter-Version: master.31+4-gbc07cd5+ X-CLX-ID: 171469000 Cc: "freebsd-scsi@freebsd.org" Subject: Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): install fails with NMI 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, 28 Aug 2012 16:41:21 -0000 On Tue, 2012-08-28 at 05:59 -0700, Mike A wrote: > Hi. I'm posting this bug report here at the suggestion of Andriy Gapon, > of the freebsd-amd64 list. > > The machine is, as stated in the Subject header, a shiny new > IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e) > > I just got handed 4 of the subject boxes with instructions "put 'em to > work". Naturally I tried FreeBSD first, on one of the machines. Boot from > the 9.0 AMD64 boot-only install CD fails. Things look fine until the last > several lines of the (verbose enabled) boot sequence, which (from an > insufficiently-wide phone camera capture) are: > > " > mpt0: port 0x3000-0x[lost off right edge of phone] > xc5d00000-0xc5deffff irq 34 at device 0.0 on pci[lost] > mpt0: attempting to allocate 1 MSI vectors (1 su[lost] > msi: routing MSI IRQ 256 to local APIC 0 vector [lost] > mpt0: using IRQ 256 for MSI > mpt0: soft reset failed, device not running > NMI ISA 2c, EISA 0 > NMI ... going to debugger > mpt0: hard reset failed > " > > after which the firmware reinitializes the system and the sequence starts > over, totally repeatable. > > The IBM literature says the RAID adapter is an IBM ServeRaid M5110e, the > RAID configuration firmware calls it a MegaRaid, and FreeBSD identifies it > as an LSILogic SAS/SATA Adapter. I don't know what it really is, but it's > getting in the way and not playing nicely. > > I'd really like to add these to the stable, and particularly want to run > them in 64-bit mode; 32-bit just isn't roomy enough. This isn't my first > rodeo. > > If this is an appropriate venue, then what do you need from me? What > can I do to help get this set of problems solved? Or have I just got > incompatible, unsupported hardware? If it's not the right venue, then a > (flameless) pointer to the appropriate venue will be greatly appreciated. > > Many thanks, from > Can you grab an 9.1-RC ISO and try that on this host? Sean ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.1/ From owner-freebsd-scsi@FreeBSD.ORG Tue Aug 28 17:26:28 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 875C1106566B for ; Tue, 28 Aug 2012 17:26:28 +0000 (UTC) (envelope-from mikea@mikea.ath.cx) Received: from mikea.ath.cx (mikea.ath.cx [70.164.65.62]) by mx1.freebsd.org (Postfix) with ESMTP id 385E48FC1E for ; Tue, 28 Aug 2012 17:26:28 +0000 (UTC) Received: from mikea.ath.cx (localhost [127.0.0.1]) by mikea.ath.cx (8.14.5/8.14.5) with ESMTP id q7SHQQBc071507 for ; Tue, 28 Aug 2012 12:26:27 -0500 (CDT) (envelope-from mikea@mikea.ath.cx) Received: (from mikea@localhost) by mikea.ath.cx (8.14.5/8.14.5/Submit) id q7SHQQwu071506 for freebsd-scsi@freebsd.org; Tue, 28 Aug 2012 12:26:26 -0500 (CDT) (envelope-from mikea) Date: Tue, 28 Aug 2012 12:26:26 -0500 From: Mike A To: freebsd-scsi@freebsd.org Message-ID: <20120828172626.GB69985@mikea.ath.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): install fails with NMI 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, 28 Aug 2012 17:26:28 -0000 Further results: At the suggestion of Fabian Wenk of the freebsd-amd64 list, I entered the following: > set hint.mpt.0.msi_enable="0" > boot using option 2 of the FreeBSD boot menu. This made no appreciable change to the symptoms. The RAID adapter is an IBM ServeRaid M5110e. It uses an LSI MegaRAID SAS-MFI BIOS Version 5.33.00 (Build March 15, 2012) I am now getting ready to test 8.3-Release amd64. -- Mike Andrews, W5EGO mikea@mikea.ath.cx Tired old sysadmin From owner-freebsd-scsi@FreeBSD.ORG Tue Aug 28 21:06:25 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 BE3FA1065677; Tue, 28 Aug 2012 21:06:25 +0000 (UTC) (envelope-from mikea@mikea.ath.cx) Received: from mikea.ath.cx (mikea.ath.cx [70.164.65.62]) by mx1.freebsd.org (Postfix) with ESMTP id 7C6EA8FC28; Tue, 28 Aug 2012 21:06:25 +0000 (UTC) Received: from mikea.ath.cx (localhost [127.0.0.1]) by mikea.ath.cx (8.14.5/8.14.5) with ESMTP id q7SL6IAe075273; Tue, 28 Aug 2012 16:06:19 -0500 (CDT) (envelope-from mikea@mikea.ath.cx) Received: (from mikea@localhost) by mikea.ath.cx (8.14.5/8.14.5/Submit) id q7SL6IKd075272; Tue, 28 Aug 2012 16:06:18 -0500 (CDT) (envelope-from mikea) Date: Tue, 28 Aug 2012 16:06:18 -0500 From: Mike A To: John Baldwin Message-ID: <20120828210618.GD69985@mikea.ath.cx> References: <20120827203817.GB44988@mikea.ath.cx> <201208280934.14161.jhb@freebsd.org> <20120828140507.GB64344@mikea.ath.cx> <201208281238.48041.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201208281238.48041.jhb@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-scsi@freebsd.org Subject: Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): fails in install with NMI 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, 28 Aug 2012 21:06:25 -0000 On Tue, Aug 28, 2012 at 12:38:47PM -0400, John Baldwin wrote: > > When the loader menu pops up, choose the "escape to loader prompt" option, > then type 'set hint.mpt.0.msi_enable=0' followed by 'boot'. There's no > guarantee this will help, btw, just something to try out first. > > If that doesn't work, you can also try setting 'machdep.kdb_on_nmi=0' using > the same trick. > > If that still doesn't help, please boot another OS that does and get the > output of 'lspci -v' or 'pciconf -lvb' or equivalent so we can see exactly > which mpt adapter it is. I think there is one class of mpt(4) cards that > we do not yet support properly. Ah, yes, this PR: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=149220 > > I think this may in fact be your adapter. This was fixed after 9.0, so try > a 9.1-RC1 install disk instead and see if it works better. No joy. In sober fact, neither 9.1 nor 9.0 will even boot reliably to the point where the usual dmesg contents are displayed. About 90% of the time, 9.0 will hit the DVD reader for a while, then go quiescent, followed by the yellow LED signaling an NMI or other serious problem and the bright blue flashing LED signaling a halted machine. I have yet to get any display out of 9.1 at all. I have changed all the changeables I can: booted from a complete power-down, booted from a halted system, etc. I can't see anything that always leads to a display or to a failure to display. It is interesting that a RedHad Enterprise Linux 5.1 (ancient!) DVD booted up first crack off the bat. It couldn't find any discs to install to, however, though it did inventory the SATA drives in its dmesg output. I'm about to try a Knoppix DVD, and will post what PCI data I can get from that. I've entered the first loader hint and got no change in symptoms; since then, I have not been able to get another display in about 10 tries, and hence been unable to enter the first and second loader hints. At about 7 minutes per try, this is enormously frustrating. If there is a way to instrument the CD/DVD boot process itself, so that I can see what leads up to the failure to display, I am greatly interested in doing this. My employer has about $40K invested in these boxes, and is interested in getting some good out of them; I'm at least equally interested in not annoying my boss. You can have pretty much 100% of my work time until I get them on the air or give up and run some flavor of Linux; I'd really rather not run Linux. At this point I don't know whether the problems stem from the RAID adapter hosing the CD/DVD boot process, or from some other impediment. It may be that this belongs in the amd64 group, instead of the scsi group. I don't see a way to tell until I (or you) can determine the cause of the CD/DVD boot problems. Thanks so much for your help so far. -- Mike Andrews, W5EGO mikea@mikea.ath.cx Tired old sysadmin From owner-freebsd-scsi@FreeBSD.ORG Tue Aug 28 21:34:37 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 71275106566B for ; Tue, 28 Aug 2012 21:34:37 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mail.egr.msu.edu (hill.egr.msu.edu [35.9.37.162]) by mx1.freebsd.org (Postfix) with ESMTP id 4373F8FC08 for ; Tue, 28 Aug 2012 21:34:36 +0000 (UTC) Received: from hill (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id 8139483DF9 for ; Tue, 28 Aug 2012 17:27:12 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by hill (hill.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iGASmwEC-9lV for ; Tue, 28 Aug 2012 17:27:12 -0400 (EDT) Received: from EGR authenticated sender Message-ID: <503D37B0.8080200@egr.msu.edu> Date: Tue, 28 Aug 2012 17:27:12 -0400 From: Adam McDougall User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120727 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: <20120827203817.GB44988@mikea.ath.cx> <201208280934.14161.jhb@freebsd.org> <20120828140507.GB64344@mikea.ath.cx> <201208281238.48041.jhb@freebsd.org> <20120828210618.GD69985@mikea.ath.cx> In-Reply-To: <20120828210618.GD69985@mikea.ath.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): fails in install with NMI 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, 28 Aug 2012 21:34:37 -0000 On 08/28/2012 17:06, Mike A wrote: > At this point I don't know whether the problems stem from the RAID adapter > hosing the CD/DVD boot process, or from some other impediment. It may be > that this belongs in the amd64 group, instead of the scsi group. I don't > see a way to tell until I (or you) can determine the cause of the CD/DVD > boot problems. > > Thanks so much for your help so far. > For the sake of debugging, can you remove or disable the RAID adapter and see if it works any better? Also, if it really is an mpt chip, I'm not sure it would do much worthwhile RAID in the first place. I'd expect a different driver to try to attach if it did full RAID. If it boots without the original card, it may be worth exploring replacement controllers, even temporarily just to get more in-depth testing going. From owner-freebsd-scsi@FreeBSD.ORG Wed Aug 29 06:54:08 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 9EC44106566B for ; Wed, 29 Aug 2012 06:54:08 +0000 (UTC) (envelope-from martin@gneto.com) Received: from smtp.mullet.se (smtp.mullet.se [94.247.168.122]) by mx1.freebsd.org (Postfix) with ESMTP id 4DFC58FC12 for ; Wed, 29 Aug 2012 06:54:08 +0000 (UTC) Received: from t129.mullet.se (213-64-247-243-no34.business.telia.com [213.64.247.243]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mullet.se (Postfix) with ESMTPSA id D7DD66270C2B for ; Wed, 29 Aug 2012 08:45:50 +0200 (CEST) Message-ID: <503DBA9D.7010209@gneto.com> Date: Wed, 29 Aug 2012 08:45:49 +0200 From: Martin Nilsson User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: <20120828172626.GB69985@mikea.ath.cx> In-Reply-To: <20120828172626.GB69985@mikea.ath.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): install fails with NMI 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, 29 Aug 2012 06:54:08 -0000 On 2012-08-28 19:26, Mike A wrote: > Further results: > > At the suggestion of Fabian Wenk of the freebsd-amd64 list, I entered > the following: > >> set hint.mpt.0.msi_enable="0" >> boot > using option 2 of the FreeBSD boot menu. > > This made no appreciable change to the symptoms. > > The RAID adapter is an IBM ServeRaid M5110e. > > It uses an LSI MegaRAID SAS-MFI BIOS Version 5.33.00 (Build March 15, 2012) > > I am now getting ready to test 8.3-Release amd64. > Hi, Googling "IBM ServeRaid M5110e" turns up the following document as hit two: http://www.redbooks.ibm.com/technotes/tips0857.pdf This is clearly a LSI 2'nd generation 6Gbps MegaRAID SAS adapter that need the mfi driver in FreeBSD. The mpt driver probably attaches to the SAS controller part in the card but there is no chance that this will work as it is built to be controlled by the raid cpu. You need to disable the mpt driver and check the PCI id of the card with lspci and hack this into the mfi driver if it's not there already. Support for this family of cards have only been available for a couple of months so you must have an os with the updated mfi driver that supports MegaRAID 9265 /Martin -- Martin Nilsson, CEO, Mullet Scandinavia AB, Malmö, SWEDEN E-mail:martin@mullet.se, Phone: +46-(0)708-59 99 91, Web:www.mullet.se Our business is well engineered servers optimised for FreeBSD & Linux From owner-freebsd-scsi@FreeBSD.ORG Wed Aug 29 12:25:49 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 EE6A0106566C for ; Wed, 29 Aug 2012 12:25:48 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id C26FC8FC18 for ; Wed, 29 Aug 2012 12:25:48 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id BAC20B91A; Wed, 29 Aug 2012 08:25:47 -0400 (EDT) From: John Baldwin To: Mike A Date: Wed, 29 Aug 2012 08:18:20 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <20120827203817.GB44988@mikea.ath.cx> <201208281238.48041.jhb@freebsd.org> <20120828210618.GD69985@mikea.ath.cx> In-Reply-To: <20120828210618.GD69985@mikea.ath.cx> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201208290818.20990.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 29 Aug 2012 08:25:47 -0400 (EDT) Cc: freebsd-scsi@freebsd.org Subject: Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): fails in install with NMI 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, 29 Aug 2012 12:25:49 -0000 On Tuesday, August 28, 2012 5:06:18 pm Mike A wrote: > On Tue, Aug 28, 2012 at 12:38:47PM -0400, John Baldwin wrote: > > > > When the loader menu pops up, choose the "escape to loader prompt" option, > > then type 'set hint.mpt.0.msi_enable=0' followed by 'boot'. There's no > > guarantee this will help, btw, just something to try out first. > > > > If that doesn't work, you can also try setting 'machdep.kdb_on_nmi=0' using > > the same trick. > > > > If that still doesn't help, please boot another OS that does and get the > > output of 'lspci -v' or 'pciconf -lvb' or equivalent so we can see exactly > > which mpt adapter it is. I think there is one class of mpt(4) cards that > > we do not yet support properly. Ah, yes, this PR: > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=149220 > > > > I think this may in fact be your adapter. This was fixed after 9.0, so try > > a 9.1-RC1 install disk instead and see if it works better. > > No joy. In sober fact, neither 9.1 nor 9.0 will even boot reliably to the > point where the usual dmesg contents are displayed. About 90% of the time, > 9.0 will hit the DVD reader for a while, then go quiescent, followed by > the yellow LED signaling an NMI or other serious problem and the bright > blue flashing LED signaling a halted machine. I have yet to get any display > out of 9.1 at all. I have changed all the changeables I can: booted from a > complete power-down, booted from a halted system, etc. I can't see anything > that always leads to a display or to a failure to display. > > It is interesting that a RedHad Enterprise Linux 5.1 (ancient!) DVD booted > up first crack off the bat. It couldn't find any discs to install to, > however, though it did inventory the SATA drives in its dmesg output. > > I'm about to try a Knoppix DVD, and will post what PCI data I can get > from that. > > I've entered the first loader hint and got no change in symptoms; since > then, I have not been able to get another display in about 10 tries, and > hence been unable to enter the first and second loader hints. At about 7 > minutes per try, this is enormously frustrating. > > If there is a way to instrument the CD/DVD boot process itself, so that I > can see what leads up to the failure to display, I am greatly interested > in doing this. My employer has about $40K invested in these boxes, and > is interested in getting some good out of them; I'm at least equally > interested in not annoying my boss. You can have pretty much 100% of my > work time until I get them on the air or give up and run some flavor of > Linux; I'd really rather not run Linux. > > At this point I don't know whether the problems stem from the RAID adapter > hosing the CD/DVD boot process, or from some other impediment. It may be > that this belongs in the amd64 group, instead of the scsi group. I don't > see a way to tell until I (or you) can determine the cause of the CD/DVD > boot problems. > > Thanks so much for your help so far. Humm, that is bizarre. All the early bootstrap code just relies on the BIOS to perform disk I/O, etc. Can you PXE boot these machines? That might be a way to get the CD out of the picture. I haven't seen any machines with your symptoms. At the least, if a machine does have a problem with the boot process due to a bug or some such, it is consistent in having the problem every time, not suddenly failing after working. Also, to be honest, the original NMI in itself is a bit odd. If you are having these problems now I do wonder if there isn't an underlying hardware issue. Regardless, I think netbooting would be a good thing to look to get the CD/DVD bit out of the way. -- John Baldwin From owner-freebsd-scsi@FreeBSD.ORG Wed Aug 29 12:46:54 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 CFD05106567A; Wed, 29 Aug 2012 12:46:54 +0000 (UTC) (envelope-from mikea@mikea.ath.cx) Received: from mikea.ath.cx (mikea.ath.cx [70.164.65.62]) by mx1.freebsd.org (Postfix) with ESMTP id 99C378FC23; Wed, 29 Aug 2012 12:46:54 +0000 (UTC) Received: from mikea.ath.cx (localhost [127.0.0.1]) by mikea.ath.cx (8.14.5/8.14.5) with ESMTP id q7TCkr3I089533; Wed, 29 Aug 2012 07:46:53 -0500 (CDT) (envelope-from mikea@mikea.ath.cx) Received: (from mikea@localhost) by mikea.ath.cx (8.14.5/8.14.5/Submit) id q7TCkrR2089532; Wed, 29 Aug 2012 07:46:53 -0500 (CDT) (envelope-from mikea) Date: Wed, 29 Aug 2012 07:46:53 -0500 From: Mike A To: John Baldwin Message-ID: <20120829124653.GA89164@mikea.ath.cx> References: <20120827203817.GB44988@mikea.ath.cx> <201208281238.48041.jhb@freebsd.org> <20120828210618.GD69985@mikea.ath.cx> <201208290818.20990.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201208290818.20990.jhb@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-scsi@freebsd.org Subject: Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): fails in install with NMI 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, 29 Aug 2012 12:46:54 -0000 On Wed, Aug 29, 2012 at 08:18:20AM -0400, John Baldwin wrote: > Humm, that is bizarre. All the early bootstrap code just relies on the BIOS > to perform disk I/O, etc. Can you PXE boot these machines? That might be a > way to get the CD out of the picture. I haven't seen any machines with your > symptoms. At the least, if a machine does have a problem with the boot process > due to a bug or some such, it is consistent in having the problem every time, > not suddenly failing after working. > > Also, to be honest, the original NMI in itself is a bit odd. If you are having > these problems now I do wonder if there isn't an underlying hardware issue. > Regardless, I think netbooting would be a good thing to look to get the CD/DVD > bit out of the way. Agreed, in spades. My experience with FreeBSD, before this machine, is that Things Just Work. I have never seen anything like this before, and am seriously considering unboxing another server just to see if this is typical of the hardware or peculiar to this one box. I am installing the stuff needed for PXE boot this morning, and will provide results as I generate them. Many thanks. -- Mike Andrews, W5EGO mikea@mikea.ath.cx Tired old sysadmin From owner-freebsd-scsi@FreeBSD.ORG Thu Aug 30 21:30:33 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 5E8551065673; Thu, 30 Aug 2012 21:30:33 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [70.91.206.90]) by mx1.freebsd.org (Postfix) with ESMTP id 30D128FC1E; Thu, 30 Aug 2012 21:30:32 +0000 (UTC) X-Ambrisko-Me: Yes Received: from server2.ambrisko.com (HELO internal.ambrisko.com) ([192.168.1.2]) by ironport.ambrisko.com with ESMTP; 30 Aug 2012 14:30:35 -0700 Received: from ambrisko.com (localhost [127.0.0.1]) by internal.ambrisko.com (8.14.4/8.14.4) with ESMTP id q7ULTO4Z023423; Thu, 30 Aug 2012 14:29:24 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.14.4/8.14.4/Submit) id q7ULTNkV023422; Thu, 30 Aug 2012 14:29:23 -0700 (PDT) (envelope-from ambrisko) Date: Thu, 30 Aug 2012 14:29:23 -0700 From: Doug Ambrisko To: John Baldwin Message-ID: <20120830212923.GA21687@ambrisko.com> References: <20120827203817.GB44988@mikea.ath.cx> <201208281238.48041.jhb@freebsd.org> <20120828210618.GD69985@mikea.ath.cx> <201208290818.20990.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201208290818.20990.jhb@freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-scsi@freebsd.org, Mike A Subject: Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): fails in install with NMI 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, 30 Aug 2012 21:30:33 -0000 On Wed, Aug 29, 2012 at 08:18:20AM -0400, John Baldwin wrote: [snip] | Also, to be honest, the original NMI in itself is a bit odd. If you are having | these problems now I do wonder if there isn't an underlying hardware issue. | Regardless, I think netbooting would be a good thing to look to get the CD/DVD | bit out of the way. The original NMI is quite common with mpt(4) attaching to an mfi(4) card. This was due to some bad code in mpt(4) probe code that has been corrected. I think this is why Sean suggested 9.1 which should have this fixed. I run into this when I run an unpatched/older FreeBSD image on newer machines with the new mfi controller. Doug A. From owner-freebsd-scsi@FreeBSD.ORG Thu Aug 30 22:22:56 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 A5BD0106564A; Thu, 30 Aug 2012 22:22:56 +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 116D08FC08; Thu, 30 Aug 2012 22:22:55 +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 q7UMIoEU093863; Fri, 31 Aug 2012 00:18:50 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.4/8.14.4/Submit) id q7UMIoij093862; Fri, 31 Aug 2012 00:18:50 +0200 (CEST) (envelope-from marius) Date: Fri, 31 Aug 2012 00:18:49 +0200 From: Marius Strobl To: Doug Ambrisko Message-ID: <20120830221849.GA93819@alchemy.franken.de> References: <20120827203817.GB44988@mikea.ath.cx> <201208281238.48041.jhb@freebsd.org> <20120828210618.GD69985@mikea.ath.cx> <201208290818.20990.jhb@freebsd.org> <20120830212923.GA21687@ambrisko.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120830212923.GA21687@ambrisko.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-scsi@freebsd.org, Mike A , John Baldwin Subject: Re: Bug Report: IBM x3650M4 (32GB, 2x4-core Xeon E5-2600, IBM ServeRaid M5110e): fails in install with NMI 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, 30 Aug 2012 22:22:56 -0000 On Thu, Aug 30, 2012 at 02:29:23PM -0700, Doug Ambrisko wrote: > On Wed, Aug 29, 2012 at 08:18:20AM -0400, John Baldwin wrote: > [snip] > | Also, to be honest, the original NMI in itself is a bit odd. If you are having > | these problems now I do wonder if there isn't an underlying hardware issue. > | Regardless, I think netbooting would be a good thing to look to get the CD/DVD > | bit out of the way. > > The original NMI is quite common with mpt(4) attaching to an mfi(4) > card. This was due to some bad code in mpt(4) probe code that has > been corrected. I think this is why Sean suggested 9.1 which should > have this fixed. I run into this when I run an unpatched/older > FreeBSD image on newer machines with the new mfi controller. > There still is the problem that there are at least some LSI HBAs that can be upgraded to MegaRAID but also use the same PCI IDs when that add-on is not in place. The mpt(4) driver has some initial support for that in place by returning BUS_PROBE_LOW_PRIORITY for one ID known so far. However, unlike the corresponding Linux driver, mfi(4) doesn't try to figure out whether such an HBA actually is in MegaRAID and attaches instead. Marius From owner-freebsd-scsi@FreeBSD.ORG Fri Aug 31 00:31:06 2012 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 821) id B56131065674; Fri, 31 Aug 2012 00:31:06 +0000 (UTC) Date: Fri, 31 Aug 2012 00:31:06 +0000 From: John To: FreeBSD SCSI Message-ID: <20120831003106.GA70561@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: camcontrol devlist device name ordering 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, 31 Aug 2012 00:31:06 -0000 Hi Folks, I've been working on a small utility to map devices and enclosures and generate a small report. Nothing special really. However, I've run into a small parsing issue I thought I'd ask about here. When running "camcontrol devlist", the device names are not always printed out the same. For instance: at scbus7 target 165 lun 0 (pass24,da21) at scbus7 target 166 lun 0 (pass25,da22) at scbus7 target 167 lun 0 (pass26,da23) at scbus7 target 168 lun 0 (pass27,da24) at scbus7 target 169 lun 0 (ses0,pass28) <--- at scbus7 target 170 lun 0 (pass29,da25) at scbus7 target 171 lun 0 (pass30,da26) at scbus7 target 172 lun 0 (pass31,da27) In the last column, the disk devices are pass device / disk device. For the enclosure, it's enclosure device / pass device. First I looked at camcontrol, but it is simply looping over the list as presented. It is not responsible for the ordering. I then started poking around in sys/cam/scsi/scsi_ses.c and I can see where the device is allocated, but I'm not sure how the insertion ordering is controlled for the pass & ses devices. Does someone with a bit more knowledge of this area have an idea where I should look? Running 9.1-PRERELEASE Fri Aug 24. 2012 Thanks, John From owner-freebsd-scsi@FreeBSD.ORG Fri Aug 31 03:28:17 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 2DB481065673; Fri, 31 Aug 2012 03:28:17 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) by mx1.freebsd.org (Postfix) with ESMTP id D960C8FC0C; Fri, 31 Aug 2012 03:28:16 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id q7V3S9kR006091 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 30 Aug 2012 20:28:09 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id q7V3S9Zv006090; Thu, 30 Aug 2012 20:28:09 -0700 (PDT) (envelope-from jmg) Date: Thu, 30 Aug 2012 20:28:09 -0700 From: John-Mark Gurney To: John Message-ID: <20120831032809.GH58312@funkthat.com> Mail-Followup-To: John-Mark Gurney , John , FreeBSD SCSI References: <20120831003106.GA70561@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120831003106.GA70561@FreeBSD.org> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Thu, 30 Aug 2012 20:28:10 -0700 (PDT) Cc: FreeBSD SCSI Subject: Re: camcontrol devlist device name ordering 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, 31 Aug 2012 03:28:17 -0000 John wrote this message on Fri, Aug 31, 2012 at 00:31 +0000: > When running "camcontrol devlist", the device names are not always > printed out the same. For instance: > > at scbus7 target 165 lun 0 (pass24,da21) > at scbus7 target 166 lun 0 (pass25,da22) > at scbus7 target 167 lun 0 (pass26,da23) > at scbus7 target 168 lun 0 (pass27,da24) > at scbus7 target 169 lun 0 (ses0,pass28) <--- > at scbus7 target 170 lun 0 (pass29,da25) > at scbus7 target 171 lun 0 (pass30,da26) > at scbus7 target 172 lun 0 (pass31,da27) > > In the last column, the disk devices are pass device / disk device. For > the enclosure, it's enclosure device / pass device. I'm going to point out that it isn't always pass/disk as is demonstrated by this: root@carbon:/home/jmg # camcontrol devlist at scbus0 target 0 lun 0 (ada0,pass0) at scbus7 target 0 lun 0 (da0,pass1) at scbus7 target 1 lun 0 (pass2,da1) at scbus7 target 2 lun 0 (da2,pass3) It depends upon the controller.. da0 and da2 are normal boot, but da1 is reverse because it came about after a disk was replaced and a rescan for the disk.. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-scsi@FreeBSD.ORG Fri Aug 31 05:02:36 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 5C498106566C; Fri, 31 Aug 2012 05:02:36 +0000 (UTC) (envelope-from ken@kdm.org) Received: from nargothrond.kdm.org (nargothrond.kdm.org [70.56.43.81]) by mx1.freebsd.org (Postfix) with ESMTP id 010C18FC14; Fri, 31 Aug 2012 05:02:35 +0000 (UTC) Received: from nargothrond.kdm.org (localhost [127.0.0.1]) by nargothrond.kdm.org (8.14.2/8.14.2) with ESMTP id q7V4g43a040723; Thu, 30 Aug 2012 22:42:04 -0600 (MDT) (envelope-from ken@nargothrond.kdm.org) Received: (from ken@localhost) by nargothrond.kdm.org (8.14.2/8.14.2/Submit) id q7V4g4Fe040722; Thu, 30 Aug 2012 22:42:04 -0600 (MDT) (envelope-from ken) Date: Thu, 30 Aug 2012 22:42:04 -0600 From: "Kenneth D. Merry" To: John Message-ID: <20120831044204.GA39391@nargothrond.kdm.org> References: <20120831003106.GA70561@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120831003106.GA70561@FreeBSD.org> User-Agent: Mutt/1.4.2i Cc: FreeBSD SCSI Subject: Re: camcontrol devlist device name ordering 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, 31 Aug 2012 05:02:36 -0000 On Fri, Aug 31, 2012 at 00:31:06 +0000, John wrote: > Hi Folks, > > I've been working on a small utility to map devices and enclosures > and generate a small report. Nothing special really. > > However, I've run into a small parsing issue I thought I'd ask > about here. > > When running "camcontrol devlist", the device names are not always > printed out the same. For instance: > > at scbus7 target 165 lun 0 (pass24,da21) > at scbus7 target 166 lun 0 (pass25,da22) > at scbus7 target 167 lun 0 (pass26,da23) > at scbus7 target 168 lun 0 (pass27,da24) > at scbus7 target 169 lun 0 (ses0,pass28) <--- > at scbus7 target 170 lun 0 (pass29,da25) > at scbus7 target 171 lun 0 (pass30,da26) > at scbus7 target 172 lun 0 (pass31,da27) > > In the last column, the disk devices are pass device / disk device. For > the enclosure, it's enclosure device / pass device. > > First I looked at camcontrol, but it is simply looping over the list > as presented. It is not responsible for the ordering. I then started > poking around in sys/cam/scsi/scsi_ses.c and I can see where the device > is allocated, but I'm not sure how the insertion ordering is controlled > for the pass & ses devices. > > Does someone with a bit more knowledge of this area have an idea > where I should look? It is done in the order that the peripherals attach, and so it is rather random and timing dependent. Specifically, see cam_periph_alloc() in sys/cam/cam_periph.c, and xpt_add_periph() in sys/cam/cam_xpt.c. You could also do a 'camcontrol periphlist' for the first peripheral or bus/target/lun in the devlist output and grep for the type of peripheral you're interested in. Some day I suppose we should do an XML output version of the devlist code, or make it more script friendly. Ken -- Kenneth Merry ken@FreeBSD.ORG From owner-freebsd-scsi@FreeBSD.ORG Fri Aug 31 18:30:37 2012 Return-Path: Delivered-To: scsi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5A6D5106566B; Fri, 31 Aug 2012 18:30:37 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0116C8FC15; Fri, 31 Aug 2012 18:30:37 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 73AA7B91A; Fri, 31 Aug 2012 14:30:36 -0400 (EDT) From: John Baldwin To: scsi@freebsd.org Date: Fri, 31 Aug 2012 14:30:32 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201208311430.32959.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 31 Aug 2012 14:30:36 -0400 (EDT) Cc: nyan@freebsd.org, non@freebsd.org Subject: [PATCH] Convert scsi_low from timeout(9) to callout(9) 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, 31 Aug 2012 18:30:37 -0000 I have a patch to convert the scsi_low code from using the deprecated timeout(9) API to using callout(9) instead. Is anyone able to review or test this patch? I have not attempted to add locking to scsi_low as I don't know it well enough to know the various entry/exit points, etc. Also, it still has a lot of compat shims to work on NetBSD. I can't seem to find a scsi_low.c on NetBSD at all anymore. Do we still need NetBSD compat shims? If not, trimming those would make this code far more readable. http://www.FreeBSD.org/~jhb/patches/scsi_low_callout.patch -- John Baldwin From owner-freebsd-scsi@FreeBSD.ORG Sat Sep 1 15:20:15 2012 Return-Path: Delivered-To: freebsd-scsi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D4630106564A for ; Sat, 1 Sep 2012 15:20:15 +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 A71D48FC0A for ; Sat, 1 Sep 2012 15:20:15 +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 q81FKF7D024627 for ; Sat, 1 Sep 2012 15:20:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q81FKFTE024626; Sat, 1 Sep 2012 15:20:15 GMT (envelope-from gnats) Date: Sat, 1 Sep 2012 15:20:15 GMT Message-Id: <201209011520.q81FKFTE024626@freefall.freebsd.org> To: freebsd-scsi@FreeBSD.org From: Martin Birgmeier Cc: Subject: Re: kern/157770: [iscsi] [panic] iscsi_initiator panic X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Martin Birgmeier List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Sep 2012 15:20:15 -0000 The following reply was made to PR kern/157770; it has been noted by GNATS. From: Martin Birgmeier To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/157770: [iscsi] [panic] iscsi_initiator panic Date: Sat, 01 Sep 2012 17:11:24 +0200 This could be resolved by merging r234233 | jpaetzel | 2012-04-13 20:21:56 +0200 (Fri, 13 Apr 2012) | 4 lines to stable/{7..9} plus the various relengs Regards, Martin