Bug 729652
| Summary: | PNP0A08: host bridge window [mem 0x000cc000-0x000cffff] conflicts with Video ROM [mem 0x000c0000-0x000cedff | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jóhann B. Guðmundsson <johannbg> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 16 | CC: | bhelgaas, collura, gansalmon, hafflys, itamar, jonathan, jones.peter.busi, kernel-maint, madhu.chinakonda, steven.chapel | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | 3.1.0-0.rc3.git0.0 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-09-01 06:50:06 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Did this just start happening with a recent kernel or has it been happening on older releases too? You can just ignore that message; it's not telling us anything useful. Upstream commit 43d786ed4df4c54cb8802a523748a7d78130a2cb should resolve this (it only downgrades the message from KERN_ERR to KERN_INFO). I'm pretty sure the display glitches are unrelated to this message. You could boot with "pci=nocrs", which will turn off the code that pays attention to the host bridge windows, and should make the message go away. I don't think "pci=nocrs" will make any difference as far as the glitches. If it *does* make a difference, then they're related and we need to investigate more. (In reply to comment #1) > Did this just start happening with a recent kernel or has it been happening on > older releases too? This started to appear with 3.0.0 I'll test with older kernels tonight (In reply to comment #2) > You can just ignore that message; it's not telling us anything useful. > > Upstream commit 43d786ed4df4c54cb8802a523748a7d78130a2cb should resolve this > (it only downgrades the message from KERN_ERR to KERN_INFO). > > I'm pretty sure the display glitches are unrelated to this message. You could > boot with "pci=nocrs", which will turn off the code that pays attention to the > host bridge windows, and should make the message go away. I don't think > "pci=nocrs" will make any difference as far as the glitches. If it *does* make > a difference, then they're related and we need to investigate more. From the test list others are seeing clitches hence this seems to be radeon/clutter/gnome-shell not the kernel that causes that. This keeps getting reported, so I've included the patch from 3.1 to reduce the severity of the warning. *** Bug 706606 has been marked as a duplicate of this bug. *** kernel-2.6.40.4-5.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/kernel-2.6.40.4-5.fc15 yes this warning disappeared when upgraded to kernel-2.6.40.4-5.fc15 (x86_64) thanks kernel-2.6.40.4-5.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. |
Created attachment 517597 [details] Dmesg Description of problem: [ 0.445252] pci_root PNP0A08:00: address space collision: host bridge window [mem 0x000cc000-0x000cffff] conflicts with Video ROM [mem 0x000c0000-0x000cedff Do see display glitches ( fonts weird not all icons showing unless I move the mouse pointer to the missing side then they appear etc.. ) but that could be Gnome-shell or the Xorg driver. The card is. 01:05.0 VGA compatible controller: ATI Technologies Inc M880G [Mobility Radeon HD 4200] Version-Release number of selected component (if applicable): 3.0.1-3.fc16.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: