dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 80690] Suddenly X halts
Date: Thu, 31 Dec 2015 18:12:31 +0000	[thread overview]
Message-ID: <bug-80690-502-8QBJdZ2XbZ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-80690-502@http.bugs.freedesktop.org/>


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

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

Timofey <kuuffff@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kuuffff@gmail.com

--- Comment #4 from Timofey <kuuffff@gmail.com> ---
Created attachment 120749
  --> https://bugs.freedesktop.org/attachment.cgi?id=120749&action=edit
Xorg.log

Hello.

I upgraded my videocard to HD7770 recently, and found this annoying hangs. Just
like described: "after some time of work screen goes dark, than blinks and than
hangs (picture stands still with no changes and no reaction on keyboard or
mouse, numlock isn't working)." I can add that the monitor draws "no signal"
message, than finds that signal, makes autoconfig and nothing happens than.

The most of such a hangs happened when I played "Heroes of The Storm". The last
3-4 times I tried to enter game system freezed. But as it seems for me, the
training games are works fine. Maybe it not relevant information, but just for
case.
The system becomes unusable, acpid don't respond on power button, the only way
out of it is reset button.

And one time right now system *almost* died when I clicked at link in firefox.
Almost. All looks the same: screen goes dark, than lit again, but I
successfully switched to first virtual terminal with C-M-F1 and see there
something like "failed to allocate virtual address for buffer" and some more
lines. But I was stupid and the next thing I done was C-M-F7. System died.

uname -a:
Linux rgo 4.1.12-gentoo-rgo #1 SMP Sun Dec 6 12:44:19 2015 x86_64 Intel(R)
Core(TM)2 Duo CPU E8400 @ 3.00GHz GenuineIntel GNU/Linux

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

[-- Attachment #1.2: Type: text/html, Size: 3125 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:[~2015-12-31 18:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29 20:09 [Bug 80690] New: Suddenly X halts bugzilla-daemon
2014-06-30  1:43 ` [Bug 80690] " bugzilla-daemon
2014-07-14 19:43 ` bugzilla-daemon
2014-07-14 19:49 ` bugzilla-daemon
2015-12-31 18:12 ` bugzilla-daemon [this message]
2018-08-31  6:16 ` 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-80690-502-8QBJdZ2XbZ@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