From: "Michel Dänzer" <michel@daenzer.net>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: GPU lockup CP stall for more than 10000msec on latest vanilla git
Date: Tue, 18 Dec 2012 12:20:32 +0100 [thread overview]
Message-ID: <1355829632.17142.59.camel@thor.local> (raw)
In-Reply-To: <20121217225534.GA219@x4>
On Mon, 2012-12-17 at 23:55 +0100, Markus Trippelsdorf wrote:
> On 2012.12.17 at 23:25 +0100, Markus Trippelsdorf wrote:
> > On 2012.12.17 at 17:00 -0500, Alex Deucher wrote:
> > > On Mon, Dec 17, 2012 at 4:48 PM, Markus Trippelsdorf
> > > <markus@trippelsdorf.de> wrote:
> > > > On 2012.12.17 at 16:32 -0500, Alex Deucher wrote:
> > > >> On Mon, Dec 17, 2012 at 1:27 PM, Markus Trippelsdorf
> > > >> <markus@trippelsdorf.de> wrote:
> > > >> > As soon as I open the following website:
> > > >> > http://www.boston.com/bigpicture/2012/12/2012_year_in_pictures_part_i.html
> > > >> >
> > > >> > my Radeon RS780 stalls (GPU lockup) leaving the machine unusable:
> > > >>
> > > >> Is this a regression? Most likely a 3D driver bug unless you are only
> > > >> seeing it with specific kernels. What browser are you using and do
> > > >> you have hw accelerated webgl, etc. enabled? If so, what version of
> > > >> mesa are you using?
> > > >
> > > > This is a regression, because it is caused by yesterdays merge of
> > > > drm-next by Linus. IOW I only see this bug when running a
> > > > v3.7-9432-g9360b53 kernel.
> > >
> > > Can you bisect? I'm guessing it may be related to the new DMA rings. Possibly:
> > > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=2d6cc7296d4ee128ab0fa3b715f0afde511f49c2
> >
> > Yes, the commit above causes the issue.
> >
> > 2d6cc72 GPU lockups
>
> With 2d6cc72 reverted I get:
>
> Dec 17 23:09:35 x4 kernel: ------------[ cut here ]------------
Probably a separate issue, can you bisect this one as well?
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Debian, X and DRI developer
next prev parent reply other threads:[~2012-12-18 11:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 18:27 GPU lockup CP stall for more than 10000msec on latest vanilla git Markus Trippelsdorf
2012-12-17 21:32 ` Alex Deucher
2012-12-17 21:48 ` Markus Trippelsdorf
2012-12-17 21:58 ` Markus Trippelsdorf
2012-12-17 22:00 ` Alex Deucher
2012-12-17 22:25 ` Markus Trippelsdorf
2012-12-17 22:55 ` Markus Trippelsdorf
2012-12-18 11:20 ` Michel Dänzer [this message]
2012-12-18 13:38 ` Markus Trippelsdorf
2012-12-18 13:51 ` Markus Trippelsdorf
2012-12-18 15:24 ` Maarten Lankhorst
2012-12-18 16:12 ` Markus Trippelsdorf
2012-12-18 18:10 ` Maarten Lankhorst
2012-12-19 13:57 ` Maarten Lankhorst
2012-12-19 14:20 ` Markus Trippelsdorf
2012-12-19 14:31 ` Maarten Lankhorst
2012-12-23 1:46 ` Alex Deucher
2012-12-23 8:43 ` Markus Trippelsdorf
2012-12-23 10:09 ` Andy Furniss
2012-12-23 10:21 ` Markus Trippelsdorf
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=1355829632.17142.59.camel@thor.local \
--to=michel@daenzer.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=markus@trippelsdorf.de \
/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.