[08:46]  * smb yawns
[08:53] <amitk> smb: \o
[08:53] <smb> amitk, Dude!
[08:54] <smb> Still alive? :) I saw you ride the same plane to Orlandi
[08:54] <smb> o
[08:57] <amitk> smb: cool, will see you in frankfurt on sunday then...
[08:58] <smb> Yep
[08:59] <amitk> I guess that will be one of the "ubuntu" flights
[09:00] <smb> Well I think I only saw ogra on the same flight. But searching the wiki is kind of error prone. And it does not show the non-canonicals
[09:00] <smb> At least it reaches cab allowance mass. :)
[09:07] <amitk> heh
[09:13] <apw> amitk, hey
[09:15] <amitk> apw: howdy?
[09:16] <apw> i hear you are linaro power management dude, checking you have the abilty to sort out getting your blueprints accepted
[09:17] <apw> you have a lot sitting on the queue for uds-n, but not yet waved through to the agenda.  i can help if not
[09:18] <apw> amitk, looks like you have 25 blueprints proposed, at the moment
[09:19] <smb> apw, speaking of those, what was the sort of target we wanted the proposed testing one be? We spoke about that but I already forgot
[09:19] <amitk> apw: I'll have to remove all the proposals except the 4 that are correctly named
[09:20] <apw> smb, i think we thoguht it should be a qa one really, maybe we need to look at marjo's ones to see if there already is one to go to or see if he wants to take it on
[09:20] <amitk> apw: or are you talking about all of linaro?
[09:21] <apw> amitk, i am talking about just the ones with your name on ... i assume most are just tracking prints to hold work items and don't need sessions?  i can accept/reject them for uds-N if you can't; if you tell me the four that need sessions i can sort out getting those in and the rest off the agenda
[09:21] <smb> apw, Ok. Want me to sent him an email?
[09:22] <apw> amitk, to get them on your work items list you need to get them series-goal of natty rather than sprint of uds-n ... if that makes sense
[09:23] <apw> amitk, overall i've been asked to help linaro clean up their blueprints so we can see the wood for the trees on the blueprint queue as you all seem to have proposed all of your blueprints rather than just the ones needing sessions
[09:23] <amitk> apw: my 4 blueprints that I care about start with "hardware-linaro-n-meta-"
[09:24] <amitk> apw: everything else doesn't require a session
[09:24] <apw> amitk, excellent ... happy for me to run through them and sort the sessions out then ?
[09:24] <amitk> apw: and for those 4, I want back to back double sessions, one per day
[09:24] <amitk> apw: yes please
[09:25] <apw> amitk, sadly i am not able to target things in linaro projects to natty series-goal, you need a linaro 'driver' for that
[09:25] <amitk> apw: I can do that (only for the 4, right?)
[09:26] <apw> amitk, if you want the blueprint to carry work items which show up on the burn-down stuff then that blueprint needs a series-goal, likely thats all of them ... presume you using blueprints as 'jobs to do' prints
[09:27] <amitk> apw: yes, but we have our own "project" - linaro-pm-wg (https://edge.launchpad.net/linaro-pm-wg) with our own series and milestones
[09:27] <amitk> and natty doesn't show up in that series
[09:27]  * apw realises there really should be a like #ubuntu-uds channel like #ubuntu-release where you can find help with things and discuss things like this
[09:27] <amitk> we also have our own burn-down infrastructure
[09:27] <apw> amitk, ah good point
[09:28]  * apw looks where the are looked for in your burndown
[09:28] <amitk> apw: http://people.canonical.com/~pitti/workitems/linaro-pm-wg/all.html
[09:29] <apw> amitk, oh you may be ok actually it may not be tied to a release
[09:29] <apw> then you'd not need to target them all, and you save loads of effort!
[09:32] <amitk> apw: we've had to shoehorn of lot of stuff to fit into the ubuntu-way for uds though we don't strictly follow the milestones and processes
[09:33] <apw> yeah i bet, the process doesn't fit snugly for us where it was designed for
[09:37] <amitk> apw: so will you reject everything but the 4?
[09:37] <apw> amitk, working on it now
[09:38] <amitk> apw: many thanks and a beer pledge :)
[09:39] <apw> amitk, nice :)
[09:42] <apw> amitk, do you have the names of the four you wanted accepted, i only saw two on the way through
[09:42] <apw> so i can double check they are right
[09:43] <amitk> apw: https://blueprints.edge.launchpad.net/linaro-pm-wg (The first four in there marked essential)
[09:44] <apw> amitk, so you personally only have 1 session (2 hours)
[09:45] <apw> ok all of those first 4 are accepted, i'll see about getting them 2 hours next
[09:47] <amitk> apw: yeah, others have been assigned to those metas. And if you could, please spread around the double slots so that one is in the morning session, one in afternoon, etc. And only 1 session per day. And start the monday session in the afternoon.
[09:48]  * amitk believes a #ubuntu-uds helpdesk is definitely called for...
[09:48] <apw> amitk, heh if they were even on the agenda at all we'd be looking better, looks like the importer is stuck
[09:50] <amitk> bi-annual circle of pain
[09:51] <apw> i know ... so much stuff is other- i think it broke
[10:07] <smb> big badaboom?
[10:11] <amitk> badaboom
[10:12] <smb> So we probably need someone who knows how to negotiate... ;-P
[10:20] <apw> amitk, ok ... currently your 'prints arn't making it into the scheduling system, something todo with a filter ... they are working on it and hope to have it fixed today
[10:22] <amitk> apw: ack, thx
[10:22] <apw> amitk, now who can i talk to about the toolchain linaro prints
[10:22] <amitk> michaelh1 on #linaro
[10:23] <apw> what timezone is he ?
[10:23] <amitk> NZ, I'm asking if he's around
[10:23] <amitk> likely not
[10:40] <apw> amitk, seems late there for him
[10:51] <apw> amitk, i see that michael has actually named a subset of his blueprints foo-linaro-n-*, so i think i can just accept the ones in that form and reject the rest 
[10:57] <apw> amitk, trying to debug this issue with the blueprints, could you move https://blueprints.edge.launchpad.net/linaro-pm-wg/+spec/hardware-linaro-n-meta-pm-tools to 'Drafting' or 'Discussion'
[11:01] <amitk> apw: i remember him mentioning doing the renames
[11:02] <amitk> apw: marked all four as discussion
[12:15] <apw> amitk, does http://summit.ubuntu.com/uds-n/track/hardware/ look like what you intended
[12:18] <amitk> apw: almost - can you interchange cpufreq with multicore? (thursday and monday)
[12:19] <apw> amitk, you bugger ... 
[12:19] <amitk> apw: I hope it doesn't involve hacking assembly code :-p
[12:20] <apw> amitk, nope ... which on monday ... i've got them both off now
[12:20] <apw> and forgotten which was which already ... doh
[12:20] <amitk> apw: lol, so cpufreq on monday and multicore on thursday
[12:22] <apw> amitk, how about that
[12:22] <apw> sadly you have to use the day views to move things at the mo (due to a bug) so three windows are involved
[12:22] <apw> amitk, its a good job we are doing these long ones now, its not easy to get them in
[12:22] <apw> even this early
[12:23] <Ampelbein> hi there! For a lcd-display driver I need the usbhid_modify_dquirk symbol address, but I can't seem to find it in /boot/System.map. Can you point me in the right direction on where to look?
[12:23] <apw> Ampelbein, which release are you trying to find it in
[12:23] <amitk> apw: looks good!
[12:23] <Ampelbein> maverick, 2.6.35-22-generic
[12:24] <apw> Ampelbein, in maverick it is a static function so its not exported at all
[12:25] <apw> amitk, keep your fingers crossed people leave them alone
[12:25] <apw> i don't think i can lock them or anything
[12:25] <apw> Ampelbein, also was static in lucid
[12:26] <Ampelbein> apw, ok, that means kernel patching for me then :-( thanks!
[12:27] <apw> amitk, as it is so hard to get things scheduled i am going to assume that the toolchain ones which are named correctly are the ones he wants in and the others not, and he can correct them if not afterwards
[12:27] <apw> else there will be no slots for them left
[12:29] <apw> smb, have you marked your participation (particularly essential ones) on your blueprints, being the owner or assignee or anything else has no effect on the attendance thing
[12:35] <smb> smb, No; I guess I should do so now
[12:41] <smb> apw, And probably I should stop talking to myself
[12:53] <JFo> lag, morning... reading the e-mails and thread on the subject now :)
[12:54] <JFo> my only concern is that I will be in Cambridge for Plumbers that week
[12:55] <JFo> will you be there too?
[12:58] <apw> JFo, i think he wandered off
[12:58] <JFo> ah
[12:58] <JFo> morning apw 
[12:58] <JFo> :)
[12:58] <apw> morning JFo 
[12:58] <lag> I'm back
[12:59] <JFo> lag, will you be at Linux Plumbers?
[12:59] <lag> Yeah :(
[12:59] <JFo> so yeah, we'll both during that meeting :)
[12:59] <lag> That's gonna suck
[13:00] <JFo> shrug* :)
[13:01] <JFo> so yeah, 4AM to 4:45AM then
[13:01] <JFo> since they are exactly 12 hrs off from this TZ
[13:01] <lag> Ouch
[13:02] <JFo> yours is 3:15 to 4 AM
[13:02] <JFo> if we keep that schedule
[13:03] <JFo> meaning, if we are present for the whole thing, we will have been up all night
[13:03] <JFo> :)
[13:03] <JFo> yay!
[13:06] <lag> Get the coffee on the go
[13:06] <JFo> yup
[13:06] <JFo> and get in bed early that next night :)
[13:07] <JFo> I've responded to his e-mail
[13:07] <JFo> so we shall see
[13:07] <JFo> only thing I see possibly impacting us is if we need to call in to them
[13:07] <JFo> but I am sure we can work around that
[13:08] <lag> Skype
[13:08] <JFo> yep :)
[13:11] <persia> apw, My opinion (which I think I've stated before) is that we ought just have powerpc be in the main kernel, to avoid config issues and scheduling issues.
[13:11] <persia> I understand that this may not happen, for workflow reasons.
[13:12] <persia> I'll continue to want it discussed each UDS until I don't notice differences in kernel function between architectures, but I don't have any strong expectations about conclusions.
[13:13] <apw> persia, right now about the only thing thats not in the main kernel is the meta package, so yes that is on my agenda at the moment
[13:13] <persia> I thought so, from the spec name.  Just figured I'd make sure when you raised that spec in another context.
[13:14] <apw> cool on the same page then
[13:14] <persia> Never doubted it :)
[13:23] <lyhana8> please patch is to be done on fglrx kernel module to compile again on kernels with CVE-2010-3081 fixed
[13:23] <ubot2> lyhana8: The compat_alloc_user_space functions in include/asm/compat.h files in the Linux kernel before 2.6.36-rc4-git2 on 64-bit platforms do not properly allocate the userspace memory required for the 32-bit compatibility layer, which allows local users to gain privileges by leveraging the ability of the compat_mc_getsockopt function (aka the MCAST_MSFILTER getsockopt support) to control a certain length value, related to a "stack pointer
[13:23] <lyhana8> need for ubuntu 10.04
[13:37] <dupondje> could somebody take a look @ https://bugs.launchpad.net/bugs/604122 ?
[13:37] <ubot2> Launchpad bug 604122 in linux (Ubuntu) "mmc0: Got command interrupt 0x00030000 even though no command operation was in progress. (affects: 2) (heat: 14)" [Undecided,Confirmed]
[13:48] <JFo> dupondje, looking
[13:49] <apw> lyhana8, i thought that that was fixed already ... tseliot <--
[13:50] <tseliot> apw, lyhana8: yes, that was done some time ago
[13:51] <apw> tseliot, thought so ... lyhana8 do you have -updates enabled on this system
[13:56] <dupondje> JFo: revert https://lists.ubuntu.com/archives/kernel-team/2010-May/010660.html, and it works again. So something must be broken in the sdhci driver ?
[13:58] <JFo> I was wondering about that. it is affected only by the config change yes?
[13:58] <dupondje> seems so
[13:58] <JFo> odd
[13:59] <JFo> apw, if you get a sec, could you take a look at bug 604122
[13:59] <dupondje> its quite annoying, as it makes SD cards useless on my computer now :s
[13:59] <ubot2> Launchpad bug 604122 in linux (Ubuntu) "mmc0: Got command interrupt 0x00030000 even though no command operation was in progress. (affects: 2) (heat: 14)" [Undecided,Confirmed] https://launchpad.net/bugs/604122
[13:59] <JFo> dupondje, I can imagine
[13:59] <JFo>  or lag ^^
[13:59] <JFo> if one of you are available
[13:59] <dupondje> the weird thing is that it sometimes works, sometimes not ...
[13:59] <JFo> that is odd
[13:59] <JFo> so if you change the config it works all the time?
[14:00] <JFo> just wanting to have it clear in my head :)
[14:00] <lag> I can take a look
[14:01] <smb> JFo, apw dupondje Though what the option does is to activate some code do disable some controller which otherwise inteferes with the generic driver. Does this really work with the option disabled?
[14:01] <dupondje> well I reverted that change, and then it worked without issues. Can try it again (was somewhere in the development stage of maverick) :)
[14:01] <JFo> dupondje, that would be awesome if you don't mind
[14:02] <dupondje> wait :) i'll boot my quadcore ^^
[14:03] <JFo> cool, thanks :)
[14:03] <smb> lyhana8, For that compile failure all the ubuntu packages should be fixed by now.
[14:21] <dupondje> btw, can I build kernel with pbuilder ?
[14:26] <apw> ogra, does https://blueprints.edge.launchpad.net/ubuntu/+spec/hardware-arm-n-omap-edid-autodetection need a UDS session ?
[14:30] <dupondje> building, gtg now, back in a hour :) then building will be done I guess also
[14:31] <lyhana8> smb: since when? cause I tried yeasterday and it wasn't working on Linux Mint 9 = Ubuntu 10.04
[14:32] <smb> lyhana8, tseliot has uploaded packages the week after that security update went out
[14:33] <smb> tseliot, I forgot the dkms package name again display-drivers something?
[14:34] <tseliot> smb: fglrx-installer
[14:34] <lyhana8> what is the package version I should look for?
[14:34] <tseliot> lyhana8: four weeks ago I uploaded 2:8.723.1-0ubuntu5 which contains the fix
[14:35] <smb> tseliot, Is that Lucid?
[14:35] <tseliot> lyhana8: if you don't have it, it's likely that you don't have -updates enabled
[14:35] <tseliot> smb: yep
[14:36] <tseliot> here you can see the source for each version of Ubuntu: https://launchpad.net/ubuntu/+source/fglrx-installer
[14:37] <tseliot> it was bug 642518, BTW
[14:37] <ubot2> Launchpad bug 642518 in linux-restricted-modules-envy-2.6.24 (Ubuntu Karmic) (and 14 other projects) "[MASTER] package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: Kernel fix for CVE-2010-3081 breaks fglrx (affects: 283) (dups: 240) (heat: 2098)" [Undecided,Invalid] https://launchpad.net/bugs/642518
[14:37] <smb> tseliot, That probably confused me because the binary is called differently
[14:37] <tseliot> lyhana8: or maybe you installed a more recent version of the driver and you're not getting the update because of that
[14:38] <tseliot> smb: yes, the binary is just fglrx
[14:38] <smb> tseliot, Which is what lyhana8 has to look for in dpkg -l :)
[14:38] <lyhana8> I got the right version 2:8.723.1-0ubuntu5
[14:39] <lyhana8> smb: I got:  fglrx-modaliases                      2:8.771-0ubuntu1
[14:40] <tseliot> lyhana8: 8.771? I'm wondering where you took that from
[14:41] <lyhana8> the binary package probably. I tried to compile from their .bin
[14:41] <lyhana8> s/.bin/.run/
[14:43] <tseliot> lyhana8: try with "sudo apt-get --purge remove fglrx" and then "sudo apt-get install fglrx" and let me know if there are any errors
[14:43] <tseliot> lyhana8: if there are errors, I'd like to see them
[14:46] <apw> slangasek, you have a number of other-linaro-* blueprints, just confirming that they all need sessions ?
[15:03] <lyhana8> tseliot: my problem was that install the fglrx driver trigger this error: http://pastebin.com/3QbWsruq
[15:05] <tseliot> lyhana8: it's not the same problem then. The security update prevented the fglrx module from compiling.
[15:09] <lyhana8> tseliot: those log are from yesterday, I didn't get any error installing fglrx fglrx-amdcccle
[15:09] <lyhana8> (just minutes ago)
[15:10] <tseliot> lyhana8: that confirms my theory. It must be something else
[15:13] <lyhana8> tseliot: well it may be that the fglrx package in the repo isn't the good version
[15:13] <tseliot> lyhana8: no, it can't be that. It's a completely different problem
[15:13] <tseliot> lyhana8: please file a new bug report about it
[15:14] <lyhana8> my card is a Mobility radeon HD 5470, which is supported by ati driver 10.9
[16:05] <slangasek> apw: the ones that are targeted to uds-n should be the ones that need sessions, yes
[16:06] <apw> slangasek, cool, most of your fellow creators have made all of their blueprints targeted to uds-n
[16:06] <apw> (probabally due to the create link they used)
[16:07] <slangasek> more likely due to it being their first time through the process and not having thought through whether each blueprint needs a session
[16:08] <slangasek> strangely, I don't see any way to *un*target a blueprint to a sprint
[16:12] <JFo> ok, stepping away for a bit. I'll be back around in a bit.
[16:25] <avinashhm> hi, is there any way to remove windows line ending from patch .. [^M] .. i tried fromdos and :s/^M//g .. .but after this, my patch isn't applying .. any help ...
[16:28] <smb> avinashhm, to do s/<ctrl-v><ctrl-m>$//g should work. But maybe there is more broken than line ending? Like linebreak added by mailer
[16:34] <avinashhm> smb, but number of lines still are same .. but some how something is getting disturbed .. not sure ..
[16:36] <bjf> avinashhm, meld is a good tool to look at the differences between two files, it might help
[16:36] <smb> avinashhm, Would you be 100% it was ok with the ^Ms. It could have been broken when sending, before you received it
[16:37] <avinashhm> bjf, ... hmmm.. let me try it now ... 
[16:38] <avinashhm> smb, .. possible ... :-) ...
[16:55] <cking_> dos2unix works well in munging windows line endings to UNIX convention
[17:17] <avinashhm> cking_, yep ...  i suppose now a days its known as fromdos .. .[ package of tofrodos ] ...
[18:17] <dupondje> I tried to build kernel with pbuilder, but now I get: EE: Previous or current ABI file missing!
[18:17] <dupondje> any ideas guys ? :)
[18:19] <kamal> dupondje: ah, the dreaded (but very very common) ABI check failure ... this will help:
[18:19] <kamal> https://wiki.ubuntu.com/KernelTeam/KernelMaintenance
[18:19] <kamal> or
[18:19] <kamal> https://wiki.ubuntu.com/KernelTeam/KernelForIdiots
[18:19] <kamal> find "ABI" on those pages to read about how and why you need to disable the ABI check.
[18:22] <kamal> dupondje: specifically for pbuilder builds, the "skipabi=true" method won't work for you ... you'll need to touch the 'ignore' files as directed in https://wiki.ubuntu.com/KernelTeam/KernelMaintenance section "Overriding ABI check failures" item #2.
[18:55] <manjo> JFo, !!! you on mumble?
[19:36] <JFo> manjo, nope, do I need to be?.
[20:01]  * ogasawara lunch
[20:12] <cking_> time to call exit(EXIT_SUCCESS) on another day
[20:59]  * jjohansen -> lunch
[22:47] <Edgan> Anyone knowledgeable about realtime kernels in the channel?