dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 65963] screen goes blank, Linux hangs - Radeon 7870, Gallium, Glamor
Date: Sun, 31 Aug 2014 13:45:05 +0000	[thread overview]
Message-ID: <bug-65963-502-FsGDlfoNWs@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-65963-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1044 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=65963

--- Comment #24 from Maximilian Böhm <winlux@gmail.com> ---
@Damian Nowak: I would gladly use Mesa 10.1.4 but with this version I don't get
any OpenGL.

Installed:
ati-dri-10.1.4-1
lib32-mesa-10.1.4-1
lib32-mesa-libgl-10.1.4-1
mesa-10.1.4-1
mesa-demos-8.1.0-2
mesa-libgl-10.1.4-1
(all from 06-08 via Arch Rollback Machine, the last day with 10.1.4*.)
+ recent X-Server 1.16 etc.

I see this bug report as the same as the linked above "Random radeonsi
crashes". The crashes are in many shapes, in the last time my screen just
freezes but the mouse pointer still moves... Can't jump into a virtual console
nor kill X. I think I will install Catalyst again, it's really sad. Catalyst
doesn't even support Firefox' OMTC GPU accelerated scrolling so all scrolling
is stuttering on my 2560x1440 monitor (if I set it to FHD the stuttering is
acceptable but of course I want full resolution...).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1897 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

  parent reply	other threads:[~2014-08-31 13:45 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-65963-502@http.bugs.freedesktop.org/>
2013-06-20 13:40 ` [Bug 65963] screen goes blank, Linux hangs - Radeon 7870, Gallium, Glamor bugzilla-daemon
2013-06-20 14:05 ` bugzilla-daemon
2013-08-09 12:50 ` bugzilla-daemon
2014-07-05 12:50 ` bugzilla-daemon
2014-07-05 12:50 ` bugzilla-daemon
2014-07-06  1:15 ` bugzilla-daemon
2014-07-06  1:15 ` bugzilla-daemon
2014-07-06  1:16 ` bugzilla-daemon
2014-07-06  1:17 ` bugzilla-daemon
2014-07-09  2:57 ` bugzilla-daemon
2014-07-09  2:59 ` bugzilla-daemon
2014-07-09  3:00 ` bugzilla-daemon
2014-07-29  9:25 ` bugzilla-daemon
2014-07-29 10:01 ` bugzilla-daemon
2014-07-29 14:40 ` bugzilla-daemon
2014-07-30  9:08 ` bugzilla-daemon
2014-07-30 11:10 ` bugzilla-daemon
2014-07-30 11:21 ` bugzilla-daemon
2014-07-31 18:59 ` bugzilla-daemon
2014-08-27 13:00 ` bugzilla-daemon
2014-08-27 13:33 ` bugzilla-daemon
2014-08-30 18:45 ` bugzilla-daemon
2014-08-30 22:25 ` bugzilla-daemon
2014-08-30 22:27 ` bugzilla-daemon
2014-08-31 13:45 ` bugzilla-daemon [this message]
2014-08-31 14:24 ` bugzilla-daemon
2014-09-01  1:43 ` bugzilla-daemon
2014-09-01  1:56 ` bugzilla-daemon
2014-10-03 23:33 ` bugzilla-daemon
2015-08-02 10:58 ` bugzilla-daemon
2015-08-03  4:06 ` bugzilla-daemon
2015-08-05  4:50 ` bugzilla-daemon
2016-01-29  7:21 ` 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-65963-502-FsGDlfoNWs@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;
as well as URLs for NNTP newsgroup(s).