Date: Sun, 08 Dec 2019 18:44:57 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 241101] i915kms working with 12.0 but not 12.1-BETA3 Message-ID: <bug-241101-7141-efbMynnApY@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-241101-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-241101-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241101 --- Comment #17 from Tomasz "CeDeROM" CEDRO <tomek@cedro.info> --- (In reply to Theron Tarigo from comment #13) Thank you Tarigo :-) I did a fix by rebuilding the module on a 12.1, but th= en it was replaced by pkg upgrade, causing the problem again. I would prefer to have such package globally blacklisted rather than blocking it myself after= it crashed my production machine. I would really prefer to see a message from PKG "Please build this package = from Ports otherwise it will not work reliably on this system" rather than getti= ng back into system crash loop after I considered problem to be solved. The root cause of this problem, and I hope no more problems like this in future, is allowing Linux like bleeding edge approach in Kernel, including Kernel API changes with each release. I am sure there can be a good solution for that, so we do don't need to "fix problems that never existed before"^T= M. Otherwise what would be the difference between FreeBSD and Linux? :-) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-241101-7141-efbMynnApY>