=== ghostcube_ is now known as ghostcube
=== pgraner-dr is now known as pgraner
[13:27] <cyphermox> arges: hello! any news about multipath-modules?
[13:29] <arges> cyphermox: patch is on the ML, smb acked the patch. So it might be applied at some point soon
[13:31] <cyphermox> cool, thanks
[13:32] <smb> arges, of course we may have added dm-queue-length along with dm-service-time ;-P
[13:32] <cyphermox> do you mean you added it as well, or that it should have been done? :)
[13:32] <smb> cyphermox, we could have done but did not
[13:33] <cyphermox> ok
[13:33] <cyphermox> well, either is fine
[13:33] <arges> so for this case, it really just matters at install time right? since this is what gets put into the udeb
[13:33] <cyphermox> yeah, it's just for the installer
[13:33] <smb> yeah as long as the other does not get default one day (which probably is not happening)
[13:33] <arges> so if the package default changes we just need to accomidate that
[13:33] <cyphermox> you could easily install with X and then update to Y after the install
[13:34] <arges> yea and in that case the module is already there
[13:34] <cyphermox> yup
[14:11] <Teduardo> does anyone know what causes cmci storm detected and cmci storm subsided messages during an install of ubuntu 14.04?
[14:12] <Teduardo> i'm testing a server from a new vendor and i've never ever seen that before
[14:22] <arges> Teduardo: sounds like a hardware issue. https://lkml.org/lkml/2012/8/7/916
[14:57] <jsalisbury> **
[14:57] <jsalisbury> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[14:57] <jsalisbury> **
[15:10] <bjf> manjo, didn't you want to discuss something this a.m.?
[15:10] <manjo> bjf, yes I did .. stuck on calls 
[15:11] <manjo> bjf, so starts in 40mts ? 
[15:12] <bjf> manjo, starts here in this channel whenever you want :-)
[15:13] <manjo> bjf, yes sir 
[15:18] <arges> bjf: 81848
[15:40] <manjo> cking, bjf, I have 3 question related to ARM64 ... I am not looking for info on specific patches etc... but just to get an idea about where we are at with these 3 things for 15.10. 
[15:40] <manjo> 1. What is the timeline for merging ARM64 + ACPI patches from upstream and linar
[15:40] <manjo> o in 15.10? is ppsati doing that work, can we work with him if our friends find
[15:40] <manjo> some missing patches that we might have to cherry pick from upstream?
[15:41] <manjo> jsalisbury, ^
[15:42] <cking> manjo, which specific ACPI features do you require?
[15:43] <manjo> cking, so I know that a lot of the platform code are already upstream, but some of the driver work is ongoing ... I just want to get a feel for who is tracking those patches 
[15:43] <manjo> cking, if not I can track those and send pull reqs
[15:43] <cking> manjo, not me personally
[15:44] <cking> again, "which patches"?
[15:45] <bjf> manjo, we don't have any, one, person specifically tasked with "track linaro ACPI patches that are not upstream"
[15:45] <manjo> cking, like I said at the beginning I am not looking at specific patches ... I just want to get a general idea from you guys 
[15:45] <bjf> manjo, if you are tracking things like that you are welcome to submit patch requests to the ML like anyone is
[15:46] <manjo> so that I could send in pull reqs
[15:46] <cking> manjo, the default is that you get what lands in the wily kernel when is released, e.g. 4.1
[15:46] <manjo> cking, cool. I will track the deta and send you any pulls reqs then 
[15:46] <cking> or 4.2 pehaps
[15:46] <manjo> cking, will you pull from linaro ?
[15:47] <manjo> cking, coz that leads into my Q2
[15:47] <manjo> What is the delta like between LEG and 15.10 dev kernel? Some of our friends want to drop using LEG and start using 15.10 dev tree as the base tree for arm64 servers. How quickly can we sync dev 15.10 with LEG ? 
[15:47] <manjo> s/quicly/frequently 
[15:48] <bjf> manjo, upstream in Linus' tree
[15:48] <cking> what's LEG?
[15:48] <bjf> s/in/is/
[15:48] <manjo> linaro engg 
[15:49] <cking> manjo, i really can't tell what the delta is, that's a homework question isn't it?
[15:49] <manjo> cking, linaro enterprize group ... ie linaro kernel 
[15:49] <bjf> manjo, we don't track everyone's kernel git repo
[15:50] <cking> not in my head, anyway
[15:51] <cking> manjo, i think if you need to know the delta, one can work that out yourself, you have access to the git repos
[15:52] <manjo> ok I was under the assumption that you guys track and pull linaro patches ... that is why I asked 
[15:52] <cking> ack
[15:53] <manjo> so I thought you might be able to tell me if there is a 6 month worth of delta or couple of weeks 
[15:54] <bjf> manjo, sorry, we just don't know. there are too many kernel git repos for us to track very many. that's certainly not one we do.
[15:56] <manjo> one more question ... but I think I know the ans already ... do you guys plan to pull in 8.1 arch support & smmuv3 support in 15.10 ? 
[15:57] <manjo> those patches are still int he works and might not have hit stable ... but from what I hear those might be upstream by october ish
[15:57] <manjo> if not .. do you see any issues with pulling those in for 16.04 dev ? 
[15:59] <bjf> manjo, if they hit Linus' tree then we'll likely pull them automatically for 16.04. if they don't reach upstream until oct. then they likely won't make it into 15.10
=== pgraner is now known as pgraner-appt
[16:56] <jsalisbury> ##
[16:56] <jsalisbury> ## Kernel team meeting in 5 minutes
[16:56] <jsalisbury> ##
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ## Meeting starting now
[17:00] <jsalisbury> ##
=== jsalisbury changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Ubuntu Kernel Team Meeting - Tues July 7th, 2015 - 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. || Channel logs: http://irclogs.ubuntu.com/
=== pgraner-appt is now known as pgraner