* Michael Smith <[EMAIL PROTECTED]> [020330 21:34] wrote: > > I just got the Adaptec 4 port IDE raid card 2400A. > > > > It doesn't probe right: > > asr0: could not map memory > > > > I added some debug printouts to the asr driver and pci code. > > > > asr0: <Adaptec Caching SCSI RAID> mem 0xf6000000-0xf7ffffff irq 5 at device 5 > > .1 on pci2 > > pcib2: device asr0 requested unsupported memory range 0xf6000000-0xf6400000 > > pcib2: device asr0 requested unsupported memory range 0x0-0xec9fffff (decodin > > g 0xec900000-0xec9fffff, 0xf6000000-0xfbffffff) > > asr: map failed at: 2602 p:f6000000 f6400000 l:00400000 > > asr0: could not map memory > > device_probe_and_attach: asr0 attach returned 6 > > > > wtf is going on here? > > 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. -- -Alfred Perlstein [[EMAIL PROTECTED]] '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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message