From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: 2.6.33: pci 0000:00:00.0: address space collision / spontaenous reboots [full dmesg]
Date: Fri, 12 Mar 2010 15:34:01 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.00.1003121532300.6929@p34.internal.lan> (raw)
In-Reply-To: <86802c441003121227j77edc017vd83b2ab866ec79d8@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1615 bytes --]
On Fri, 12 Mar 2010, Yinghai Lu wrote:
> On Fri, Mar 12, 2010 at 12:02 PM, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>>
>>
>> On Fri, 12 Mar 2010, Yinghai Lu wrote:
>>
>>> On Fri, Mar 12, 2010 at 5:10 AM, Justin Piszcz <jpiszcz@lucidpixels.com>
>>> wrote:
>>>>
>>>> [ 0.112379] pci 0000:00:00.0: reg 1c: [mem 0xe0000000-0xffffffff
>>>> 64bit]
>>>
>>>> [ 0.133510] PCI: pci_cache_line_size set to 64 bytes
>>>> [ 0.133515] pci 0000:00:00.0: BAR 3: reserving [mem
>>>> 0xe0000000-0xffffffff
>>>> flags 0x120204] (d=0, p=0)
>>>> [ 0.133518] pci 0000:00:00.0: address space collision: [mem
>>>> 0xe0000000-0xffffffff 64bit] already in use
>>>> [ 0.133522] pci 0000:00:00.0: can't reserve [mem 0xe0000000-0xffffffff
>>>> 64bit]
>>>> [ 0.137020] system 00:09: [mem 0xe0000000-0xefffffff] has been
>>>> reserved
>>>> [ 0.172034] pci_bus 0000:00: resource 0 [io 0x0000-0xffff]
>>>> [ 0.172035] pci_bus 0000:00: resource 1 [mem 0x00000000-0xffffffff]
>>>
>>> looks like the silicon report wrong size in that BAR3
>>>
>>> YH
>>
>> Hi,
>>
>> Is there anyway to work around this? Or is it a bad motherboard?
>>
>
> maybe one new BIOS could hide that register
Hi,
It is using the latest F8c BIOS:
http://www.gigabyte.us/Products/Motherboard/Products_Overview.aspx?ProductID=3007
Other (earlier) bios' have been tested, that did not help either.
Is there anyway to to the kernel not to touch that range of memory?
0xe0000000-0xffffffff?
Justin.
>
> or use pci quirk to hide that in OS.
>
> may need to access the chipset doc.
>
> YH
>
next prev parent reply other threads:[~2010-03-12 20:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-12 10:25 2.6.33: pci 0000:00:00.0: address space collision / spontaenous reboots Justin Piszcz
2010-03-12 10:49 ` Justin Piszcz
2010-03-12 10:57 ` Justin Piszcz
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 [this message]
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.1003121532300.6929@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=yinghai@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®