[07:39] <ppisati> moin
[07:40] <smb> wiki
=== amitk is now known as amitk-afk
[08:17]  * apw yawns
[08:25] <czajkowski> apw: morning to you too
[08:26] <apw> he
[08:26] <apw> heh
[08:50] <ppisati> brb
[10:14]  * ppisati -> out for an early lunch
=== amitk is now known as amitk-afk
[12:39]  * henrix starts to think it was a bad idea to try to bring the efi patches into 3.5.y
[12:47] <rtg> apw, ogasawara: just pushed Ubuntu-3.8.0-19.29 w/v3.8.7 and v3.8.8. gonna build and smoke test for a few hours on various bits of kit before uploading.
[12:47] <ogasawara> rtg: ack
[12:47] <ogasawara> rtg: lemme know when you have a test build and I can throw it at some of the kit I have here too
[12:48] <rtg> ogasawara, will do. that reminds me, I should update some chroots since we have a new binutils.
=== amitk-afk is now known as amitk
[13:13] <ppisati> rtg: i just sent a fix for R/master-next, and then i've another one coming today
[13:13] <rtg> ppisati, ok
[13:15]  * rtg reboots for kernel update
[13:34]  * cking can't ack patches quick enough today
[13:43]  * henrix -> back in 15
=== hggdh_ is now known as hggdh
[14:43] <ogasawara> ahh the joys of a 2yr old crashing a meeting
[14:43]  * ogasawara back in 20
[14:45] <rtg> ogasawara, I guess you were done, huh? whether you wanted to be or not.
[14:54] <ppisati> rtg: last fix sent to the ml, with this applied, i'm done with R.
[14:54] <rtg> ppisati, ack. good timing.
[14:54] <ppisati> :)
=== kentb is now known as kentb-afk
[15:19] <rtg> bjf, do you remember if we have some wiki info on kernel versioning ?
[15:20]  * rtg is too busy listening to Rush to be bothered to look for himself.
[15:21] <bjf> rtg, not that i know but it would be a good thing
[15:22] <rtg> bjf, seems like we have to explain our versioning scheme every so often
[15:23] <robher> rtg, ppisati: I've got a fix for the highbank reset issue. I'll be sending it out to lakml soon as I can write a decent commit msg. It's heavily tested to work 3 out of 3 times.
[15:24] <rtg> robher, I thought that was the PL310_ERRATA_769419 thingy ?
[15:24] <ppisati> rtg: that was a workaround
[15:24] <ppisati> rtg: in case the fix didn't make for the release
[15:24] <rtg> ppisati, well, I think we'll stick with the workaround until after release, OK ?
[15:24] <ppisati> rtg: i'm good with it
[15:25] <rtg> robher, you too ?
[15:25] <robher> rtg: That's not the real problem. It just makes the issue 100% reproducible. It is still possible to hit it on reset or cpu hotplug.
[15:27] <rtg> *sigh* - we're getting kind of close to the wire
[15:27] <robher> Errata 769419 is the fix for that USB performance issue on Panda that Canonical spent a long time root causing.
[15:28] <rtg> thats why it looked familiar
[15:34] <bjf> rtg, i'm working on that version wiki "problem"
[15:35] <rtg> huh :) imagine that.
[15:38] <bjf> rtg, read https://wiki.ubuntu.com/Kernel/FAQ#Kernel.2BAC8-FAQ.2BAC8-GeneralVersionMeaning.What_does_a_specific_Ubuntu_kernel_version_number_mean.3F and the following 3 sections
[15:38] <bjf> rtg, i don't think this matches your email though i believe your email is correct
[15:40] <rtg> bjf, perhaps we could add some of that email to the section 'What differentiates the Ubuntu Kernel from the upstream Linux Kernel?'
[15:42] <bjf> rtg, i don't think the other sections are exactly correct either since 3.0 but i can start with your suggestion
[15:43]  * cking --> back later, car stuff to do
=== kentb-afk is now known as kentb
[15:53] <rtg> robher, can I set CONFIG_PL310_ERRATA_769419=y after applying your patch 'ARM: highbank: fix cache flush ordering for cpu hotplug' ?
[15:53] <ppisati> robher: ok, saw the patch
[16:00] <rtg> ppisati, you gonna test a kernel with this patch and PL310_ERRATA_769419=y ?
[16:03] <bjf> rtg, i didn't change much from your email ... https://wiki.ubuntu.com/Kernel/FAQ/GeneralUbuntuDelta
[16:04] <rtg> bjf, looks good. thanks.
[16:15] <ppisati> rtg: ok, patch sent as a followup
[16:16] <rtg> ppisati, I repushed master-next. have a look to make sure I have it correct
[16:17] <ppisati> rtg: yes it is
[16:29] <wolfgang8741> I was asked to test an upstream version for 3.9-rc7, but no amd64 build is listed in the directory.  Are the mainline kernel building of 3.9-rc7 complete (http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc7-raring/)? I saw the release announcement saying the building is complete (https://lists.ubuntu.com/archives/kernel-team/2013-April/027614.html), but not all architectures display on the site.
[16:31] <rtg> apw, ^^
[16:46] <bjf> psivaa, all kernels are through verification. i know you folks are going to be pretty busy next week so if you wanted to get a jump on them you can
[16:46] <psivaa> bjf: ok, thanks for the info. one of our servers is down. will get going once that comes up
[17:11]  * ppisati -> out for the usual routine
[17:11] <ppisati> back later
[17:27]  * rtg -> lunch
[17:49] <apw> wolfgang8741, if there are no binaries for an arch it likely did not complete
[17:53] <apw> kamal, it is all your fault :)
[17:53] <apw> rtg, it is the new module dependancies checker
[17:54] <rtg> apw, which is why mainline isn't building ?
[17:54] <apw> it is aborting the amd64 build
[17:54] <apw> rtg yes
[17:54] <rtg> apw, why are you building an extras package ?
[17:54] <apw> WARNING: /home/apw/COD/linux/debian/linux-image-3.9.0-030900rc7-generic/lib/modules/3.9.0-030900rc7-generic/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko needs unknown symbol ptp_clock_index
[17:54] <apw> WARNING: /home/apw/COD/linux/debian/linux-image-3.9.0-030900rc7-generic/lib/modules/3.9.0-030900rc7-generic/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko needs unknown symbol ptp_clock_register
[17:54] <apw> WARNING: /home/apw/COD/linux/debian/linux-image-3.9.0-030900rc7-generic/lib/modules/3.9.0-030900rc7-generic/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko needs unknown symbol ptp_clock_unregister
[17:54] <apw> EE: Unresolved module dependencies in base package!
[17:54] <apw> make: *** [install-generic] Error 1
[17:55] <apw> rtg, it builds wahtever the primary would build, which is split in that release
[17:55] <kamal> apw: my fault?  what'd I do!?
[17:55] <rtg> apw, the LTS kernels only build one package. maybe mainline should do the same ?
[17:57] <apw> i suspect i need to find this new check and wack it in mainline builds
[17:57] <apw> rtg, yeah i think i can just wack do_extras_package=false
[17:57] <apw> and be happy
[17:58] <apw> kamal, wasn't this your doing:
[17:58] <apw> EE: Unresolved module dependencies in base package!
[17:58] <rtg> apw, I think that was an smb patch, not kamal.
[17:58] <kamal> apw: I don't think so -- I'm not the droid you're looking for
[17:58] <apw> kamal, :)
[17:58] <kamal> apw: but hey, thanks for thinking of me, man!  ;-)
[18:02] <apw> kamal, i always do ... always do
[18:04] <wolfgang8741> apw, thanks knew something might have broke
[19:00] <rtg> ogasawara, uploaded raring. I'm outta here to recycle some HW.
[19:01] <ogasawara> rtg: ack, thanks
[19:01]  * rtg -> EOD
[20:02] <smallfoot-> Linux 3.8.8 released today
=== mathor is now known as crhrabal
[20:18] <jsalisbury> bjf: File "/usr/lib/pymodules/python2.6/launchpadlib/launchpad.py", line 28,
[20:18] <jsalisbury> in <module>
[20:18] <jsalisbury> from lazr.uri import URI
[20:18] <jsalisbury> ImportError: No module named uri
[20:19] <bjf> jsalisbury, http://pastebin.ubuntu.com/5716959/
=== hggdh_ is now known as hggdh
=== kentb is now known as kentb-out