On Tue, 2010-07-27 at 16:22 -0400, Andrew Lee wrote:
> Hi Julien and Ben,
>
> On 2010年07月27日 14:58, Ben Hutchings wrote:
> >> The fix mentioned in previous message from waldi, says this fixed in
> >> 2.6.35-rc5.
> > [...]
> >
> > waldi's system has a GM965 chip whereas you have an 'Ironlake M' integrated
> > GPU. These aren't even from the same generation of Intel GPUs, so you
> > cannot assume that they will be affected from the same driver bugs.
>
> Thanks Ben,
> I assume that also affected from the same driver bugs cause I didn't
> know so much on the generation of Intel GPUs. But my experience is the
> bug appear from 2.6.32-10 and later version. So I am still running
> 2.6.32-9 on my laptop.
>
> @Julien, How do I bisect between 2.6.32-9 to 2.6.32-10?
Since we applied all the DRM changes from Linux 2.6.33 in 2.6.32-10, you
could start bisecting with this command:
git bisect v2.6.33 v2.6.32 drivers/gpu/drm/i915
> And should I also test 2.6.35-rc5 vanilla kernel to see if I can
> reproduce this problem still?
I suggest you test a 2.6.35-rc6 kernel package from experimental.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part