Date: Sat, 23 Nov 2019 17:02:20 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 236003] x11-drivers/xf86-video-intel: update to 2019-11-17 snapshot and refactor Message-ID: <bug-236003-7141-RnTEQtbCt8@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-236003-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-236003-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=3D236003 --- Comment #25 from Jan Beich <jbeich@FreeBSD.org> --- (In reply to Alexandr Krivulya from comment #23) Can you try v7? If it doesn't help track down which version introduced the regression (may require downgrading the entire ports tree to avoid patch conflicts). After that it should be easy to bisect e.g., 1. Run "git clone https://gitlab.freedesktop.org/xorg/driver/xf86-video-int= el/" 2. Run "git bisect" using upstream commits from DISTVERSIONSUFFIX (strip "-= g") or GL_COMMIT for the first bad and the last good version of the patch 3. Adjust DISTVERSION + DISTVERSIONSUFFIX in the port 4. Run "make makesum" to regen distinfo 5. Run "make clean all deinstall install" to start runtime testing 6. Run "git bisect bad" if still you can reproduce or "git bisect good" if = you cannot 7. Repeat 3-6 steps until "git bisect" points to a single commit 8. Append the hash of the first bad to https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/commit/ to get = an URL of the commit Once you find what caused upstream regression it should be easier to unders= tand why (unless kernel- or chip-specific), hack to make it work again or simply revert the change. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-236003-7141-RnTEQtbCt8>