From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932605Ab0CLKZ5 (ORCPT <rfc822;w@1wt.eu>);
	Fri, 12 Mar 2010 05:25:57 -0500
Received: from lucidpixels.com ([75.144.35.66]:46808 "EHLO lucidpixels.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S932482Ab0CLKZ4 (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Fri, 12 Mar 2010 05:25:56 -0500
Date: Fri, 12 Mar 2010 05:25:53 -0500 (EST)
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.33: pci 0000:00:00.0: address space collision / spontaenous
 reboots
Message-ID: <alpine.DEB.2.00.1003120522550.6420@p34.internal.lan>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hello,

I am trying to figure out why a particular host using a Gigabyte motherboard
(AMD) continues to crash, memory/CPU OK, voltages normal, I see this in
the kernel log:

[    0.138774] PCI: Using ACPI for IRQ routing
[    0.138825] PCI: pci_cache_line_size set to 64 bytes
[    0.138830] pci 0000:00:00.0: address space collision: [mem 0xe0000000-0xffffffff 64bit] already in use

If memory gets mapped into this space somehow, can that cause a spontaenous
reboot?  What is the workaround for this problem?

There are no PCI cards in this system, only a graphics card.

I suppose the next things to try:
apic=off
lapic=off

Justin.