From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 78238] GPU lockup on opening new tab in Chromium
Date: Sun, 08 Jun 2014 09:04:44 +0000 [thread overview]
Message-ID: <bug-78238-502-J66WIpMr0N@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-78238-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 885 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=78238
--- Comment #4 from russianneuromancer@ya.ru ---
Created attachment 100644
--> https://bugs.freedesktop.org/attachment.cgi?id=100644&action=edit
lockup
While GPU lockup doesn't happen anymore on opening new tab in Chromium, two
other lockups happened for me with 3.15rc7 (system idle, Firefox with simple
page without any video or HTML5 animation was opened; after three days of
uptime) and 3.15rc8 (while fullscreen video playback in VLC, OpenGL GLX output;
after five days of uptime). On latest lockup system become inaccessible via ssh
(however cursor is still moving). Please look into attached log.
Do I need to open another bugreport, to report this SUMO lockups with 3.15 that
wasn't reproducible with 3.14, or add more information here is fine?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1737 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 prev parent reply other threads:[~2014-06-08 9:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 3:43 [Bug 78238] New: GPU lockup on opening new tab in Chromium bugzilla-daemon
2014-05-04 3:45 ` [Bug 78238] " bugzilla-daemon
2014-05-08 2:55 ` bugzilla-daemon
2014-05-11 8:51 ` bugzilla-daemon
2014-06-08 9:04 ` bugzilla-daemon [this message]
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-J66WIpMr0N@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