From: Thomas Meyer <thomas@m3y3r.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: 3.13.1 - WARNING at drivers/gpu/drm/i915/i915_irq.c:1240
Date: Fri, 14 Feb 2014 07:16:39 +0100 [thread overview]
Message-ID: <1392358599.5349.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20140210085801.GJ17001@phenom.ffwll.local>
Am Montag, den 10.02.2014, 09:58 +0100 schrieb Daniel Vetter:
> On Sat, Feb 08, 2014 at 07:30:54PM +0100, Thomas Meyer wrote:
> > Am Samstag, den 08.02.2014, 17:38 +0100 schrieb Daniel Vetter:
> > > On Sat, Feb 8, 2014 at 12:51 PM, Thomas Meyer <thomas@m3y3r.de> wrote:
> > > > Am Freitag, den 07.02.2014, 09:46 +0100 schrieb Daniel Vetter:
> > > >> On Thu, Feb 06, 2014 at 11:29:34PM +0100, Thomas Meyer wrote:
> > > >> > Am Dienstag, den 04.02.2014, 21:17 +0100 schrieb Daniel Vetter:
> > > >> > > On Tue, Feb 04, 2014 at 08:37:02PM +0100, Thomas Meyer wrote:
> > > >> > > >
> > > >> > > > Hi,
> > > >> > > >
> > > >> > > > I see a *lot* of these warning in 3.13.1.
> > > >> > > > 3.12.x never showed this problem.
> > > >> > > > Any ideas?!
> > > >> > >
> > > >> > > Can you please try latest the drm-intel-nightly git branch from
> > > >> > > git://anongit.freedesktop.org/drm-intel ?
> > > >> > >
> > > >> > > If that one's still affected then please boot with drm.debug=0xe added to
> > > >> > > your kernel cmdline, reproduce the WARN and attach the complete dmesg.
> > > >> > >
> > > >> >
> > > >> > Hi,
> > > >> >
> > > >> > with 3.13.0-drm-00890-g4055ebc (drm-intel-nightly) I get these warnings:
> > > >>
> > > >> Can you please boot with drm.debug=0xe and attach the complete dmesg?
> > > >
> > > > here you go. dmesg in attachment.
> > >
> > > Hm, this one doesn't contain the WARN backtrace when the driver loads.
> > > Does it only happen occasionally? If so can you please try to grab a
> > > dmesg with drm debugging enabled and the backtrace in it?
> >
> > Hi,
> >
> > the WARNINGs did only show in 3.13.1 without the debug option. With the
> > debug option turned on the WARNINGs show up in neither drm-intel-nightly
> > nor 3.13.2.
> > So either the debug option somehow interfere with the WARNINGs or the
> > bug was fixed between 3.13.1 and drm-intel-nightly resp. 3.13.2.
>
> Can you please double-check that the bug is gone in 3.13.2, even without
> the debug output enabled? I've looked at the stable patches and there's
> nothing for i915 between .1 and .2.
Mhh. strange. I don't encounter these warning anymore with 3.13.2...
Maybe something else did trigger those?!
Anyway, I'll watch out for those warning in the future. And a big thanks
for your great support.
I'll update to 3.13.3 now.
> -Daniel
next prev parent reply other threads:[~2014-02-14 6:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 19:37 3.13.1 - WARNING at drivers/gpu/drm/i915/i915_irq.c:1240 Thomas Meyer
2014-02-04 20:17 ` Daniel Vetter
2014-02-06 22:29 ` Thomas Meyer
2014-02-07 8:46 ` Daniel Vetter
2014-02-08 11:51 ` Thomas Meyer
2014-02-08 16:38 ` Daniel Vetter
2014-02-08 18:30 ` Thomas Meyer
2014-02-10 8:58 ` Daniel Vetter
2014-02-14 6:16 ` Thomas Meyer [this message]
2014-02-20 20:17 ` Thomas Meyer
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=1392358599.5349.2.camel@localhost.localdomain \
--to=thomas@m3y3r.de \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@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