[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2764782f-d411-4142-aa56-f1af0968ecd5@mailbox.org>
Date: Mon, 8 Sep 2025 19:05:17 +0200
From: Michel Dänzer <michel.daenzer@...lbox.org>
To: Borislav Petkov <bp@...en8.de>
Cc: Alex Deucher <alexdeucher@...il.com>, 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 01.09.25 12:10, Borislav Petkov wrote:
> On Mon, Sep 01, 2025 at 11:27:01AM +0200, Michel Dänzer wrote:
>> use some kind of debug output API which doesn't hit dmesg by default
>
> You still want to be enabled by default so that normal users can see it and
> actually report it.
These messages are primarily intended for developers, not users (which will notice and report the corresponding user-space issues instead).
>> (can be a non-once variant instead, that's more useful for user-space
>> developers).
>
> I don't see how a non-once variant can tell you anything new - it is repeating
> one cryptic message to most users so what's the point of parroting it more
> than once?
The once variant means user-space developers need to reboot after hitting it once.
--
Earthling Michel Dänzer \ GNOME / Xwayland / Mesa developer
https://redhat.com \ Libre software enthusiast
Powered by blists - more mailing lists