On Sat, 8 Nov 2025, Steve Kargl wrote:
On 11/8/25 20:26, Mark Millard wrote:
Steve Kargl <kargls_at_comcast.net> wrote on
Date: Sun, 09 Nov 2025 01:55:40 UTC :
Can someone back out the git commit 4179e6b78297369f?
This is causing pkg-fallout@ to spam the freebsd-x11
mailing list. It seems no one reads replies to pkg-fallout.
See for detail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=290432
It appears that commit is in stable/15 and in releng/15.0 as:
https://cgit.freebsd.org/src/commit/sys/compat/linuxkpi/common?h=releng/15.0&id=62c3b77d1d1084dc46663eed52e288307b5c7e64
Your request is probably a very big ask as this point.
Yes, the patch was merged into stable/15. It should not have
been!
It's not a big ask. Either back out the commit or maybe,
just maybe, someone can commit the patch in PR290432.
There are dozens of pkg-fallout@ emails to freebsd-x11.
Many have a reply from me pointing to the patch in
PR290432.
So, either back out the patch that breaks X11 for many
people or commit the patch in the PR.
I followed-up on the PR but I have no clue where pkg-fallout stuff
for drm-kmod modules go -- do you have a link to them? Not that I am doing
drm work or ports but I'll be happy to look.
If the commit was a problem it must have been one for almost 6 weeks.
Someone could have mentioned this since somwhere.
The above + nvidia blocked wireless updates for more than two months and all of
this was known since some time in July so it's quite late now.
The above LinuxKPI change cleans up stuff in drm-kmod which should have happened
a long time ago (or never been done that way in first place but I guess years
ago
LinuxKPI just wasn't there yet) and there's more of that needed to avoid
blockers
for other things in the future.
The workaround I suggested for you in the PR would likely have to be applied
conditionally to 5.15-lts (or maybe even 5.10) but 5.15-lts is not referenced
at all by graphics/drm-kmod.
So if you want things to work, it's the ports which needs to be fixed.
/bz
--
Bjoern A. Zeeb r15:7
