From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 195231] Continuous messages of "*ERROR* UVD not responding, trying to reset the VCPU!!!" and frozen screen
Date: Mon, 03 Apr 2017 18:16:59 +0000 [thread overview]
Message-ID: <bug-195231-2300-zrWz8P8kx6@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-195231-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=195231
--- Comment #3 from Rogério Brito (rbrito@ime.usp.br) ---
Dear Alex,
(In reply to Alex Deucher from comment #2)
> Please attach your xorg log and dmesg output. Does appending radeon.runpm=0
> on the kernel command line in grub help?
I'm attaching them.
The dmesg output shows an Ooops when I start X from a command line. I had to
arrange things via SSH, since the keyboard stops responding and, sometimes, the
kernel reboots the system.
Regarding your question, appending radeon.runpm=0 does help. The Oops is
absent, but "UVD not responding messages are still present". At least, the
system boots up to the desktop and it works, but I don't quite know how to
check which card is working at a given point in time (if the Intel one or the
if the radeon card).
Thanks,
Rogério.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-04-03 18:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 15:37 [Bug 195231] New: Continuous messages of "*ERROR* UVD not responding, trying to reset the VCPU!!!" and frozen screen bugzilla-daemon
2017-04-03 15:38 ` [Bug 195231] " bugzilla-daemon
2017-04-03 16:02 ` bugzilla-daemon
2017-04-03 18:16 ` bugzilla-daemon [this message]
2017-04-03 18:20 ` bugzilla-daemon
2017-04-03 18:21 ` bugzilla-daemon
2017-04-03 18:22 ` bugzilla-daemon
2017-04-03 18:23 ` bugzilla-daemon
2017-04-03 18:25 ` bugzilla-daemon
2017-04-06 4:03 ` bugzilla-daemon
2017-04-07 20:54 ` bugzilla-daemon
2017-04-10 6:50 ` bugzilla-daemon
2017-04-10 17:27 ` bugzilla-daemon
2018-07-20 22:16 ` bugzilla-daemon
[not found] <bug-195231-5003@https.bugzilla.kernel.org/>
[not found] ` <bug-195231-5003-cZEz4zVa8h@https.bugzilla.kernel.org/>
2017-04-07 20:54 ` Rogério Brito
[not found] ` <bug-195231-5003-Ydxnu5vlZN@https.bugzilla.kernel.org/>
2017-04-10 17:27 ` Rogério Brito
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-195231-2300-zrWz8P8kx6@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.