From owner-freebsd-current@FreeBSD.ORG Thu Oct 11 17:32:38 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 447A816A41A for ; Thu, 11 Oct 2007 17:32:38 +0000 (UTC) (envelope-from chris@arnold.se) Received: from mailstore.infotropic.com (mailstore.infotropic.com [213.136.34.3]) by mx1.freebsd.org (Postfix) with ESMTP id A3E3F13C474 for ; Thu, 11 Oct 2007 17:32:37 +0000 (UTC) (envelope-from chris@arnold.se) Received: (qmail 14600 invoked by uid 89); 11 Oct 2007 17:32:35 -0000 Received: by simscan 1.2.0 ppid: 14595, pid: 14597, t: 0.1335s scanners: attach: 1.2.0 clamav: 0.90/m:42 Received: from unknown (HELO ?192.168.123.123?) (chris@arnold.se@82.182.86.134) by mailstore.infotropic.com with ESMTPA; 11 Oct 2007 17:32:35 -0000 Date: Thu, 11 Oct 2007 19:32:34 +0200 (CEST) From: Christopher Arnold X-X-Sender: chris@chrishome.localnet To: Jeremy Chadwick In-Reply-To: <20071010185416.GA38522@eos.sc1.parodius.com> Message-ID: <20071011192303.P30804@chrishome.localnet> References: <20071010195157.O24133@chrishome.localnet> <20071010185416.GA38522@eos.sc1.parodius.com> X-message-flag: =?ISO-8859-1?Q?Outlook_isn=B4t_compliant_with_current_standards?= =?ISO-8859-1?Q?_please_install_another_mail_client!?= MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: Compaq Smart Array 5300 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2007 17:32:38 -0000 On Wed, 10 Oct 2007, Jeremy Chadwick wrote: > On Wed, Oct 10, 2007 at 08:06:21PM +0200, Christopher Arnold wrote: >> >> anyone aware of issues with Compaq Smart Array 5300 on a current only a day >> old? >> >> This is what i get in the boot message: >> ciss0: port 0xe800-0xe8ff mem >> 0xfebc0000-0xfebfffff,0xfea00000-0xfeafffff irq 22 at device 1.0 on pci2 >> ciss0: can't allocate config window >> device_attach: ciss0 attach returned 6 >> >> The full output can be found at: >> http://www.arnold.se/boot.txt >> http://www.arnold.se/pciconf.txt >> >> Im trying to run it in a Supermicro 6010 with 370DER+ motherboard. >> >> Anyone who has any input on what this could be? > > It's one of those bloody QLogic GEM chips; on this motherboard, it's > probably the QLogic GEM 354. The motherboard manual does indicate this, > although only in the Windows driver section (this does not surprise me, > as some other vendors use GEM chips and don't tell you until you > actually have to deal with them...) > I havn't actually verified this, but it may be true. > In general: I wouldn't worry about the lack of ciss0 device. In fact, > I'd go so far to recommend you remove ses and ciss from the kernel on > that box, and hope for the best. Scott (Long) may have some better > (and more accurate) advice on the matter; my experiences are my own. > Removing ciss from the kernel dosn't help. Now i get: kernel: pcib2: on acpi0 kernel: pci2: on pcib2 kernel: pci2: at device 1.0 (no driver attached) Which seems reasonable... Does anyone have an idea what "ciss0 attach returned 6" could stand for? /Chris