From owner-freebsd-current Sat Mar 30 22:16:30 2002 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id B711737B419; Sat, 30 Mar 2002 22:16:26 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 63AB9AE1BB; Sat, 30 Mar 2002 22:16:26 -0800 (PST) Date: Sat, 30 Mar 2002 22:16:26 -0800 From: Alfred Perlstein To: Michael Smith Cc: scott_long@btc.adaptec.com, mark_salyzyn@adaptec.com, obrien@freebsd.org, current@freebsd.org Subject: Re: asr can not map memory? Message-ID: <20020331061626.GJ93885@elvis.mu.org> References: <20020331044558.GD93885@elvis.mu.org> <200203310533.g2V5XMc02681@mass.dis.org> <20020331055054.GI93885@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020331055054.GI93885@elvis.mu.org> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Alfred Perlstein [020330 21:51] wrote: > * Michael Smith [020330 21:34] wrote: > > > > Your BIOS is assigning a memory range to the card that we don't believe > > the bridge passes through. Our check is bogus because (as you see) the > > range is actually legitimate (and we booger up some calculations). Add > > the PCI_ALLOW_UNSUPPORTED_IO_RANGE option and this should go away. > > I was about to do that (add PCI_ALLOW_UNSUPPORTED_IO_RANGE) I'll toss > a patch to make this a tunable/sysctl in a bit. > > Is there a way that we can "fix" this without blindly allowing bad > bus_alloc_resources ? I'm a bit confused as to wheather our code is > behaving oddly or if it's just the device violating some spec... > > > You should have bought a 3ware controller. 8) > > 3ware should talk to Frys. :) > > Thanks for responding so promptly. This avoids a panic when probing, there's probably still some badness going on with make/destroy dev in this driver. Should I hold onto this card or should I suck it up and get a 3ware online somewhere? Index: asr.c =================================================================== RCS file: /home/ncvs/src/sys/dev/asr/asr.c,v retrieving revision 1.18 diff -u -r1.18 asr.c --- asr.c 20 Mar 2002 02:02:35 -0000 1.18 +++ asr.c 30 Mar 2002 22:15:01 -0000 @@ -3179,7 +3192,6 @@ * Generate the device node information */ (void)make_dev(&asr_cdevsw, unit, 0, 0, S_IRWXU, "rasr%d", unit); - destroy_dev(makedev(asr_cdevsw.d_maj,unit+1)); ATTACH_RETURN(0); } /* asr_attach */ -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message