Bug 16871
Summary: | i915: bisected - "TV1 connected" with no tv | ||
---|---|---|---|
Product: | Drivers | Reporter: | Luca (lbonco) |
Component: | Video(DRI - Intel) | Assignee: | drivers_video-dri-intel (drivers_video-dri-intel) |
Status: | CLOSED CODE_FIX | ||
Severity: | normal | CC: | chris, combuster, florian |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.36-rc2 | Subsystem: | |
Regression: | Yes | Bisected commit-id: |
Description
Luca
2010-08-24 12:04:00 UTC
You might want to double check your bisection. That code isn't even touched for your chipset. Sporadic TV misdetection has been around for a long time, and other bisection results indicate that the problem has been exacerbated by: commit 9d0498a2bf7455159b317f19531a3e5db2ecc9c4 Author: Jesse Barnes <jbarnes@virtuousgeek.org> Date: Wed Aug 18 13:20:54 2010 -0700 drm/i915: wait for actual vblank, not just 20ms Waiting for a hard coded 20ms isn't always enough to make sure a vblank period has actually occurred, so add code to make sure we really have passed through a vblank period (or that the pipe is off when disabling). This prevents problems with mode setting and link training, and seems to fix a bug like https://bugs.freedesktop.org/show_bug.cgi?id=29278, but on an HP 8440p instead. Hopefully also fixes https://bugs.freedesktop.org/show_bug.cgi?id=29141. Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org> Signed-off-by: Eric Anholt <eric@anholt.net> I double check my bisection, I can confirm you that 9d0498a2bf7455159b317f19531a3e5db2ecc9c4 is the bad commit. Thanks, Luca On Tue, Aug 24, 2010 at 2:43 PM, <bugzilla-daemon@bugzilla.kernel.org> wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=16871 > > > Chris Wilson <chris@chris-wilson.co.uk> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |chris@chris-wilson.co.uk > > > > > --- Comment #1 from Chris Wilson <chris@chris-wilson.co.uk> 2010-08-24 > 12:42:51 --- > You might want to double check your bisection. That code isn't even touched > for > your chipset. Sporadic TV misdetection has been around for a long time, and > other bisection results indicate that the problem has been exacerbated by: > > commit 9d0498a2bf7455159b317f19531a3e5db2ecc9c4 > Author: Jesse Barnes <jbarnes@virtuousgeek.org> > Date: Wed Aug 18 13:20:54 2010 -0700 > > drm/i915: wait for actual vblank, not just 20ms > > Waiting for a hard coded 20ms isn't always enough to make sure a vblank > period has actually occurred, so add code to make sure we really have > passed through a vblank period (or that the pipe is off when disabling). > > This prevents problems with mode setting and link training, and seems to > fix a bug like https://bugs.freedesktop.org/show_bug.cgi?id=29278, but > on an HP 8440p instead. Hopefully also fixes > https://bugs.freedesktop.org/show_bug.cgi?id=29141. > > Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org> > Signed-off-by: Eric Anholt <eric@anholt.net> > > -- > Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug. > fixed in .37-rc1: commit b7ac36dadafa69214faa75a34844d56bd0c14e89 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Tue Aug 24 16:07:16 2010 +0100 drm/i915/tv: After disabling the pipe, use wait_for_vblank_off() |