Re: [Intel-gfx] agp/intel: can't ioremap flush page - no chipset flushing
From: Bjorn Helgaas
Date: Mon Feb 10 2014 - 16:34:08 EST
On Sun, Feb 9, 2014 at 6:25 AM, Paul Bolle <pebolle@xxxxxxxxxx> wrote:
> On Sun, 2014-02-09 at 13:15 +0000, Steven Newbury wrote:
>> PCI resource allocation is undergoing some changes at the moment, it's
>> definitely a bug if the Flush Page isn't getting allocated. I'm looking
>> forward to hopefully getting pci_bus_alloc_resource_fit() behaviour in
>> mainline, it will provide much better resource allocation in the 32 bit
>> PCI address space, and prevent problems like this from cropping up.
>>
>> See Yinghai Lu's for-pci-res-alloc branch.
>>
>> I've been carrying the changes in my local tree, but right now the
>> upstream PCI changes are quite extensive. He's planning on rebasing the
>> branch soon.
>
> Does this mean I might be better of not bisecting this just yet? Or are
> these changes targeted at v3.15 (or later)?
Yinghai's changes would probably be in v3.15 or later.
Can you open a kernel.org bugzilla report and attach complete dmesg
logs of the working and broken kernels to it? There might be more
useful resource-related messages from the PCI core.
I wouldn't start bisecting yet, but if you're in the mood, this
commit: 96702be56037 "Merge branch 'pci/resource' into next" looks
like a good place to start, so you could try the pre-merge commit:
04f982beb900 "Merge branch 'pci/msi' into next". If 04f982beb900 is
good, there are only about 15 commits on the pci/resource branch to
look at.
Thanks for the report!
Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/