[01:25] zequence: If you get a chance, can you smoketest your lowlatency kernel? We're trying to release a tiny bit early this cycle to accomodate the entire kernel team traveling next week. [09:40] infinity: alright === rbasak_ is now known as rbasak [11:46] infinity: All done === arges` is now known as arges [12:58] ## [12:58] ## Kernel team meeting today @ 17:00 UTC [12:58] ## [15:05] apw: so, this thing about having to disable 11n on intel wifi (assuming it fixes the connection drops - i haven't tried it, i just keep hitting f8 to turn off wifi and back on :) - is there a fix in the works so we dn't have to? new firmware on the way from intel or something? [15:13] hallyn: what model? [15:15] checking [15:15] Wireless 7260 (rev 83) [15:15] ID=cafe Rev=1 Len=014 [15:17] hallyn: I don't really think I've heard of needing to disable 11n on that one, just for the 6xxx models [15:17] oh [15:17] the last kernel update had a fix for some connection drops [15:17] ok. mine might be a dif fproblem then [15:17] which version? [15:17] are you up to date? [15:17] * sforshee looks [15:17] i'm on 3.16.0-20-generic #27-Ubuntu [15:18] i do think i had fewer drops yesterday than usual, but not 0 [15:18] * hallyn updates to check [15:18] that should have it, they were all upstream as of 3.14 or so [15:18] we just recently backported them to trusty [15:19] i suppose this would annoy me much more if mosh didn't exist [15:19] hallyn: if you open a bug and point me to it I'll have a look at your logs [15:19] i may have already opened one. i'll check in a bit, and otherwise open a new one next time it happens, thx [15:21] sforshee: bug 1370262 [15:21] Error: Launchpad bug 1370262 could not be found [15:22] * hallyn checks the log info to see if anything private [15:22] ugh, firmware crashes [15:23] hallyn: don't make that public, it has a firmware crash dump [15:24] sforshee: color me ignorant - what's the problem with that? [15:25] sforshee: so the firmware actually "crashes" ? [15:25] tha'ts special [15:29] hallyn: yes, the firmware crashes. I don't know exactly what's in the dump, but it could presumably have things like keys for whatever network you were connected to at the time. [15:30] yuck [15:37] zequence: Thanks! [16:55] ## [16:55] ## Kernel team meeting in 5 minutes [16:55] ## === jsalisbury changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Ubuntu Kernel Team Meeting - Tues October 21st, 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. === bjf is now known as bjf[afk] [20:19] jsalisbury: bug 1377851 seems to be trusty only. mind if I target it as such [20:19] bug 1377851 in linux (Ubuntu) "Kernel panic skb_segment+0x5d7/0x980" [High,Confirmed] https://launchpad.net/bugs/1377851 [20:19] jsalisbury: also i have a guess at a few patches that might be able to fix it [20:20] arges, sure [20:22] arges, It's fixed upstream, so I asked to test 3.13.11.8. Maybe the patches you believe can fix this are already in there [20:23] jsalisbury: yea they tested 3.16.3, but 3.13.x fails [20:23] arges, ahh, ok [20:30] kamal: hey is c3caf1192f904de2f1381211f564537235d50de3 queued for 3.13 stable? [20:34] kamal: i don't see it, i'll sent an email [20:51] kaslr finally works okay on Xen with 3.16.4, fwiw [21:18] arges, hmmm... you say that c3caf1192 applies cleanly (to 3.13-stable?), but no it doesn't :-) ... which doesn't surprise me since its description says: [21:18] Fixed a bug that was introduced by my GRE-GRO patch [21:18] (bf5a755f5e9186406bbf50f4087100af5bd68e40 net-gre-gro: Add GRE [21:18] support to the GRO stack) that breaks [21:19] kamal: i applied it to ubuntu-3.13 [21:19] and 3.13 doesn't contain bf5a755 either [21:20] $ git tag --contains 277038d81b3a280ec793e2b05ba8369ff31c1d12 [21:20] Ubuntu-3.13.0-24.46 [21:20] looks like tim cherry-picked it, but I don't see a bug reference [21:20] arges, ok, so then that kernel (trusty) probably does contain the supporting commit to add the feature, but 3.13-stable does not [21:21] kamal: gotcha, i guess i'll go through the SRU approach then [21:21] since it isn't needed in 3.13 stable [21:21] arges, so did you specifically want c3caf1192 in 3.13-stable for some reason? yes, it looks to me like this should just go to trusty as an SRU. [21:22] kamal: no. it fixes a commit that isn't in 3.13-stable (For some reason I assumed it was. so next time i'll check) [21:22] arges, no worries man! [21:22] kamal: : ) === JanC_ is now known as JanC