[10:37] <fling> How do I extract shiftfs from this 15M patch? -> https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.63/0001-base-packaging.patch
[10:39] <lotuspsychje> tjaalton: i updated my flickering bug a bit with some different ubuntu releases/kernels and seems like lubuntu 19.04 with kernel 5.0.0.13 works bug #1838644
[10:39] <ubot5> bug 1838644 in linux-hwe (Ubuntu) "Booting into desktop results in flickering" [Undecided,Confirmed] https://launchpad.net/bugs/1838644
[10:46] <TJ-> fling: don't; use the git repo
[10:47] <fling> TJ-: I have no idea in which repo to get a shiftfs patch for the specific version
[10:47] <TJ-> fling: the index page gives the repo URL and branch to pull from
[10:48] <fling> thanks
[10:50] <tjaalton> lotuspsychje: ok, I'm building 5.0.0-23 with one revert
[10:51] <lotuspsychje> tnx
[11:24] <lotuspsychje> tjaalton: ill be afk for a while, ill find your ping later ok
[11:25] <tjaalton> ok, should be ready any minute now
[11:26] <lotuspsychje> oh all wait up then
[11:26] <tjaalton> silly kernel build is mostly serial
[11:26] <tjaalton> at least with >64 cores
[11:26] <lotuspsychje> :p
[11:27] <lotuspsychje> tjaalton: we are looking for a working one this time right?
[11:27] <tjaalton> maybe
[11:27] <tjaalton> hopefully
[11:27] <lotuspsychje> kk
[11:27] <tjaalton> only seven commits to i915 since 5.0.0-13, and one looks suspicious
[11:28] <lotuspsychje> tjaalton: i saw that underrun error on lubuntu too, but it didnt flicker
[11:29] <tjaalton> ah
[11:29] <tjaalton> didn't try ubuntu 19.04?
[11:29] <lotuspsychje> yes in a live
[11:29] <lotuspsychje> those gave me flickering
[11:30] <tjaalton> 19.04 live with 5.0.0-23? how's that possible
[11:30] <tjaalton> it shipped with -13
[11:30] <lotuspsychje> oh i might be wrong about that perhaps
[11:30] <lotuspsychje> but 19.04 desktop surely flickered
[11:31] <tjaalton> then this test build is likely pointless
[11:32] <lotuspsychje> well if both have -13 and one works and the other not?
[11:32] <lotuspsychje> its an ubuntu-desktop related issue then?
[11:32] <tjaalton> no
[11:32] <tjaalton> it just manifests in a different way
[11:32] <tjaalton> you still get underruns
[11:32] <lotuspsychje> ah
[11:33] <tjaalton> did you look for bios updates?
[11:33] <lotuspsychje> not yet no, i found the clevo updates link
[11:34] <lotuspsychje> tjaalton: also weird is, i didnt get calls yet from any other clevo customer
[11:35] <lotuspsychje> and they the other guy from my bug, its also a clevo with a different bios version
[11:35] <lotuspsychje> anyway, need to bbl first
[11:35] <lotuspsychje> ill test it when im back
[11:35] <tjaalton> copying to the repo
[11:39] <tjaalton> done
[11:41] <TJ-> we really ought to have an automated tool for this :)
[11:41] <TJ-> self-service
[16:19] <lotuspsychje> tjaalton: no dice : (
[17:01] <tjaalton> not surprised
[17:17] <fling> TJ-: is there a tool for getting the shiftfs patch off there?
[17:18] <fling> git is way too slow
[18:24] <fling> I cloned deep enough but I only found shifts in the log in commit fea6d2a610c899bb7fd8e95fcbf46900b886e5a3 vfs: Use upper filesystem inode in bprm_fill_uid()
[18:24] <fling> This does not look like a shiftfs patch
[18:24] <fling> So how do I get it exactly?