linux-kernel - Re: [Bug 195231] Continuous messages of "*ERROR* UVD not responding, trying to reset the VCPU!!!" and frozen screen

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAOtrxKNecX3y7mVCdAFRxd-=yfv1yzDnRpvxZaRtuog7aqHXdg@mail.gmail.com>
Date:   Mon, 10 Apr 2017 14:27:13 -0300
From:   Rogério Brito <rbrito@...il.com>
To:     bugzilla-daemon@...zilla.kernel.org
Cc:     Alex Deucher <alexdeucher@...il.com>,
        dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
        deathsimple@...afone.de,
        Márcia Coutinho de Brito <mcbrito@...il.com>
Subject: Re: [Bug 195231] Continuous messages of "*ERROR* UVD not responding,
 trying to reset the VCPU!!!" and frozen screen

Dear Alex, Christian and others,

On Mon, Apr 10, 2017 at 3:50 AM,  <bugzilla-daemon@...zilla.kernel.org> wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=195231
> --- Comment #11 from Christian König (deathsimple@...afone.de) ---
> Well bisecting which patch caused the break would be a good idea.

First of all, I hope you don't mind that I'm including my mom here, so
that she can follow how her computer is doing, or, rather, what I am
doing with her computer.

> To start that I suggest you try to compile kernel 4.4 by yourself first.
>
> That should also yield a temporary solution until we can narrow down the root
> cause.

I tried using Ubuntu's unpatched/precompiled kernels 4.2, 4.4, 4.8,
4.10 and 4.11-rc5 and, apparently, they now always show this message
*and* it frequently freezes to the point that no magic Sysrq keys
work, sometimes the caps lock kernel blinks and so on.

Booting with radeon.modeset=0 allows the computer to boot to the
desktop environment, but makes the CPU so hot when she plays her
flashplayer-based games that the kernel shows many messages of thermal
limit being reached and CPU speed being throttled.

Booting with radeon.runpm=0 still gets me all the error messages
listed in the subject (and present in the logs that I sent to
bugzilla), but the temperature *seems* to be slightly lower (not
enough testing was done with this configuration).

I don't know how to see/check what GPU is being used at a given time:
if the Intel GPU or if the AMD GPU...

So, given that the problem now seems to be present with all those
kernel versions that I tested, is it worthwhile to compile my own
kernels?

As before, I will try to do whatever I'm directed to.

Thanks a lot,

Rogério.

-- 
Rogério Brito : rbrito@...e.usp.br,gmail.com} : GPG key 4096R/BCFCAAAA
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br