From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 44121] Reproducible GPU lockup CP stall on Radeon HD 6450
Date: Thu, 5 Jul 2012 07:30:03 +0000 (UTC) [thread overview]
Message-ID: <20120705073003.5AB3211FA5E@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-44121-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=44121
--- Comment #13 from Jean Delvare <khali@linux-fr.org> 2012-07-05 07:30:03 ---
Reproducibility information:
* I cannot reproduce the GPU lockup on a Radeon HD 4350 card.
* On the Radeon HD 6450, I can reproduce the GPU lockup with applications other
than Firefox. I was able to do so with Claws Mail for example. The parent
window has to be maximized for it to happen. Then, as soon as a title-less
dialog box is opened (for example by pressing Ctrl+S for "Save As..."), the GPU
lockup happens.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-07-05 7:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-01 19:54 [Bug 44121] New: Reproducible GPU lockup CP stall on Radeon HD 6450 bugzilla-daemon
2012-07-03 14:53 ` [Bug 44121] " bugzilla-daemon
2012-07-03 15:27 ` bugzilla-daemon
2012-07-03 15:42 ` bugzilla-daemon
2012-07-03 16:21 ` bugzilla-daemon
2012-07-03 16:39 ` bugzilla-daemon
2012-07-03 17:09 ` bugzilla-daemon
2012-07-03 17:31 ` bugzilla-daemon
2012-07-03 18:00 ` bugzilla-daemon
2012-07-03 18:08 ` bugzilla-daemon
2012-07-03 18:56 ` bugzilla-daemon
2012-07-03 19:03 ` bugzilla-daemon
2012-07-03 21:40 ` bugzilla-daemon
2012-07-05 7:30 ` bugzilla-daemon [this message]
2012-07-06 11:01 ` bugzilla-daemon
2012-07-06 12:09 ` bugzilla-daemon
2012-07-06 13:13 ` bugzilla-daemon
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=20120705073003.5AB3211FA5E@bugzilla.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@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