[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1003121502160.6929@p34.internal.lan>
Date: Fri, 12 Mar 2010 15:02:52 -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, Yinghai Lu wrote:
> On Fri, Mar 12, 2010 at 5:10 AM, Justin Piszcz <jpiszcz@...idpixels.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?
Justin.
Powered by blists - more mailing lists