Description of problem: When X starts it attempts to query the PCI bus -- in the current (and upstream) versions of X it does not successfully do this on ia64. Version-Release number of selected component (if applicable): xorg-x11-drivers-7.0-2 from rawhide-20060310 How reproducible: 100% Steps to Reproduce: 1. startx Actual results: Log shows (II) Addressable bus resource ranges are (II) OS-reported resource ranges: (II) OS-reported resource ranges after removing overlaps with PCI: (II) All system resource ranges: Expected results: X should query the PCI bus properly. Additional info: I know ia64 graphics equipment is hard to find. If anyone needs an ia64 graphics box, please email prarit.
Dump of RH BZ 185100, which will track the problem closely. Adam Jackson was with me and determined the nature of the bug -- he will more than likely be assigned to the issue. Description of problem: When X starts it attempts to query the PCI bus -- in the current (and upstream) versions of X it does not successfully do this on ia64. Version-Release number of selected component (if applicable): xorg-x11-drivers-7.0-2 from rawhide-20060310 How reproducible: 100% Steps to Reproduce: 1. startx Actual results: Log shows (II) Addressable bus resource ranges are (II) OS-reported resource ranges: (II) OS-reported resource ranges after removing overlaps with PCI: (II) All system resource ranges: Expected results: X should query the PCI bus properly. Additional info: I know ia64 graphics equipment is hard to find. If anyone needs an ia64 graphics box, please email prarit.
Oops. That was cut and pasted to the wrong window :( P.
Would be interested to know if this still happens with xorg-x11-server-1.1.1-43 or later. There was some mild domain-awareness committed there.
-> NEEDINFO
George, please see if you can answer ajax's comment #3 ... P.
You'll need the same patches as bug #211530.
For reference, the only one of those patches that's not currently upstream in xserver 1.3 is: https://bugs.freedesktop.org/attachment.cgi?id=7713&action=view Which looks... mostly okay? The bits that change the generic code I'm still slightly uncomfortable with.
Prarit, is this still an issue for us?
Ajax, I haven't tested on the PRISM for a while as it now is in the hands of gbeshers -- I'll assign the NEEDINFO to him. P.
gbeshers, could you please try to reproduce this bug and let us know the results? Thank you.
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
No information requested provided, no joy for anybody -- closing this bug as INSUFFICIENT_DATA. Reporter, if you could, please, reopen with additional information.