=== amitk is now known as amitk-afk
=== JanC_ is now known as JanC
[05:24] <MTecknology> jjohansen: Hey- you weren't around when I wanted to give you a big gargantuan hug. Thanks for the help. :)
[05:55] <jjohansen> MTecknology: glad to here it worked for you
=== amitk-afk is now known as amitk
[08:25] <smb> morning
[08:36] <abogani> smb: Good morning to you.
[09:45] <eugenesan> Hi all, I am experiencing frequent OOM kills with -25 from proposed. I am I alone?
[09:47] <jjohansen> eugenesan: hrmm, I haven't heard any complaints of OOM kills, do you have a bug with some logs attached?
[09:48] <jk-> hey cking 
[09:48] <smb> I have not seen any OOM kills either
[09:49] <cking> jk-, hiya
[09:49]  * cking forgot to start irc, doh
[09:49] <eugenesan> jjohansen: Nope, I wanted to consult here first. I am seeing it on 2 different machines, without a reason with plenty free pages...
[09:49] <smb> cking, what a wonderful world this seemed to be ;-)
[09:50] <cking> smb, indeedy
[09:51] <jjohansen> eugenesan: open a bug using ubuntu-bug linux
[09:51] <eugenesan> I need suggestion for correct bug title, to be self explaining for non technical users?
[09:52] <eugenesan> From my expirience OOM causes long hangs and applications termination.
[09:52] <jjohansen> eugenesan: hrmm, I'm not sure the non technical users will understand that the oom killer is what causing their apps to die
[10:11] <eugenesan> Just been hit by OOM with 2.6.32-24-generic-pae... very odd
[10:13] <eugenesan> Please take a look at http://paste.ubuntu.com/497587/
=== amitk is now known as amitk-afk
[11:26] <tseliot> smb: I guess I'll have to update fglrx in Jaunty and Hardy too in addition to Lucid and Karmic
[11:31] <tseliot> :/
[11:42] <Kano> hi, when will 2.6.35.5 mainline ready
[11:45] <Kano> 36rc5 would be good too
[11:58] <apw> Kano, .5 is second in the queue so i'd say now+4hrs, -rc5 is after that say +6hrs
=== amitk-afk is now known as amitk
[11:59] <Kano> ok
[12:19] <tseliot> apw, smb: I guess you'll have to apply the patch to fglrx in the linux-restricted-modules in Hardy (I should do the same with envyng, I guess)
[12:21] <smb> tseliot, Yes thats true. Will see about lrm
[12:21] <tseliot> ok
=== jjohansen is now known as jj-afk
[13:12] <mjg59> Keybuk: No, there's two nvidias, no Intel
[13:15] <Keybuk> mjg59: the spec says it's an Intel GMA HD and an NVIDIA GT330M
[13:21] <mjg59> Keybuk: Which mbp?
[13:22] <Keybuk> 6,2 - the 15" 2.66Ghz i7
[13:25] <mjg59> Oh, of course, it's an arrandale. Ok.
[13:25] <mjg59> Apple seem to have their own magic video muxing device. I'm not clear on how they handle the PCI devices, though.
[13:25] <mjg59> In their nvidia setups both are visible.
[13:26] <Keybuk> yeah only the NV is visible in lspci
[15:51] <hallyn> jj-afk: at k by chance?
=== bjf[afk] is now known as bjf
[16:20] <ogasawara> smb: from the ml thread, it seems everyone is fine to drop support for fsl-imx51 in karmic.  so I'm just going to delete the work item from the blueprint.
[16:20] <smb> ogasawara, ack. I'll mothball the branch soonish
[16:21]  * smb likes a work-item being completed without doing work
=== ivoks-afk is now known as ivoks
=== jj-afk is now known as jjohansen
=== amitk is now known as amitk-afk
[17:13] <jjohansen> hallyn: pong
[17:14] <hallyn> jjohansen: i was going to ask if you had any hints on how to specify your debug kernel to be used (bc it wasn't being used by default despite being the highest version #) but think i've got it, thanks
[18:45] <bjf> ogasawara: is there a wiki page which explains what the conditions are to change a bug status from "New" to "Triaged"? (or any other state for that matter)
[18:52] <popey> hullo linux kernel people!
[18:53] <ogasawara> bjf: I know there is, I just have to remember now where it is in our black hole of wiki pages
[18:54] <popey> if someone has a moment, could they look at bug 642792 which appears to be a regression, breaking ALT+PrintScreen functionality in GNOME
[18:54] <ubot2> Launchpad bug 642792 in linux (Ubuntu) "ALT+PrtSc not recognised (affects: 3) (heat: 3390)" [Undecided,Confirmed] https://launchpad.net/bugs/642792
[18:54] <bjf> ogasawara: the other thing is we seem to be generating logs of bugs due to various kernel "WARNING" messages
[18:55] <ogasawara> bjf: I think those will go away when they turn off kerneloops after release
[18:55] <ogasawara> bjf: and I believe there's been a lingering work item to fix that up
[18:56] <ogasawara> bjf: https://wiki.ubuntu.com/Kernel/BugTriage/BugStates
[18:57] <bjf> ogasawara: thanks
[20:06] <jjohansen> -> lunch
[20:29]  * ogasawara lunch
[21:42] <MTecknology> pgraner: Ya know... I remember all of a sudden getting a crap ton less email... I didn't even notice I dropped myself from the team. I think I meant to drop from another one I was in..
=== ivoks is now known as ivoks-afk
[22:27] <Keybuk> Sep 21 22:10:45 deathspank kernel: [   16.122012] intel ips 0000:00:1f.6: Warning: CPU TDP doesn't match expected value (found 26, expected 35)
[22:27] <Keybuk> Sep 21 22:10:45 deathspank kernel: [   16.122178] intel ips 0000:00:1f.6: failed to get i915 symbols, graphics turbo disabled
[22:27] <Keybuk> Sep 21 22:10:45 deathspank kernel: [   16.122260] intel ips 0000:00:1f.6: request irq failed, aborting
[22:27] <Keybuk> Sep 21 22:10:45 deathspank kernel: [   16.122338] intel ips: probe of 0000:00:1f.6 failed with error -16
[22:27] <Keybuk> mjg59: ^ of possible relevance, perhaps
[22:28] <mjg59> Keybuk: That's just the ips driver complaining that it can't get at the i915 symbols, presumably because i915 never loaded
[22:29] <mjg59> Because the PCI device isn't there
[22:29] <Keybuk> ah right
[22:29] <Keybuk> IPS being the power stuff?
[22:29] <mjg59> Yeah