5.3-BETA5 panics when inserting dc0 carbus card (only with ACPI
enabled) enabled)
Nate Lawson
nate at root.org
Wed Sep 22 16:37:01 PDT 2004
M. Warner Losh wrote:
> In message: <4151DA08.6010602 at root.org>
> Nate Lawson <nate at root.org> writes:
> : Um, what is the dc0 card doing mapping ports 0-0xff:
> :
> : Below the analogous output Johan Karlsson <johan at freebsd.org> posted
> : for his Xircom X3201 10/100BaseTX card for 5.3-BETA5:
> :
> : dc0: <Netgear FA511 10/100BaseTX> port 0-0xff mem 0x88000000-0x880003ff
> : at device 0.0 on cardbus0
> : cbb alloc res fail
> : dc0: couldn't map ports/memory
> :
> : Dmesg from boot with a working kernel for dc0 would help as well as
> : devinfo -r from a non-working one.
>
> Is there a pci bridge involved? It is a well known problem for
> cardbus systems that if there isn't, you get mappings like this.
I don't know, but it looks like cbb0 is directly under pci0. Here's the
devinfo -r results from his working boot:
pcib0
pci0
pcib1
pci1
cbb0
Interrupt request lines:
0xb
I/O memory addresses:
0x50000000-0x50000fff
cardbus0
pccard0
cbb1
I/O memory addresses:
0x50100000-0x50100fff
cardbus1
pccard1
I can't see how ACPI sysresources affect this since ACPI doesn't claim
0x1080-0x10ff IO which the card asks for.
--
Nate
More information about the freebsd-current
mailing list