| View previous topic :: View next topic |
| Author |
Message |
agrypa1
Apprentice
Joined: 31 Mar 2005
Posts: 244
|
 Posted: Wed Mar 10, 2010 9:42 am Post subject: address space collision, first line at boot time? |
 |
|
Hi,
The first line at boot time that I can see is this:
| Code: | | pci 0000:00:00.0: address space collision: [mem 0xd0000000-0xdfffffff pref] already in use |
And dmesg output reveals such things:
| Code: | PCI: Using ACPI for IRQ routing
PCI: pci_cache_line_size set to 64 bytes
pci 0000:00:00.0: address space collision: [mem 0xd0000000-0xdfffffff pref] already in use
pci 0000:00:00.0: can't reserve [mem 0xd0000000-0xdfffffff pref]
Switching to clocksource jiffies
pnp: PnP ACPI init
|
where should I start to even think about resolving this issue?
I don't even know whether it hurts my system or not.
Agryppa
_________________
The first successor of Saint Peter was Linus (a.d. 68-79) - whose namesake became the creator of Linux in our time. Torvalds' middle name is Benedict - the name assumed by the previous Pope who resigned from office. |
|
| Back to top |
|
 |
eccerr0r
Watchman
Joined: 01 Jul 2004
Posts: 9893
Location: almost Mile High in the USA
|
| Posted: Wed Mar 10, 2010 10:24 pm Post subject: |
|
|
Question is...anything not working? if everything looks good, then there's no problem 
The d000-0000 region is usually mapped to video card memory, so that would be the first suspect. Two video cards?
lspci -vvv might give some more clues as to what's occupying the memory region.
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
| Back to top |
|
|
roarinelk
Guru
Joined: 04 Mar 2004
Posts: 520
|
| Posted: Sat Mar 13, 2010 8:05 am Post subject: |
|
|
Try adding "pci=use_crs" to the kernel's commandline.
It solved similar collisions for me. |
|
| Back to top |
|
|
|
Kernel & Hardware
