linux-kernel - Re: Linux v2.6.17 - PCI Bus hidden behind transparent bridge

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: <20060717141315.GB2771@colo.lackof.org>
Date:	Mon, 17 Jul 2006 08:13:15 -0600
From:	Grant Grundler <grundler@...isc-linux.org>
To:	Julien Cristau <julien.cristau@...-lyon.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-pci@...ey.karlin.mff.cuni.cz
Subject: Re: Linux v2.6.17 - PCI Bus hidden behind transparent bridge

On Sun, Jul 16, 2006 at 09:34:53PM +0200, Julien Cristau wrote:
> Hi,
> 
> I have a cardbus wireless adapter which worked until 2.6.16, but doesn't
> on 2.6.17. I use standard Debian kernels, .config and dmesg outputs
> available at:
> http://liafa.jussieu.fr/~jcristau/tmp/dmesg-2.6.16
> http://liafa.jussieu.fr/~jcristau/tmp/dmesg-2.6.17
> http://liafa.jussieu.fr/~jcristau/tmp/config-2.6.16-2-686
> http://liafa.jussieu.fr/~jcristau/tmp/config-2.6.17-1-686

Julien,
thanks for posting this.

I diff'ed the dmesg output and I think this is the chunk
might be more explicit symptom of your problem:
-Loaded prism54 driver, version 1.2

This output comes from drivers/net/wireless/prism54/islpci_hotplug.c:
	printk(KERN_INFO "Loaded %s driver, version %s\n",

You can verify if the driver isn't getting loaded until later (udev?)
or not all by doing "modprobe prism54" and see of that starts
working. If not, then my next guess would be something changed in the
prism54 driver so it doesn't claim your device.

The other thing I noticed is IRQ11 is assigned to a different PCI device:
2.6.16 :
-PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
-ACPI: PCI Interrupt 0000:03:00.0[A] -> Link [PILC] -> GSI 11 (level, low) -> IR
Q 11


vs 2.6.17:
+ACPI: PCI Interrupt Link [PILA] enabled at IRQ 11
+ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [PILA] -> GSI 11 (level, low) -> IR
Q 11

This seems relevant since IRQ11 seems to be have been assigned by
the BIOS to _7_ devices according to the 2.6.16 lspci output.
This seems a bit unusual to me but maybe it's ok.

hth,
grant
-
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/