[00:07] <Sarvatt_> vanhoof: ping
[07:37] <fairuz> morning
=== smb` is now known as smb
=== skaet is now known as skaet_afk
=== yofel_ is now known as yofel
=== diwic is now known as diwic_afk
=== diwic_afk is now known as diwic
=== herton_ is now known as herton
=== _LibertyZero is now known as LibertyZero
[14:17] <tgardner> ogasawara, 'just say no' email sent
[14:17] <ogasawara> tgardner: ack
[14:21] <ogasawara> sforshee: bug 508516, care if I just mark that Won't Fix?
[14:22] <sforshee> ogasawara: d'oh, I meant to do that bug guess I forgot. Please do.
[14:22] <ogasawara> sforshee: cool, thanks.  just cleaning up some bugs on the release meeting agenda.
[14:29]  * ogasawara back in 20
=== sconklin-gone is now known as sconklin
[14:43] <jan_d> Hello! I am new to this channel... yesterday I installed & upgraded kubuntu-natty, and I am now running into this bug in a most severe way. As I was under the impression that this but had been fixed in 2.6.38 final, I am now wondering how it still happens in natty (with 2.6.38-8). this is the bug: http://www.mentby.com/Group/linux-kernel/mass-udp-flow-reboot-linux-with-realtek-rtl-8169-gigabit.html 
[14:43] <jan_d> has anybody else noticed this?
[14:44] <jjohansen> jan_d: the rrl8192 driver is not very stable, I have been suffering through it this week
[14:45] <jjohansen> jan_d: I am not sure I would attribute the errors I am seeing to this specific bug
[14:46] <jan_d> ok
[14:46] <jan_d> I can undestand that
[14:46] <jan_d> that bug report however details my problems, which is why I cited it
[14:46] <jan_d> in 10.10 I had no such problem, ever
[14:47] <jan_d> so Now I was wondering if I should go back to Maverick + Kubuntu-PPA, instead of testing Natty
[14:47] <jan_d> which would be a pitty, but if there is no immediate (or short-term) solution, then I will have no choice
[14:47] <jan_d> luckily, it's not a production machine
[14:48] <jjohansen> jan_d: well that is going to depend on if you can live with the bug until it gets fixed
[14:48] <jan_d> normal internet usage does not trigger a crash, but if I want to do image processing or mathematical processing, it's going to crash every 5min
[14:48] <jjohansen> jan_d: if you need stability and you aren't getting it with natty and were with maverick then the choice seems obvious
[14:49] <jan_d> yep
[14:49] <jan_d> ok, so I take it that there is no already-existant solution
[14:49] <jan_d> Would it make sense to file a bug with (k)ubuntu? Seems like upstream...
[14:50] <jjohansen> jan_d: can you boot a maverick livecd/usbkey and double check which driver is being used
[14:50] <jan_d> ic
[14:50] <jan_d> you thing I should maybe try 8168 instead?
[14:50] <jjohansen> jan_d: not atm, I haven't followed through on the bugs to closely yet, but I plan to, as I am experiencing them
[14:51] <jjohansen> jan_d: hrmm maybe, and yes you should file a bug
[14:51] <jan_d> ok, will do when I get home tonight. Thank you for now.
[14:53] <fairuz> hey jjohansen: 
[14:53] <jjohansen> hi fairuz
[14:53] <fairuz> jjohansen: doing good?
[14:56] <jjohansen> fairuz: heh, lets just say its been an interesting week.
[14:56] <fairuz> jjohansen: good to hear that
[15:15] <ogasawara> cooloney: bug 608312, looks like you had some patches to fix this, did they ever get pushed upstream?
[15:17] <cooloney> ogasawara: oh, yeah, i posted that patch to upstream
[15:17] <ogasawara> cooloney: did it get picked up?
[15:18] <cooloney> ogasawara: i don't think so, not much review about that
[15:18] <ogasawara> cooloney: so I assume we would need it for Natty?
[15:20] <ogasawara> cooloney: if so, I'll leave it in your hands to get it tested and submitted to the kernel-team mailing list.
=== skaet_afk is now known as skaet
[15:23] <cooloney> ogasawara: yeah, i will take care of that. 
[15:23] <ogasawara> cooloney: awesome, thanks.
=== nik0 is now known as niko
[16:42] <tgardner> bjf, do you know if there a repo for the tests that Q/Q is running?
[16:42] <tgardner> Q/A*
[16:43] <bjf> tgardner, depends on which tests you are talking about, i know there is for the security tests, for the others I don't know 
[16:43] <bjf> tgardner, i'm talking to them right now, you want me to ask?
[16:43] <tgardner> bjf, I guess the security tests will do for now
[16:43] <bjf> tgardner, one sec
[16:43] <tgardner> bjf, no rush
[16:48] <bjf> tgardner, not sure if that's all the regression tests, but i think the security is in there       bzr branch lp:qa-regression-testing
[16:48] <tgardner> bjf, tahnks
[16:48]  * tgardner has fat fingers this morning. must be all the snow....
[16:49] <bjf> sconklin, ^ in case you needed that as well
[16:49] <sconklin> bjf: thanks
=== herton is now known as herton_lunch
[17:32] <tgardner> launchpad timeouts suck
=== herton_lunch is now known as herton
[18:03] <kees> bjf: uhm, what the heck is going on? why did QA test 2.6.35-22.33 instead of 2.6.35-28.50 ?
[18:03] <bjf> looking
=== sforshee is now known as sforshee-lunch
[18:06] <bjf> kees, nice catch, i missed that, i just asked, they tested the right kernel, https://wiki.ubuntu.com/QATeam/KernelSRU-maverick-2.6.35-28.50
[18:38] <kees> bjf: well, I think it's still a kvm bug
[18:40] <bjf> kees, you were not able to reproduce it, right ?
[18:40] <kees> bjf: correct. also, in those new results, there are no aslr failures. they tested the wrong kernel before, afaict.
[18:42] <kees> hggdh: https://wiki.ubuntu.com/QATeam/KernelSRU-maverick-2.6.35-28.50 shows no aslr failures.
[18:42] <hggdh> kees: no, it does not. I tried multiple times, last one succeeded
[18:43] <bjf> kees, i might buy that there is a kvm bug lurking in there, but looking at the commits that went into that release, it's difficult to see that it was caused by one of them
[18:44] <bjf> kees, unless it was your commit :-)
[18:44] <kees> bjf: I mean a kvm _host_ bug -- i.e. not the kernel.
[18:45] <kees> bjf: we've seen evidence of all kinds of weird rare memory corruption when running under kvm.
[18:46] <kees> bjf: it just happens that the aslr collision test is at about the same level of brutality to uncover such host bugs
[18:48] <kees> bjf: here's an example of such a kvm host bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/694029
[18:49] <bjf> kees, yes, sounds like something someone should look into
[18:50] <kees> hggdh: how could that have been a typo, the kernel that was tested actually reported itself as -22.
[18:51]  * tgardner --> lunch
[18:51] <kees> hggdh: http://reports.qa.ubuntu.com/reports/kernel-sru/home/ubuntu/sru-kernel-test/maverick-2.6.35-22.33-server/kvm-amd64/qrt-kernel-aslr.txt
[18:52] <hggdh> kees: a typo running the test, no upgrades were installed
[18:52] <kees> bjf: anyway, I don't see any of these issues as needing to hold back the 2.6.35-28.50 kernel
[18:52] <kees> hggdh: oooooh, okay
[18:52] <kees> hggdh: well, in that regard, the test worked. :) -22 had that flaw. :)
[18:52] <hggdh> kees: heh. At least something worked :-)
[18:53] <kees> :)
=== sforshee-lunch is now known as sforshee
[19:00] <hggdh> BTW, updated kernel SRU tests tarball created & published
[19:23]  * bjf -> lunch
=== bjf is now known as bjf[afk]
[19:48] <vanhoof> herton: heya
[19:48] <vanhoof> herton: you still around
[19:48] <herton> vanhoof: hi, yes
[19:49] <vanhoof> herton: quick q on a bug you chimed in on
[19:49] <vanhoof> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/720949
[19:49] <vanhoof> herton: just noticed this: https://bugzilla.kernel.org/show_bug.cgi?id=27402#c7
[19:50] <vanhoof> herton: wondering if we should do the same in natty
[19:51] <herton> vanhoof: I think is a sensible thing to do, as ath3k doesn't seems to handle it ok, and by reports should be working with btusb before
[19:51] <vanhoof> herton: its awesome it made its way through -stable :D
[19:52] <vanhoof> ogasawara: sounds like you're already putting together the final natty upload?
[19:53] <ogasawara> vanhoof: I am, fixing up some build failures and then will get it packaged
[19:54] <ogasawara> vanhoof: is there a last minute patch we need?
[19:54] <vanhoof> its not end of the world, but does impact a number of machines destined for 11.04 cert
[19:54] <vanhoof> I think it could be SRU'd
[19:55] <slangasek> ogasawara: could you pull in the patch from bug #750585 as part of this upload?  Just got FFe approved today
[19:55] <vanhoof> I just got a list of natty cert failures, oh about 3 hours ago ;)
[19:55] <slangasek> it would be a big help for multiarch to have that in the archive
[19:56] <ogasawara> vanhoof: if you can get a patch to the list in the next hour or so, I can probably squeeze it in.  otherwise we'll target for SRU.
[19:58] <ogasawara> slangasek: care to send it to the kernel-team@lists.ubuntu.com just so we can get proper Ack's on it?  I'll be sure to pull it in before I upload.
[19:59] <slangasek> ogasawara: hmm, strange process.. ok :)
[20:01] <vanhoof> herton: do you know where gustavo might have submitted the revert? ... I'm not seeing it in linux-next
[20:02] <herton> hmm no idea, let me check here
[20:03] <herton> vanhoof: found it, it is on his tree at git://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth-2.6.git
[20:03] <herton> http://git.kernel.org/?p=linux/kernel/git/padovan/bluetooth-2.6.git;a=patch;h=8390679da56a903b916a5d86423fcc872814d99a
[20:05] <vanhoof> herton: think its reasonable to pull in for natty since it breaks things?
[20:06] <ogasawara> tgardner: I'm gonna disable rts_pstor staging driver on armel and powerpc, it's throwing me multiple build errors
[20:08] <herton> vanhoof: yes, it's a small change for only these devices, and regression
[20:10] <vanhoof> herton: mind sending it to k-t?  If you're tied up I can torture manjo :)
[20:11] <herton> np, I can send
[20:12] <vanhoof> herton: awesome, thank you
[20:13]  * vanhoof loves the final day fire drill :)
[20:15] <tgardner> ogasawara, ack
[20:19] <tgardner> ogasawara, I'm handling the multi-arch patch
[20:19] <ogasawara> tgardner: ack
[20:19] <ogasawara> tgardner: I just pushed the rts_pstor config change to master-next
[20:22] <tgardner> ogasawara, ok, pushed the multi-arch patch. I'll get a test build going on my emerald, but it looks pretty simple.
[20:22] <ogasawara> tgardner: ack
[20:23] <vanhoof> ogasawara: herton sent it along to k-t
[20:23] <vanhoof> herton: i appreciate it :)
[20:24]  * vanhoof makes mental beer note
[20:24] <ogasawara> vanhoof: thanks, will review it
[20:25] <tgardner> herton, is this from upstream, or from a maintainers repo?
[20:25] <herton> tgardner: from one of bluetooth maintainers tree
[20:25] <herton>  git://git.kernel.org/pub/scm/linux/kernel/git/padovan/bluetooth-2.6.git
=== bjf[afk] is now known as bjf
[20:27] <herton> I forgot to add that in the patch I sent to kernel-team ML
[20:27] <tgardner> herton, vanhoof: so this patch effectively drops support for that part, right?
[20:27] <vanhoof> tgardner: it drops support for that part, and fixes others as a result
[20:27] <tgardner> vanhoof, so you'd consider it a regression fix?
[20:28] <vanhoof> tgardner: from my point of view definately
[20:28] <vanhoof> tgardner: we have machines needing 11.04 cert that are broken because of this
[20:28] <tgardner> vanhoof, alright.
[20:28] <vanhoof> and ive not seen any actual real work come through wanting that part
[20:28] <vanhoof> tgardner: if its sketchy to you, we can wait for SRU
[20:28] <vanhoof> but it seemed like a quick win to me
[20:29] <vanhoof> tgardner: i got a laundry list of bugs mid-day today against 11.04 cert :\
[20:29] <tgardner> vanhoof, right on time :)
[20:29] <vanhoof> tgardner: yeah seriously :)
[20:31] <tgardner> herton, do you think we'll need this oneiric, or will upstream solve the issue?
[20:31] <herton> tgardner: I expect this to be pulled in for 2.6.39, so will end up automatically on oneiric I think
[20:32] <tgardner> herton, ok, then I won't pick the patch for oneiric
[20:32] <tgardner> vanhoof, applied and pushed
[20:32] <vanhoof> tgardner: herton: thanks guys!
[20:33] <vanhoof> i hear the beer is cheap in budapest :)
[20:33] <tgardner> vanhoof, $1.80 per pint as near as I can tell
[20:33]  * ogasawara pulls and kicks off new test builds
[20:33] <vanhoof> tgardner: i think i'm up to at least a 100 bucks w/ you then ;)
[20:34] <tgardner> vanhoof, of course the kernel team drinks for free with all the favours we've racked up.
[20:34] <vanhoof> tgardner: i wonder if there is miller lite in budapest ;)
[20:34] <tgardner> blech!
[20:46] <elmo> tgardner: so, FWIW, LP are really working hard to eliminate the timeouts, you might want to ping lifeless next week, if you can tell him which pages are timing out, I suspect he'll fix them for you
[20:46] <tgardner> elmo, its seemed transient
[20:47] <tgardner> e.g., it happened on several pages within a few minute period, then all started working again.
[20:47] <bjf> elmo, lots of timeouts for a number of us today
[20:48] <bjf> elmo, not specific to individual pages, also on qastaging 
[20:48] <elmo> did you guys happen to get OOPS numbers or remember any of the pages?
[20:48] <elmo> (the particular pages + a rough time would probably allow them to find the OOPSes)
[20:49] <tgardner> can't remember for sure, but I think it was the generic 'try again later'
[20:49] <elmo> huh, ok
[20:50] <tgardner> elmo, it was especially annoying because LP has been so well behaved lately. whatever you're doing seems to be the right thing despite this momentary outage.
[20:51] <elmo> tgardner: oh, it's not me, all credit to lifeless and the LP team - but good to hear
[20:58] <bjf> tgardner, https://bugs.launchpad.net/launchpad/+bugs?field.tag=timeout
[20:59] <tgardner> bjf, whoa, lotta critical bugs there
[21:00] <bjf> tgardner, looks like they are taking timeouts seriously 
[21:31] <bryceh_> tgardner, yeah LP team policy is that all timeout bugs are handled as criticals
[21:32] <bryceh_> tgardner, I find pretty much whenever I get one of those "try again later" pages, I copy the OOPS id into a bug report and send it in, and they take care of the rest
[21:33] <bryceh_> tgardner, part of the grand scheme as I gather is that they're slowly ratcheting down the timeout duration in order to improve performance
[21:40] <tgardner> bryceh_, I guess they are making progress. its the first timeout in awhile.
[21:40] <kristian-aalborg> evening
[21:41] <bryceh_> tgardner, yeah things are a lot better
[21:41] <tgardner> ogasawara, EOD, I'm off to trudge through the snow. 
[21:41] <ogasawara> tgardner: cool.  I'm about to bounce for a bit too, the suns actually out today.
[21:41] <kristian-aalborg> I just ran strace and mpc update (because the latter halts"... I got "erestartnohand" (in caps), which seems to be a kernel error?!
[21:42] <ogasawara> tgardner: not much else to do for the kernel.  just waiting for some builds to finish, then will upload over the weekend sometime.
[21:42] <tgardner> ogasawara, we've about 5 inches since this morning. gonna make getting to the brewery a long walk
[21:42] <tgardner> ogasawara, k, I'll keep watch as well.
[21:42] <bryceh_> ogasawara, how's the little one?  Is he giving you better sleep finally?
[21:43] <ogasawara> bryceh_: he's doing great!  well, not so great on the sleeping part though :)
[21:43] <bryceh_> :-)
[21:43] <ogasawara> bryceh_: still wakes up about every 2hrs
[21:44] <bryceh_> yeah, something I'm not looking forward to for #2...
[22:03] <hallyn> smb`: hi, re bug 747090,
[22:03] <hallyn> smb`: wondering if i should be going to the kvm mailing list, or if you'd like to do it (or someone else from your team)
[22:08] <hallyn> nm, mailing :)
=== hallyn is now known as hallyn_afk
=== sconklin is now known as sconklin-gone