[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86802c440808291727nbd297c0w8a2a60bed423c0f7@mail.gmail.com>
Date: Fri, 29 Aug 2008 17:27:50 -0700
From: "Yinghai Lu" <yhlu.kernel@...il.com>
To: "Linus Torvalds" <torvalds@...ux-foundation.org>,
"Rafael J. Wysocki" <rjw@...k.pl>
Cc: "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
"Jeff Garzik" <jeff@...zik.org>, "Tejun Heo" <htejun@...il.com>,
"Ingo Molnar" <mingo@...e.hu>,
"David Witbrodt" <dawitbro@...global.net>,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Kernel Testers" <kernel-testers@...r.kernel.org>
Subject: Re: Linux 2.6.27-rc5: System boot regression caused by commit a2bd7274b47124d2fc4dfdb8c0591f545ba749dd
On Fri, Aug 29, 2008 at 5:20 PM, Yinghai Lu <yhlu.kernel@...il.com> wrote:
> On Fri, Aug 29, 2008 at 5:08 PM, Linus Torvalds
> <torvalds@...ux-foundation.org> wrote:
>>
>>
>> On Fri, 29 Aug 2008, Yinghai Lu wrote:
>>> >
>>> > http://www.sisk.pl/kernel/debug/mainline/2.6.27-rc5/broken.log
>>>
>>> pci 0000:00:00.0: BAR has MMCONFIG at e0000000-ffffffff
>>
>> And that seems utter crap to begin with.
>>
>> PCI: Using MMCONFIG at e0000000 - efffffff
>>
>> Where did it get that bogus "ffffffff" end address?
>>
>> Anyway, that whole MMCONFIG/BAR thing was totally broken to begin with,
>> and it's reverted now in my tree, so I guess it doesn't much matter.
>
> we need to handle it. otherwise if the BAR go first, and it will stop
> other BARs to be registered...
>
> a quirk should do the work....
>
> Rafael, can you send out lspci -tv and lspci --vvxxx too.
cat /proc/iomem please.
YH
--
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