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 101746] radeonsi: Kernel syscall lockup caused probably by GPU crash
Date: Fri, 14 Jul 2017 00:47:03 +0000	[thread overview]
Message-ID: <bug-101746-502-TJKe9PSOCH@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101746-502@http.bugs.freedesktop.org/>


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

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

--- Comment #2 from Tobias Auerochs <tobi291019@gmail.com> ---
Sadly could not find any useful information out of various process logs, in
particular Xorg.0.log contains nothing error related. The only thing that is
somewhat interesting is that some processes that ought to use OpenGL do not end
up stuck in D state, whilst it appears only specifically plasmashell and Xorg
get stuck. (Obviously no graphical output works on any other processes either
anymore, nor can one switch virtual terminals anymore with Xorg being dead.)

If anyone knows any specific things that may be useful to debug, I can see if
anything helps.

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

[-- Attachment #1.2: Type: text/html, Size: 1576 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-07-14  0:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10 19:10 [Bug 101746] radeonsi: Kernel syscall lockup caused probably by GPU crash bugzilla-daemon
2017-07-10 19:20 ` bugzilla-daemon
2017-07-14  0:47 ` bugzilla-daemon [this message]
2017-09-22  1:24 ` bugzilla-daemon
2018-04-03  5:42 ` 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-101746-502-TJKe9PSOCH@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