[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1499858703.23742.25.camel@gmx.de>
Date: Wed, 12 Jul 2017 13:25:03 +0200
From: Mike Galbraith <efault@....de>
To: Ilia Mirkin <imirkin@...m.mit.edu>
Cc: LKML <linux-kernel@...r.kernel.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"nouveau@...ts.freedesktop.org" <nouveau@...ts.freedesktop.org>,
David Airlie <airlied@...ux.ie>,
Ben Skeggs <bskeggs@...hat.com>
Subject: Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP:
drm_calc_vbltimestamp_from_scanoutpos+335
On Wed, 2017-07-12 at 11:55 +0200, Mike Galbraith wrote:
> On Tue, 2017-07-11 at 14:22 -0400, Ilia Mirkin wrote:
> >
> > Some display stuff did change for 4.13 for GM20x+ boards. If it's not
> > too much trouble, a bisect would be pretty useful.
>
> Bisection seemingly went fine, but the result is odd.
>
> e98c58e55f68f8785aebfab1f8c9a03d8de0afe1 is the first bad commit
But it really really is bad. Looking at gitk fork in the road leading
to it...
52d9d38c183b drm/sti:fix spelling mistake: "compoment" -> "component" - good
e4e818cc2d7c drm: make drm_panel.h self-contained - good
9cf8f5802f39 drm: add missing declaration to drm_blend.h - good
Before the git highway splits, all is well. The lane with commits
works fine at both ends, but e98c58e55f68 is busted. Merge arfifact?
-Mike
Powered by blists - more mailing lists