linux-kernel - Re: radeon 0000:1d:00.0: GPU lockup (current fence id 0x00000000010da43f last fence id 0x00000000010da52d on ring 0)

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 6 Jun 2018 10:26:15 +0200
From:   Christian König <christian.koenig@....com>
To:     Borislav Petkov <bp@...en8.de>, amd-gfx@...ts.freedesktop.org
Cc:     Alex Deucher <alexander.deucher@....com>,
        Christian König <christian.koenig@....com>,
        lkml <linux-kernel@...r.kernel.org>
Subject: Re: radeon 0000:1d:00.0: GPU lockup (current fence id
 0x00000000010da43f last fence id 0x00000000010da52d on ring 0)

Am 05.06.2018 um 16:44 schrieb Borislav Petkov:
> Hi guys,
>
> X just froze here ontop of 4.17-rc7+ tip/master (kernel is from last
> week) with the splat at the end.
>
> Box is a x470 chipset with Ryzen 2700X.
>
> GPU gets detected as
>
> [    7.440971] [drm] radeon kernel modesetting enabled.
> [    7.441220] [drm] initializing kernel modesetting (RV635 0x1002:0x9598 0x1043:0x01DA 0x00).
...
>
> in the PCIe slot with two monitors connected to it. radeon firmware is
>
> Version: 20170823-1
>
> What practically happened is X froze and got restarted after the GPU
> reset. It seems to be ok now, as I'm typing in it.
>
> Thoughts?

Well what did you do to trigger the lockup? Looks like an application 
send something to the hardware to crash the GFX block.

Christian.