[00:00] <hallyn> well bug 602060 does seem to be a kernel bug, fixed in maverick.  haven't found an obvious commit responsible for fixing it...
[00:00] <ubot2> Launchpad bug 602060 in libvirt (Ubuntu) (and 1 other project) "Virtio network stops working after dynamic virtio disk attachment (affects: 1) (heat: 6)" [Medium,Confirmed] https://launchpad.net/bugs/602060
[00:03] <jjohansen> hallyn: thanks, looks like we will need to do some bisecting
[00:03] <hallyn> jjohansen: the painful part is bisecting in a guest :)  reckon there are ways around that.
[00:06] <jjohansen> heh, yeah bisecting in a guest would be painful :)
[00:07] <hallyn> jjohansen: anyway i wasn't quite sure whether i should be marking this as 'affects kernel', in case someone on kernel team recognizes the source of the bug
[00:08] <jjohansen> hallyn: yeah that is the best way to make sure it gets looked at
[00:09] <hallyn> i was spared having to decide by launchpad going down (hence my piping up here)  :)
[00:09] <jjohansen> :)
[00:14] <hallyn> jjohansen: but thx, i'll do that tonight or tomorrow
[00:14]  * hallyn out
[00:14] <jjohansen> night hallyn
[08:36] <apw> morning
[08:37] <lag> Morning
[08:54] <ogra> apw, could i get an updated omap4 meta ? the new kernel built and is in the archive (so i can roll images with the new kernel)
[09:16] <apw> ogra, they look to match to me ?
[09:16] <apw> moduleo the .35 hack in meta
[09:17]  * smb waves to apw
[09:18] <apw> morning smb
[09:19] <apw> ogra, ?
[09:21] <ogra> apw, meta has a versioned dep on the linux-image package, no ?
[09:22] <ogra> so i need a new meta to build images with the new kernel
[09:23] <ogra> (tim uploaded a new omap4 kernel yesterday)
[09:28] <apw> ogra, the linux-meta is dependant only on the abi number, they are both at 901 so i think we are good
[09:28] <ogra> oh, ok
[09:28] <ogra> i wonder what i have on my images then
[09:29] <ogra> since if the meta depended on 901 and we only had 900 in the archive i dont get how the images could have a kernel image
[09:29]  * ogra checks versions
[09:29] <ogra> 2.6.34-900.1 was the old image
[09:29] <apw> no the last upload was from 901.4 to 901.5 or whatever
[09:30] <ogra> then the changes list lies
[09:31] <ogra> i only see two uploads of linux-ti-omap4 ... one was 2.6.34-900.1 the next was yesterday and 2.6.34-901.4
[09:31] <ogra> between the two you made the change to meta
[09:31] <ogra> and livecd-rootfs only installs meta 
[09:31] <ogra> i dont get how i got the kernel then
[09:32] <apw> ogra, there was a 901.2 as well
[09:32] <ogra> weird, i dont see it on maverick-changes
[09:32] <apw> i did the meta update after the 901.2 was in
[09:34] <ogra> hrm, LP agrees with you https://edge.launchpad.net/ubuntu/+source/linux-ti-omap4/2.6.34-901.2
[09:34]  * ogra doesnt get why that was swallowed on changes then
[10:09]  * abogani waves
[10:09] <abogani> apw, Do you have some news for me? :-)
[10:09] <apw> not as yet, but you are very close to the top of my list ...
[10:10] <abogani> apw, Ok. Sorry to bother you so frequently.
[10:11] <apw> nope you are fine, i need reminding, i have a lot of people doing the same and sometimes it is a case of he who whines loudest :
[10:15] <abogani> apw, I understand but however I don't like doing it although Italians are famous for that.
[10:23] <apw> abogani, can you explain why this would need the getsource change, i cannot see why it would as we are in a full source tree ?
[10:25] <abogani> apw, Sorry?
[10:25] <apw> you have added a getsource clause, and i am wondering why
[10:27] <abogani> apw, Ah sorry. Because -lowlatency (it change only configuration not code) don't need to have a full copy of sources. It uses linux-source-2.6.3x. It should do archive admin happy (save a lot of space).
[10:27] <apw> abogani, if we upload it with an orig it would share the source anyhow
[10:28] <apw> which exists after we hit 2.6.35
[10:28] <jpds> Hey, could someone tell me what might be the cause of http://people.canonical.com/~jpds/pic2.jpg ?
[10:28] <apw> and from what i can see you commit doesn't remove the source from the tree so it would be in there anyhow
[10:29] <apw> jpds, what were you doing when it occurred ?
[10:29] <jpds> apw: Booting the device.
[10:29] <apw> jpds, also what kernel version is this, on what release
[10:30] <jpds> apw: Lucid, 2.6.32-22-generic-pae kernel on an Acer Revo.
[10:30] <apw> jpds, the key information is off the top of the scree
[10:30] <apw> screen, so its not easy to be 100% sure what happened, but it looks like the allocator exploded
[10:30] <apw> is it kernel specific, ie can you move back a kernel?
[10:35] <gnosek> hi all, is there an archive of the repo at http://kernel.ubuntu.com/git-repos/ubuntu/ubuntu-intrepid.git ?
[10:36] <abogani> apw, Should I remove getsource so?
[10:36] <smb> gnosek, http://kernel.ubuntu.com/git-repos/ubuntu-archive/ubuntu-intrepid.git
[10:37] <apw> abogani, i'll spend a bit of time looking over things and give you a proper response in email, its looking pretty good overall, some oddies which i think need cleanup, but much due to our stuff, ie things we should make configurable so you don't have to hack the rules
[10:37] <abogani> apw, Ok. Thanks again for all.
[10:40] <apw> smb, remind me how to make the font small on boot ...
[10:40] <smb> apw, must be in cking blog somewhere
[10:40] <apw> heheh must be
[10:41]  * apw waits on his-holiness
[10:41] <smb> apw, Maybe something in /etc/default/term...?
[10:41] <apw> yeah if its a boot issue?  i am sure you used to be able to do foo=ask, though ask stopped working i think
[10:41] <smb> err no /etc/default/console-setup
[10:42] <smb> apw, Would vga=6 still work? at least until kms kicks in
[10:42] <apw> smb, might do yeah ... gnosek ^^
[10:44]  * cking checks
[10:44] <cking> http://smackerelofopinion.blogspot.com/2009/06/getting-more-out-of-your-kernel-oops.html
[10:44] <cking> probably out of date now
[10:45] <lag> jpds: Did you try using Ctrl+Page up? to see the top of the trace log?
[11:10] <gnosek> smb: thanks a lot
[11:14] <apw> gnosek, checkout that cking link
[11:26] <gnosek> apw: ? smb already gave me the link to .../ubuntu-archive/...
[11:28] <apw> gnosek, ok
[11:56] <mdz> apw,smb: I'm getting ready to upgrade another system to Maverick, where I've seen the memory starvation issue before
[11:57] <mdz> it's currently running 2.6.32-23.37
[11:57] <apw> mdz ok
[11:57] <mdz> what do you think I should try?
[11:57] <mdz> I wonder if I should try using mvo's rollbackable upgrader so I can test it more than once
[12:02] <mdz> apw: should I try with ionice or without? should I update to -24 first?
[12:04] <apw> mdz, its a tricky one, as its not generally reproducible its hard to know what any specific positive means
[12:04] <apw> i guess we want to know if the version you were on is generally at fault for your method
[12:04] <mdz> apw: I guess my goal should be to try to reproduce it, so I should match the conditions from my previous upgrade as far as I can
[12:04] <apw> so i'd be inclined not to upgrade and to use ionice
[12:04] <mdz> right
[12:04] <mdz> agreed
[12:32] <htorque> hello, is the latest mainline kernel from the PPA known to cause problems with input devices?
[12:32] <htorque> PC: keyboard not working (PS/2), notebook: keyboard and touchpad not wokring. with a tailord custom kernel config, -rc4 seems to work fine on the notebook, though.
[12:35] <apw> htorque, i think there was a suspect patch which broke the keyboard controller but i thought that was fixed in -rc4
[12:38] <mdz> apw: remember how I was saying that even with ionice -c3, heavy I/O was very disruptive on my laptop? this system is *much* more well-behaved under high I/O regardless of the scheduler used
[12:39] <apw> mdz i386 can only use somewhat less than 1GB for the kernel direct mapped data, so that has an effect on allocation balance, though quite why that would trigger this result is unclear
[12:40] <mdz> it seems like perhaps I have a general I/O misbehavior on the other system which I don't have here
[12:40] <mdz> I'm going to go ahead and upgrade this one to maverick anyway and see what happens
[13:43] <Omahn> Quickie.. Is https://help.ubuntu.com/community/Kernel/Compile the official guide to compiling a kernel on Lucid?
[13:44] <tgardner> Omahn, start here: https://wiki.ubuntu.com/Kernel
[13:44] <Omahn> tgardner: I did, spent quite a while looking and then gave in.
[13:46] <Omahn> The background. I have a problem that I believe can be worked around by disabling a single option in the kernel so I would like to compile a fresh kernel that matches the Lucid kernel as close as possible, albeit with that option disabled. But that Kernel/Compile link I mentioned above doesn't appear to include information on Lucid. 
[14:19] <apw> Omahn, that is one of the bits of documentation thats a bit thing
[14:19] <apw> thin, and indeed on manjo's todo for the next couple of days
[14:19] <apw> the idea will be to have a 'how to change one option only and build a personal kernel' guide
[14:20] <apw> but right now we do not really have that in a simple form
[14:20] <apw> Omahn, which option is it
[14:51] <Omahn> apw: CONFIG_CIFS_XATTR - related to bug #557890
[14:51] <ubot2> Launchpad bug 557890 in linux (Ubuntu) "transfer lockup connecting to a NetApp/CIFS share (affects: 3) (heat: 53)" [Medium,Confirmed] https://launchpad.net/bugs/557890
[15:13] <htorque> awp: i see "CONFIG_SERIO_I8042=y" in 2.6.35-6-generic and my custom config, but not in the PPA's kernel
[15:17] <htorque> apw: ^^^ (sorry, typo)
[15:43] <tgardner> ogra, have you had a chance to try the ti-omap4 kernel?
[15:43] <ogra> tgardner, yeah, its awesome
[15:44] <tgardner> ogra, cool. no hangs?
[15:44] <ogra> it still locks up at some point but i currently blame the framebuffer driver 
[15:44] <ogra> and its random after like 1-2h of use 
[15:44] <ogra> (before you could only use the system for a few mins if it came up at all)
[15:44] <tgardner> ogra, sounds like memory corruption or exhaustion
[15:45] <ogra> right
[15:45] <apw> JFo, about ?
[15:45] <ogra> but its related to video, it only happens if i use X
[15:51] <bjf> manjo, https://wiki.ubuntu.com/Kernel/kteam-tools
[15:52] <JFo> apw, yep
[15:52] <apw> JFo, you mentioned you had a bunch of FAQ entries you wanted to add, and wondered if there was a list somewhere
[15:53] <manjo> bjf, thanks
[15:53] <JFo> I have a rough one written in some of my notes
[15:53] <JFo> let me see if I can find it
[15:53] <JFo> if not I will make you up some off the top of my head and we can discuss them
[15:54] <JFo> I need to take another look at what is there already as my notes were written in something of a vacuum
[15:54] <tgardner> manjo, when was the last time you checked out kteam-tools ? Your page on https://wiki.ubuntu.com/Kernel/Action/Scriptbuildmkschroot is not accurate
[15:55] <manjo> tgardner, I just got pinged by bjf about that.. thanks
[15:56] <bjf> manjo, i was pointing out we were starting to duplicate our wiki pages
[15:56] <manjo> bjf, I am working on removing dups & putting them in correct places 
[15:58] <htorque> apw: 'CONFIG_SERIO_I8042' was set to 'no' due to 'CONFIG_X86_MRST=y', which got set to 'n' with the latest update (the PPA will follow I guess?) - so, everything's fine :)
[15:58] <apw> htorque, thought so, yep, thats a mess and needs someone upstream to fix it
[15:59] <apw> JFo, yeah figured if we had the 'questions we should but do not have' people could fill them in as they had time
[15:59] <JFo> yep
[15:59] <JFo> I'll add the ones I have to the page so they can be answered as we go
[15:59] <JFo> some of them... well ok most, I don't have the answers for :)
[16:00] <apw> JFo, i suggest you add a == Needed Questions == section to the FAQEdit page
[16:00] <apw> and put the raw questions there, then we know where to look for them
[16:00] <JFo> sounds good. Will do
[16:01] <JFo> apw, want it after the existing questions?
[16:02] <apw> jfo before i recon
[16:02] <JFo> ok
[17:14] <apw> JFo, hrm did you add those questions, seems to only be a * now
[17:14] <JFo> not yet, I'm reviewing what we have already versus what I thought was missing back when I took my notes
[17:15] <JFo> plus I am digging through bank statements and receipts for petra
[17:41] <bjf> manjo, i'm confused why we need both https://wiki.ubuntu.com/Kernel/Action/GetKernelToolsScripts and https://wiki.ubuntu.com/Kernel/kteam-tools
[17:42] <manjo> bjf, don't worry about it now, it will be all dealt with at the sprint 
[17:49] <bjf> manjo, just seems like wasted effort doing them both
[18:25] <apw> bjf, i suspect they will end up sharing the contents
[18:47] <bjf> pgraner, any thoughts on apport symptoms?
[18:55]  * smb prepares for watching tv
[18:56]  * tgardner lunches
[19:39] <omry> is there a known issue with 2.6.34 that can cause lockups with dell laptops (inspiron 17) ?
[19:40] <omry> I am running lucid, and had to upgrade due to a suspend/resume issue with 2.6.32, but then my box started to freeze up randomly. issue was resolved when I booted 2.6.32 again.
[19:40] <apw> omry, not many people are runnig .34 it not being a kernel we are based on.  does it appear with the maverick kernels
[19:42] <omry> didn't try yet actually.
[19:43] <omry> got the 2.6.34 deb here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-rc5-lucid/linux-image-2.6.34-020634rc5-generic_2.6.34-020634rc5_amd64.deb , if it matters
[19:44] <tgardner> omry, subscribe to the Maverick LTS backport kernel at http://ppa.launchpad.net/kernel-ppa/ppa/ubuntu
[19:48] <omry> tgardner, NO_PUBKEY A8267963484B044F , where do I get the key?
[19:50] <tgardner> omry, go to the page at http://launchpad.net/~kernel-ppa/+archive/ppa
[19:51] <tgardner> omry, click on 'What is this?" next to the signing key.
[20:05]  * cking_ shifts gear to zzz mode
[20:06] <omry> tgardner, thanks. that all apt-add-repository thing confused me but it's good now.
[20:06] <omry> installing 2.6.35-7-generic, hopefully this one will work for me.
[20:07] <tgardner> omry, that kernel will be updated until Maverick is released at which time it will appear as a component in Lucid (i.e., you won't have to do anything)
[20:09] <omry> you mean my system will keep upgrading it till maverick is released, right?
[20:10] <tgardner> actually, it'll keep upgrading it until Maverick is no longer maintained
[20:10] <omry> right
[20:31] <apw> manjo, were you looking for me ?
[20:47] <jjohansen> -> Lunch
[21:32] <manjo> apw, looks like olivia won some money 
[23:00]  * bjf is taking a break, will be back later
[23:23] <ripps> what's taking so long to get linux-2.6.35-7.11 out of maverick queue. Getting some aptitude errors because linux-meta was pushed to repo before it.
[23:47] <kees> ripps: looks like it's still in the binary-NEW queue.