Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 27 Mar 2005 08:25:34 GMT
From:      Jukka Ukkonen <jau@iki.fi>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   misc/79274: Autoconfigure fails for O2Micro OZ6812/6872 PCI-CardBus Bridge
Message-ID:  <200503270825.j2R8PYVw013630@www.freebsd.org>
Resent-Message-ID: <200503270830.j2R8U3ln055719@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         79274
>Category:       misc
>Synopsis:       Autoconfigure fails for O2Micro OZ6812/6872 PCI-CardBus Bridge
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Mar 27 08:30:02 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Jukka Ukkonen
>Release:        FreeBSD 5.4-PRERELEASE
>Organization:
>Environment:
FreeBSD mimir 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE #3: Sat Mar 26 12:23:43 EET 2005     root@mimir:/usr/obj/usr/src/sys/GENERIC  i386


>Description:
      At boot time autoconfigure of an O2 Micro single slot PCI-CardBus bridge
fails. The output from autoconfigure goes as follows...

cbb0: <O2Micro OZ6812/6872 PCI-CardBus Bridge> at device 9.0 on pci0
cardbus0: <CardBus bus> on cbb0
pccard0: <16-bit PCCard bus> on cbb0
pcib0: unable to route slot 9 INTA
cbb: Unable to map IRQ...
device_attach: cbb0 attach returned 12

So, there is something odd about how the IRQs work.


When the system has booted a quick check with pciconf (pciconf -l -v)
reports the card as shown below. This gives me the impression that
the card should be a known one.

cbb0@pci0:9:0:  class=0x060700 card=0x00000000 chip=0x68721217 rev=0x05 hdr=0x02
    vendor   = 'O2 Micro Inc'
    device   = 'OZ6812 CardBus Controller'
    class    = bridge
    subclass = PCI-CardBus



>How-To-Repeat:
      You need only the OZ6812/6872 card and boot.
If there is a need for more debug info, just let me know.
For the moment the system in which I found this problem is
just a testing environment. So, producing more test data
should be relatively quick and easy.

>Fix:
      None known yet.

>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200503270825.j2R8PYVw013630>