[08:05] <jk-> cooloney: ping?
[08:13] <cooloney> jk-: hi
[08:16] <jk-> cooloney: could I get you to test my clk code on omap?
[08:16] <jk-> cooloney: sorry, s/clk/debug macro/
[08:19] <jk-> cooloney: the 'debug' branch here: http://kernel.ubuntu.com/git?p=jk/dt/linux-2.6.git;a=shortlog;h=refs/heads/debug
[08:21] <cooloney> jk-: no problem, just a moment 
[08:43] <cooloney> jk-: it's quite slow for me to git fetch, pls wait for a while
[08:44]  * cooloney will upgrade his network to 4MB
[08:45] <jk-> cooloney: no problem, thanks :)
[08:46] <amitk> cooloney: 4Mbps? Will that really change anything? I thought the problem was due to limited bandwidth between China and US...
[08:47] <cooloney> amitk: yeah, that won't change the problem here. 
[08:47] <cooloney> amitk: but it's double my speed soon
[08:47] <cooloney> and the upgrade is free
[08:47] <amitk> cooloney: heh :) free is good
[08:50] <lag> cooloney: Morning
[08:50] <lag> Hey jk- amitk 
[08:50] <jk-> hey lag
[08:51] <lag> cooloney: ...
[08:53] <lag> cooloney: You're not getting away from me that easily 
[08:56] <amitk> lag: how is it going?
[08:56] <lag> amitk: Chugging along, and you?
[08:59] <amitk> lag: I see light at the end of the tunnel (and it is moving away from me)
[09:00] <lag> amitk: Ouch! :)
[09:00] <lag> amitk: My situation will improve when I catch hold of that slippery cooloney ;)
[09:00] <amitk> heh
[09:02] <cooloney> lag: morning man
[09:04] <lag> cooloney: There you are :)
[09:04] <lag> cooloney: What's going on with L24.9?
[09:04] <lag> cooloney: I haven't heard anything; no emails, messages or calls
[09:09] <cooloney> lag: yeah, sebjan is back
[09:09] <cooloney> lag: and he is working on that, 
[09:09] <cooloney> lag: i'm also waiting for that
[09:11] <lag> cooloney: No worries - I'll continue to wait ...
[09:13] <cooloney> lag: np, man
[09:39] <cooloney_> jk-: good news, it boots fine
[09:40] <jk-> cooloney_: woot! thank you for testing
[09:41] <cooloney_> jk-: oh, wait, CONFIG_DEBUG_LL=y is right?
[09:41] <cooloney_> jk-: i am using the omep3_defconfig
[09:41] <jk-> cooloney_: yeah,  CONFIG_DEBUG_LL=y and CONFIG_EARLY_PRINTK=y
[09:42] <jk-> (and maybe with 'earlyprintk' on the cmdline)
[09:42] <jk-> (to give it a thorough test :) )
[09:44] <cooloney_> ok, np, 1 sec
[09:46] <jk-> it *should* be the same as the !CONFIG_DEBUG_LL case, but I'd like to make sure
[09:47] <cooloney_> jk-: yeah, it works fine too
[09:47] <jk-> cooloney_: awesome, thanks
[09:50] <cooloney_> jk-: one question, 
[09:51] <jk-> cooloney_: yup?
[09:51] <cooloney_> jk-: if i wanna debug in a arch/arm/kernel/head.S, just wanna print out some register value,
[09:51] <cooloney_> beside printhex helpers
[09:52] <cooloney_> any other choice
[09:53] <jk-> cooloney_: yeah, i'd suggest printhex and printascii - are these not suitable for your usage?
[09:54] <cooloney_> jk-: i'm afraid that will corrupt some registers
[09:55] <cooloney_> jk-: http://pastebin.ubuntu.com/482255/, booting message of your kernel
[09:55] <jk-> cooloney_: yeah, corrupts r0-r3.
[09:56] <jk-> cooloney_: looks good
[11:22] <moldy> hi
[11:23] <lag> Has anyone been working with Sony Fn buttons? I vaguely remember someone working on them recently
[11:23] <lag> jk-: Was it you?
[11:23] <jk-> lag: not me :/
[11:24] <lag> I remember someone saying something like "I have them fixed, and I didn't even have the hardware"
[11:24] <lag> jk-: Okay :(
[11:24] <moldy> http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html mentions (for example) an ubuntu kernel version 2.6.34-5.14 for lucid. how would i install that kernel for testing?
[11:24] <jk-> sounds like something Colin would say :)
[11:25] <lag> moldy: Wait one, I'll get you the URL
[11:27] <lag> moldy: You can either look them up here: https://edge.launchpad.net/ubuntu/+source/linux
[11:27] <lag> moldy: If they're not there you can use your git tree to build your own *.deb
[11:27] <moldy> lag: thanks, i will have a look
[11:28] <lag> moldy: Our git tree: http://kernel.ubuntu.com/git
[11:29] <lag> moldy: The Lucid repo: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid.git;a=summary
[11:30] <lag> moldy: tag 2.6.34-5.14: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid.git;a=tag;h=b2c6db6e3155efd7f3af1d871c7a279f4f116d37
[11:34] <moldy> could i just install a kernel .deb from maverick on lucid?
[11:35] <lag> Sure
[11:35] <moldy> lag: would that also install all the modules, or would i have to install them separately?
[11:36] <lag> moldy: If you install the .deb, the modules will be installs with the kernel
[11:36] <lag> installed*
[11:36] <moldy> ok, thanks
[11:36] <lag> moldy: No problem 
[13:45] <lag> Hey JFo 
[13:46] <JFo> hey lag 
[13:47] <lag> JFo: How do you search just for kernel bugs on Launchpad?
[13:47] <smb> with much despair
[13:47] <lag> :(
[13:49] <smb> lag, It should be possible to limit them to package linux I guess/hope
[13:49] <lag> smb: You mean like this - https://bugs.edge.launchpad.net/ubuntu/+source/linux
[13:50] <smb> yeah that looks ok
[13:51] <lag> But then you get really random ones like bug 43531
[13:51] <ubot2> Launchpad bug 43531 in linux (Ubuntu) "Kernel isn't very useful without a boot loader, but doesn't depend on one (affects: 1) (heat: 5)" [Medium,In progress] https://launchpad.net/bugs/43531
[13:51] <lag> How is that a kernel bug?
[13:52] <smb> Would be a bug in the packaging
[13:52] <smb> And one we probably should look at
[13:53] <JFo> lag, sorry, got distracted by something shiny
[13:53] <lag> smb: It's 4 years old :)
[13:53]  * lag is not surprised :)
[13:53] <smb> Heh, yeah. 
[13:53] <lag> Is Ben Collins still with us?
[13:53] <smb> At least we then should check whether this is really valid
[13:53] <smb> Nod
[13:53] <smb> No
[13:54] <lag> The last person to complain about it did so 3 years ago
[13:54] <smb> Sounds like a real good candidate for getting rid of.
[13:55] <smb> Though we probably need to check whether you could clean up away your boot loader
[13:56] <smb> lag, You could do that in your copious spare time. :)
[13:57]  * ogra wouldnt blindly close it regarding the initial reporter :)
[13:57] <ogra> there should be plenty of duplicates of that one btw 
[13:58] <ogra> we had a time where we had one for each arm flavour to at least recommend a bootloader iirc 
[13:59] <lag> I'll assign myself to it and try to put it to bed
[13:59] <lag> smb: Hmm ...
[14:00] <smb> lag, Actually there is a "Recommends: BOOTLOADER" in flavour.control.stub
[14:00] <smb> So this rather looks fixed by now
[14:00] <jdstrand> smb: hey. I saw your email response re xen/hardy. have you gotten any upstream feedback?
[14:00] <lag> smb: I have to confess, I don't know a great deal about packaging, but I guess there's always time to learn
[14:00] <JFo> smb, I've added to the needs-review list so we can verify before responding and closing
[14:01] <lag> What's the best way to review this?
[14:01] <smb> jdstrand, I updated the bug report. There is/was an upstream discussion about this. For Hardy and earlier the code is so different that we ended up doing what the upstream code intended but was wrong
[14:01] <lag> Teach me sensai
[14:01] <pgraner> smb, am I correct in my assumption that the gobi-loader package is not yet in Lucid?
[14:02] <tgardner> pgraner, should be universe
[14:02] <smb> pgraner, It won't ever be. In Lucid all is included in lbm
[14:02] <smb> tgardner, pgraner Only Maverick has the universe package
[14:02] <pgraner> smb, ok, then is the lbm package there yet? I'm assuming it will be -wwan?
[14:02] <jdstrand> smb: ack. don't let me keep you. ping me when you are ready and I can get it uploaded and building
[14:02] <smb> Uploaded but I think not accepted yet
[14:03] <pgraner> smb, ack
[14:03] <smb> jdstrand, Test kernel compiling right now
[14:04] <smb> pgraner, And yes, will be lbm-wwan
[14:04] <lag> JFo: Should bug 525801 still be on the Top50?
[14:04] <ubot2> Launchpad bug 525801 in linux (Ubuntu) (and 1 other project) "[i915] NULL pointer dereference in intel_tv_detect() (affects: 18) (dups: 9) (heat: 90)" [High,Invalid] https://launchpad.net/bugs/525801
[14:04] <lag> JFo: bug 527361 - same
[14:04] <ubot2> Launchpad bug 527361 in linux (Ubuntu Lucid) (and 2 other projects) "hotplug interferes with ethernet card (affects: 1) (heat: 23)" [Medium,Incomplete] https://launchpad.net/bugs/527361
[14:05]  * JFo looks
[14:05] <lag> JFo: bug 553498 - same
[14:05] <ubot2> Launchpad bug 553498 in linux (Ubuntu Maverick) (and 2 other projects) "Dell Studio 155x hang on resume from suspend (SCI_EN) (affects: 15) (heat: 85)" [High,Fix released] https://launchpad.net/bugs/553498
[14:05] <lag> I think the Top50 is out of date
[14:05] <JFo> first one you gave me is marked invalid
[14:05] <lag> Exactly 
[14:05] <pgraner> smb, thx
[14:06] <lag> Second is fixed released
[14:07] <JFo> oh, you are saying the list is out of date
[14:07] <JFo> of course it is
[14:07] <lag> As is the third
[14:07] <JFo> I was in meetings all last week
[14:07] <lag> Ohhhhhhh
[14:07] <lag> np
[14:07] <JFo> and we had no meeting
[14:07] <lag> Was getting confused 
[14:07] <JFo> I see
[14:07] <lag> I'm guessing the Top50 is static 
[14:07] <JFo> there is a bug meeting today
[14:07] <JFo> it is
[14:07] <lag> kk
[14:08] <smb> jdstrand, To be clear here. This is not any upstream solution as anything upstream did might be really hard to get backported and it just went into 2.6.36-rc2. We might in the long term want to fix the other issues in there. But they are different. 
[14:08] <lag> You'd best get on your Python course ;)
[14:08] <pgraner> tgardner, you been seeing issues with the latest maverick kernel? I'm getting real bad jitter on music playing doing normal day to day tasks, I mainly see it on window opens
[14:09] <smb> jdstrand, I hope the explanation in the bug is understandable. But basically I would like to get the test kernels tested on xen (I can do normal bootup) to make sure this is really the fix.
[14:09] <tgardner> pgraner, I haven't been using Maverick on a laptop whilst playing music. I've mostly been testing the Lucid ext4 stuff for stability
[14:09] <jdstrand> smb: ok
[14:09] <JFo> pgraner, I don't see it on my desktop
[14:09] <jdstrand> smb: I have started reading https://help.ubuntu.com/community/Xen myself
[14:09] <JFo> will fire up my Mav lappy to test
[14:10] <jdstrand> smb: I wonder if lamont has a spare builder he could try it out on
[14:10] <pgraner> tgardner, I can get it to do it every time, its on this i5 box 
[14:10]  * pgraner wonders
[14:11] <smb> jdstrand, There is a link to kernel trap in the bug now for some of the discussion. It has been kicked off abit earlier by someone doing xen. Though it did not sound fatal at the beginning.
[14:11] <smb> jdstrand, lamont maybe can. But it sounds a bit more complicated. Have been chatting with him
[14:12] <pgraner> tgardner, this box is still having huge issues with memory, it has 2 gigs and it has a half gig in swap
[14:13] <tgardner> pgraner, wouldn't swapping account for the jitter? I have to wonder _why_ its swapping. are you running some huge mem hog, or you still have a leak somewhere?
[14:14] <pgraner> tgardner, I have Evolution, Xchat, Chromium and Rhythmbox open, nothing big other than Chromium
[14:14] <tgardner> pgraner, ok, does it jitter right after a reboot, or does it take awhile?
[14:15] <pgraner> tgardner, takes awhile a few hours
[14:15] <pgraner> tgardner, I just killed chromium and it stopped and it freed a ton of memory
[14:15] <tgardner> pgraner, then that sounds like a leak (no pun intended)
[14:16] <pgraner> tgardner, swap went down to 229meg from 500
[14:16] <tgardner> pgraner, did it completely clear your swap?
[14:16] <pgraner> tgardner, nope
[14:16] <tgardner> pgraner, how about after 'sudo sync'
[14:17] <tgardner> you really shouldn't have much in swap if all your progs are active.
[14:17] <pgraner> tgardner, with 2 gigs your right, it only dropped it a hundred kb
[14:18] <tgardner> pgraner, what does slabtop show? anything exceptional?
[14:19] <pgraner> tgardner, 135936 135919  99%    0.03K   1062      128      4248K kmalloc-32
[14:19] <pgraner> thats the top entry
[14:20] <tgardner> pgraner, just reading the man page to see how its sorted
[14:20] <tgardner> pgraner, 'c' sorts by cache size
[14:20] <pgraner>  31956  14366  44%    0.96K   1998       16     31968K ext4_inode_cache
[14:20] <pgraner> top entry after "c" sort
[14:21] <tgardner> pgraner, thats consistent with tangerine which is running a lucid kernel
[14:21] <tgardner> did your music stop stuttering after killing chromium?
[14:21] <pgraner> tgardner, yep
[14:23] <tgardner> pgraner, the evidence kind of points there, though I _still_ don't think you should be swapping
[14:24] <pgraner> tgardner, me either, it was doing this in Prague and the ureadahead fix made it better, but seems to not have fixed it
[14:25] <lamont> smb: yeah, I can test for you
[14:25] <tgardner> pgraner, all ureadahead did was free some mem which just pushed back the time when swapping started
[14:25] <pgraner> tgardner, my netbook has 2gig and it never swaps (cuz I didn't crate a swap partition on the SSD)
[14:25] <tgardner> pgraner, same with mine, i.e., no swap
[14:26] <pgraner> tgardner, understand, but its similiar symptoms, due to that the ureadahead I never noticed this
[14:26] <tgardner> lemme wrap up a few things and I'll go play with my SSD based machine on Maverik
[14:26] <smb> lamont, Currently uploading the 64bit versions to people.c.c which have been at least booting on the generic version. So 64bit should be available in a couple of minutes
[14:28] <lamont> cool.  say when/where and I'll go grab it for testing
[14:30] <amitk> pgraner: do you have some power save mechanism enabled for the disk? e.g. sata link controller
[14:33] <pgraner> amitk, nope
[14:33] <pgraner> amitk, stock out of the box
[14:37] <smb> lamont, 64bit test kernels ready at http://people.canonical.com/~smb/lp620994/ , the 32bit versions will follow later (and if I may add a little whining here: it would all be quicker if I would be able to scp from tangerine to people directly :-P)
[14:39] <lamont> smb: yes, I'm very familiar with that challenge
[14:52] <tgardner> ogasawara_, lemme know when you're done on tangerine so I can bounce for the -security kernel
[14:54] <lamont> smb: so... good news, bad news... domU boots
[14:54] <lamont> Error: /usr/lib64/xen/bin/xc_restore 23 7 1 2 0 0 0 failed
[14:55] <smb> Hm, any kernel errors?
[14:55] <jdstrand> fyi, since lp deleted the last kernel, I made the previous hardy kernel available in ubuntu-security-proposed, with appropriate warnings etc in the bug
[14:56] <lamont> [  381.653530] audit(1282571471.116:7): dev=vif7.0 prom=256 old_prom=0 auid=4294967295
[14:56] <lamont> and some entries about learning, propagating, forwarding, disabled, disabled state for vif7.0
[14:56] <smb> jdstrand, Yep, saw that.
[14:56] <lamont> that is all dmesg has
[14:56] <lamont> and daemon.log looks pretty benign
[14:57] <lamont> http://paste.ubuntu.com/482411/
[14:57] <smb> lamont, Darn, not very helpful. Not being familiar with xen, so what should xc_restore do?
[14:58] <lamont> I'll admit to using xen, not to understanding it
[14:58] <lamont> basically, the guest has a golden image that is being restored.  I additionally rebuilt said image from scratch, to the same result
[15:03] <smb> lamont, Somehow the paste looks like the errors are in bringing down several interfaces. But then it claims success anyway... Confusing
[15:03] <smb> lamont, Is the end result a usable DomU or one without any networking?
[15:04] <lamont> I'm sshed into domU
[15:04] <lamont> so that feels like "networking" :-D
[15:04] <smb> lamont, Also, even if that maybe should be obvious, were those errors probably there before? :) Ok, I'd be counting this as network, too
[15:05] <lamont> dunno
[15:06] <lamont> http://paste.ubuntu.com/482413/ <-- smb: the previous reset of the (then up) guest
[15:08] <smb> Looks shorter but also has the error about brctl failing
[15:09] <smb> lamont, jdstrand I wonder whether jj knows the xen output better to tell whether this is bad or ok... 
[15:10] <jdstrand> maybe. zul might as well
[15:10] <jdstrand> zul: would you mind taking a look at ^
[15:10] <smb> It is at least not crashing anymore. But I want to be a bit more confidence before calling this a fix
[15:12] <jdstrand> smb: what I would like to do when you are ready is to build the kernel in the ubuntu-security ppa, copy it to hardy-proposed and get feedback in the bug from the reporters/subscribers
[15:12] <jdstrand> smb: once we have positive feedback, I can publish to -security
[15:13] <jdstrand> smb: for you, just use 'hardy-security' as the distribution name and I'll take care of the rest
[15:13] <smb> jdstrand, The test kernels I am uploading to the people page are exactly that. Based of the last release and the patch added
[15:13] <smb> I just did not finalize it
[15:13] <smb> So the version number is smaller that the actual security release
[15:13] <jdstrand> smb: sounds great. I too would like some more feedback from zul and jj
[15:14] <lamont> smb: I'd be -1 with the current state
[15:14] <jdstrand> smb: but when you feel they are ready for wider testing, let me know
[15:15] <smb> jdstrand, Exactly. As soon as we are confident about the fix. I would finalize the source package and all. But at the moment as lamont says there might be issues and this might not be the final resolution
[15:15] <jdstrand> right
[15:15] <jdstrand> smb: I was just trying to communicate my plan. specifically, not going straight to -security
[15:16] <smb> jdstrand, Ah, maybe missed that. Ok with that
[15:18] <smb> lamont, Another question for my understanding: is the same kernel used for the host and the guest or are they different?
[15:18] <lamont> same
[15:19] <smb> Ok, thanks
[15:19] <jdstrand> smb: oh, I missed your comment regarding test kernels in the bug
[15:19] <jdstrand> smb: sorry for the confusion
[15:20] <smb> jdstrand, np. we might have been adding comments around the same time
[15:20] <jdstrand> yes I think so
[15:20] <jdstrand> smb: anyway, people testing your kernels is just fine by me
[15:22] <smb> yeah does not matter exactly from where they come. And coming from a people page might stress more on the "this is maybe not final" thing
[15:26] <pmatulis> how can i troubleshoot a network module (igb) having difficulty with bonding when booting?  need to manually load 'bonding' module
[15:55] <ogasawara> tgardner: go ahead and bounce tangerine
[15:55] <tgardner> ogasawara, ack
[15:56] <bjf> Sarvatt: wecome aboard
[15:57] <bjf> s/wecome/welcome/
[16:00] <Sarvatt> thanks bjf! :)
[16:05] <JFo> yeah Sarvatt great to have you! :)
[16:20] <vanhoof> pgraner: ping
[16:20] <pgraner> vanhoof, yo
[16:20] <vanhoof> pgraner: yooo
[16:20] <vanhoof> pgraner: can you add ~canonical-hwe-team to c-k-t in lp?
[16:20]  * pgraner looks
[16:21] <vanhoof> pgraner: getting Sarvatt setup, so adding our team to yours should get him access indirectly
[16:21] <vanhoof> otherwise if you want, just add sarvatt
[16:22] <Sarvatt> sorry for the trouble, and thanks :)
[16:23] <pgraner> Sarvatt, whats your lp id?
[16:23] <Sarvatt> sarvatt
[16:23] <pgraner> vanhoof, I'm going to add him as that how all the hew guys are done
[16:23] <bjf> Sarvatt: that's very tricky of you :-)
[16:24] <Sarvatt> :)
[16:24] <vanhoof> pgraner: cool
[16:24] <pgraner> Sarvatt, vanhoof: done
[16:24] <Sarvatt> pgraner: thanks a ton!
[16:24] <pgraner> Sarvatt, np
[16:25] <smb> tgardner, tangerine bounced ok and I can use it again?
[16:25] <tgardner> smb, yep
[16:25] <smb> ok. ta
[16:41] <JFo> bjf, do you have a minute to help me test out my desktop mumble settings in the Ad-hoc room??
[16:59] <smb> JFo, I won't be able to join the bug review call as I am still busy with the xen regression
[17:00] <JFo> smb, no sweat
[17:00] <JFo> thanks for the heads-up
[17:00] <smb> It more a head down. And sort of late... 
[17:01] <JFo> heh
[17:23] <ogasawara> manjo: there's a work item you have for the kernel-maverick-config-review - "investigate memory stick options and produce proposal"
[17:24] <ogasawara> manjo: I actually have no recollection of what the reasoning behind that was for or the proposal that was going to be produced.
[17:24] <ogasawara> manjo: just curious if you still have that on your radar? or is it something we should just postpone and readdress for Natty?
[17:26] <jdstrand> lamont: you mentioned a 'pristine' image for your xen instance. how do you guys do snapshots with xen. I have xen setup here on some real hardware and am looking for anohter test case...
[17:30] <jdstrand> smb: I just rebooted into the .75 kernel after setting up on i386. my trace is very similar but slightly different than what is in the report
[17:32] <smb> jdstrand, Without using xen?
[17:33] <jdstrand> smb: I setup hardy/xen on some real hardware with the -xen kernel. Got it all working with .73. Rebooted into .75 and have a similar but slightly different trace
[17:35] <smb> jdstrand, Ok, sort of gives a test system and shows the issue. Can you pastbin the trace?
[17:35] <jdstrand> smb: actually, I attached it to the bug
[17:35] <jdstrand> smb: http://launchpadlibrarian.net/54226707/620994.log
[17:36] <jdstrand> smb: this machine is dedicated to testing this bug atm, so just let me know what you want me to test
[17:37] <smb> jdstrand, Ah ok. Seems splitup can also be a single page which then gets avoided and ends in a zero range 
[17:38] <jdstrand> jjohansen: re me testing> ^
[17:38] <smb> jdstrand, Basically there are two approaches. #1 don't avoid touching the guard page in mlock. Which could be used to use mlock to grow the stack
[17:38] <smb> #2 implement even better testing that in my version 1 of patches
[17:38] <smb> Which I am currently trying to implement
[17:39] <jdstrand> I have only the highest level understanding of the issue, as I came into this CVE late in the game. I'm happy with what you decide and am able to test
[17:40] <jjohansen> I think #2 is probably the way to go
[17:40] <jjohansen> though /me is still trying to catchup on this one
[17:41] <smb> I guess yes. (which will need some fixing in more recent kernels too). Seems in the older version I actually can make use of the fact that mlock there actually passes around the previous vma pointer.
[17:41] <smb> But I need to be carefull
[17:41] <jdstrand> it would seem #2 is the better of the two, since it seems closest to upstream intent
[17:42] <smb> For Jaunty to Lucid/Maverick we might take the upstream version (after a bit of cooking there)
[17:54] <manjo> ogasawara, I think we can move it for N
[17:54] <ogasawara> manjo: ack, will get it moved.  thanks.
[17:54] <manjo> ogasawara, I don't think I will have the bandwidth to do any investigation this cycle 
[17:54] <manjo> ogasawara, thanks
[18:00] <ogasawara> JFo: I've moved your kernel triage summit work items to have a maverick-beta milestone since a 10.10.10 milestone will be too late.
[18:02] <JFo> ?
[18:02] <JFo> not sure what you mean ogasawara 
[18:03] <ogasawara> JFo: you had some work items for organizing the triage summit (in the kernel-maverick-bug-handling bp).  I thought you'd set the date to be sept 11 for that?
[18:04] <lamont> jdstrand: lvm snapshotting.  I'm a bit fuzzy on it, but can point at the scriptages
[18:04] <ogasawara> JFo: assuming that date is still correct, the work items for organizing I suspect would need to be done by maverick-beta (sept 2).
[18:04] <lamont> smb: any new news?
[18:06] <smb> lamont, Not finite ones. I think I got something better, but probably would let jjohansen look over the patch and then start building it
[18:06] <JFo> ogasawara, oh heh yeah, sorry. my brain is moving way slow
[18:06] <lamont> cool
[18:07] <jdstrand> lamont: nah, thanks. it sounds like you are probably doing it outside of the xen-tools commands
[18:08] <lamont> jdstrand: I'm pretty sure our use predates those commands
[18:19] <smoser> hey all. is there an expected/target date for the next lucid SRU kernel ?
[18:20] <bjf> smoser, it's looking like the end of next month right now
[18:20] <smoser> for entry into -proposed ?
[18:21] <bjf> smoser, honestly, there is a proposed in right now and then a security upload and then the following will be the next regular upload
[18:21] <bjf> smoser, ack
[18:22] <smoser> can i see the changelog for the "proposed in right now" ?
[18:22] <bjf> smoser: is there one you are looking for?
[18:23] <bjf> smoser, commit that is
[18:23] <rabidsnail> Hi all.
[18:24] <rabidsnail> Is there any way I can tell the kernel "don't allow this process to access swap; when I run out of physical memory, fire a signal"?
[18:24] <smoser> bjf, bug 574910 is what i am hoping for
[18:24] <bjf> smoser, if you are asking about the patch jj posted on friday, that's not in proposed
[18:24] <ubot2> Launchpad bug 574910 in linux-meta (Ubuntu) (and 4 other projects) "High load averages on Lucid while idling (affects: 25) (dups: 3) (heat: 174)" [Undecided,New] https://launchpad.net/bugs/574910
[18:24] <smoser> :-(
[18:24] <smoser> yeah, i was hoping
[18:25] <bjf> smoser: it's going to be at least 3 weeks before that gets into proposed, and probably not that soon
[18:26] <smoser> bjf, thanks for your time.
[18:43] <lag> dpkg-gencontrol: error: package linux-image-2.6.35-18-omap not in control info
[18:43] <lag> What does that mean?
[18:44] <smb> often that you forgot to run clean
[18:44] <lag> I thought control was built by fdr clean
[18:44] <lag> The scripts run clean
[18:45] <smb> Then it depends whether there is the right info in debian/control.d to include that arch/flavour in the control file
[18:46] <lag> Okay, I'll look into it
[18:46] <smb> lag Is this a new flavour?
[18:46] <lag> Thanks
[18:46] <lag> No
[18:46] <lag> OMAP3
[18:46] <lag> I've built it 100's of times before
[18:46] <tgardner> ;aglucid?
[18:47] <tgardner> lag, lucid?
[18:47] <lag> tgardner: Maverick
[18:49] <lag> The build before it said something about a stamp
[18:50] <tgardner> lag, its in the debian/control that I just generated. 
[18:50] <lag> I've fdr cleaned manually and rebuilding 
[18:50] <lag> Okay
[18:51] <lag> I'll let you know if it's still an issue 
[19:21]  * tgardner lunches
[19:43] <jdstrand> jjohansen, smb: fyi-- I only have i386 available for testing the xen issue
[19:43] <jdstrand> jjohansen, smb: so whenever you are ready, please also compile i386
[19:43] <jjohansen> jdstrand: hrmm, okay I can install an amd64
[19:44] <jjohansen> jdstrand: actually smb kicked off the compiles
[19:44] <smb> I am compiling both. Though i386 is slower
[19:44]  * jjohansen notes it would sure help if x86 virtualization could be nested
[19:45] <smb> jdstrand, Do you have access to tangerine?
[19:46] <jjohansen> smb: I don't believe he does but I can copy kernels out for him
[19:46] <jdstrand> smb: I do not
[19:47] <smb> jjohansen, Ok, amd64 is done already, but i386 is still doing xen, so that takes a bit more.
[19:47] <smb> Also note that this is a totally untested version
[19:47] <jjohansen> smb: yep :)
[20:12] <lamont> jdstrand: it also didn't fit my use model.  I see the guest exist, but when we save it and then try to restore, it falls flat
[20:13] <lamont> that is, when I rebuilt it (which does a wipe-n-build, save, restore), the guest was pingable for many of the steps, and then failed to restore in the end
[20:17] <smb> jjohansen, jdstrand its probably not really useful, but the i386 build on tangerine finished now as well
[20:18] <jjohansen> smb: thanks, I'll copy it over for jd
[20:21] <jdstrand> it is quite useful to me, it is all I can test :)
[20:22] <smb> jjohansen, When looking at the patches, the mistake might be trying to avoid find_vma in the checking function...
[20:22] <smb> jdstrand, Only unusful insofar as lamont is not happy with the 64bit version
[20:23] <jjohansen> right, I was thinking that may be an issue
[20:23] <smb> I hoped that it would be possible to avoid it as do_mlock uses find_vma_prev and passes in the prev pointer.
[20:24] <jdstrand> ah, I missed that :)
[20:25] <jjohansen> smb: right
[20:26] <smb> jdstrand, I hope with the current patch it will be relatively simple to make a version with find_vma. That could even skip the new variable and do the checking below. Just be aware not to change anything around the splitting. openvz patches break if touching that. the custom-binaries are so much fun... :-P
[20:26] <smb> s/jdstrand/jjohanson/
[20:27]  * smb feels like he needs to go away from the keyboard when already mixing up names
[20:28] <ogasawara> slangasek: are you on archive admin duty today?  If so, could I get the 2.6.35-18.24 kernels in the new queue processed?
[20:29] <jjohansen> hehe, smb go eod already :)
[20:29]  * smb hears and obeys
[20:29] <jdstrand> jjohansen, lamont, smb: rebooting with pre3 on i386 doesn't trace back, but gives:
[20:30] <jdstrand> Error: /usr/lib/xen/bin/xc_restore 4 1 1 2 0 0 0 failed
[20:30] <jdstrand> let me try with .73 to be sure
[20:34] <lamont> jdstrand: different numbers here, but same answer: Error: /usr/lib64/xen/bin/xc_restore 23 5 1 2 0 0 0 failed
[20:38] <slangasek> ogasawara: yes, will do
[20:45] <jdstrand> jjohansen, lamont, smb: k, I rebooted with .73 with a guest that was running (ie, it triggers xc_restore on boot) with no error
[20:46] <jjohansen> jdstrand: thanks
[20:58]  * ogasawara lunch
[20:58] <Akendo> Hi gyus
[21:00] <Akendo> Someone know, about a bug by compiling a kernel with a gcc4.4 under Ubuntu 10.04? 
[21:16] <bjf> Akendo: what does 'gcc --version' return?
[21:17] <Akendo> root@akendo:~/kernel/linux-2.6.35.2# gcc --version
[21:17] <Akendo> gcc (Ubuntu 4.4.3-4ubuntu5) 4.4.3
[21:17] <Akendo> Copyright (C) 2009 Free Software Foundation, Inc.
[21:17] <Akendo> This is free software; see the source for copying conditions.  There is NO
[21:17] <Akendo> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
[21:17] <bjf> Akendo: ok, that looks like the stock gcc
[21:17] <Akendo> stock gcc?
[21:18] <bjf> Akendo: lucid one
[21:18] <bjf> Akendo: what "bug" are you referring to?
[21:18] <Akendo> Hm
[21:18] <Akendo> My config to compile the kernel do not work anymore
[21:19] <bjf> Akendo: then i'd suspect your config changes and no the compiler, are you saying you can't build the kernel?
[21:20] <Akendo> I've tryed to compile the 2.6.35.2 but now getting after a successfully compiling the errror during the boot " no sync fs" but the same confi runns with the 2.6.34 without a doubt....
[21:21] <bjf> Akendo: have you tried using our 2.6.35 kernel?
[21:22] <Akendo> Was my first guess too, tried with complete new config :/ 
[21:22] <Akendo> hm
[21:22] <Akendo> No
[21:22] <bjf> Akendo: http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.35.3-maverick/
[21:23] <Akendo> Hm
[21:23] <Akendo> Nice :D, i will give it a try :/
[21:24] <bjf> Akendo: hold on one sec. looking for another url for you :-)
[21:24] <Akendo> Very kind of you ;-)
[21:25] <Akendo> Don't end this in a error using a kernel from a (testing) next release?
[21:26] <bjf> Akendo: I don't understand that last question
[21:27] <Akendo> If i install a kernel that is for the next Ubuntu release, shout this not made an error in the current running system? 
[21:28] <\_^_\> I hav esome questions regarding #616501.
[21:28] <\_^_\> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/616501
[21:28] <ubot2> Launchpad bug 616501 in linux (Ubuntu) "Kernel > 2.6.32-20 doesn’t boot, /dev/disk/by-uuid/... not found (affects: 1) (heat: 582)" [Undecided,New]
[21:28] <bjf> Akendo: could be that's why i'm trying to find you a different link, we have a "maverick" kernel on lts package that i'm looking for
[21:28] <Akendo> xD
[21:29] <\_^_\> Every kernel after 2.6.32-20 (Ubuntu) doesn't boot with root=UUID=.. option.
[21:29] <tgardner> bjf, http://launchpad.net/~kernel-ppa/+archive/ppa
[21:29] <bjf> tgardner: thanks!
[21:29] <Akendo> Thanks
[21:29] <\_^_\> But when I change it to root=/dev/... it works.
[21:29] <bjf> Akendo: ^
[21:29] <Akendo> i also use this
[21:30] <Akendo> There was some errors in the history with that, don't like uuid
[21:30] <Akendo> :)
[21:30] <\_^_\> The hard drive is a PATA. As far as I know there was some change regarding PATA in kernel.
[21:30] <bjf> Akendo: hmm, don't know about that issue, maybe tgardner is aware of it
[21:30] <\_^_\> However I want to find out why this happens. So where should I start investigating.
[21:31] <Akendo> I remeber this problem a time ago
[21:32] <Akendo> i guess that was why i prefer self compiled kernels
[21:33] <bjf> Akendo: the thing is, if there is an issue with that kernel, we'd like to know about it and get it fixed for everyone
[21:34] <bjf> Akendo: that way we keep the kernel up-to-date for you (you have better things to do than build kernels) :-)
[21:34] <Akendo> normaly it's just 1 min work so i dones't care. It's also easyare than running a gentoo :D
[21:35] <Akendo> essayer*
[21:35] <bjf> Akendo: so, that's my recommendation, not sure i helped you out or not
[21:35] <Akendo> we will see
[21:36] <Akendo> Was just wondering, normaly there was no problem doing it. But i has removed some old stuff an i still used the gcc-4.2 
[21:37] <Akendo> i  think after switch to a newer version, he miss something ... but not sure about :/
[21:38]  * jjohansen -> Lunch
[21:40] <Akendo> But thanks for the help
[21:45] <bjf> \_^_\: that bug has a work around specified in it, have you tried that?
[21:46] <bjf> \_^_\: comment #5
[21:48] <\_^_\> bjf: comment #1--#5 are mine. So I tried everything which is written there. ;)
[21:55] <bjf> \_^_\: so you have a workaround, i've added it to the list of bugs that the kernel team will discuss tomorrow morning
[21:57] <\_^_\> bjf: Great. Thanks. If I can do anything to help, please add a comment to my report.
[21:57] <bjf> \_^_\: will do