Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1500485
| From | Paul Bolle <pebolle@tiscali.nl> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [Intel-gfx] drm/i915: WARN_ON_ONCE(!crtc_clock || cdclk < crtc_clock) |
| Date | 2016-10-13 20:10 +0200 |
| Message-ID | <srSC6-71Q-33@gated-at.bofh.it> (permalink) |
| References | <sroum-2vS-13@gated-at.bofh.it> <srpA6-3Ax-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Adding Matt]
On Wed, 2016-10-12 at 14:08 +0300, Joonas Lahtinen wrote:
> Bisecting the offending commit between v4.8 and v4.8.1 would be a good
> start.
0) Why use a personal notebook when one can just post any half baked
idea to lkml?
1) I stumbled on https://bugzilla.redhat.com/show_bug.cgi?id=1361357 (s
ame hardware, rather similar trace).
2) That report was about the first Fedora (rawhide) kernel release
after this commit http://pkgs.fedoraproject.org/cgit/rpms/kernel.git/co
mmit/?h=f25&id=7d2c2f2d91793b5da452bee9bea4fa32051c8608 ("Bring in
patch-series from drm-next to fix skl_update_other_pipe_wm issues").
3) That seventeen part series ended up in v4.8. The last commit of that
series is commit 5b483747a925 ("drm/i915: Remove wm_config from
dev_priv/intel_atomic_state").
4) So, with a little bit of luck, my bisect might only need to look at
those seventeen commits. Still, it will probably be next week before I
have a day or two to actually perform that bisect.
To be continued,
Paul Bolle
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
drm/i915: WARN_ON_ONCE(!crtc_clock || cdclk < crtc_clock) Paul Bolle <pebolle@tiscali.nl> - 2016-10-12 12:00 +0200
Re: [Intel-gfx] drm/i915: WARN_ON_ONCE(!crtc_clock || cdclk < crtc_clock) Joonas Lahtinen <joonas.lahtinen@linux.intel.com> - 2016-10-12 13:10 +0200
Re: [Intel-gfx] drm/i915: WARN_ON_ONCE(!crtc_clock || cdclk < crtc_clock) Paul Bolle <pebolle@tiscali.nl> - 2016-10-12 14:10 +0200
Re: [Intel-gfx] drm/i915: WARN_ON_ONCE(!crtc_clock || cdclk < crtc_clock) Jani Nikula <jani.nikula@linux.intel.com> - 2016-10-12 16:40 +0200
Re: [Intel-gfx] drm/i915: WARN_ON_ONCE(!crtc_clock || cdclk < crtc_clock) Paul Bolle <pebolle@tiscali.nl> - 2016-10-12 16:50 +0200
Re: [Intel-gfx] drm/i915: WARN_ON_ONCE(!crtc_clock || cdclk < crtc_clock) Paul Bolle <pebolle@tiscali.nl> - 2016-10-12 20:50 +0200
Re: [Intel-gfx] drm/i915: WARN_ON_ONCE(!crtc_clock || cdclk < crtc_clock) Paul Bolle <pebolle@tiscali.nl> - 2016-10-24 22:50 +0200
Re: [Intel-gfx] drm/i915: WARN_ON_ONCE(!crtc_clock || cdclk < crtc_clock) Jani Nikula <jani.nikula@linux.intel.com> - 2016-10-25 10:40 +0200
Re: [Intel-gfx] drm/i915: WARN_ON_ONCE(!crtc_clock || cdclk < crtc_clock) Paul Bolle <pebolle@tiscali.nl> - 2016-10-13 20:10 +0200
csiph-web