linux-kernel - Re: PCI Express-to-PCI Bridge: yenta

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200909300115.54263.rjw@sisk.pl>
Date:	Wed, 30 Sep 2009 01:15:54 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Stefani Seibold <stefani@...bold.net>
Cc:	"linux-kernel" <linux-kernel@...r.kernel.org>,
	Linux PCI <linux-pci@...r.kernel.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: PCI Express-to-PCI Bridge: yenta_cardbus  no bus associated!

[Adding CCs.]

On Tuesday 29 September 2009, Stefani Seibold wrote:
> Hi PCI Hackers,
> 
> i have trouble with an ExpressCard PCI Express-to-PCI Bridge
> manufactured by DUEL System under X86/32 Linux kernel 2.6.31.
> 
> The kernel will recognized the Texas Instruments XIO2000(A)/XIO2200(A)
> PCI Express-to-PCI Bridge and the attached Texas Instruments PCIxx12
> Cardbus Controller, but the yenta socket driver will fail with the
> message:
> 
> yenta_cardbus 0000:0f:00.0: no bus associated! (try 'pci=assign-busses')
> 
> The output of dmesg looks like:
> 
> pci 0000:0e:00.0: supports D1 D2
> pci 0000:0f:00.0: reg 10 32bit mmio: [0x000000-0x000fff]
> pci 0000:0f:00.0: supports D1 D2
> pci 0000:0f:00.0: PME# supported from D0 D1 D2 D3hot D3cold
> pci 0000:0f:00.0: PME# disabled
> pci 0000:0e:00.0: bridge io port: [0x00-0xfff]
> pci 0000:0e:00.0: bridge 32bit mmio: [0x000000-0x0fffff]
> pci 0000:0e:00.0: bridge 64bit mmio pref: [0x000000-0x0fffff]
> pci 0000:0e:00.0: PCI bridge, secondary bus 0000:0f
> pci 0000:0e:00.0:   IO window: disabled
> pci 0000:0e:00.0:   MEM window: 0xf1c00000-0xf1cfffff
> pci 0000:0e:00.0:   PREFETCH window: disabled
> decode_hpp: Could not get hotplug parameters. Use defaults
> pci 0000:0e:00.0: enabling device (0000 -> 0002)
> pci 0000:0e:00.0: setting latency timer to 64
> yenta_cardbus 0000:0f:00.0: no bus associated! (try 'pci=assign-busses')
> 
> lspci -v shows:
> 
> 0e:00.0 PCI bridge: Texas Instruments XIO2000(A)/XIO2200(A) PCI Express-to-PCI Bridge (rev 03) (prog-if 00 [Normal decode])
> 	Physical Slot: 1
> 	Flags: bus master, fast devsel, latency 0
> 	Bus: primary=0e, secondary=0f, subordinate=0f, sec-latency=64
> 	Memory behind bridge: f1c00000-f1cfffff
> 	Capabilities: [50] Power Management version 2
> 	Capabilities: [60] MSI: Enable- Count=1/16 Maskable- 64bit+
> 	Capabilities: [80] Subsystem: Device 5678:1234
> 	Capabilities: [90] Express PCI/PCI-X Bridge, MSI 00
> 	Capabilities: [100] Advanced Error Reporting
> 
> 0f:00.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller
> 	Subsystem: Texas Instruments Device ac48
> 	Flags: medium devsel, IRQ 255
> 	Memory at f1c00000 (32-bit, non-prefetchable) [disabled] [size=4K]
> 	Bus: primary=00, secondary=00, subordinate=00, sec-latency=0
> 	I/O window 0: 00000000-00000003 [disabled]
> 	I/O window 1: 00000000-00000003 [disabled]
> 	16-bit legacy interface ports at 0001
> 
> 
> Any idea where the problem is located or how can i fix it?
> 
> If you need further information or dumps please contact me.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/