[01:16] <slangasek> infinity: so, I see that linux-ti-omap4 is in the list of rebuild failures for raring... related to the eglibc 2.17 -Wunused-result strictness.  Even if raring's -omap4 is just a copy, maybe we want to make it buildable?
[01:17] <infinity> slangasek: http://pad.lv/1163443
[01:17] <ubot2`> Launchpad bug 1163443 in linux-ti-omap4 "linux-ti-omap4 ftbfs in raring" [High,Won't fix]
[01:17] <slangasek> heh
[01:17] <infinity> slangasek: If we want to fix the quantal package to also be buildable in raring, that's fine, I suppose, but it's just creating work for people if we fork the packaging.
[01:18] <slangasek> right, I'm not suggesting we fix it via raring
[01:18] <infinity> Of course, the easy fix is to disable tools, which would be a regression in Q.
[01:18] <infinity> We could fix it properly, but I'm not sure I actually care deeply.  Do you?
[01:19] <slangasek> if I cared about it deeply I would fix it myself instead of trying to trick you into fixing it
[01:19] <infinity> *smirk*
[01:20] <infinity> I would rather someone had just given me the goahead to drop the ti-omap4/desktop images, thus allowing me to drop pvr-omap4 and the ti-omap4 kernel.
[01:20] <infinity> (And we could do server/d-i with -generic)
[01:21] <infinity> But I suppose it was a valid point that we don't (currently) have any other ARM desktop for people to play with.
[01:21] <infinity> Would have been nice to make that Chromebook, perhaps.
[01:21] <slangasek> s/nice/expensive/ given that we already have the pandae
[01:28] <infinity> slangasek: True.  We'll need to pick a new proof-of-concept desktop platform at SOME point, though.
[01:29] <infinity> Well, or, I suppose the unity-next convergence story might make it all moot, and the PoC can just be a few phone devices that we bless.
[01:30] <slangasek> yes; I need to follow up with ogasawara and bryce on this, but the tentative plan is precisely that, carry over panda until such time as Ubuntu Touch is on its feet
[01:32] <infinity> slangasek: Well, I didn't just mean Touch, but the converged desktop, so I can plug a phone into a monitor and test desktop applications on it in the same way I can on a Panda.
[01:35] <slangasek> infinity: I'm not sure it's a good use of anyone's time to be testing desktop-only apps on Panda in the 13.10 timeframe; as far as I'm concerned, the purpose in testing the desktop on Panda between now and 13.10 is to make sure our infrastructure code doesn't bitrot between now and Unity Next getting on its feet
[01:36] <infinity> slangasek: Sure, I agree on that score.
[07:03] <ppisati> moin
[07:20] <apw> ppisati, moin
[07:21] <ppisati> apw: ciao
[07:21]  * apw has an engineer on his way to bring him decent interwebs :)
[07:35] <smb> apw, Is it the "cable guy"? :)
[07:35]  * smb hopes the engineers will be in order
[08:13] <apw> smb, it turns out the two guys are really one, its just the ordering system that thinks he is scitsophrenic (sp?)
[08:14]  * smb will need to ask gnarl to explain that
[08:20] <apw> yeah :)
[09:00] <ppisati> brb
[09:18] <brendand> henrix, are -generic and -generic-pae kernels still going to be released for Lucid or just -server kernels?
[09:42] <henrix> brendand: good question :p i believe all the images will still be produced, but i may be wrong
[09:42] <henrix> bjf: ^^
[10:05] <ppisati> cking: http://paste.ubuntu.com/5673156/
[10:05] <ppisati> cking: this was done on a nexus7
[10:05] <ppisati> cking: but the procedure is the same
[10:05] <cking> ppisati, cool, thanks
[10:05] <ppisati> cking: i promise this afternoon i'll write up a decent wiki page about all the steps :P
[10:06] <cking> heh, no stress
[10:10]  * ppisati -> out for lunch
[11:48] <apw> henrix, we normally keep updating all the kernels regardless
[11:49] <henrix> apw: yeah, i believe there'll be no changes for the kernel team with the desktop EOL
[11:49] <henrix> apw: thanks
[11:49] <apw> indeed
[11:50] <henrix> brendand: ^
[12:47] <rtg_> apw, any progress on bug #1157952 ? It would be nice to have a fix before freeze.
[12:47] <ubot2`> Launchpad bug 1157952 in linux (Ubuntu Raring) "SCSI keysense errors on console with Raring (3.8 kernel) within Windows Azure" [High,In progress] https://launchpad.net/bugs/1157952
[12:49] <rtg_> henrix, whats the story on https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1140716/comments/63 - are you reverting that patch from stable ?
[12:49] <ubot2`> Launchpad bug 1140716 in linux "[regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge" [Critical,Confirmed]
[12:50] <henrix> rtg_: i'll need to review all the comments. i started following that bug but haven't been looking for a while
[12:51] <henrix> rtg_: i'll take a look in a bit and eventually revert it. and ask upstream to revert it as well if necessary
[12:51] <henrix> rtg_: thanks
[12:51] <rtg_> henrix, can you chase it to ground soon? its bugging a lot of folks.
[12:51] <rtg_> ack
[13:06] <ppisati> ok, so here is a first crude transcipt on how to get, compile and flash a kernel for the nexus4/7
[13:06] <ppisati> https://wiki.ubuntu.com/Kernel/Dev/AndroidKernel
[13:06] <ppisati> i tested only the nexus7 side, cking is testing the nexus4 one :)
[13:07] <cking> :-)
[13:08] <rtg_> cking, an interesting patch on LKML: 'RAPL (Running Average Power Limit) driver'
[13:09]  * cking looks
[13:11] <cking> lots of MSR tweakables
[13:11] <rtg_> cking, I didn't realize SNB has that kind of support
[13:12] <cking> me neither, mind you I don't spend my life reading the Intel handbooks
[13:13] <rtg_> nor I. I go skiing instead :)
[13:13]  * ogra_ is curious if abootimg will just work on the nexus4 
[13:13] <ogra_> it definitely has probs on my sansung galayx S2 here 
[13:13] <cking> ogra_, I tried it with the existing kernel image and it didn't breakit
[13:14] <ogra_> awesome
[13:14] <ogra_> i guess the samsung code does some signing stuff or so then
[13:14] <cking> who knows
[13:14] <ogra_> i could :) if i bothered to look 
[13:29] <rtg_> ppisati, nice wiki doc
[13:30] <ppisati> anyone with wiki formatting style can contribute :)
[13:36] <ogra_> update the kernel
[13:36] <ogra_> aboot -u /dev/block/mmcblk0p2 -k mykernel
[13:36] <ogra_> ppisati, ^^^ do you mean abootimg ?
[13:37] <ppisati> ogra_: right
[13:37] <ppisati> ogra_: fix it! :)
[13:37] <ogra_> done
[13:58] <diwic> jsalisbury, hi! Just a reminder that people are waiting for a test kernel in bug 1136110. I asked upstream too and they would like more bisection.
[13:58] <ubot2`> Launchpad bug 1136110 in linux (Ubuntu) "USB Audio Codec choppy playback" [Medium,Confirmed] https://launchpad.net/bugs/1136110
[13:59] <jsalisbury> diwic, ack.  I'll post the next kernel shortly
[13:59] <diwic> jsalisbury, thanks for helping out! I should learn that bisection stuff some time.
[14:00] <jsalisbury> diwic, np
[14:44]  * ogasawara back in 20
[15:36] <rtg_> jjohansen, why aren't the AA mount and network mediation patches upstream ? 'UBUNTU: SAUCE: AppArmor: basic networking rules' and 'UBUNTU: SAUCE: apparmor: Add the ability to mediate mount'
[16:02] <henrix> rtg_: ok, i've took a closer look at bug #1140716 and looks like i'll be reverting it from 3.5 stable 
[16:02] <ubot2`> Launchpad bug 1140716 in linux (Ubuntu Quantal) "[regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge" [Critical,Confirmed] https://launchpad.net/bugs/1140716
[16:03] <rtg_> henrix, good.
[16:03] <henrix> rtg_: i'll just wait for a while until someone tests brad's kernel (with the patch reverted)
[16:03] <henrix> rtg_: i'll go through the other upstream stable trees and see if they have this commit (i believe 3.2 has it, so debian should have this bug as well)
[16:07] <bjf> henrix, did you see that i added test kernels?
[16:08] <henrix> bjf: yes, i did.  i'll wait for someone to test it
[16:08] <henrix> and revert the commit in for next release
[16:08] <bjf> henrix, i guess i could actually READ what you typed into the channel
[16:08] <bjf> doh!
[16:08] <henrix> bjf: heh
[16:21]  * ppisati wanders away for a bit...
[16:30] <jjohansen> rtg_: because they have had a major rework, along with the rest of apparmor, you will see the beginning of the set going up for 3.10, and hopefully the rest for 3.11
[16:30] <rtg_> jjohansen, ok, then I can note in the patch that they should get replaced for 13.10
[16:34] <jsalisbury> rtg_, infinity It looks like 3.8.0.16.31 is the latest kernel version in the repositories, but the changlog indicates it should be Ubuntu-3.8.0-16.26.  see bug 1163296
[16:34] <ubot2`> Launchpad bug 1163296 in linux (Ubuntu) "Version / Dependency Mismatch" [Medium,Confirmed] https://launchpad.net/bugs/1163296
[16:39] <jjohansen> rtg_, apw: if you are curious I am keeping a raring version of the apparmor dev tree on zinc in my ubuntu-raring.git aa3.0 branch, it needs to be update it for some recent bug fixes that I am testing
[16:40] <rtg_> jjohansen, I assume you're planning to drop those on me soon ? April 11 is freeze.
[16:40] <jjohansen> rtg_: no, we decided we are not going to drop the new version of apparmor in to raring
[16:41] <jjohansen> rtg_: we are shooting for 13.10, and as much upstream as possible
[16:41] <rtg_> jjohansen, oh, I guess I misunderstood
[16:41] <rtg_> ok, works for me
[16:42] <jjohansen> rtg_: the tree pointer is just if you are curious to see what is going to becoming from upstream over the next few months. There really is no need to look at it
[16:42] <rtg_> jsalisbury, that almost looks like a Launchpad issue. 
[16:42] <rtg_> jjohansen, ack
[16:44] <jsalisbury> rtg_, rmadison also reports 3.8.0.16.31 as the latest kernel version.  Not sure if rmadison pulls this infor from launchpad as well
[16:44] <rtg_> jsalisbury, dunno, but I don't think its a kernel issue.
[16:44] <jsalisbury> rtg_, ack
[16:51] <apw> jsalisbury, rtg_, no that is just a person being confused by the difference in version numbers between the meta package and the main package
[16:51] <jsalisbury> kamal, if you have a chance, can you take a look at bug 1163720  I can kick off a bisect but wanted to run it by you, in case its similar to something your already looking at.
[16:51] <ubot2`> Launchpad bug 1163720 in linux (Ubuntu) "Brightness control broken on XPS13 with 3.8.0-16" [Medium,Confirmed] https://launchpad.net/bugs/1163720
[16:52] <apw> jsalisbury, rtg_ 3.8.0.16.31 is the version number of linux-meta
[16:52] <rtg_> apw, ah, didn't look close enough
[16:52] <kamal> jsalisbury: curiously, I was just looking at that exact problem, and was about to file a bug for it
[16:52] <kamal> jsalisbury: no bisect necessary -- I know exactly what's causing it
[16:52] <jsalisbury> kamal, awesome, thanks!
[16:53] <apw> rtg_, jsalisbury, i have commented in the bug.  invalid is correct
[16:53] <Sarvatt> kamal: thats going to be http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-raring.git;a=commit;h=0e7a2fe01333f72c1cec1cd4d5293a62c770fa4f
[16:53] <kamal> Sarvatt: yes, that's correct
[16:54] <kamal> Sarvatt: "write backlight harder" was the bit that made it work for the XPS13 . . .  sigh.
[16:54] <jsalisbury> apw, thanks
[16:55] <rtg_> kamal, apw: be carefull with raring master-next as I'm doing lots of push + whilst annotating SAUCE patches.
[16:56] <kamal> rtg_: this brightness regression has already landed in master (came from upstream)
[16:56] <rtg_> kamal, stable ?
[16:57] <apw> rtg_, ack, with my lack of internet don't expect me to be pushing over you
[16:57] <kamal> it has been cc'd stable too, but it doesn't affect XPS 13 in stable since brightness control doesn't work until raring anyway (without my PPA)
[16:58] <kamal> rtg_: wait, maybe not cc:'d stable -- I thought I saw that, but now I don't
[17:23]  * rtg_ -> lunch
[17:38]  * cking -> food
[18:08] <bjf> sbeattie, anyone besides myself started running security QRT tests on touch image?
[18:08] <sbeattie> bjf: not that I'm aware of.
[18:09] <bjf> sbeattie, ack
[18:11]  * sbeattie expects that being based on the android kernel, there's going to be things missing.
[18:15] <bjf> sbeattie, kernel_panic and kernel_hardening just work. i'm looking at kernel_security to see what it's issues are
[18:15] <sbeattie> kewl
[18:16] <bjf> sbeattie, when i say they just work i mean the run and don't report any errors. i don't know if they are really doing anything :-P
[18:16] <sbeattie> hehe
[18:17] <bjf> sbeattie, anyone on your team have any of these mobile devices?
[18:17] <sbeattie> bjf: yeah
[18:18] <sbeattie> I do and ty hicks for sure, I can't remember if jj has one or not. 
[18:19] <rtg_> kamal, is 'UBUNTU: SAUCE: Input: fix Cypress PS/2 Trackpad in Dell XPS12' gonna make it upstream ? I don't see it in linux-next.
[18:20] <kamal> rtg_: I'll go figure out what happened to that
[18:27] <kamal> rtg_: ok, it did actually land upstream already in 3.9-rc3, but the maintainer renamed the commit (for some reason I cannot fathom):
[18:27] <kamal>    81bb5d3 Input: cypress_ps2 - fix trackpadi found in Dell XPS12
[18:27] <rtg_> kamal, ok, thanks
[18:28] <kamal> rtg_: do you want me to send a revert/replace request for that?
[18:28] <rtg_> kamal, no, I've got it
[18:28] <kamal> rtg_: thanks
[18:28] <rtg_> kamal, the original SAUCE patch will simply disappear
[18:28] <kamal> rtg_: perfect
[20:10]  * rtg_ -> EOD