On Sat, Jan 10, 2026 at 03:45:56PM -0800, patrick keshishian wrote: > On Sat, Jan 10, 2026 at 3:05???AM Crystal Kolipe > <[email protected]> wrote: > > > > On Fri, Jan 09, 2026 at 11:03:59AM -0800, patrick keshishian wrote: > > > For what it's worth, I think I see the same warning messages > > > since upgrade 7.8 (also on -current). I was hoping to post > > > about this after I tested this AI summarized change > > > > What exactly in this "AI summarized change" are you hoping to test? > > The suggested change was to rate-limit the warning message, and thus > stop the flooding in dmesg.
Well if you don't mind compiling your own kernel you can test that right now by just removing the, (only), call to dev_warn_ratelimited() in: sys/dev/pci/drm/radeon/evergreen_cs.c no need to wait months or years for the proposted change in the linux kernel to trickle down. But that will just prevent the log flooding. It doesn't fix the actual problem. >From a casual read of the code, my understanding is that when this error condition is met, the buffer gets truncated to the maximum size supported by the hardware. Yet nobody has reported seeing graphical glitches. So maybe try changing the warning to dump the actual values being compared and see if it's something obvious like an off-by-one or bad signed to unsigned conversaion. But without more information from somewhere or someone with the affected hardware we're not going to get very far.
