From: Nick Alcock <nick.alcock-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: "Michel Dänzer" <michel-otUistvHUpPR7s880joybQ@public.gmane.org>
Cc: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [PATCH] drm/radeon: ratelimit bo warnings
Date: Mon, 05 Nov 2018 19:01:41 +0000 [thread overview]
Message-ID: <87tvkvic16.fsf@esperi.org.uk> (raw)
In-Reply-To: <8890a9ed-e469-b20b-f3bb-75bc18beb739-otUistvHUpPR7s880joybQ@public.gmane.org> ("Michel \=\?utf-8\?Q\?D\=C3\=A4nzer\=22's\?\= message of "Tue, 9 Oct 2018 16:32:38 +0200")
On 9 Oct 2018, Michel Dänzer stated:
> On 2018-10-05 7:14 p.m., Nick Alcock wrote:
>> 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).
I have upgraded and the warnings do appear to have gone away, so thank
you for the remote diagnosis :)
> Merged the patch for amd-staging-drm-next, will probably land for 4.20,
> thanks!
Great!
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2018-11-05 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 19:58 [PATCH] drm/radeon: ratelimit bo warnings Nick Alcock
[not found] ` <874le1h4by.fsf-dKoSMcxRz+Te9xe1eoZjHA@public.gmane.org>
2018-10-05 14:39 ` Michel Dänzer
[not found] ` <529ea1f2-d6dc-d127-35f6-6dba33af00cd-otUistvHUpPR7s880joybQ@public.gmane.org>
2018-10-05 17:14 ` Nick Alcock
[not found] ` <87a7nsfh9e.fsf-dKoSMcxRz+Te9xe1eoZjHA@public.gmane.org>
2018-10-09 14:32 ` Michel Dänzer
[not found] ` <8890a9ed-e469-b20b-f3bb-75bc18beb739-otUistvHUpPR7s880joybQ@public.gmane.org>
2018-11-05 19:01 ` Nick Alcock [this message]
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=87tvkvic16.fsf@esperi.org.uk \
--to=nick.alcock-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=michel-otUistvHUpPR7s880joybQ@public.gmane.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.