On Thu, Mar 6, 2014 at 1:25 PM, Paul Bolle <pebolle@xxxxxxxxxx> wrote: > Bjorn Helgaas schreef op ma 10-02-2014 om 14:33 [-0700]: >> 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. > > That took me quite a bit longer than I hoped, but I finally opened a > report at > https://bugzilla.kernel.org/show_bug.cgi?id=71611 . > > Note that the dmesg's are identical (up to that error). Are you still > interested? Yep, I wouldn't mind seeing the dmesg log to compare with the /proc/iomem contents you posted earlier. Since they're identical, there might not be a clue, but you never know, and it would be really great to squash this regression before v3.14. >> 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. > > I hope to do a bisect in the next few days. If that bisect pinpoints an > interesting commit that might just be in time for v3.14. > > > Paul Bolle > _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
