Geoff Crompton wrote: > I had been considering building a kernel for each patch where the kernel > only includes that one patch. But with 17 patches, that seems like a lot > of kernels to test (for me anyway). So I've further whittled that down > by looking for patches that mention 'backport': > > geoffc@hulk:~/debs/linux-3.2.39$ cat ../i915_bug_patch_shortlist | xargs > grep -li backport > debian/patches/bugfix/all/i915-ensure-that-VGA-plane-is-disabled.patch > debian/patches/bugfix/x86/drm-i915-add-quirk_invert_brightness-for-ncr-machine.patch > debian/patches/bugfix/x86/drm-i915-Close-race-between-processing-unpin-task-an.patch > debian/patches/bugfix/x86/drm-i915-Disable-AsyncFlip-performance-optimisations.patch > debian/patches/bugfix/x86/drm-i915-dump-UTS_RELEASE-into-the-error_state.patch > debian/patches/bugfix/x86/drm-i915-GFX_MODE-Flush-TLB-Invalidate-Mode-must-be-.patch > debian/patches/bugfix/x86/drm-i915-kick-any-firmware-framebuffers-before-claim.patch > debian/patches/bugfix/x86/drm-i915-Only-increment-the-user-pin-count-after-suc.patch > > For these 8 patches I'll attempt to build packages that only include a > single patch from this short list, and see if one of those kernels > crashes. I don't have access to the machine that I've seen the bug on > until next week.
Unfortunately I don't think the patches are independent. If you can find a way to bisect among them to see which introduces the problem, that would be great, but please also do test the 3.8.y kernel from experimental so we can get upstream help. Thanks again and sorry for the trouble, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130402223058.ga30...@google.com
