| infinity | 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. | 01:25 |
|---|---|---|
| zequence | infinity: alright | 09:40 |
| === rbasak_ is now known as rbasak | ||
| zequence | infinity: All done | 11:46 |
| === arges` is now known as arges | ||
| jsalisbury | ## | 12:58 |
| jsalisbury | ## Kernel team meeting today @ 17:00 UTC | 12:58 |
| jsalisbury | ## | 12:58 |
| hallyn | 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:05 |
| sforshee | hallyn: what model? | 15:13 |
| hallyn | checking | 15:15 |
| hallyn | Wireless 7260 (rev 83) | 15:15 |
| hallyn | ID=cafe Rev=1 Len=014 | 15:15 |
| sforshee | hallyn: I don't really think I've heard of needing to disable 11n on that one, just for the 6xxx models | 15:17 |
| hallyn | oh | 15:17 |
| sforshee | the last kernel update had a fix for some connection drops | 15:17 |
| hallyn | ok. mine might be a dif fproblem then | 15:17 |
| hallyn | which version? | 15:17 |
| sforshee | are you up to date? | 15:17 |
| * sforshee looks | 15:17 | |
| hallyn | i'm on 3.16.0-20-generic #27-Ubuntu | 15:17 |
| hallyn | i do think i had fewer drops yesterday than usual, but not 0 | 15:18 |
| * hallyn updates to check | 15:18 | |
| sforshee | that should have it, they were all upstream as of 3.14 or so | 15:18 |
| sforshee | we just recently backported them to trusty | 15:18 |
| hallyn | i suppose this would annoy me much more if mosh didn't exist | 15:19 |
| sforshee | hallyn: if you open a bug and point me to it I'll have a look at your logs | 15:19 |
| hallyn | i may have already opened one. i'll check in a bit, and otherwise open a new one next time it happens, thx | 15:19 |
| hallyn | sforshee: bug 1370262 | 15:21 |
| ubot5 | Error: Launchpad bug 1370262 could not be found | 15:21 |
| * hallyn checks the log info to see if anything private | 15:22 | |
| sforshee | ugh, firmware crashes | 15:22 |
| sforshee | hallyn: don't make that public, it has a firmware crash dump | 15:23 |
| hallyn | sforshee: color me ignorant - what's the problem with that? | 15:24 |
| hallyn | sforshee: so the firmware actually "crashes" ? | 15:25 |
| hallyn | tha'ts special | 15:25 |
| sforshee | 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:29 |
| hallyn | yuck | 15:30 |
| infinity | zequence: Thanks! | 15:37 |
| jsalisbury | ## | 16:55 |
| jsalisbury | ## Kernel team meeting in 5 minutes | 16:55 |
| jsalisbury | ## | 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] | ||
| arges | jsalisbury: bug 1377851 seems to be trusty only. mind if I target it as such | 20:19 |
| ubot5 | bug 1377851 in linux (Ubuntu) "Kernel panic skb_segment+0x5d7/0x980" [High,Confirmed] https://launchpad.net/bugs/1377851 | 20:19 |
| arges | jsalisbury: also i have a guess at a few patches that might be able to fix it | 20:19 |
| jsalisbury | arges, sure | 20:20 |
| jsalisbury | 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:22 |
| arges | jsalisbury: yea they tested 3.16.3, but 3.13.x fails | 20:23 |
| jsalisbury | arges, ahh, ok | 20:23 |
| arges | kamal: hey is c3caf1192f904de2f1381211f564537235d50de3 queued for 3.13 stable? | 20:30 |
| arges | kamal: i don't see it, i'll sent an email | 20:34 |
| trippeh | kaslr finally works okay on Xen with 3.16.4, fwiw | 20:51 |
| kamal | 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 |
| kamal | Fixed a bug that was introduced by my GRE-GRO patch | 21:18 |
| kamal | (bf5a755f5e9186406bbf50f4087100af5bd68e40 net-gre-gro: Add GRE | 21:18 |
| kamal | support to the GRO stack) that breaks | 21:18 |
| arges | kamal: i applied it to ubuntu-3.13 | 21:19 |
| kamal | and 3.13 doesn't contain bf5a755 either | 21:19 |
| arges | $ git tag --contains 277038d81b3a280ec793e2b05ba8369ff31c1d12 | 21:20 |
| arges | Ubuntu-3.13.0-24.46 | 21:20 |
| arges | looks like tim cherry-picked it, but I don't see a bug reference | 21:20 |
| kamal | arges, ok, so then that kernel (trusty) probably does contain the supporting commit to add the feature, but 3.13-stable does not | 21:20 |
| arges | kamal: gotcha, i guess i'll go through the SRU approach then | 21:21 |
| arges | since it isn't needed in 3.13 stable | 21:21 |
| kamal | 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:21 |
| arges | 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 |
| kamal | arges, no worries man! | 21:22 |
| arges | kamal: : ) | 21:22 |
| === JanC_ is now known as JanC | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!