[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1003121647400.6929@p34.internal.lan>
Date: Fri, 12 Mar 2010 16:48: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.34-rc1: pci 0000:00:00.0: address space collision / spontaenous
reboots [now 2.6.34-rc1]
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists