From: "Michel Dänzer" <michel.daenzer@mailbox.org>
To: Alex Deucher <alexdeucher@gmail.com>, Borislav Petkov <bp@alien8.de>
Cc: amd-gfx@lists.freedesktop.org,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: evergreen_packet3_check:... radeon 0000:1d:00.0: vbo resource seems too big for the bo
Date: Tue, 9 Sep 2025 19:00:04 +0200 [thread overview]
Message-ID: <fc135a6e-fe79-4fc0-b3aa-c110cc3676eb@mailbox.org> (raw)
In-Reply-To: <CADnq5_MOazXJ4tUNa5uMdkWY7ZCu70M49yG00JsNHB-FO7XNvA@mail.gmail.com>
On 09.09.25 18:21, Alex Deucher wrote:
> On Tue, Sep 9, 2025 at 12:17 PM Borislav Petkov <bp@alien8.de> wrote:
>> On Tue, Sep 09, 2025 at 10:43:47AM +0200, Michel Dänzer wrote:
>>> Then the developer needs to tell the user how to enable the debugging output
>>> and get it to them. That's pretty standard.
>>
>> *IF* the user even notices anything. As said earlier, it didn't cause any
>> anomalies on my machine besides flooding dmesg. Which I look at for obvious
>> reasons but users probably don't.
>
> Right. I think there needs to be something otherwise no one will notice at all.
I concede that in this specific case, dev_warn_once might be the best compromise.
(More to come in a follow-up to Alex's corresponding patch for the other similar log messages in this file)
--
Earthling Michel Dänzer \ GNOME / Xwayland / Mesa developer
https://redhat.com \ Libre software enthusiast
next prev parent reply other threads:[~2025-09-09 17:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 17:16 Borislav Petkov
2025-08-29 18:26 ` Alex Deucher
2025-08-29 19:40 ` Borislav Petkov
2025-08-29 20:48 ` Borislav Petkov
2025-08-30 16:30 ` Alex Deucher
2025-08-30 17:48 ` Borislav Petkov
2025-08-31 21:42 ` Timur Kristóf
2025-08-31 22:08 ` Borislav Petkov
2025-09-01 9:27 ` Michel Dänzer
2025-09-01 10:10 ` Borislav Petkov
2025-09-08 17:05 ` Michel Dänzer
2025-09-08 18:00 ` Borislav Petkov
2025-09-09 8:43 ` Michel Dänzer
2025-09-09 16:16 ` Borislav Petkov
2025-09-09 16:21 ` Alex Deucher
2025-09-09 17:00 ` Michel Dänzer [this message]
2025-09-10 8:02 ` Christian König
2025-09-10 8:12 ` Michel Dänzer
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=fc135a6e-fe79-4fc0-b3aa-c110cc3676eb@mailbox.org \
--to=michel.daenzer@mailbox.org \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bp@alien8.de \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®