On 10.09.25 10:02, Christian König wrote: > On 09.09.25 18:21, Alex Deucher wrote: >> On Tue, Sep 9, 2025 at 12:17 PM Borislav Petkov <b...@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. > > Well doesn't the cause of the warning result in corrupted rendering?
Per https://gitlab.freedesktop.org/mesa/mesa/-/issues/13838#note_3088335 it would result in one dropped vertex, which might be hard to notice. That's why I agree that in this specific case, not logging anything by default might have resulted in the issue taking much longer to be discovered (if ever). (A potential counter argument being: If it's not noticeable, does the kernel need to log anything about it by default?) -- Earthling Michel Dänzer \ GNOME / Xwayland / Mesa developer https://redhat.com \ Libre software enthusiast
