Most recent kernel where this bug did *NOT* occur: Distribution: Ubuntu Edgy Hardware Environment: https://wiki.ubuntu.com/LaptopTestingTeam/CompaqPresarioV2417LA/Hardware Software Environment: Default + updates + automatix2 Problem Description: Message in log [17179573.656000] Please report the result to linux-kernel to fix this permanently [17179573.656000] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] [17179573.660000] ACPI: PCI Interrupt Link [LNKA] (IRQs 10 11) *0, disabled. [17179573.660000] ACPI: PCI Interrupt Link [LNKB] (IRQs 10 11) *0, disabled. [17179573.660000] ACPI: PCI Interrupt Link [LNKC] (IRQs 10 11) *0, disabled. [17179573.660000] ACPI: PCI Interrupt Link [LNKD] (IRQs 10 11) *0, disabled. [17179573.660000] ACPI: PCI Interrupt Link [LNKE] (IRQs 10 11) *0, disabled. [17179573.660000] ACPI: PCI Interrupt Link [LNKF] (IRQs 10 11) *0, disabled. [17179573.660000] ACPI: PCI Interrupt Link [LNKG] (IRQs 10 11) *0, disabled. [17179573.660000] ACPI: PCI Interrupt Link [LNKH] (IRQs 10 11) *0, disabled. [17179573.660000] ACPI: Embedded Controller [EC0] (gpe 24) interrupt mode. [17179573.664000] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P2P_._PRT] [17179573.664000] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT] [17179573.664000] Linux Plug and Play Support v0.97 (c) Adam Belay Steps to reproduce:
Package: linux-image-2.6.17-10-generic Version: 2.6.17-10.33 -- System Information: Debian Release: testing/unstable APT prefers edgy-updates APT policy: (500, 'edgy-updates'), (500, 'edgy-security'), (500, 'edgy-backports'), (500, 'edgy') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.17-10-generic Locale: LANG=es_CL.UTF-8, LC_CTYPE=es_CL.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.17-10-generic depends on: ii coreutils [fileutils] 5.96-5ubuntu4 The GNU core utilities ii initramfs-tools 0.69ubuntu20 tools for generating an initramfs ii module-init-tools 3.2.2-3ubuntu3 tools for managing Linux kernel mo Versions of packages linux-image-2.6.17-10-generic recommends: ii grub 0.97-11ubuntu14 GRand Unified Bootloader -- debconf-show failed
I think it'd be better if you attached the full dmesg
Created attachment 9555 [details] $dmesg 2.6.17-10-generic
I'm not sure but i think you must try the 'pci=assign-busses' kernel boot option and attach the dmesg again.
Created attachment 9913 [details] $sudo cat /boot/grub/menu.lst
Created attachment 9914 [details] $dmesg 2.6.17-10-generic
Thanks Diego for you comment.
Created attachment 9916 [details] $sudo cat /boot/grub/menu.lst Ups
Created attachment 9917 [details] $dmesg 2.6.17-10-generic with pci=assign-busses ups
Created attachment 10018 [details] $dmesg 2.6.20-5-lowlatency update linux. Now work with 2.6.20RC2
I test proyect http://www.linuxfirmwarekit.org/ Unfo my BIOS: http://www.bughost.org/pipermail/firmwarekit-results/2007-February/000094.html (Revise file results-0001.xml)
> Linux version 2.6.20-5-lowlatency ... > PCI: Bus #06 (-#09) is hidden behind transparent bridge #05 (-#05) (try 'pci=assign-busses') > Please report the result to linux-kernel to fix this permanently assigning this to the PCI sub-system.
Created attachment 11852 [details] Kernel command line: [...] pci=assign-busses
So assigned to the PCI subsystem. Any hint of progress? Is this a hw bug that needs a workaround, or is this a kernel bug?
Original bug report: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/78340
For Greg and others: This the same text as I used in bug 7831, so you do not have to read it again. Many thanks for the report, I reviewed it and have this result: The message Bus #06 (-#09) is hidden behind transparent bridge #05 (-#05) indicates that some PCI busses may not reachable by your system, but it is very likely that if these buses are allocated to a CardBus slot. In this (likely case), yenta-socket fixes this in current kernels, and your drivers see your Cardbus cards. This means that when they are shown in lspci, there is no real issue except that the too sensitve check for this message needs to be fixed or the message removed. Unless you have PCI hardware (such as CardBus cards, not old PCMCIA cards) connected to your machine which is not shown by lspci after loading all neccessary drivers (eg. yenta_socket), we can close this bug: I'd then go forward and simply propose to either delete this warning check or to change to it a PCI-internal warning message which is normally supressed and only enabled when developers debug PCI bus scanning and refine it a bit so that it only is triggered in cases which are not addressed by yenta-socket. Not that if a secific driver is not working, then this is not in relation to this bug report, this bug report is only about PCI devices which may potentially not show up in lspci and for which the driver also will never see. Unless the PCI device is not shown in PCI, open a new bug if you have an issue with a driver. With your laptop, there would only be an issue if you connect an external PCI enclosure which itself has further internal PCI busses thru your cardbus slot to your laptop, but that case is also adressed by yenta-socket in current kernels. Again many thanks for the report and if I hear nothing new regarding this bug report, I'll close it when the 'bus hidden behind bridge' message is fixed.
Created attachment 12261 [details] Linux ubuntu 2.6.22-8-generic I testing Ubuntu Tribe 3, Ubuntu tribe 3 work with kernel 2.6.22-8. I update attach of dmesg with pci=assign-busses. Thanks!
The PCI misconfiguration which is being indicated in this message only turned out to be an issue with CardBus and it is being fixed up within the possible limits of that approach in CardBus driver with yenta_fixup_parent_bridge() (since 2.6.18) and as that has turned out as sufficient, we changed the reporting of this misconfiguration to be printed only when debugging PCI: In a patch which is merged mainline with 2.6.22.6 and 2.6.23, I improved the the message and changed it a PCI debugging message only, so it's not shown unless PCI is being debugged. The issue can be considered to be closed now. Is this just a warning which I left in to be sure that the reason for it is properly dealt with, but we removed it from the normal user's sight now because we found * that the PCI misconfiguration which is being indicated in this message only seems to be an issue with CardBus. * that the CardBus fixup code which we have in place since 2.6.18 with appears to be sufficient. Thus, I submitted a patch which was merged mainline with 2.6.22.6 and 2.6.23 that turns it into a message which is only enabled when debugging PCI, so in practical users terms, the warning is gone.
*** Bug 8480 has been marked as a duplicate of this bug. ***
*** Bug 6783 has been marked as a duplicate of this bug. ***
*** Bug 9049 has been marked as a duplicate of this bug. ***
*** Bug 7575 has been marked as a duplicate of this bug. ***
*** Bug 8903 has been marked as a duplicate of this bug. ***
*** Bug 8899 has been marked as a duplicate of this bug. ***
*** Bug 8772 has been marked as a duplicate of this bug. ***
*** Bug 7831 has been marked as a duplicate of this bug. ***
*** Bug 8748 has been marked as a duplicate of this bug. ***
Created attachment 13260 [details] $dmesg in kernel 2.23.1 Hello, attach dmesg with kernel 2.6.23.1, now not message. Thanks