From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] amdgpu randomly crashing with linux5.1.16
Date: Mon, 22 Jul 2019 17:42:28 +0200 [thread overview]
Message-ID: <20190722154228.d5lEc-5aOuphUWEvhN2U36gYIMHOX0sKiHU_SXZLTJE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12853@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 906 bytes --]
Closed issue by HadetTheUndying on void-packages repository
https://github.com/void-linux/void-packages/issues/12853
Description: ### System
* xuname:
Void 5.1.16_1 x86_64 AuthenticAMD notuptodate hold rrrmFFFFFFFFF
* package: linux5.1.16
### Expected behavior
No Random Crashing.
### Actual behavior
Occassionally the screen will go corrupted and just lock up it then spams tty with these errors
[54948.226250] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
### Steps to reproduce the behavior
Running a game it just happens randomlly I forgot to take a picture of the screen corruption but it's the standard pixelated rainbow stuff. Restarting the Display Manager got me back into the display manager but it's still spamming tty.
I'll attach the full output of dmesg
[dmesg.log](https://github.com/void-linux/void-packages/files/3365018/dmesg.log)
prev parent reply other threads:[~2019-07-22 15:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-06 20:55 [ISSUE] " voidlinux-github
2019-07-06 21:00 ` voidlinux-github
2019-07-07 10:17 ` voidlinux-github
2019-07-07 20:19 ` voidlinux-github
2019-07-10 6:58 ` voidlinux-github
2019-07-10 7:26 ` voidlinux-github
2019-07-16 10:27 ` voidlinux-github
2019-07-17 0:08 ` voidlinux-github
2019-07-17 0:09 ` [ISSUE] [CLOSED] " voidlinux-github
2019-07-17 0:20 ` voidlinux-github
2019-07-17 9:34 ` voidlinux-github
2019-07-22 15:42 ` voidlinux-github
2019-07-22 15:42 ` voidlinux-github [this message]
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=20190722154228.d5lEc-5aOuphUWEvhN2U36gYIMHOX0sKiHU_SXZLTJE@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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).