public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: sedat.dilek@gmail.com
Cc: Dave Airlie <airlied@redhat.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [Linux v4.0-rc5] Warnings in drm_framebuffer_reference() and drm_atomic_check_only()
Date: Fri, 27 Mar 2015 12:06:40 +0100	[thread overview]
Message-ID: <s5hegoabsxr.wl-tiwai@suse.de> (raw)
In-Reply-To: <CA+icZUUCOaXrusKxbBcYJGXx57Cc9+PT3mvLWA2TQYxqT0XZKA@mail.gmail.com>

At Fri, 27 Mar 2015 12:01:33 +0100,
Sedat Dilek wrote:
> 
> On Wed, Mar 25, 2015 at 3:34 PM, Takashi Iwai <tiwai@suse.de> wrote:
> > At Wed, 25 Mar 2015 14:26:50 +0100,
> > Daniel Vetter wrote:
> >>
> >> On Tue, Mar 24, 2015 at 07:09:03PM +0100, Sedat Dilek wrote:
> >> > On Mon, Mar 23, 2015 at 9:25 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
> >> > > On Mon, Mar 23, 2015 at 07:25:27AM +0100, Sedat Dilek wrote:
> >> > >> Hi,
> >> > >>
> >> > >> I did my weekly update of the Linux RC (here: v4.0-rc5) and fell over
> >> > >> some warning in the drm area.
> >> > >>
> >> > >> Please have a look...
> >> > >
> >> >
> >> > Hi Daniel,
> >> >
> >> > > Just to confirm: Both are new in -rc5 and haven't been around in -rc4?
> >> > >
> >> >
> >> > Yeah, rc4 was OK but with rc5 I have seen these warnings.
> >> >
> >> > > Also can you pls give -nightly a spin and see what happens there?
> >> > >
> >> >
> >> > drm-intel-nightly (2015y-03m-24d-09h-19m-43s UTC) pulled on top of rc5
> >> > does not show any warnings in the drm | i915 area.
> >>
> >> drm-fixes has 2 cherry-picks from -next to address the worst offenders,
> >> there's one more which is waiting for confirmation:
> >>
> >> commit fb9981aa675eb7b398849915364916fd98833cfa
> >> Author: Damien Lespiau <damien.lespiau@intel.com>
> >> Date:   Thu Feb 5 19:24:25 2015 +0000
> >>
> >>     drm/i915: Fix atomic state when reusing the firmware fb
> >>
> >> Please apply that commit from -next on top of drm-fixes and retest.
> >
> > The problem is introduced by the commit
> > 319c1d420a0b62d9dbb88104afebaabc968cdbfa
> >     drm/i915: Ensure plane->state->fb stays in sync with plane->fb
> >
> > Obviously it accesses the uninitialized kref in
> > get_initial_plane_config().
> >
> > The commit in next
> > f55548b5af87ebfc586ca75748947f1c1b1a4a52
> >     drm/i915: Don't try to reference the fb in get_initial_plane_config()
> >
> > fixes the bug itself, but it leads to another similar warnings.  For
> > avoiding this, yet another cherry-picks (including the commit you
> > mentioned above):
> >
> > fb9981aa675eb7b398849915364916fd98833cfa
> >     drm/i915: Fix atomic state when reusing the firmware fb
> > 2d14030b1a9d0e89cfdca6f16851e2eac8cb4de0
> >     drm/i915: Store the initial framebuffer in initial_plane_config
> >
> > then warnings are finally gone.
> >
> > But, the second one can't be applied cleanly, so I had to adjust many
> > codes manually by replacing primary fb references.
> >
> >
> > Takashi
> 
> Hi Takashi, hi Daniel,
> 
> first of all thank you for your replies.
> The last days I did not use my notebook and will try
> "drm-intel-fixes-2015-03-26".
> Takashi, is that Git branch on top of rc5 OK for you?

The fixes have been already merged to Linus tree.


Takashi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-03-27 11:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23  6:25 [Linux v4.0-rc5] Warnings in drm_framebuffer_reference() and drm_atomic_check_only() Sedat Dilek
2015-03-23  8:25 ` Daniel Vetter
2015-03-24 18:09   ` Sedat Dilek
2015-03-25 13:26     ` Daniel Vetter
2015-03-25 14:34       ` Takashi Iwai
2015-03-27 11:01         ` [Intel-gfx] " Sedat Dilek
2015-03-27 11:06           ` Takashi Iwai [this message]
2015-03-27 11:09             ` Sedat Dilek
2015-03-25  8:04   ` Takashi Iwai

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=s5hegoabsxr.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=airlied@redhat.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    /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