[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1003121538110.6929@p34.internal.lan>
Date: Fri, 12 Mar 2010 15:39:10 -0500 (EST)
From: Justin Piszcz <jpiszcz@...idpixels.com>
To: Yinghai Lu <yinghai@...nel.org>
cc: linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: 2.6.33: pci 0000:00:00.0: address space collision / spontaenous
reboots [full dmesg]
On Fri, 12 Mar 2010, Justin Piszcz wrote:
>
>
> On Fri, 12 Mar 2010, Yinghai Lu wrote:
>>>>
>>>> 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
>
Here is the lshw output:
*-pci:0
description: Host bridge
product: RD790 Northbridge only dual slot PCI-e_GFX and HT3 K8 part
vendor: ATI Technologies Inc
physical id: 100
bus info: pci@...0:00:00.0
version: 00
width: 64 bits
clock: 66MHz
configuration: latency=32
resources: memory:0-1fffffff
Justin.
Powered by blists - more mailing lists