dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
	David Airlie <airlied@linux.ie>, Ben Skeggs <bskeggs@redhat.com>
Subject: Re: [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335
Date: Wed, 12 Jul 2017 13:25:03 +0200	[thread overview]
Message-ID: <1499858703.23742.25.camel@gmx.de> (raw)
In-Reply-To: <1499853345.23742.8.camel@gmx.de>

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

  reply	other threads:[~2017-07-12 11:25 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-11 17:32 [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 Mike Galbraith
     [not found] ` <1499794333.5315.8.camel-Mmb7MZpHnFY@public.gmane.org>
2017-07-11 17:51   ` Ilia Mirkin
2017-07-11 18:08     ` Mike Galbraith
     [not found]       ` <1499796510.5315.27.camel-Mmb7MZpHnFY@public.gmane.org>
2017-07-11 18:22         ` Ilia Mirkin
2017-07-11 18:53           ` Mike Galbraith
2017-07-12  7:45             ` Mike Galbraith
2017-07-12  9:55           ` Mike Galbraith
2017-07-12 11:25             ` Mike Galbraith [this message]
2017-07-12 11:37               ` Ilia Mirkin
2017-07-12 17:19                 ` Mike Galbraith
     [not found]                   ` <1499879972.23742.50.camel-Mmb7MZpHnFY@public.gmane.org>
2017-07-12 19:33                     ` Tobias Klausmann
2017-07-14 13:36                 ` Mike Galbraith
2017-07-14 13:41                   ` Mike Galbraith
     [not found]                     ` <1500039693.5763.15.camel-Mmb7MZpHnFY@public.gmane.org>
2017-07-14 15:05                       ` Tobias Klausmann
     [not found]                         ` <6341f91f-1c56-2188-f55b-2f47d23262fc-AqjdNwhu20eELgA04lAiVw@public.gmane.org>
2017-07-14 15:10                           ` Karol Herbst
2017-07-14 15:15                             ` [Nouveau] " Mike Galbraith
     [not found]                               ` <1500045346.5763.21.camel-Mmb7MZpHnFY@public.gmane.org>
2017-07-14 15:16                                 ` Ilia Mirkin
2017-07-14 15:19                             ` [Nouveau] " Tobias Klausmann
     [not found]                               ` <31d327dd-bc3d-cb80-45a9-6a8eb9eb2a9d-AqjdNwhu20eELgA04lAiVw@public.gmane.org>
2017-07-14 15:20                                 ` Ilia Mirkin
2017-07-14 15:55                                   ` [Nouveau] " Peter Zijlstra
2017-07-14 15:11                         ` Mike Galbraith
2017-07-14 15:50                   ` Peter Zijlstra
2017-07-14 15:58                     ` Mike Galbraith
2017-07-14 16:10                       ` Peter Zijlstra
2017-07-14 16:33                         ` Mike Galbraith
2017-07-14 19:42                           ` Josh Poimboeuf
2017-07-15  2:45                             ` Mike Galbraith
2017-07-17 17:20                         ` Jessica Yu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1499858703.23742.25.camel@gmx.de \
    --to=efault@gmx.de \
    --cc=airlied@linux.ie \
    --cc=bskeggs@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=imirkin@alum.mit.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).