From: Ben Skeggs <skeggsb@gmail.com>
To: "Berck E. Nash" <flyboy@gmail.com>
Cc: Dave Airlie <airlied@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: DRM nouveau crash with 3.2.0-rc5
Date: Tue, 13 Dec 2011 15:18:57 +1000 [thread overview]
Message-ID: <1323753537.10514.0.camel@nisroch> (raw)
In-Reply-To: <4EE564CF.8090203@gmail.com>
On Sun, 2011-12-11 at 19:19 -0700, Berck E. Nash wrote:
> On 12/11/2011 12:56 AM, Ben Skeggs wrote:
> > If you can manage to reproduce it, hopefully in some reliable way, it'll
> > be a huge help.
>
> Well, I can confirm it's a real regression. It's happened again, and
> I've never seen anything like it before. Unfortunately, I can't offer
> any reasonable steps to reproduce it for testing. It's only happened
> when watching video with mplayer, but it seems to happen at a rate of
> about once per hour while watching video. Enough to be seriously
> annoying, but not enough to be seriously useful when testing.
> Definitely enough to keep me from upgrading.
>
> I'm open to whatever else might be helpful if you have any ideas. Log
> of the last occurrence attached.
Are you able to bisect this back to a commit? I've attempted on a few
different cards to cause this and I'm not seeing it.
It might take a while to bisect given that it's hard for you to
reproduce, but, it'd be *very* helpful.
Ben.
>
> Berck Nash
next prev parent reply other threads:[~2011-12-13 5:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-10 5:10 DRM nouveau crash with 3.2.0-rc5 Berck E. Nash
2011-12-10 7:06 ` Dave Airlie
[not found] ` <CACAvsv6g+qz+-ja+4Qfinz04rr0EAyxwxQpFyfcE1fAtqQyuEA@mail.gmail.com>
2011-12-11 4:00 ` Berck E. Nash
2011-12-11 7:56 ` Ben Skeggs
2011-12-12 2:19 ` Berck E. Nash
2011-12-13 5:18 ` Ben Skeggs [this message]
2011-12-13 5:23 ` Berck E. Nash
2012-02-05 17:02 ` Berck E. Nash
2011-12-12 5:19 ` Berck E. Nash
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=1323753537.10514.0.camel@nisroch \
--to=skeggsb@gmail.com \
--cc=airlied@gmail.com \
--cc=flyboy@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).