Mailinglist Archive: opensuse-bugs (8080 mails)

< Previous Next >
[Bug 237229] report for using pci=assign-busses kernel parameter
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 2 Feb 2007 14:58:17 -0700 (MST)
  • Message-id: <20070202215817.009E325C887@xxxxxxxxxxxxxxxxxxxxxx>

f.alabas@xxxxxxxxxxxx changed:

What |Removed |Added
Info Provider|f.alabas@xxxxxxxxxxxx |

------- Comment #3 from f.alabas@xxxxxxxxxxxx 2007-02-02 14:58 MST -------
(In reply to comment #2)
> From my observations so far, this message is printed mainly on notebooks
> with Cardbus slots, and on some of those, the BIOS-configured PCI bus
> numbering is so that CardBus cards which are inserted in one of the
> CardBus slots never detected by the kernel and not shown in lspci.
> Your messages look like you have a BIOS with such PCI configuration,
> hence the warning, and booting with pci=assign-busses causes the kernel
> ignore the BIOS numbering and do PCI bus numbering himself, which fixes
> the issue in any case.

My BIOS has no PCI configuration option, but yes, I have a notebook with a
CardBus slot.

> If this message was just related to the CardBus bridge, the CardBus
> driver (Yenta) would have attempted to correct the misconfiguration
> itself, without pci=assign-busses.
> If you boot without pci=assign-busses, and this warning was indeed
> about the PCI ranges regarding the CardBus bridge, you should see
> messages from the Yenta driver, where it tries to fix the PCI ranges
> regarding the CardBus bridge.
> If you see: "Yenta: Raising subordinate bus# of parent bus ....",
> then in the kernel messages (boot log / dmesg) then Yenta has taken
> care of it already and your Cardbus cards should work even without
> pci=assign-busses.

Yes, this message seems to be related to just CardBus bridge, I think that's
why I see Yenta fixing the PCI ranges without pci=assign-busses at boot.

> In case they do not, please report it here please.
> If you do not have any isses with/without pci=assign-busses,
> please report as well.

Ok, I understand that I should find a PC card and test the both cases, should
With lspci, I see all the devices shown properly in both cases.

> Adding/removing pci=assign-busses may however invalidate your
> X congiuration (no GUI then, only text mode, but running "sax2 -a"
> should fix that) and possibly network configuration.

No problem occurs with X configuration and network when adding that parameter.

> I all works for you without pci=assign-busses the message is
> superflous in your case and should be removed in this case.
> I'll try to find the time to write a proper check to catch that then.

Should I check something else other than CardBus functionality ?

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

< Previous Next >