From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.33: pci 0000:00:00.0: address space collision / spontaenous reboots
Date: Fri, 12 Mar 2010 05:57:53 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.00.1003120556590.15732@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.2.00.1003120548551.6420@p34.internal.lan>
On Fri, 12 Mar 2010, Justin Piszcz wrote:
>
>
> On Fri, 12 Mar 2010, Justin Piszcz wrote:
>
>> 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
>
> Correction-
> noapic
> nolapic
>
--
[ 0.029932] pci_root PNP0A03:00: ignoring host bridge windows from ACPI; boot with "pci=use_crs" to use them
After booting with pci=use_crs, the collision goes away, as does another
problem with the jmicron controller, will see if this fixes it.
Justin.
next prev parent reply other threads:[~2010-03-12 10:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 10:25 Justin Piszcz
2010-03-12 10:49 ` Justin Piszcz
2010-03-12 10:57 ` Justin Piszcz [this message]
2010-03-12 12:44 ` Justin Piszcz
2010-03-12 12:56 ` Justin Piszcz
2010-03-12 13:10 ` 2.6.33: pci 0000:00:00.0: address space collision / spontaenous reboots [full dmesg] Justin Piszcz
2010-03-12 20:01 ` Yinghai Lu
2010-03-12 20:02 ` Justin Piszcz
2010-03-12 20:27 ` Yinghai Lu
2010-03-12 20:34 ` Justin Piszcz
2010-03-12 20:39 ` Justin Piszcz
2010-03-12 21:30 ` 2.6.34-rc1: pci 0000:00:00.0: address space collision / spontaenous reboots [now 2.6.34-rc1] Justin Piszcz
2010-03-12 21:43 ` Yinghai Lu
2010-03-12 21:48 ` Justin Piszcz
2010-03-12 21:50 ` Yinghai Lu
2010-03-12 21:52 ` Justin Piszcz
2010-03-12 21:52 ` Yinghai Lu
2010-03-13 9:01 ` Justin Piszcz
2010-03-18 22:58 ` Bjorn Helgaas
2010-03-18 23:00 ` Justin Piszcz
2010-03-18 23:19 ` Bjorn Helgaas
2010-03-19 9:45 ` Justin Piszcz
2010-03-12 21:43 ` 2.6.33: pci 0000:00:00.0: address space collision / spontaenous reboots [full dmesg] Yinghai Lu
2010-03-12 19:44 ` 2.6.33: pci 0000:00:00.0: address space collision / spontaenous reboots Yinghai Lu
2010-03-12 20:32 ` Justin Piszcz
2010-03-12 21:10 ` Yinghai Lu
2010-03-12 21:59 ` Bjorn Helgaas
2010-03-12 22:07 ` Justin Piszcz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.00.1003120556590.15732@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®