=== shuduo-afk is now known as shuduo
=== JanC_ is now known as JanC
[08:52] <yofel> FYI: lp 1566726
[08:52] <ubot5`> Launchpad bug 1566726 in linux-lts-utopic (Ubuntu) "System freeze after update to 3.16.0-69-generic [NULL pointer reference in radeon_fence_ref]" [Undecided,New] https://launchpad.net/bugs/1566726
[09:03] <infinity> That sounds ungood.
[09:03] <infinity> jsalisbury: ^-- Care to escalate that a bit?
[10:32] <apw> kamal, ^
[14:35] <jsalisbury> infinity, thanks for the pointer on that bug.  yofel, I'll post a test kernel shortly.
[14:44] <jsalisbury> apw, kamal, looks like the offending commit is already reverted in -next:
[14:44] <jsalisbury> a907233 Revert "drm/radeon: hold reference to fences in radeon_sa_bo_new"
[14:44] <jsalisbury> 72a5cff drm/radeon: hold reference to fences in radeon_sa_bo_new
[14:45]  * jsalisbury is building a test kernel of -next for testing
[14:45] <kamal> jsalisbury, ha!  yup, I was _just_ confirming exactly that with Luis.
[14:47] <kamal> jsalisbury, that is indeed the fix, and yes, its already committed.   How about you build a test kernel (either of the top of utopic-next, or with just that revert applied), so we can get the bug submitters to verify it?
[14:48] <jsalisbury> kamal, I have test kernel of the top of utopic-next building now.  I'll have it verified
[14:48] <kamal> jsalisbury, very good, thanks
[14:48] <jsalisbury> np
[14:49] <kamal> jsalisbury, also fyi, I've determined that the problem should only affect 3.16 (so Utopic only, no other Ubuntu kernels)
[14:49] <jsalisbury> great
[15:06] <dschatzberg> hey all, I'm trying to test an upstream kernel (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc2-wily/), how do I apply the patches provided? Applying them naively doesn't seem to set the permissions right?
[20:05] <genkgo> jsalisbury: exciting, coming really close now
[20:05] <genkgo> where can i look that bad commit 5044635f00, is that a commit from linus?
[20:06] <genkgo> i mean linus' repo linux on github
[20:37] <jsalisbury> genkgo, yes, it's in Linus' tree.  That particular commit isn't the cause.  That was just the tip of the kernel tree for that test kernel build.
[20:37] <genkgo> ok, i think i don't get what a bisect actually means
[20:38] <genkgo> i will read upon that
[20:38] <jsalisbury> genkgo, there is a wiki page that has some info: https://wiki.ubuntu.com/Kernel/KernelBisection
[20:38] <genkgo> jsalisbury: wonderful, i will read that!
[21:21] <genkgo> jsalisbury: ah, i get it, it just a fast way to pick a wrong commit
[21:22] <genkgo> just like you did by picking the latest good and first bad version of the kernel
[21:22] <genkgo> but only with those sha identifiers it's less obvious