From owner-freebsd-scsi@FreeBSD.ORG Fri May 7 03:44:17 2010 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 81B9D106564A for ; Fri, 7 May 2010 03:44:17 +0000 (UTC) (envelope-from ulf@alameda.net) Received: from mail.alameda.net (mail.alameda.net [194.55.105.10]) by mx1.freebsd.org (Postfix) with ESMTP id 60BAB8FC08 for ; Fri, 7 May 2010 03:44:17 +0000 (UTC) Received: by mail.alameda.net (Postfix, from userid 1000) id AD53A1CCAC; Thu, 6 May 2010 20:44:09 -0700 (PDT) Date: Thu, 6 May 2010 20:44:09 -0700 From: Ulf Zimmermann To: Scott Long Message-ID: <20100507034409.GW30353@evil.alameda.net> References: <1273092737.2487.5.camel@localhost.localdomain> <20100506014748.GR30353@evil.alameda.net> <1273165130.2465.4.camel@localhost.localdomain> <20100506174113.GS30353@evil.alameda.net> <1273169980.2465.6.camel@localhost.localdomain> <4BE318A8.6050108@fuujingroup.com> <1273172053.2465.8.camel@localhost.localdomain> <20100506211713.GT30353@evil.alameda.net> <20100506213349.GU30353@evil.alameda.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 5.5-PRERELEASE X-ANI-MailScanner-Information: Please contact the ISP for more information X-ANI-MailScanner-ID: AD53A1CCAC.ACFA4 X-ANI-MailScanner: Found to be clean X-ANI-MailScanner-From: ulf@alameda.net Cc: "freebsd-scsi@freebsd.org" , "Erich Jenkins, Fuujin Group Ltd" , ulf@Alameda.net, Sean Bruno Subject: Re: kern/146287: [ciss] ciss(4) cannot see more than one SmartArray controller X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ulf@Alameda.net List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 May 2010 03:44:17 -0000 On Thu, May 06, 2010 at 09:41:30PM -0600, Scott Long wrote: > On May 6, 2010, at 3:33 PM, Ulf Zimmermann wrote: > > On Thu, May 06, 2010 at 02:17:13PM -0700, Ulf Zimmermann wrote: > >> On Thu, May 06, 2010 at 11:54:13AM -0700, Sean Bruno wrote: > >>> > >>>>> > >>>> > >>>> Not sure if this helps or not, but we've got about 20 of these machines, > >>>> as well as the DL580 version in production. I've seen this very same > >>>> issue on the ML series machines also. If I remember correctly, there > >>>> were two different PCI bridges used in the same production models, one > >>>> was from IBM and the other was a ServerWorks (Broadcom) chipset. One > >>>> didn't show up at all (not even when probed) and the other one was > >>>> displayed. Can't remember which was which, but I know it had to do with > >>>> hot-swap PCI subsystem, and I suspect this is what you're experiencing. > >>>> We had a similar experience with MyriCom 10GE cards in an ML570 with a > >>>> hot-swap PCI option. The card wouldn't show up in slot closest to the > >>>> Mem card (can't remember if the DL380's have a riser card for ram or if > >>>> this is onboard), but it worked in the next slot over. > >>>> > >>>> > >>>> Erich M. Jenkins > >>>> Fuujin Group Limited > >>>> > >>>> > >>>> "You should never, never doubt what no one is sure about." > >>>> -- Gene Wilder > >>>> > >>> > >>> It does help a bit. > >>> > >>> Basically, we need an AML dump of the ACPI information from one of the > >>> machines that has an IBM based bridge chip. > >>> > >>> acpidump -dt > >>> > >>> sean > >>> > >>> > >> > >> I wonder what bridge chip is used in the DL380 g3, as far I know the ones > >> we have should be hotswap PCI-X. On the DL380 g4 the standard cage was not > >> hotswap and I think we don't have any of those. > >> > >> Looking at the product specs of a DL380 g3, it shows different > >> bus for slot 1 (bottom at 64-bit/133Mhz PCI-X) against slot 2+3 (middle > >> and top slot at 64-bit/100Mhz PCI-X). > >> > >> I got one DL380 g3 myself, which isn't running much right now, so I will > >> check out what PCI devices I can see. > >> > > > > 03:01.0 PCI bridge: IBM PCI-X to PCI-X Bridge (rev 02) (prog-if 00 [Normal decode]) > > Flags: bus master, 66Mhz, medium devsel, latency 64 > > Bus: primary=03, secondary=04, subordinate=04, sec-latency=64 > > I/O behind bridge: 00003000-00003fff > > Memory behind bridge: f7e00000-f7efffff > > Prefetchable memory behind bridge: 00000000f1100000-00000000f11fffff > > Capabilities: [80] PCI-X bridge device > > Capabilities: [90] Power Management version 2 > > > > Is that the same bridge chip? This comes from a DL380 g3 with hot-swap cage. > > > > > > Yup, that's the bridge chip that we suspected from the original poster. > > Scott Ok, I will go and install -CURRENT on a DL380 g3 tomorrow. -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 You can find my resume at: http://www.Alameda.net/~ulf/resume.html