All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Sedat Dilek <sedat.dilek@gmail.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	linux-fbdev@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Johannes Berg <johannes.berg@intel.com>,
	Thorsten Leemhuis <thl@ct.de>
Subject: Re: [drm-intel-nightly] 2016y-07m-14d-21h-13m-02s UTC: locking dependency: drm_modeset_lock_all() ||
Date: Wed, 17 Aug 2016 19:27:00 +0000	[thread overview]
Message-ID: <CA+icZUWn+zFjCHT+O6ihb7+kQDmn9N3Y588F45_=U=KYHZsoAw@mail.gmail.com> (raw)
In-Reply-To: <20160715084045.GD1841@nuc-i3427.alporthouse.com>

On Fri, Jul 15, 2016 at 10:40 AM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Fri, Jul 15, 2016 at 08:00:25AM +0200, Sedat Dilek wrote:
>> Hi,
>>
>> I see the below call-trace with latest d-i-n, guess latest linux-next
>> will cause same issues.
>> ( Beyond this, there exist also a build failure which me and Stephen
>> have reported. )
>> The call-trace is reproducible with my setup and seen on every boot.
>>
>> Not sure if this is a problem in intel-gfx or fbdev.
>
> Personally, I blamed backlight,
> https://patchwork.freedesktop.org/patch/95769/

[ CC Peter, Johannes and Thorsten "The regression reporter" ]

Peter has 2 fixes from Johannes in peterz/queue.git#locking/urgent
which fix the issue for me.

[1/2] Revert "drm/fb-helper: Reduce READ_ONCE(master) to lockless_dereference"
[2/2] locking/barriers: suppress sparse warnings in lockless_dereference()

I tried today's Linus tree with those two fixes.

Chris backlight fix is no more needed here.

- Sedat -

[1] http://git.kernel.org/cgit/linux/kernel/git/peterz/queue.git/commit/?h=locking/urgent&idùd089b7830bbaa6ccaad29dff5fbb01d2a69945
[2] http://git.kernel.org/cgit/linux/kernel/git/peterz/queue.git/commit/?h=locking/urgent&id\x1804f7121995e8ca341427d848c0c8d267147720

WARNING: multiple messages have this Message-ID (diff)
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Sedat Dilek <sedat.dilek@gmail.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	linux-fbdev@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Johannes Berg <johannes.berg@intel.com>,
	Thorsten Leemhuis <thl@ct.de>
Subject: Re: [drm-intel-nightly] 2016y-07m-14d-21h-13m-02s UTC: locking dependency: drm_modeset_lock_all() || __blocking_notifier_call_chain
Date: Wed, 17 Aug 2016 21:27:00 +0200	[thread overview]
Message-ID: <CA+icZUWn+zFjCHT+O6ihb7+kQDmn9N3Y588F45_=U=KYHZsoAw@mail.gmail.com> (raw)
In-Reply-To: <20160715084045.GD1841@nuc-i3427.alporthouse.com>

On Fri, Jul 15, 2016 at 10:40 AM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Fri, Jul 15, 2016 at 08:00:25AM +0200, Sedat Dilek wrote:
>> Hi,
>>
>> I see the below call-trace with latest d-i-n, guess latest linux-next
>> will cause same issues.
>> ( Beyond this, there exist also a build failure which me and Stephen
>> have reported. )
>> The call-trace is reproducible with my setup and seen on every boot.
>>
>> Not sure if this is a problem in intel-gfx or fbdev.
>
> Personally, I blamed backlight,
> https://patchwork.freedesktop.org/patch/95769/

[ CC Peter, Johannes and Thorsten "The regression reporter" ]

Peter has 2 fixes from Johannes in peterz/queue.git#locking/urgent
which fix the issue for me.

[1/2] Revert "drm/fb-helper: Reduce READ_ONCE(master) to lockless_dereference"
[2/2] locking/barriers: suppress sparse warnings in lockless_dereference()

I tried today's Linus tree with those two fixes.

Chris backlight fix is no more needed here.

- Sedat -

[1] http://git.kernel.org/cgit/linux/kernel/git/peterz/queue.git/commit/?h=locking/urgent&id=f9d089b7830bbaa6ccaad29dff5fbb01d2a69945
[2] http://git.kernel.org/cgit/linux/kernel/git/peterz/queue.git/commit/?h=locking/urgent&id=1804f7121995e8ca341427d848c0c8d267147720
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2016-08-17 19:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15  6:00 [drm-intel-nightly] 2016y-07m-14d-21h-13m-02s UTC: locking dependency: drm_modeset_lock_all() || __blocking_notifier_call_chain Sedat Dilek
2016-07-15  8:40 ` [drm-intel-nightly] 2016y-07m-14d-21h-13m-02s UTC: locking dependency: drm_modeset_lock_all() || Chris Wilson
2016-07-15  8:40   ` [drm-intel-nightly] 2016y-07m-14d-21h-13m-02s UTC: locking dependency: drm_modeset_lock_all() || __blocking_notifier_call_chain Chris Wilson
2016-07-15 10:37   ` [drm-intel-nightly] 2016y-07m-14d-21h-13m-02s UTC: locking dependency: drm_modeset_lock_all() || Sedat Dilek
2016-07-15 10:37     ` [drm-intel-nightly] 2016y-07m-14d-21h-13m-02s UTC: locking dependency: drm_modeset_lock_all() || __blocking_notifier_call_chain Sedat Dilek
2016-07-15 21:10     ` Sedat Dilek
2016-08-17 19:27   ` Sedat Dilek [this message]
2016-08-17 19:27     ` Sedat Dilek
2016-08-17 19:36     ` [drm-intel-nightly] 2016y-07m-14d-21h-13m-02s UTC: locking dependency: drm_modeset_lock_all() || Johannes Berg
2016-08-17 19:36       ` [drm-intel-nightly] 2016y-07m-14d-21h-13m-02s UTC: locking dependency: drm_modeset_lock_all() || __blocking_notifier_call_chain Johannes Berg
2016-08-17 20:29       ` Sedat Dilek
2016-08-01 13:33 ` [Intel-gfx] [drm-intel-nightly] 2016y-07m-14d-21h-13m-02s UTC: locking dependency: drm_modeset_l Jani Nikula
2016-08-01 13:33   ` [drm-intel-nightly] 2016y-07m-14d-21h-13m-02s UTC: locking dependency: drm_modeset_lock_all() || __blocking_notifier_call_chain Jani Nikula
2016-08-02 17:47   ` [Intel-gfx] [drm-intel-nightly] 2016y-07m-14d-21h-13m-02s UTC: locking dependency: drm_modeset_l Sedat Dilek
2016-08-02 17:47     ` [drm-intel-nightly] 2016y-07m-14d-21h-13m-02s UTC: locking dependency: drm_modeset_lock_all() || __blocking_notifier_call_chain Sedat Dilek
2016-08-02 19:56     ` Sedat Dilek
2016-08-03  8:42     ` [Intel-gfx] [drm-intel-nightly] 2016y-07m-14d-21h-13m-02s UTC: locking dependency: drm_modeset_l Jani Nikula
2016-08-03  8:42       ` [drm-intel-nightly] 2016y-07m-14d-21h-13m-02s UTC: locking dependency: drm_modeset_lock_all() || __blocking_notifier_call_chain Jani Nikula
2016-08-03  5:16 ` ✗ Ro.CI.BAT: warning for " Patchwork

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='CA+icZUWn+zFjCHT+O6ihb7+kQDmn9N3Y588F45_=U=KYHZsoAw@mail.gmail.com' \
    --to=sedat.dilek@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=johannes.berg@intel.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=plagnioj@jcrosoft.com \
    --cc=thl@ct.de \
    --cc=tomi.valkeinen@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.