lkml.org 
[lkml]   [2008]   [Aug]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: Linux 2.6.27-rc5: System boot regression caused by commit a2bd7274b47124d2fc4dfdb8c0591f545ba749dd
    Date
    On Saturday, 30 of August 2008, Yinghai Lu wrote:
    > On Fri, Aug 29, 2008 at 5:20 PM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
    > > On Fri, Aug 29, 2008 at 5:08 PM, Linus Torvalds
    > > <torvalds@linux-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.

    http://www.sisk.pl/kernel/debug/mainline/2.6.27-rc5/lspci-tv.txt
    http://www.sisk.pl/kernel/debug/mainline/2.6.27-rc5/lspci-vvxxx.txt
    http://www.sisk.pl/kernel/debug/mainline/2.6.27-rc5/proc_iomem.txt

    Thanks,
    Rafael


    \
     
     \ /
      Last update: 2008-08-30 15:31    [W:2.486 / U:0.076 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site