PCI Address space collision memory 0000xxxx Already in use,etc?

linus72 · 06-26-2010, 12:05 PM

When booting my new x86_64 arch install using custom 2.6.33.3 kernel
I see that message scrool by quickly when booting

Is it bad thing or nothing serious?
The message scrolls by too fast to see all of it...

Just need to know if it's hurting my PC or what?

PC is HP a810n amd athlon64 3300+ 1GB RAM 2.4ghz
this is my first 64bit distro
as all others are 32bit and have never seen this boot message with them...

Thanks

H_TeXMeX_H · 06-26-2010, 01:47 PM

You can view anything that has scrolled by if you run 'dmesg' in a terminal. Try doing that and post the output.

linus72 · 06-26-2010, 02:09 PM

OK
well, I'm compiling new kernel so I have to reboot on that kernel to get messages
However; after installing default kernel26 2.6.34 x86_64
it now says PCI memory colliding with GART?

Here's present dmesg output
http://multidistro.com/dmesg.txt

seems like Chinese to me...?

H_TeXMeX_H · 06-26-2010, 02:30 PM

There are also:

Code:

spurious 8259A interrupt: IRQ7.

Code:

EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
 Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
 (Note that use of the override may cause unknown side effects.)
amd64_edac: probe of 0000:00:18.2 failed with error -22

Interestingly they are the same as:
http://www.linuxquestions.org/questi...8/#post4012853

For the other message, you can try the 'noioapic' boot option.

Can you also post the output of 'cat /proc/interrupts', maybe it says what IRQ 7 is associated with.

linus72 · 06-26-2010, 02:40 PM

OK
here's 'cat /proc/interrupts'
http://multidistro.com/interrupts

So, is it 'cause it's not really a 64bit PC or what?
thanks H_TeXMeX_H

H_TeXMeX_H · 06-26-2010, 03:01 PM

Code:

  7:          1   IO-APIC-edge      parport0

Looks like IRQ 7 is the parallel port, you got a printer attached to it ?

I doubt it has something to do with 64-bit. It may have something to do with visualization tho (but maybe not), from the dmesg it seems you're using Xen perhaps ?

linus72 · 06-26-2010, 04:15 PM

Ummm...no printer and no Xen...
it's pretty strange huh?

But, it's no harm or what?

I dont have any of this with any 32bit OS'
maybe I should stick with 32bit stuff or what?

H_TeXMeX_H · 06-27-2010, 04:23 AM

Well it says 'Booting paravirtualized kernel on bare hardware', which is odd. Are you sure this kernel was build properly. You can stick to 32-bit if this only happens with 64-bit. Although, I do wonder why this would happen only with 64-bit.

linus72 · 06-27-2010, 06:14 AM

hey H_TeXMeX_H

The kernel is ARCH's default kernel25 for x86_64

I'm gonna try again today to compile one from source
any hints?
also, I'm gonna post what dmesg, etc says on same PC with ARCH 32bit
Thanks

linus72 · 06-27-2010, 06:21 AM

OK
heres dmesg and /proc/interrupts on same PC but arch 32bit
any differences?

http://multidistro.com/dmesg32

http://multidistro.com/interrupts32

H_TeXMeX_H · 06-27-2010, 06:23 AM

Well, read the help if you don't understand an item, and if it says "say N here if you aren't sure", then say no for that option. My other recommendations were mostly for performance, but in general you should build things as modules, not built-in, that way they can be unloaded if they cause problems. You should also disable things that you never use, they just make the kernel large and can cause problems.