[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.1.10.0808311039330.12958@nehalem.linux-foundation.org>
Date: Sun, 31 Aug 2008 10:42:41 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: "Rafael J. Wysocki" <rjw@...k.pl>
cc: Yinghai Lu <yhlu.kernel@...il.com>,
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 Sun, 31 Aug 2008, Rafael J. Wysocki wrote:
>
> Works, dmesg is at:
> http://www.sisk.pl/kernel/debug/mainline/2.6.27-rc5/2.6.27-rc5-test.log
That BAR is indeed "locked". Now that we try to reallocate it, you get
this in the log:
pci 0000:00:00.0: BAR 3: error updating (0x40000004 != 0xe0000004)
pci 0000:00:00.0: BAR 3: error updating (high 0x000001 != 0x000000)
ie now the code _tried_ to update the BAR to point to 0x1_4000_0000
instead, but the hardware refused, and it is still at 0x0_e000_0000.
So Yinghai's patch "worked", but it worked by doing nothing.
See my earlier guess about locked read-only resources a few emails back.
IOW, I'm not at all surprised. I really do suspect that that BAR is some
very special "this is the HT->PCIE region" BAR.
Linus
--
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