[10:58] <amitk> apw: are we going to pull in 2.6.33.y updates into the OMAP branch? (I guess this is an smb question)
[10:59] <apw> amitk, that would be the expectation, and why that branch is a huge maintenance burden ... its entiryly separate
[10:59]  * amitk nods
[16:01] <bjf> ##                                                                                           
[16:01] <bjf> ## Kernel team meeting today @ 17:00 UTC                                                     
[16:01] <bjf> ##                                                                                           
[16:20] <ricotz> ogasawara, hello, i am using your ubuntu-m.git branch, i have a short question: are you going to synchronize it with every rc release?
[16:21] <ogasawara> ricotz: yes
[16:21] <ricotz> ogasawara, great, thank you
[16:22] <ogasawara> ricotz: I've got it built and uploaded to my PPA as well if you're interested
[16:23] <ricotz> ogasawara, i have packaged it myself, but a ppa is a lot easier, where can i find it?
[16:24] <ogasawara> ricotz: https://edge.launchpad.net/~leannogasawara/+archive/ppa
[16:26] <ricotz> thanks!
[17:37] <crimsun> bjf: which symptom are you trying to address in #331589?
[17:39] <crimsun> bjf: also, please bump debian/changelog for karmic's alsa-driver cod
[17:40] <bjf> crimsun, will do the bump
[17:41] <bjf> crimsun, i haven't completely groked the bug so i need to identify the issue with lucid, i've not experienced it myself
[17:42] <bjf> crimsun, i was asked 5 minutes ago to take it on and i'm in the middle of an interview :-)
[17:42] <crimsun> bjf: apw and I looked into the config issue a while back (~2 months ago IIRC); you may wish to ping him
[17:43] <bjf> crimsun, he's the one that asked me to take it on :-), I'll talk with him
[17:44] <apw> crimsun, as i remember it all circled back to not being that configuration option but a new bug, something appears to be wrong with the frequency calculation on a small number of codecs rather than a general 'it being enabled'
[17:44] <apw> in the original issue, we had the high pithed beep on all hda's (i think), now we have a 'mains hum' on some systems, my dell 1537 for one
[17:46] <apw> though i have it muted and don't get an issue per-see
[17:48] <crimsun> that freq calc was supposed to be fixed by 369693dc9
[17:48] <crimsun> (which is in ubuntu-lucid.git)
[17:51] <crimsun> apw: what is "mains hum"?
[17:52] <apw> 50hz sounding buzz.  the noise you hear also when touching the headphones plug on the housing when shoving it in
[17:52] <apw> often at max volume in my experience
[17:53] <apw> unmuting my HDA PC Beep seems to imply its still there
[17:53] <apw> i have to switch to VT-1 to trigger it mind here
[17:53] <apw> i hear on some machines it occurs during reboot etc 
[17:53] <apw> though i've not seen that myself
[17:54] <crimsun> oh, that
[17:54] <apw> crimsun, having just tried it, its more harsh than mains hum, all breaky up and raspy
[17:54] <crimsun> so, that's a very different issue from the original bug report
[17:54] <crimsun> bjf: which is why I asked in the response which symptom you're chasing :-)
[17:55] <apw> ahh so we have conflated bug report, so we should split it up and close the fixed bit :)
[17:56] <Sarvatt> apw: does it go away if you disable the mic? 
[17:57] <apw> Sarvatt, disable as in mute?
[17:58] <apw> Sarvatt, and while i think about it, we need to get with bryce and work out what to do about these LID things
[17:58] <Sarvatt> sound preferences - hardware - change to analog stereo instead of duplex, or mute yeah
[17:59] <apw> Sarvatt, in that case ... nope unchanged by switching off input
[18:02] <crimsun> it isn't a feedback loop; this latest symptom is related to the "shutup" code on powering down/rebooting
[18:07] <apw> cking, that patch is now on the kernel-team list
[18:07] <cking> ta
[18:07]  * cking looks
[18:08] <Sarvatt> apw: digging into it now, was taking a break and working on xserver and input stuff after the nonstop flood of dupe intel reports that week you were gone :)
[18:08] <crimsun> jjohansen: that apparmor symptom can be worked around by disabling swap.
[18:09] <crimsun> jjohansen: granted, may not be useful for actually finding the culprit(s)
[18:09] <crimsun> ah, bah, just saw in -meeting
[18:15] <jjohansen> crimsun: no, thanks its really good to here from another source
[18:15] <johanbr> for the latest mainline kernel build of 2.6.34-rc3, linux-headers-2.6.34-020634rc3-generic depends on linux-headers-2.6.34-020634rc3
[18:15] <johanbr> but the latter package seems not to have been built...
[18:19] <apw> johanbr, that sounds incorrect
[18:21] <johanbr> well, generally, linux-headers-*-generic depends on linux-headers-*, right?
[18:22] <johanbr> so the problem seems to be that linux-headers-2.6.34-020634rc3 is missing
[18:28] <crimsun> right, according to the buildlog, dh_builddeb -plinux-headers-2.6.34-020634rc3 isn't called
[18:28] <manjo> kamalm, does that work the similerly  for brighness keys too ? 
[18:29] <manjo> kamalm, I have samsung netbooks which have issues with brightness keys 
[18:29] <kamalm> manjo: no, the brightness keys problem(s) seem to be a different problem altogether -- on my Dell Studio 1558, the brightness keys do seem to make it to ACPI fine but dmesg records that ACPI was "unable to adjust brightness" or something -- not the same "never releases the key" problem (for me at least)
[18:30] <manjo> kamalm, yeah its the same for samsung as well
[18:34] <apw> johanbr, indeed ... missing it is
[18:34] <apw> crimsun, looks like we didn't do the indep pass ... hrmph
[18:35]  * apw needs the bit of the log which is not preserved, so will have to rebuild it
[19:17] <jjohansen> apw: ping question on potential Lucid patch that will partly address Bug #552225, and maybe Bug #549428
[19:17] <ubot3> Malone bug 552225 in apparmor "system bogs down when apparmor is running" [Undecided,New] https://launchpad.net/bugs/552225
[19:17] <ubot3> Malone bug 549428 in apparmor "Triggers permanent high i/o load after upgrade" [Undecided,Incomplete] https://launchpad.net/bugs/549428
[19:18] <jjohansen> basically, its an optimization patch that removes 1 set of cases where revalidation is done
[19:19] <jjohansen> it is not what is going into the upstream side, as that is a much larger series of patches, which is just to risky to drop into Lucid
[19:19] <apw> ok
[19:19] <apw> if it fixes a known issue and you can handle the skew the different patch directions cause ... i am happy
[19:19] <jjohansen> so is a patch that will only address some potential performance problems worth dropping in this late
[19:20] <jjohansen> okay
[19:20] <jjohansen> I'll run through testing it today and drop a patch or two
[20:34] <gzmask> how long it takes to compile linux kernel 2.6?
[20:34] <gzmask> on a quad core mac pro but in VBox?
[20:37] <florianTS> Hi. I am the viafb maintainer in the linux kernel and just found this bugreport. I think I identified it as a bug that was present in 2.6.32 and fixed in 2.6.33. As I am not an Ubuntu user myself and additionally can't reproduce this on the hardware I have I am wondering how to solve this issue.
[20:37] <florianTS> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539020
[20:37] <ubot3> Malone bug 539020 in linux "Lucid Beta 1 installation CD gives blank screen and freezes" [Undecided,New] 
[20:42] <ogasawara> florianTS: I can build the bug reporter a test kernel with the patch(es) you mention backported.
[20:42] <apw> florianTS, hrm tricky
[20:43]  * apw realises ogasawara is taking the words out of his mouth and shuts up :)
[20:44] <ogasawara> florianTS: I'll post a comment to the bug once I've got something built
[20:44] <florianTS> ogasawara: thanks I think this would help very much.
[21:12] <jonmasters> Ubuntu bug 356317 - "MAke click-and-drag work for Macbook(Pro) 5,1+"
[21:12] <ubot3> jonmasters: Error: Could not parse XML returned by Ubuntu: HTTP Error 404: Not Found
[21:12] <jonmasters> did anyone attempt to get that upstream?
[21:14] <bjf> florianTS, sorry if you got bounced around a bit this morning
[21:24] <florianTS> bjf: No problem. At least this could now be a happy end for users, Ubuntu and viafb. That's far more pleasant than frequently querying VIA for some bits of documentation for about one month.