From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 78238] New: GPU lockup on opening new tab in Chromium
Date: Sun, 04 May 2014 03:43:44 +0000 [thread overview]
Message-ID: <bug-78238-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1276 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=78238
Priority: medium
Bug ID: 78238
Assignee: dri-devel@lists.freedesktop.org
Summary: GPU lockup on opening new tab in Chromium
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: russianneuromancer@ya.ru
Hardware: x86-64 (AMD64)
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Created attachment 98395
--> https://bugs.freedesktop.org/attachment.cgi?id=98395&action=edit
dmesg
If GPU blacklist is disabled in Chromium (on chrome://flags; so hardware
accelerated rendering become enabled, judging from chrome://gpu) GPU sometimes
lockup on just opening new tab (at least one time per day). After lockup I
observe same behaviour like in Bug 77892 - reset happens but X is unresponsive
except mouse.
Radeon HD 6620G, Kubuntu 14.04 x86_64, Linux 3.15rc3, X.Org Server 1.15.1,
libdrm 2.4.54+git1405030630.5126fc, Mesa 10.3~git1405030730.64c467, radeon
driver 7.3.99+git1405030730.be1469.
As I remember, this behaviour (GPU hang on opening new tab) introduced since
Linux 3.15.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2856 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2014-05-04 3:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 3:43 bugzilla-daemon [this message]
2014-05-04 3:45 ` [Bug 78238] GPU lockup on opening new tab in Chromium bugzilla-daemon
2014-05-08 2:55 ` bugzilla-daemon
2014-05-11 8:51 ` bugzilla-daemon
2014-06-08 9:04 ` bugzilla-daemon
2015-03-06 8:04 ` 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-78238-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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