From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 61941] New: Random GPU lockups/resets on Mobility Radeon HD 3650 with radeon.dpm=1
Date: Mon, 23 Sep 2013 21:40:21 +0000 [thread overview]
Message-ID: <bug-61941-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=61941
Bug ID: 61941
Summary: Random GPU lockups/resets on Mobility Radeon HD 3650
with radeon.dpm=1
Product: Drivers
Version: 2.5
Kernel Version: >=3.11.0
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: itumaykin@gmail.com
Regression: No
Created attachment 109311
--> https://bugzilla.kernel.org/attachment.cgi?id=109311&action=edit
lspci -vvv
Hello.
I have 3.11 kernel with radeon.dpm enabled via kernel boot option. Sometimes
under unknown circumstances my GPU resets. It happens seldom and randomly
during a common desktop workflow: web browsing, document typing, video
playback. No games or video benchmarks or any other GPU-eating stuff.
During such lockup my screen turns black, but backlight is still on. After a
while image reappears, though it is blurry and after 10-15 seconds my screen is
back to normal state completely. Also sometimes after such reset I am able to
continue working, but sometimes screen is stuck with one image that appeared
after screen restoration and I have to reboot machine to fix this.
Everything else seems to work fine during lockups, for example music is playing
without any problems. I can't say for sure, but it looks like this bug happens
more often when some video is played in Firefox. (JIC: I don't have Adobe Flash
installed.)
My OS is Gentoo amd64 with vanilla kernel 3.11.{0,1}. And this happens with
power_dpm_state set to "balanced". I've attached two dmesg outputs after such
lockups.
I do understand that it is probably too vague description to fix this and I am
ready to provide any other additional info.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2013-09-23 21:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 21:40 bugzilla-daemon [this message]
2013-09-23 21:40 ` [Bug 61941] Random GPU lockups/resets on Mobility Radeon HD 3650 with radeon.dpm=1 bugzilla-daemon
2013-09-23 21:41 ` bugzilla-daemon
2013-09-23 22:15 ` bugzilla-daemon
2013-09-25 15:44 ` bugzilla-daemon
2013-10-19 18:17 ` bugzilla-daemon
2013-10-19 18:48 ` bugzilla-daemon
2013-10-22 16:39 ` bugzilla-daemon
2013-10-22 16:47 ` bugzilla-daemon
2013-10-25 18:55 ` bugzilla-daemon
2013-11-10 18:22 ` bugzilla-daemon
2013-11-21 8:54 ` bugzilla-daemon
2013-11-21 13:14 ` bugzilla-daemon
2013-11-21 16:14 ` bugzilla-daemon
2013-11-21 17:55 ` bugzilla-daemon
2013-11-22 15:10 ` bugzilla-daemon
2013-12-20 6:21 ` bugzilla-daemon
2014-01-10 7:14 ` bugzilla-daemon
2014-01-18 19:01 ` bugzilla-daemon
2014-02-15 18:25 ` bugzilla-daemon
2014-02-15 19:19 ` bugzilla-daemon
2014-02-16 2:48 ` bugzilla-daemon
2014-04-15 12:24 ` bugzilla-daemon
2014-11-19 19:37 ` bugzilla-daemon
2015-03-23 18:22 ` bugzilla-daemon
2016-08-19 22:24 ` 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=bug-61941-2300@https.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 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.