public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: David Airlie <airlied@linux.ie>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [v3.8 Regression] Merge tag 'v3.7-rc2' into drm-intel-next-queued
Date: Wed, 03 Apr 2013 15:18:05 -0400	[thread overview]
Message-ID: <515C806D.7040100@canonical.com> (raw)
In-Reply-To: <CAKMK7uFRBXJZQo8k5AgiT-xAtk_g_P1zhuWSic35gdWmrcVQ=A@mail.gmail.com>

On 04/03/2013 03:16 PM, Daniel Vetter wrote:
> On Wed, Apr 3, 2013 at 9:08 PM, Joseph Salisbury 
> <joseph.salisbury@canonical.com 
> <mailto:joseph.salisbury@canonical.com>> wrote:
>
>     Hi Daniel,
>
>     A bug was opened against the Ubuntu kernel[0].  After a kernel
>     bisect, it was found the following was the first bad commit:
>
>
>     commit c2fb7916927e989ea424e61ce5fe617e54878827
>     Merge: 29de6ce 6f0c058
>     Author: Daniel Vetter <daniel.vetter@ffwll.ch
>     <mailto:daniel.vetter@ffwll.ch>>
>     Date:   Mon Oct 22 14:34:51 2012 +0200
>
>         Merge tag 'v3.7-rc2' into drm-intel-next-queued
>
>
>
>     The regression was introduced as of v3.8-rc1.  However, further
>     testing also shows this bug is now fixed in v3.9-rc4.
>
>     I see that you are the author of this patch, so I wanted see if I
>     can get your feedback.  Do you happen to have an idea what may
>     have fixed this in v3.9-rc4, so we can send a request to stable,
>     if not already done?  Otherwise, I can perform a reverse bisect to
>     see which commit fixed this.
>
>
> So apparently it's an oops somewhere in the nouveau setup code, which 
> bisected to a backmerge which has _only_ conflicts in drm/i915 driver 
> code.
>
> I have no idea what blew up here, sorry.
> -Daniel

Thanks for the info, Daniel.  I'll go the reverse bisect route.

>
>
>
>
>     Thanks,
>
>     Joe
>
>     [0] http://pad.lv/1109309
>
>
>
>
> -- 
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch


      parent reply	other threads:[~2013-04-03 19:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03 19:08 [v3.8 Regression] Merge tag 'v3.7-rc2' into drm-intel-next-queued Joseph Salisbury
     [not found] ` <CAKMK7uFRBXJZQo8k5AgiT-xAtk_g_P1zhuWSic35gdWmrcVQ=A@mail.gmail.com>
2013-04-03 19:18   ` Joseph Salisbury [this message]

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=515C806D.7040100@canonical.com \
    --to=joseph.salisbury@canonical.com \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.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