From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934597Ab0CLUeH (ORCPT ); Fri, 12 Mar 2010 15:34:07 -0500 Received: from lucidpixels.com ([75.144.35.66]:55787 "EHLO lucidpixels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934556Ab0CLUeC (ORCPT ); Fri, 12 Mar 2010 15:34:02 -0500 Date: Fri, 12 Mar 2010 15:34:01 -0500 (EST) From: Justin Piszcz To: Yinghai Lu 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] In-Reply-To: <86802c441003121227j77edc017vd83b2ab866ec79d8@mail.gmail.com> Message-ID: References: <86802c441003121201y4c946fecrda5463b056f1ba58@mail.gmail.com> <86802c441003121227j77edc017vd83b2ab866ec79d8@mail.gmail.com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1463747160-643406446-1268426041=:6929" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---1463747160-643406446-1268426041=:6929 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Fri, 12 Mar 2010, Yinghai Lu wrote: > On Fri, Mar 12, 2010 at 12:02 PM, Justin Piszcz = wrote: >> >> >> On Fri, 12 Mar 2010, Yinghai Lu wrote: >> >>> On Fri, Mar 12, 2010 at 5:10 AM, Justin Piszcz >>> wrote: >>>> >>>> [ =A0 =A00.112379] pci 0000:00:00.0: reg 1c: [mem 0xe0000000-0xfffffff= f >>>> 64bit] >>> >>>> [ =A0 =A00.133510] PCI: pci_cache_line_size set to 64 bytes >>>> [ =A0 =A00.133515] pci 0000:00:00.0: BAR 3: reserving [mem >>>> 0xe0000000-0xffffffff >>>> flags 0x120204] (d=3D0, p=3D0) >>>> [ =A0 =A00.133518] pci 0000:00:00.0: address space collision: [mem >>>> 0xe0000000-0xffffffff 64bit] already in use >>>> [ =A0 =A00.133522] pci 0000:00:00.0: can't reserve [mem 0xe0000000-0xf= fffffff >>>> 64bit] >>>> [ =A0 =A00.137020] system 00:09: [mem 0xe0000000-0xefffffff] has been >>>> reserved >>>> [ =A0 =A00.172034] pci_bus 0000:00: resource 0 [io =A00x0000-0xffff] >>>> [ =A0 =A00.172035] pci_bus 0000:00: resource 1 [mem 0x00000000-0xfffff= fff] >>> >>> looks like the silicon report wrong size in that BAR3 >>> >>> YH >> >> Hi, >> >> Is there anyway to work around this? =A0Or 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?ProductI= D=3D3007 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 > ---1463747160-643406446-1268426041=:6929--