[00:59] <vanhoof> kentb_out: \o/
[06:45] <superm1> hey anyone around that can chat with me a little bit about fixing up lirc in the maverick tree?
[06:47] <superm1> particularly what's there right now is going to oops left and right on 2.6.35, and after chatting with jarod wilson about, probably the best thing to do at this point is to rebase it on the stuff he's submitting for 2.6.36 at http://git.kernel.org/?p=linux/kernel/git/jarod/linux-2.6-lirc.git;a=summary and pull lirc 0.8.7ish userspace into maverick
[06:50] <superm1> so mostly my question is how the best way to handle this is.  for the past few releases, lirc has lived in the ubuntu/ directory by hand injected tarballs.  would it be better to just stick with that model for now, and grab latest from his git and drop them in place with the intention that they get removed for ubuntu-n since they should be available without this hackery?
[06:51] <superm1> or is there still value in trying to merge/cherry pick/rebase commits out of his tree, shuffle them around and keep all that history if the stuff would only be around for one more release
[08:20] <apw> superm1, we've just taken tarballs from you in the past, so i don't think there is any value in doing anything else this time, especially if its coming in mainline in .36
[08:21]  * smb waves to apw
[08:21]  * apw waves
[08:24] <RAOF> apw: I did see that radeon+GRUB2+graphics mode bug, but it looked like you and Colin were on it, so I wandered off to less well-tended bugs.  Also, I don't think *my* radeon system is affected, although I haven't tried particularly hard to prod the beast.
[08:25] <apw> ahhh i think its fallen through the cracks
[08:26] <RAOF> Also, in Prague the radeon systems that seemed to have problems got magically better once we killed vga16fb with fire.
[08:27] <apw> RAOF, well thats good at least, that thing is sooooo old i am amazed it can even start
[08:46] <apw> RAOF, i wonder if you would have any time to cast an eye over that radeon/grub2 thingy, as i am about to vacation
[08:47] <RAOF> I shall see if I can reproduce on my local radeon.
[08:47] <RAOF> I'm in a radeon bugfixing mood.
[08:48] <apw> heh thanks man ...
[08:57] <RAOF> apw: In return, would you kindly pass your wandering eye over bug #586325 and accept the lucid task for me?
[08:57] <ubot2> Launchpad bug 586325 in linux (Ubuntu) (and 1 other project) "[i965q] Fujitsu Siemens Esprimo E: changing resolution results in non working X (affects: 1) (heat: 57)" [Medium,Triaged] https://launchpad.net/bugs/586325
[08:59] <apw> RAOF, ahh your cursor patch finally made it round the houses
[08:59] <apw> nomination accepted, that sounds like a patch we'd consider for lucid, though its not tiny
[09:09] <TeTeT> apw: awesome, our customer will be all excited
[09:15] <apw> heh don't let them get tooo excited
[09:16] <JFo> apw, it seems you were right with your Natty Narwhal naming
[09:16] <apw> JFo, ?
[09:16] <JFo> when we were discussing what the next release would be named in fun
[09:16] <JFo> I think it was you that said something about natty narwhal
[09:17] <apw> heh narwhal i may have got, i doubt i'd have gotten natty
[09:17] <JFo> hmmm
[09:17] <JFo> well, we were close anyway :)
[09:17] <apw> heh ... at last natty is easy to type
[09:33] <JFo> indeed
[09:33] <JFo> for this natty new release
[09:41] <JFo> apw, do you know if we have SRU plans for bug 586325?
[09:41] <ubot2> Launchpad bug 586325 in linux (Ubuntu Lucid) (and 2 other projects) "[i965q] Fujitsu Siemens Esprimo E: changing resolution results in non working X (affects: 1) (heat: 18)" [Undecided,Triaged] https://launchpad.net/bugs/586325
[09:42] <JFo> I didn't see anything in the bug suggesting we were considering it
[09:42] <JFo> but that doesn't mean we are not
[09:55]  * abogani waves all!
[09:55] <abogani> FYI I have updated -lowlatency kernel flavour in the git tree on Zinc if anyone could-would want review it.
[09:55] <abogani> Thanks in advance for all!
[09:55] <JFo> hiya abogani 
[11:18] <lag> JFo: Are you in the UK?
[11:18] <JFo> lag, yep
[11:19] <JFo> in Oxford
[11:20] <lag> JFo: I wondered why you were on the internet at some ungodly hour this morning :)
[11:23] <JFo> heh
[11:23] <JFo> sprinting with the QA folks for a community of practice meeting
[11:23] <JFo> for the week
[11:24] <lag> Isn't that like doing community service at an old folks home or special school? 
[11:25] <JFo> hah
[11:25] <lag> :)
[12:24] <luftikuss> What is "kernel mode setting" generally? https://wiki.ubuntu.com/X/KernelModeSetting: "X/KernelModeSetting: Kernel mode-setting (KMS) shifts responsibility for selecting and setting up the graphics mode from X.org to the kernel." I don't want to know what it does but rather I'd like to know what KMS is. (It occasionally produces error messages on my Ubuntu 10.04.1 computer.)
[12:25] <JFo> luftikuss, it is the changing of the screen resolution of your machine
[12:26] <JFo> it is handled by the kernel now versus X
[12:48] <luftikuss> JFo: Thank you for your information.
[12:49] <JFo> luftikuss, my pleasure :)
[12:54] <luftikuss> JFo: If the X server has crashed: Is there all I can do to analyze the cause to access the crashed computer via ssh and read the /var/log/Xor.0.log? 
[12:55] <luftikuss> s/Xor/Xorg/
[12:55] <JFo> luftikuss, I'm afraid my X knowledge is rather limited.
[12:55] <JFo> this may be a better resource: https://wiki.ubuntu.com/X/Debugging
[12:55] <JFo> have you taken a look there?
[13:21]  * amitk just compiled a 12Mb kernel! \o/
[13:21] <amitk> sed -i -e's/=m/=y/' .config
[13:48] <apw> smb, is master.kernel.org up for you ?
[13:48] <smb> apw, yep seems ok
[13:49] <apw> smb, hrm, seems down for me
[13:49] <smb> apw, I see other people there, too. Must be some weird routing issue
[13:51] <apw> smb, yeah must be ... can get in there via frylock
[13:51] <smb> apw, local credentials busted?
[13:51] <luftikuss> JFo: What is a "paint-by-numbers fashion" in https://wiki.ubuntu.com/X/Debugging?
[13:52] <apw> smb, its a network level connection timed out
[13:52] <smb> apw, Weird indeed. Maybe the gov is upon you ;-P
[13:52] <apw> heh maybe indeed
[13:53] <luftikuss> JFo: ~$ dict paint-by-numbers
[13:53] <luftikuss> No definitions found for "paint-by-numbers"
[13:54] <smb> malen nach Zahlen
[13:54] <apw> luftikuss, to paint by numbers is a phrase meaning 'the easy way' it comes from books with black and white outline pictures with the number of the colour to use to fill each box
[13:54] <luftikuss> smb, apw Thank you for your help.
[13:55] <JFo> luftikuss, apologies, I was away at lunch.
[13:56] <tgardner> JFo, being "out to lunch" has its own connotations.
[13:56] <JFo> tgardner, :)
[13:56] <apw> smb, does that .de translation have the same meaning as in english
[13:56] <JFo> in that case, I am always "out to lunch"
[13:56] <smb> apw, In the literal sense. Its the name for that painting style
[13:57] <apw> but you wouldn't use it to mean 'easy' generally
[13:58] <smb> I don't think commonly. You might probably say it is like paining by numbers
[14:04] <apw> smb, heh ...
[14:04] <apw> confirmed i've triggered some counter-measure ... by logging in successfully ... changed IP address at home and its all fixed
[14:05] <diwic> *paining* by numbers, is that a freudian slip?
[14:05] <smb> apw, You must have been bad.
[14:05] <apw> probabally logged in 100 times today
[14:05] <smb> diwic, Must be. Or incompetence at the keyboard
[14:18] <jdub> hey there
[14:18] <jdub> have you guys been hearing about lucid block layer issues under kvm and xen?
[14:18] <jdub> https://bugs.launchpad.net/bugs/618529
[14:18] <jdub> ^ i filed that earlier
[14:18] <ubot2> Ubuntu bug 618529 in linux (Ubuntu) "kernel call traces from blk-core.c (affects: 1) (heat: 6)" [Undecided,New]
[14:18] <jdub> there's a link to a debian bug
[14:19] <jdub> i'm having regular freezes on my linode vm
[14:19] <jdub> and it looks like there are references to this being fixed around the place
[14:21] <smb> jdub, Depends a bit whether it is real freeze or just slow as hell. If things move on after a while (possibly a long while) it probably is the general problem with writeback
[14:23] <jdub> hmm
[14:23] <jdub> ah, well, i don't mean kernel freeze
[14:23] <jdub> just to be clear
[14:23] <jdub> disk, block or vm or something sure
[14:24] <jdub> i can type 'ps afx' over ssh, for instance, but it never* returns ;-)
[14:24] <jdub> * (may not have tested this to the ultimate conclusion of "never")
[14:24] <smb> Right, so in that case its likely that writeback (block layer)  has some issues. We are working on that
[14:26] <jdub> ah, known probs
[14:26] <jdub> lovely
[14:26] <jdub> particularly on xen/kvm?
[14:27] <smb> Yeah, just not that simple to come by (there is a set of 14 patches or so). No in general on higher io loads its seems and in particular when unmounting
[14:28] <smb> I saw the same kind of messages just yesterday while compiling kernels
[14:56] <jdub> smb: is it a lucid-worthy issue?
[14:58] <smb> jdub, Definitely. There are some tests I want to do which are next on my todo list. And then moving forward. But it should get fixed sooner than later.
[14:58] <jdub> sweet! thanks smb
[14:59] <jdub> in the mean time, i will keep an eye on my poor, suffering linde... and perhaps not post more big videos :-)
[14:59] <cooloney> quit
[15:00] <smb> There might be some test kernel mentioned in bug 585092. Though they might be slightly outdated or rather suited for systems not needing dkms packages (like binary gf drivers)
[15:00] <ubot2> Launchpad bug 585092 in linux (Ubuntu Maverick) (and 2 other projects) "giant IO delays on unmount (affects: 1) (heat: 65)" [Medium,Fix released] https://launchpad.net/bugs/585092
[15:11] <gzerphey> any reason I cant load backports jaunty with the 2.6.32-24-generic kernel?
[15:14] <tgardner> gzerphey, many, many reasons, not the least of which is "it won't work"
[15:16] <gzerphey> kind of what i thought
[15:17] <gzerphey> the reason i ask is that used to be a fix for the wireless disconnect problem with 2.6.x kernels but now im not sure what to do
[15:17] <tgardner> gzerphey, try a Lucid compat-wireless package?
[15:18] <smb> tgardner, In Jaunty?
[15:18] <apw> he has a lucid kernel no ?
[15:18] <gzerphey> yes im in lucid
[15:18] <tgardner> I guess thats why I assumed Lucid
[15:18] <smb> Ah ok. thought I read jaunty
[15:19] <gzerphey> i have tried 32-21 and 32-23 with little success
[15:23] <tgardner> gzerphey, have you tried linux-backports-modules-wireless-lucid-generic ?
[15:24] <gzerphey> yes
[15:24] <gzerphey> that loaded 32-24
[15:24] <gzerphey> also no help
[15:25] <gzerphey> are you guys familiar with the problem i am running into.... the wireless randomly disconnects and I have to disconnect and reconnect to get it operational again.  this seems to happen under load
[15:49] <superm1> apw, okay i'll get a patch together that does it that way then soon, thanks
[15:49] <JFo> bjf, do we still have testing images supposed to be building daily?
[15:49] <JFo> or whenever?
[15:50] <bjf> JFo: that's the theory though i don't check on them every day
[15:50] <JFo> looks like they last built on the 5th
[15:50] <bjf> JFo: i accept patches
[15:51] <JFo> bjf :)
[15:51] <JFo> not sure what is broken, but I'll have a look later. just wanted to make sure we actually expected them to be building regularly
[15:52] <bjf> JFo: i've added it to my stack for today
[15:55] <JFo> k, or if you like I can look at it next week
[15:56] <JFo> I do need to get my knowledge together on the testing images anyway
[15:56] <bjf> JFo: whoever gets to it first
[15:56] <JFo> k :)
[17:25]  * smb -> out
[17:47] <apw> ogasawara, ok i've started the sync for the ports meta into our tree
[17:47] <apw> generally we try and keep a vagly recent copy of that in our ports branch, so that it doesn't get lost
[17:47] <apw> obviously he is maintaining that currently
[17:48] <ogasawara> apw: sweet, thanks
[18:08] <bjf> JFo: i think i fixed the daily iso image building
[18:09] <bjf> JFo: am testing now
[18:09] <JFo> sweet!
[18:15] <bjf> JFo: but is anyone using them?
[18:20] <JFo> bjf, I am planning on testing them, but I keep getting sidetracked
[18:21] <JFo> I want to make sure we are building them well before I start giving them away
[18:50]  * tgardner knows its lunchtime somewhere.
[20:27] <kees> apw: should "linux-linaro" be added to https://wiki.ubuntu.com/Kernel/Dev/ABIPackages ?
[20:29] <apw> kees, probabally, though i've never seen it before :) 
[20:30] <tgardner> apw, linux-linaro is a 1000 series, the most recent upload was 2.6.35-1002.6
[20:31]  * jjohansen -> lunch
[20:33] <apw> tgardner, do we have a meta package for l
[20:33] <apw> linaro ?
[20:33] <tgardner> apw, we do, its a branch in the maverick meta repo
[20:34] <tgardner> apw, I'd have thought the k-t list traffic would have twigged you to it
[20:34] <apw> tgardner, i thought it was there, just too lazy to confirm
[21:00] <bjf> tgardner: did i miss my time?
[21:01] <tgardner> bjf, we;re in mumble  just qwaiting
[21:07] <apw> pgraner, have you dropped me that goals email ?
[21:08] <pgraner> apw, nope in 5 mins or so
[21:10] <apw> pgraner, ok i'll go grab dinner
[23:24] <jjohansen> rebooting