From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Niel Lambrechts <niel.lambrechts@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Andrew Morton <akpm@linux-foundation.org>,
"linux.kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [BUG 13180]: Warning at i915_gem_idle
Date: Fri, 7 Aug 2009 10:20:05 -0700 [thread overview]
Message-ID: <20090807102005.67800b3b@jbarnes-g45> (raw)
In-Reply-To: <4A721077.9020607@gmail.com>
On Thu, 30 Jul 2009 23:28:23 +0200
Niel Lambrechts <niel.lambrechts@gmail.com> wrote:
> Hi Rafael,
>
> I just noticed you already opened a previous bugzilla entry for a
> problem I'm seeing again (below) at
> http://bugzilla.kernel.org/show_bug.cgi?id=13180. Is it perhaps
> possible that you can re-open it, it is recurring in 2.6.30.2 up to
> 2.6.31-rc4 again?
>
> X is intermittently soft-freezing and at other times I notice Xorg is
> 100% busy, it could be at the same time than this message I'm not
> absolutely certain. It seems to happen either during a screen-saver
> period or auto-suspend to RAM.
>
> Previously, Andrew had the following comment:
> > That is
> >
> > WARN_ON(!list_empty(&dev_priv->mm.flushing_list));
> >
> > Does the warning persist in 2.6.30-rc3 or later? If so, we should
> > add it to the post-2.6.29 regression list (if there's any room
> > left).
>
> So I'd like to request that it be added to the regression list for
> 2.6.30 and 2.6.31...
Niel, can you move or file a bug for this at bugs.freedesktop.org
against drm/intel? We try to track gfx bugs there... I assume you
still see this with -rc5?
--
Jesse Barnes, Intel Open Source Technology Center
next parent reply other threads:[~2009-08-07 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A721077.9020607@gmail.com>
2009-08-07 17:20 ` Jesse Barnes [this message]
2009-07-30 21:32 [Bug 13180]: Warning at i915_gem_idle Niel Lambrechts
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=20090807102005.67800b3b@jbarnes-g45 \
--to=jbarnes@virtuousgeek.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=niel.lambrechts@gmail.com \
--cc=rjw@sisk.pl \
/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