From: Grant Grundler <grundler@parisc-linux.org>
To: Julien Cristau <julien.cristau@ens-lyon.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: Linux v2.6.17 - PCI Bus hidden behind transparent bridge
Date: Mon, 17 Jul 2006 08:13:15 -0600 [thread overview]
Message-ID: <20060717141315.GB2771@colo.lackof.org> (raw)
In-Reply-To: <20060716193452.GA5299@bryan.is-a-geek.org>
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
next prev parent reply other threads:[~2006-07-17 14:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 1:59 Linux v2.6.17 Linus Torvalds
2006-06-18 2:06 ` Linus Torvalds
2006-06-18 3:30 ` Brice Goglin
2006-06-18 3:47 ` Linus Torvalds
2006-06-19 1:39 ` Petr Baudis
2006-06-18 13:49 ` Adrian Bunk
2006-06-18 16:44 ` Linus Torvalds
2006-06-19 21:25 ` Adrian Bunk
2006-06-19 14:23 ` Mark Lord
2006-06-18 10:54 ` Michael Buesch
2006-06-18 16:47 ` Andre Tomt
2006-06-18 17:05 ` Michael Buesch
2006-07-16 19:34 ` Linux v2.6.17 - PCI Bus hidden behind transparent bridge Julien Cristau
2006-07-17 14:13 ` Grant Grundler [this message]
2006-07-17 14:29 ` Julien Cristau
2006-07-17 15:31 ` Grant Grundler
2006-07-17 16:13 ` Julien Cristau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060717141315.GB2771@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=julien.cristau@ens-lyon.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®