From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757299Ab0CLVsN (ORCPT ); Fri, 12 Mar 2010 16:48:13 -0500 Received: from lucidpixels.com ([75.144.35.66]:59619 "EHLO lucidpixels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753582Ab0CLVsL (ORCPT ); Fri, 12 Mar 2010 16:48:11 -0500 Date: Fri, 12 Mar 2010 16:48:10 -0500 (EST) From: Justin Piszcz To: Yinghai Lu 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] In-Reply-To: <4B9AB58D.4010305@kernel.org> Message-ID: References: <86802c441003121201y4c946fecrda5463b056f1ba58@mail.gmail.com> <86802c441003121227j77edc017vd83b2ab866ec79d8@mail.gmail.com> <4B9AB58D.4010305@kernel.org> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > > so it boots well? > > YH > Hi, They all boot well, but when there is I/O going on (disk) it crashes, so far I am running 2.6.34-rc1 and waiting for the next crash. Justin.