[07:42] <tjaalton> lotuspsychje: which nvme does your machine have?
[07:42] <tjaalton> ssd
[07:42] <lotuspsychje> tjaalton: its an 860 EVO 250GB sata
[07:42] <lotuspsychje> samsung
[07:43] <tjaalton> try nvme_core.default_ps_max_latency_us=0
[07:43] <lotuspsychje> ok
[07:43] <tjaalton> with 5.0
[07:43] <tjaalton> distro
[07:43] <tjaalton> sata?
[07:44] <lotuspsychje> its not an nvme one, classic sata
[07:44] <tjaalton> sorry, not nvme
[07:44] <tjaalton> right
[07:44] <lotuspsychje> still try it?
[07:44] <tjaalton> no, it won't do anything
[07:44] <lotuspsychje> allrighty
[07:45] <tjaalton> https://www.mail-archive.com/intel-gfx@lists.freedesktop.org/msg145779.html
[07:45] <lotuspsychje> tjaalton: noticed a new bug, but not sure its related to mine: https://bugs.launchpad.net/bugs/1839353
[07:45] <tjaalton> that's fairly old, but still weird
[07:46] <tjaalton> radeon
[07:46] <tjaalton> not related
[07:46] <lotuspsychje> kk
[07:47] <lotuspsychje> tjaalton: padoka or oibaf ppa drivers wont do much neither i suppose?
[07:47] <tjaalton> but, another one where 19.04 works fine, backport is busted
[07:47] <tjaalton> no
[07:48] <lotuspsychje> tjaalton: i also tryed the makelinuxfastagain kernel param, but no dice
[07:48] <tjaalton> what's that?
[07:48] <lotuspsychje> noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off 
[07:48] <lotuspsychje> https://make-linux-fast-again.com/
[07:49] <tjaalton> aha
[07:50] <lotuspsychje> tjaalton: another weird fact is, i only had 1 call yet from an ubuntu customer updated to 5.0.0.23 yet
[07:50] <lotuspsychje> and i installed surely alot on bionic hwe
[07:51] <lotuspsychje> puzzle bug :p
[07:51] <lotuspsychje> or maybe they didnt update yet..
[07:51] <tjaalton> apw: can you kick the drm-intel-next/2019-07-31 mainline build now that there's space? it'd be nice to have that for future debugging
[07:52] <tjaalton> lotuspsychje: apparently the tiniest change to power management can change things, which is why my build of 5.0 worked and distro doesn't
[07:52] <tjaalton> which is probably why the bisect results were "weird"
[07:53] <lotuspsychje> i see
[07:53] <tjaalton> maybe try https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/
[07:54] <lotuspsychje> got this one in my list, is it the same? vmlinuz-5.3.0-994-generic
[07:54] <tjaalton> this is built daily
[07:54] <lotuspsychje> ah ok, on it
[07:54] <tjaalton> which version is yours?
[07:55] <tjaalton> apt-cache policy linux-image-5.3.0-994-generic
[07:55] <lotuspsychje> not a daily for sure
[07:55] <tjaalton> "994" is drm-tip
[07:55] <tjaalton> that part doesn't change
[07:55] <lotuspsychje> hmm, installed: none
[07:55] <tjaalton> 997 is drm-intel-next
[07:55] <tjaalton> ok, removed already
[07:56] <lotuspsychje> lemme try your daily holdon
[08:00] <lotuspsychje> tjaalton: yeah, thats working Linux Rootbox 5.3.0-994-generic #201908072204 SMP Thu Aug 8 02:09:23 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[08:00] <tjaalton> ok
[12:14] <fling> I got the linus tree!
[12:15] <fling> What kernel versions include shiftfs patch?
[12:16] <sforshee> fling: only ubuntu kernels have shiftfs currently
[12:16] <fling> But what versions?
[12:16] <fling> I'm trying to extract the shiftfs patch :P
[12:17] <sforshee> 19.04 onward, so 5.0+
[12:17] <fling> ok
[12:18] <fling> So how would I clone the repo containing 5.1 properly?
[12:19] <sforshee> we don't have a tree that we currently maintain with 5.1, for 5.2 you can use https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/eoan
[12:19] <sforshee> or for 5.0: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/disco
[12:20] <fling> hmmm
[12:20] <fling> zfs does not work with 5.2 yet
[12:20] <fling> and no 5.0 sources in portage anymore :P
[12:20] <fling> Can still use 5.0…
[12:21] <sforshee> the patches from either ought to work fine with 5.1 too, I don't recall any updates being needed between those versions
[12:21] <fling> are 5.0 and 5.2 shiftfs the same?
[12:22] <fling> I should probably compare
[12:22] <sforshee> I'm fairly sure they are the same
[14:32] <fling> sforshee: can't figure out how to glue commits together to form a single patch
[14:42] <sforshee> fling: if you apply the whole set you can then use 'git rebase -i' and squash them into one
[14:43] <cjwatson> Or if you're just trying to inspect a series in bulk then you can use "git diff" from the start to the end of the series
[16:07] <amitk>  /quit