Re: [PATCH] drm/radeon: ratelimit bo warnings

[Nick Alcock <nick.alcock-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>]

On 5 Oct 2018, Michel Dänzer told this:

> On 2018-10-04 9:58 p.m., Nick Alcock wrote:
>> So a few days ago I started getting sprays of these warnings --
>> sorry, but because it was a few days ago I'm not sure what I was
>> running at the time (but it was probably either Stellaris or Chromium).
>> 
>> Sep 25 22:06:34 mutilate err: : [  544.718905] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0xc
>> Sep 25 22:06:34 mutilate err: : [  544.718909] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
>> Sep 25 22:06:34 mutilate err: : [  544.719710] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0xc
>> Sep 25 22:06:34 mutilate err: : [  544.719714] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
>> Sep 25 22:06:34 mutilate err: : [  544.719862] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0xc
>> Sep 25 22:06:34 mutilate err: : [  544.719865] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
>> Sep 25 22:06:34 mutilate err: : [  544.720772] [drm:radeon_cs_parser_relocs] *ERROR* gem object lookup failed 0xc
>> Sep 25 22:06:34 mutilate err: : [  544.720778] [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -2!
>
> These are likely due to https://bugs.freedesktop.org/105381 , fixed in
> xf86-video-ati 18.1.0.

This is with X server 1.20.0 and xf86-video-ati 18.0.1, so I concur.

I'll upgrade once I'm back near the machine in question (I mean, I could
upgrade now but I'm 200 miles away so running an X server on it at
present is a bit pointless).

>> Sep 25 22:06:34 mutilate warning: : [  544.721415] radeon 0000:01:00.0: vbo resource seems too big for the bo
>
> Not sure this can also be caused by the above, but I guess it's possible.

It can clearly be caused by *something*, and without anything obvious
going wrong in the user interface you can clearly get crazy log flooding
without the user being any the wiser. It doesn't really matter what
causes it, just that it is causable. :)

>> This patch is against 4.18.11: I saw the warnings on 4.17.6 with Mesa
>> 18.1.2, but nothing much seems to have changed in this area so I bet
>> this could recur.
>
> Not sure it makes sense to have the last paragraph in the Git commit
> log, but either way:

Yeah, I stuck it in the wrong place in the mail. (I meant to move it and
then completely forgot. Mea culpa.)

> Reviewed-by: Michel Dänzer <michel.daenzer@amd.com>

Thanks!

-- 
NULL && (void)
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx