[SOLVED] Address space collision after kernel 3.0 upgrade

king.flasher.dave · 2011-08-08 12:31:09

After upgrading to linux 3.0.1 I get the following error messages from kernel:

kernel: [    0.313527] pci_root PNP0A08:00: address space collision: host bridge window [mem 0x000cc000-0x000cffff] conflicts with Video ROM [mem 0x000c0000-0x000ce9ff]
kernel: [    0.313537] pci_root PNP0A08:00: address space collision: host bridge window [mem 0x000d0000-0x000d3fff] conflicts with Adapter ROM [mem 0x000cf000-0x000d0fff]

Anyone having similar issues? What could this be related to?
Everything seems to work fine so far... but this message is making me a little nervous....

Last edited by king.flasher.dave (2011-08-31 14:20:33)

_will · 2011-08-08 13:48:39

I have something similar.
I don't know what it means, or even if it is a new message.

sudo grep collision /var/log/everything.log 
Aug  8 09:32:39 localhost kernel: [    0.297811] pci 0000:00:1d.7: address space collision: [mem 0xf0504000-0xf05043ff] conflicts with PCI Bus 0000:09 [mem 0xf0500000-0xf05fffff 64bit pref]
Aug  8 09:32:39 localhost kernel: [    0.297832] pci 0000:00:1f.2: address space collision: [mem 0xf0504400-0xf05047ff] conflicts with PCI Bus 0000:09 [mem 0xf0500000-0xf05fffff 64bit pref]

king.flasher.dave · 2011-08-09 10:47:56

I have another machine that is not on the new kernel yet.
It does not produce this message, but after all it has different hardware...
Hmm, hope it'll be different after the upgrade. Will post some updates later on.

ataraxia · 2011-08-09 16:10:04

The kernel is reporting a BIOS bug (in the DSDT table). Many BIOS tables say nonsense things like two pieces of hardware being addressable at the same location of memory. Most likely it's been that way all along, but over time the kernel devs check for more of these things, thus new error messages come out.

If all of your hardware still works, then you can ignore it. Otherwise, you can try upgrading BIOS firmware in the hope that a newer version doesn't have the bug. (Or you can correct the table yourself and get the kernel to use the corrected copy from disk instead of the one in firmware, but I've found that to be very hard to accomplish.)

cpurodriguez · 2011-08-09 21:35:04

I'm having this issue too.

pci_root PNP0A08:00: address space collision: host bridge window [mem 0x000cc000-0x000cffff] conflicts with Video ROM [mem 0x000c0000-0x000cf1ff]

After I updated the kernel, I got a black screen.
I had to add nomodeset argument to the boot options in order to log in, but I still don't know if this is related to the collision issue.

exiquio · 2011-08-18 16:19:12

Same thing happening with me and my laptop after a 3.0.* update of core/linux. I like ataraxia's answer. Makes sense to me. Everything is working as fine as it was before.

Thedemon007 · 2011-08-20 09:56:55

My messages: http://pastebin.archlinux.fr/433636

[    0.187751] pci_root PNP0A03:00: address space collision: host bridge window [mem 0x000d0000-0x000dffff] conflicts with Adapter ROM [mem 0x000cf000-0x000dbfff]

in kernel lts no see this message

king.flasher.dave · 2011-08-25 16:31:34

Alrite... it seems that at least for my laptop it is not posing a problem.
There is one small issue though: It slows down the bootup (as it seems) before init.

jakobm · 2011-08-26 10:49:28

Upstream bug #16497, patch has been merged in linux-next (see commit)

king.flasher.dave · 2011-08-31 14:20:14

Thanks for the info, Jakob!
Hope this will find its way to our kernel soon.
Closing this.

kgas · 2011-09-25 13:27:40

In hp-dv5 I got similar message. using pci=nocrs in kernel line is workaround for now

Arch Linux

#1 2011-08-08 12:31:09

[SOLVED] Address space collision after kernel 3.0 upgrade

#2 2011-08-08 13:48:39

Re: [SOLVED] Address space collision after kernel 3.0 upgrade

#3 2011-08-09 10:47:56

Re: [SOLVED] Address space collision after kernel 3.0 upgrade

#4 2011-08-09 16:10:04

Re: [SOLVED] Address space collision after kernel 3.0 upgrade

#5 2011-08-09 21:35:04

Re: [SOLVED] Address space collision after kernel 3.0 upgrade

#6 2011-08-18 16:19:12

Re: [SOLVED] Address space collision after kernel 3.0 upgrade

#7 2011-08-20 09:56:55

Re: [SOLVED] Address space collision after kernel 3.0 upgrade

#8 2011-08-25 16:31:34

Re: [SOLVED] Address space collision after kernel 3.0 upgrade

#9 2011-08-26 10:49:28

Re: [SOLVED] Address space collision after kernel 3.0 upgrade

#10 2011-08-31 14:20:14

Re: [SOLVED] Address space collision after kernel 3.0 upgrade

#11 2011-09-25 13:27:40

Re: [SOLVED] Address space collision after kernel 3.0 upgrade

Board footer