[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51ae551b-6708-4fcd-84f9-fc1400f02427@mailbox.org>
Date: Mon, 1 Sep 2025 11:27:01 +0200
From: Michel Dänzer <michel.daenzer@...lbox.org>
To: Borislav Petkov <bp@...en8.de>, Alex Deucher <alexdeucher@...il.com>
Cc: amd-gfx@...ts.freedesktop.org, Alex Deucher <alexander.deucher@....com>,
Christian König <christian.koenig@....com>,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Re: evergreen_packet3_check:... radeon 0000:1d:00.0: vbo resource
seems too big for the bo
On 30.08.25 19:48, Borislav Petkov wrote:
>
> diff --git a/drivers/gpu/drm/radeon/evergreen_cs.c b/drivers/gpu/drm/radeon/evergreen_cs.c
> index a46613283393..6285ff1b1bff 100644
> --- a/drivers/gpu/drm/radeon/evergreen_cs.c
> +++ b/drivers/gpu/drm/radeon/evergreen_cs.c
> @@ -2418,7 +2418,7 @@ static int evergreen_packet3_check(struct radeon_cs_parser *p,
> size = radeon_get_ib_value(p, idx+1+(i*8)+1);
> if (p->rdev && (size + offset) > radeon_bo_size(reloc->robj)) {
> /* force size to size of the buffer */
> - dev_warn_ratelimited(p->dev, "vbo resource seems too big for the bo\n");
> + dev_warn_once(p->dev, "vbo resource seems too big for the bo\n");
> ib[idx+1+(i*8)+1] = radeon_bo_size(reloc->robj) - offset;
> }
>
Like all scenarios which can be triggered by user space, this should rather use some kind of debug output API which doesn't hit dmesg by default (can be a non-once variant instead, that's more useful for user-space developers).
--
Earthling Michel Dänzer \ GNOME / Xwayland / Mesa developer
https://redhat.com \ Libre software enthusiast
Powered by blists - more mailing lists