From: Yinghai Lu <yinghai@kernel.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: 2.6.34-rc1: pci 0000:00:00.0: address space collision / spontaenous reboots [now 2.6.34-rc1]
Date: Fri, 12 Mar 2010 13:52:46 -0800 [thread overview]
Message-ID: <4B9AB7AE.7000002@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1003121651460.6929@p34.internal.lan>
On 03/12/2010 01:52 PM, Justin Piszcz wrote:
>
>
> On Fri, 12 Mar 2010, Yinghai Lu wrote:
>
>> On 03/12/2010 01:30 PM, Justin Piszcz wrote:
>>>
>>>
>>> On Fri, 12 Mar 2010, Justin Piszcz wrote:
>>>
>>>> On Fri, 12 Mar 2010, Justin Piszcz wrote:
>>>>
>>>
>>> # Disable Bootmem code (NO_BOOTMEM) [Y/n/?] (NEW)
>>>
>>> I see this new option ^
>>>
>>> Ok, booting 2.6.34-rc1:
>>>
>>> [ 0.132248] PCI: pci_cache_line_size set to 64 bytes
>>> [ 0.132248] pci 0000:00:00.0: BAR 3: reserving [mem
>>> 0xe0000000-0xffffffff flags 0x120204] (d=0, p=0)
>>> [ 0.132248] pci 0000:00:00.0: no compatible bridge window for [mem
>>> 0xe0000000-0xffffffff 64bit]
>>> [ 0.132248] pci 0000:00:00.0: can't reserve [mem
>>> 0xe0000000-0xffffffff 64bit]
>>>
>>> Full dmesg:
>>> http://home.comcast.net/~jpiszcz/20100312/dmesg-2.6.34-rc1.txt
>>>
>> [ 0.097651] node 0 link 0: io port [b000, ffff]
>> [ 0.097654] TOM: 0000000040000000 aka 1024M
>> [ 0.097657] Fam 10h mmconf [e0000000, e00fffff]
>> [ 0.097659] node 0 link 0: mmio [a0000, bffff]
>> [ 0.097661] node 0 link 0: mmio [40000000, dfffffff]
>> [ 0.097663] node 0 link 0: mmio [f0000000, fe02ffff]
>> [ 0.097665] node 0 link 0: mmio [e0000000, e04fffff] ==> [e0100000,
>> e04fffff]
>> [ 0.097668] bus: [00, 04] on node 0 link 0
>> [ 0.097670] bus: 00 index 0 [io 0x0000-0xffff]
>> [ 0.097672] bus: 00 index 1 [mem 0x000a0000-0x000bffff]
>> [ 0.097674] bus: 00 index 2 [mem 0x40000000-0xdfffffff]
>> [ 0.097676] bus: 00 index 3 [mem 0xe0500000-0xffffffff]
>> [ 0.097677] bus: 00 index 4 [mem 0xe0100000-0xe04fffff]
>>
>> that looks like setting MMCONFIG through ATI chipset.
>>
>> and cpu northbridge set 1M for accessing 1M...
>>
>> BIOS really should only use northbridge MSR to set that to cover bus
>> [0, 255]
>>
>> and just disable the ATI pci 00:00.0 BAR3
>
> Ok, so the BIOS is broken, is there a pci= option to workaround this in
> the interim, or does a quirk need to be implemented?
should be ok, just some warning.
YH
next prev parent reply other threads:[~2010-03-12 21:53 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
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 [this message]
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=4B9AB7AE.7000002@kernel.org \
--to=yinghai@kernel.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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