=== hughhalf is now known as hugh_food === hughhalf is now known as hugh_afk [06:15] Er, whats the proposed kernel for Utopic? [06:15] 3.17 or higher? [06:50] http://paste.ubuntu.com/8598461/ [06:50] this is with the patch https://launchpadlibrarian.net/183190658/0013-add-support-for-Linux-3.17.patch applied, but as 0014 [07:11] TheFakeazneD525 (N,BFTL), v3.16 [07:13] tseliot, that looks like one you will need for brcmwl for VV [07:15] apw: I'm probably missing context here. What is it that I need for bcmwl? [07:16] TheFakeazneD525 | http://paste.ubuntu.com/8598461/ [07:16] TheFakeazneD525 | this is with the patch https://launchpadlibrarian.net/183190658/0013-add-support-for-Linux-3.17.patch applied, but as 0014 [07:17] tseliot, that has an error on v3.17 i believe and possible fixes, not sure we care till VV opens, but ... [07:18] apw: we can simply use the driver in utopic [07:25] tseliot, ok great [07:26] apw: I'm working on a high priority bug now but, as soon as I'm done with it, I'll deal with the update [07:27] tseliot, whenever if this is v3.17 related, VV won't even open for a week let alone have a new kernel [07:29] apw: ok, good [07:47] infinity, ok it looks like i have a possible fix for that left-mouse issue ... am building some test kernels right now [07:47] infinity, and if that is the fix, then i expect it will make stables in short order for T et al. [08:08] I started hitting https://lkml.org/lkml/2014/8/20/6 and it's still present on 3.13.0-38-generic on trusty. Is that on anyone's radar or should I report a bug? It doesn't seem like it was Cc'ed to stable. :( [08:12] pkern: actually, it looks like it was tagged for stable -- commit 21e81002f9788a3af591416b6dec60d7b67f2fb2 [08:13] Oh, https://lists.ubuntu.com/archives/kernel-team/2014-October/049094.html [08:13] henrix: Hm, thanks. [08:13] I guess it's too late for -38 at this point. [08:13] pkern: and it is already in 3.13, so it shouldn't take too long ti hit the trusty kernel [08:16] yes, it is too late. but the good news is that that commit is already in the master-next branch for trusty so it should be in the next SRU cycle [09:08] jtaylor, hey ... i've posted a test kerenl for uutopic so we can confirm this, and hopefully fix this in the release [09:14] henrix, It was not in master-next a few minutes ago. I would currently be building test-kernels. Does that still make sense? [09:15] smb: hmm? are you talking about commit 21e81002f9788a3af591416b6dec60d7b67f2fb2? [09:16] smb: it's upstream 21e81002f9788a3af591416b6dec60d7b67f2fb2, which corresponds to d1614714e30178f8bbb8568dfb905dd1356ff8aa in trusty tree [09:16] henrix, Oops no but similar [09:16] smb: ah :) [09:16] henrix, talking about 2f3169fb18f4643ac9a6a097a6a6c71f0b2cef75 [09:17] Just read remove proc entry warning and thought those were the same [09:17] ah, that one. ok, kamal should queue it soon, but it's not there yet [09:17] Yeah, it just made it into 3.18-rc1 which is rather fresh === jsalisbury changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Ubuntu Kernel Team Meeting - Tues October 28th 14 - 17:00 UTC || If you have a question just ask, and do wait around for an answer! If the question is should I file a bug for something, likely you can assume yes. === jsalisbury changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Ubuntu Kernel Team Meeting - Tues October 28th, 2014 - 17:00 UTC || If you have a question just ask, and do wait around for an answer! If the question is should I file a bug for something, likely you can assume yes. [16:44] apw: the fix works, but the kernel breaks my network [16:44] note that the same patch also applies to the current trusty kernel in -proposed [16:46] jtaylor, ack, yes, that one will get it via stable, we are in rather more of a rush for release [16:48] yes I'd just like to ensure the kernel stays in proposed for now [16:48] apw: is the kernel you posted a complete utopic kernel with only the one fix applied or more? [16:49] jtaylor, that indeed. did you install -extra as well ? [16:49] just wondering if the missing network is a regression (which can't be related to the touchpad fix) or just a build with some drivers missing? [16:49] hm [16:49] no didn't install extras, [16:49] I'll try that [16:49] ok so you half your kernel [16:50] I nevers installed extras when bisecting the bug [16:50] we don't use the split in the mainline builds for instance [16:53] apw: thx with extras it works [16:53] jtaylor, ack thanks, if you could (if you havent) report your testing in the bug too, i'll get that wrapped and stacked in the morning [16:54] I posted the same in the bug [16:54] great [18:53] henrix: gah, thanks for the ARM syscall # catch. Looks like they operate in padded steps, and it was already at the old max :) [18:53] I've fixed it in my tree now. Not sure if you want to re-pull or just fix up that specific problem, but I sent a new pull-request. [19:19] kees: thanks, i'll take a look at again it tomorrow [19:23] henrix: thanks!