[05:33] <Taggnostr> hello
[05:34] <Taggnostr> I was wondering when kernel 4.13.8 will be released for artful -- I found https://insights.ubuntu.com/2017/10/18/kernel-team-summary-october-18th-2017/ and it has a release date for the 30th, but doesn't mention the release version and doesn't seem to include artful
[06:40] <tjaalton> Taggnostr: don't think that applies to artful yet, but a new sru cycle starts next week so it should get tagged for proposed then
[06:40] <tjaalton> git has 4.13.8
[22:00] <slangasek> jsalisbury: hi, I tested the last three kernels you posted on LP: #1724911, and they confirm the earlier results but don't bring us any closer to having a clean commit to grab :/
[22:00] <jsalisbury> slangasek, yeah, I just saw your comments.  I'm going to have to dig further to under stand that Merge.  
[22:00] <slangasek> ok
[22:03] <slangasek> perhaps it's legitimately a bug that's fixed only by a combination of commits from both branches?
[22:04] <jsalisbury> slangasek, yeah, that's what I was thinking, maybe multiple commits are needed.  
[22:05] <jsalisbury> slangasek, I need to confirm whether or not the commits in the merege are compiled in before the merge tag is added.  
[22:06] <jsalisbury> slangasek, becuase when the HEAD is set to 3840ed9548f, I would think all of the commits in the entire merge are being used since that is the last commit in the merge.
[22:21] <TJ-> jsalisbury: slangasek looking at all the commits in that tty-4.14-rc1 merge, the commit that stands out is a09ac3974d0c0b25dfa70f8076546bc4876dd7a8 "tty: resolve tty contention between kernel and user space"
[22:25] <slangasek> TJ-: ok, but 3840ed9548f778717aaab5eab744da798c3ea055 is bad, so where is that commit coming in from?
[22:49] <slangasek> TJ-: and more to the point, 3840ed9548f778717aaab5eab744da798c3ea055..e63a94f12b5fc67b2b92a89d4058e7a9021e900e shows none of the differences from that commit, or basically anything of interest in the tty driver
[22:50] <slangasek> a bunch of pty stuff
[22:53] <TJ-> slangasek: yeah, I knew that, but I went looking for commit messages that suggested the functionality had been touched. Looking at the commit history there are 3379 commits between those 2 points. I suspect the fix is not in  drivers/tty/ but possibly in drivers/gpu/ or possibly arch/x86/mm/
[22:56] <slangasek> yes
[23:46] <slangasek> jsalisbury: fwiw I'm attempting a rebisect now of e63a94f12b5fc67b2b92a89d4058e7a9021e900e .. 1a3b85ea36d38d5732fdd86b321b10bcaeb53512 (i.e. down the tty branch) with a rebase onto 1a3b85ea36d38d5732fdd86b321b10bcaeb53512 on each step
[23:47] <slangasek> jsalisbury: this is with my 2h iteration cycle again, so if you were to jump ahead of me I would not mind ;)