All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 195231] New: Continuous messages of "*ERROR* UVD not responding, trying to reset the VCPU!!!" and frozen screen
Date: Mon, 03 Apr 2017 15:37:22 +0000	[thread overview]
Message-ID: <bug-195231-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=195231

            Bug ID: 195231
           Summary: Continuous messages of "*ERROR* UVD not responding,
                    trying to reset the VCPU!!!" and frozen screen
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.10.3
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: rbrito@ime.usp.br
        Regression: No

Hi.

First of all, I'm not sure if I selected the correct category when filing this
bug. I don't mind being corrected here.

OK, now, to the actual bug report.

My mother has a Dell Inspiron 15R N5110, which has an intel Sandy Bridge
integrated card and an AMD Radeon card (if I'm not mistaken it is reported as
an HD6400 series card, not being more specific).

According to my mother, it was working correctly with an Ubuntu running their
kernel 4.4 until it started only showing a black screen about 15 days ago.

I took her notebook and saw that the problem is that the kernel is now showing
many times the message "*ERROR* UVD not responding, trying to reset the
VCPU!!!" and the graphical environment does not completes loading.

I tried using Ubuntu's precompiled and unpatched 4.10.3, but the problem
persists (in fact, I was ping-pong'ing with many kernel versions to see if
something worked).

Besides working around the issue with radeon.modeset=0, so that the computer
can successfully boot, I don't know what to do to fix this issue, but I can
provide as much information as needed about it.

The unfortunate thing with the radeon.modeset=0 (that wasn't necessary, say,
about one month ago) is that she can't play some games that she used to and
that's her only entertainment, after having been diagnosed with some serious
illness. :(

Again, I can provide as much information as needed.


Thanks,

Rogério Brito.

-- 
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

             reply	other threads:[~2017-04-03 15:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-03 15:37 bugzilla-daemon [this message]
2017-04-03 15:38 ` [Bug 195231] Continuous messages of "*ERROR* UVD not responding, trying to reset the VCPU!!!" and frozen screen bugzilla-daemon
2017-04-03 16:02 ` bugzilla-daemon
2017-04-03 18:16 ` bugzilla-daemon
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

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@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.