Which branch to test latest support for Raven Ridge?

Bráulio Bhavamitra brauliobo at gmail.com
Wed Apr 18 20:34:03 UTC 2018


FYI, getting a blank screen and system freeze when lightdm is loaded with
both drm-next-4.18-wip
<https://cgit.freedesktop.org/~agd5f/linux/log/?h=drm-next-4.18-wip> and
amd-staging-drm-next
<https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next>
 branches.

On Fri, Apr 13, 2018 at 10:05 PM Bráulio Bhavamitra <brauliobo at gmail.com>
wrote:

> Hi all,
>
> I've been testing and mitigating the Raven Ridge crashes. I've just
> compiled the kernel https://cgit.freedesktop.org/~agd5f/linux/ at branch
> drm-next-4.18-wip to see if it would have the necessary fix for video
> hangs/freezes. Unfortunetely, it still crashes in the same situations.
>
> Which branch should I compile for the latest Raven Ridge support?
>
> Cheers,
> Bráulio
>
> ---------- Forwarded message ---------
> From: Bráulio Bhavamitra <brauliobo at gmail.com>
> Date: Fri, Apr 13, 2018 at 7:24 PM
> Subject: Re: Raven Ridge Ryzen 2500U hang reproduced
> To: <amd-gfx at lists.freedesktop.org>
>
>
> It ALWAYS crashes on shader15 of
> http://www.graphicsfuzz.com/benchmark/android-v1.html.
>
> Also reported at https://bugzilla.redhat.com/show_bug.cgi?id=1562530
>
> Using kernel 4.16 with options rcu_nocb=0-15 and amdgpu.dpm=0
>
> Cheers,
> Bráulio
>
>
> On Mon, Mar 26, 2018 at 8:30 PM Bráulio Bhavamitra <brauliobo at gmail.com>
> wrote:
>
>> Hi all,
>>
>> Following the random crashes happenning with many users (e.g.
>> https://www.phoronix.com/scan.php?page=news_item&px=Raven-Ridge-March-Update),
>> not only on Linux but also Windows, I've been struggling to reproduce and
>> generate any error log.
>>
>> After discovering that the error only happenned with KDE and games (at
>> least for me, see https://bugs.kde.org/show_bug.cgi?id=392378), I could
>> reproduce after a failing suspend.
>>
>> The crash most of the times allows the mouse to keep moving, but anything
>> else works. Except for this time the keyboard worked so I could switch the
>> tty and save the dmesg messages. After this I had to force reboot as it got
>> stuck trying to kill the lightdm service (gpu hanged?).
>>
>> The errors are, see attached the full dmesg:
>> [ 2899.525650] amdgpu 0000:03:00.0: couldn't schedule ib on ring <sdma0>
>> [ 2899.525769] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs
>> (-22)
>> [ 2909.125047] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
>> timeout, last signaled seq=174624, last emitted seq=174627
>> [ 2909.125060] [drm] IP block:psp is hung!
>> [ 2909.125063] [drm] GPU recovery disabled.
>> [ 2914.756931] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR*
>> amdgpu_cs_list_validate(validated) failed.
>> [ 2914.756997] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to process
>> the buffer list -16!
>> [ 2914.997372] amdgpu 0000:03:00.0: couldn't schedule ib on ring <sdma0>
>> [ 2914.997498] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs
>> (-22)
>> [ 2930.117275] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR*
>> amdgpu_cs_list_validate(validated) failed.
>> [ 2930.117405] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to process
>> the buffer list -16!
>> [ 2930.152015] [drm:amdgpu_fill_buffer [amdgpu]] *ERROR* Trying to clear
>> memory with ring turned off.
>> [ 2930.157940] [drm:amdgpu_fill_buffer [amdgpu]] *ERROR* Trying to clear
>> memory with ring turned off.
>> [ 2930.180535] [drm:amdgpu_fill_buffer [amdgpu]] *ERROR* Trying to clear
>> memory with ring turned off.
>> [ 2933.781692] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
>> [ 2945.477205] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR*
>> amdgpu_cs_list_validate(validated) failed.
>> [ 2945.477348] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to process
>> the buffer list -16!
>>
>> System details:
>> HP Envy x360 Ryzen 2500U
>> ArchLinux, kernel 4.16rc6 and 4.15.12
>>
>> Cheers,
>> bráulio
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/amd-gfx/attachments/20180418/af6931eb/attachment.html>


More information about the amd-gfx mailing list