From: Michal Hocko <mhocko@suse.cz>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Ander Conselvan de Oliveira
<ander.conselvan.de.oliveira@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: WARNING: CPU: 0 PID: 3634 at drivers/gpu/drm/drm_irq.c:1141 drm_wait_one_vblank
Date: Wed, 8 Jul 2015 08:40:17 +0200 [thread overview]
Message-ID: <20150708064017.GA5335@dhcp22.suse.cz> (raw)
In-Reply-To: <20150707084358.GS7568@phenom.ffwll.local>
I have just tried to boot 4.2-rc1 and cannot seem to reproduce the issue
anymore.
On Tue 07-07-15 10:43:58, Daniel Vetter wrote:
[...]
> Can you please
> boot with drm.debug=0xf (lots more nois in dmesg with this) and reproduce?
> I only need the last few pages before the WARNING backtrace, just to
> understand a bit better what's going on there.
And 0xf debug level seem to paper over the problem because I do not see
the warning even with 4.1 where I am able to reproduce this reliably.
This suggests this is a timing sensitive issue.
--
Michal Hocko
SUSE Labs
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-07-08 6:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150630115707.GA4578@dhcp22.suse.cz>
[not found] ` <20150630143249.GA30960@phenom.ffwll.local>
[not found] ` <20150630160743.GA4590@dhcp22.suse.cz>
[not found] ` <20150630165929.GB30960@phenom.ffwll.local>
[not found] ` <20150630201335.GA4496@dhcp22.suse.cz>
[not found] ` <20150701082639.GE30960@phenom.ffwll.local>
[not found] ` <20150701121241.GB5010@dhcp22.suse.cz>
2015-07-01 12:23 ` WARNING: CPU: 0 PID: 3634 at drivers/gpu/drm/drm_irq.c:1141 drm_wait_one_vblank Jani Nikula
2015-07-07 8:43 ` Daniel Vetter
2015-07-08 6:40 ` Michal Hocko [this message]
2015-07-08 7:32 ` Daniel Vetter
2015-07-08 7:46 ` Michal Hocko
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=20150708064017.GA5335@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=ander.conselvan.de.oliveira@intel.com \
--cc=daniel@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