[01:48] <DanaG> hmm, anyone know why the kernel-ppa stuff hasn't been updated in a while?  the only 34-rc2 kernel there says "karmic" specifically, and the same is true of the latest drm-next kernel there.
[01:49] <DanaG> Does it matter that it says "karmic", if I want to use it on Lucid?  I've seen it matter before, on ARM, at least.... try a karmic kernel with lucid userspace, it doesn't boot.
[02:03] <JanC> I guess "karmic" means it was compiled with karmic's configuration file?
[02:06] <DanaG> beats me.  I'm about to try the drm-next "karmic" kernel.
[02:06] <DanaG> I've also noticed that the kernel-ppa kernels all have the STAGING dir entirely disabled... as well as MMC_RICOH_MMC
[02:07] <DanaG> Something about "symbol 'm' not valid for ... "
[12:55] <nosse1> How do I build a (fresh git) kernel when I dont have the debian/ dirs installed and get it installed on the system (preferrably via a deb-file)
[12:55] <nosse1> Will make-kpkg handle that?
[13:09] <smb> preferably (if you don't want to use git) by apt-get source linux-image-2.6.x-y-generic which gives you the kernel source including the debian dirs
[13:11] <nosse1> smb: I can't use the ubuntu source, as there are none for my target, so I need to go with a 3rd part kernel branch.
[13:11] <nosse1> So I have the kernel source and a working config, but I need to wrap this into ubuntu-world
[13:13] <smb> You could clone the git tree and copy the debian* dirs into your tree
[13:13] <nosse1> smb: Thats all that's needed? What happens to my local kernel config?
[13:14] <smb> nosse1, You would need to see how you get it integrated with debian.master/configs/...
[13:17] <smb> nosse1, Maybe it does work with make-kpkg but I never use that
[13:17] <nosse1> smb, I'm trying to integrate debian* right now.
[13:18] <nosse1> smb, What do you do to compile kernels then?
[13:19] <smb> nosse1, I only do the Ubuntu kernels. No need for me to do anything special. :-P
[13:19] <nosse1> But you use make-kpkg to build them, right?
[13:20] <smb> nosse1, No. Either debuild, or dpkg-buildpackage or fakeroot debian-rules ... when I am in a hurry
[13:21] <nosse1> OK, thanks
[13:46] <mozmck> smb: did you see my post here about the kernelconfig script not working because DROOT is not defined?
[13:47] <smb> mozmck, I cannot recall it. Where did you post it?
[13:47] <mozmck> here on IRC a couple days ago.
[13:47] <mozmck> To fix it here I just added DROOT=debian to debian/debian.env
[13:48] <mozmck> this is in the lucid git tree
[13:48] <smb> IRC is quite prone to loose things. But on Lucid debian.env should be always set
[13:48] <smb> Are you using a special tree?
[13:49] <smb> Actually it should be debian.master which it points to
[13:49] <mozmck> no
[13:50] <smb> ~/src/ubuntu-lucid/kernel$ cat debian/debian.env 
[13:50] <smb> DEBIAN=debian.master
[13:50] <mozmck> I'm using kernel.ubuntu.com/ubuntu/ubuntu-lucid.git
[13:51] <mozmck> yes, but DROOT is used in the kernelconfig script and is not defined anywhere.
[13:51] <mozmck> this is both on karmic and in 10.04 beta1
[13:53] <mozmck> and looking at the kernelconfig script, line 29 is bindir="`pwd`/${DROOT}/scripts/misc"
[13:53] <smb> which script are you talking about?
[13:53] <mozmck> so I figured DROOT had to be 'debian'
[13:53] <smb> ok found it
[13:54] <smb> apw, Is that meant to be called directly
[13:55] <apw> mozmck, smb, nope thats not menat to be run directly
[13:55] <mozmck> all the instructions I found have you call "kernelconfig editconfig" to edit the configs.  this worked on karmic fine but not in lucid
[13:55] <apw> its used from debian/rules updateconfigs and the like
[13:55] <mozmck> so how are you supposed to edit the configs now?
[13:55] <apw> where are those instructions?  they are wrong
[13:55] <smb> Right, where does it say to call it directly?
[13:55] <apw> debian/rules editconfigs would make sense
[13:55] <smb> yep
[13:56] <apw> and should work for all releases too
[13:56] <smb> mozmck, To call "debian/rules editconfig" was always the intended way
[13:57] <mozmck> http://blog.avirtualhome.com/2009/11/03/how-to-compile-a-kernel-for-ubuntu-karmic/
[13:57] <mozmck> That's linked to from here: https://help.ubuntu.com/community/Kernel/Compile
[13:57] <apw> yay ... random community randomness
[13:57] <Keybuk> https://wiki.ubuntu.com/KernelTeam/KernelForIdiots ;-)
[13:58] <apw> Keybuk, heh yeah i like that one better :)
[13:59] <mozmck> I see.  It seems quite hard to find good information on this subject!
[13:59] <apw> i wonder if we should rename that dummies :)
[13:59] <apw> mozmck, mostly because there is such a lot of bad information out there
[13:59] <mozmck> I've seen that link, but it doesn't mention editconfig, and I am a dummy so I need menuconfig :)
[14:00] <apw> do feel free to help us make the ForIdiots page better ... Keybuk only did the bits he needed :)
[14:01] <mozmck> oh, ok! I forget I can change those pages.
[14:01]  * apw adds a comment to the random blog telling them they are wrong :)
[14:01] <mozmck> thanks for the help.
[14:01] <Keybuk> it's basically where I put notes so I don't have to keep rediscovering them each time
[14:03] <mozmck> is there a way to tell it to just edit the config for one flavour or do you just have to step through them all?
[14:03] <Keybuk> I just tend to edit the config file itself
[14:03] <Keybuk> then use updateconfigs to fill in the bits I missed
[14:03] <apw> mozmck, no you have to step through them all with that interface
[14:04] <mozmck> ok
[14:04] <apw> yeah mostly i am in bulk update mode and want to do them all at once, so i tend to do the update by adding things to the toplevel common files and doing an updateconfigs
[14:06] <mozmck> I'm working on a custom flavour with rtai patches for running CNC machines with EMC2, so I just add and change settings for that one flavour.
[14:10] <mozmck> 'debian/rules editconfig' -> make: *** No rule to make target `editconfig'.  Stop.
[14:11] <mozmck> 'debian/rules editconfigs' -> dh_testdir: cannot read debian/control: No such file or directory
[14:11] <Keybuk> mozmck: fakeroot debian/rules clean first
[14:11] <mozmck> ah, that works
[14:11] <mozmck> thanks
[16:02] <bjf> ##                                                                                     
[16:02] <bjf> ## Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting                    
[16:02] <bjf> ##      agenda: https://wiki.ubuntu.com/KernelTeam/Meeting                             
[16:02] <bjf> ##                                                                                     
[16:57] <IdleOne> ogasawara: Congrats!!! awesome,incredible,great news :D
[16:57] <ogasawara> IdleOne: thanks!
[17:27] <cnd> apw: I'm interested in cleaning up the linux-firmware-nonfree package, partially to learn more about packaging
[17:27] <cnd> rtg is gone for a bit, and I'd like my changes to get into lucid
[17:27] <cnd> would you be able to review them?
[17:53] <apw> cnd sure thing
[18:00] <ogasawara> apw: https://launchpad.net/~leannogasawara/+archive/ppa/+build/1590208/+files/buildlog_ubuntu-lucid-i386.linux_2.6.34-1.1~oga2_FAILEDTOBUILD.txt.gz
[18:12] <JFo> bug 507416
[18:12] <ubot3> Malone bug 507416 in linux-fsl-imx51 "CONFIG_NEON=y causes platform lockups with certain application/platform combinations" [Medium,Fix committed] https://launchpad.net/bugs/507416
[18:14] <smb> JFo, That should be ok as far as I know, they just don't bother update their bug status. :/
[18:14] <JFo> ok :)
[18:33] <crimsun> pgraner: JFo: could you ping Jane S and ask her permission to put a Reported-by in the git changelog for LP 551606, 548661?
[18:34] <crimsun> (ideally an e-mail address, too, but I understand if she doesn't want it in the kernel changelog)
[18:35] <JFo> crimsun, will see what I can do about that. :)
[18:35] <bjf> crimsun, you're doing an upstream fix for 551606?
[18:37] <crimsun> bjf: yes, I'm about to push the button on git commit -e -a -s
[18:38] <bjf> crimsun, ok, you are doing a quirk for her SSID?
[18:38] <crimsun> bjf: no, for all models using that quirk; I'll attach the diff
[18:39] <bjf> crimsun, ack
[18:39] <crimsun> bjf: also, I believe I have a fix for her hp mute issue, but there are at least two further debugging steps necessary, one of which requires rolling a new alsa-driver snap (I'll attach a diff to 548661 if the first option is insufficient)
[18:41] <bjf> crimsun, when does takashi "release" new alsa-driver versions? is there a schedule or just when he feels things are "right"
[18:42] <crimsun> bjf: he doesn't generally roll those; Jaroslav tends to push the buttons
[18:42] <bjf> crimsun, ah, ok
[18:43] <cnd> apw: while I work with #launchpad to figure out the merge request, feel free to review the last four commits at https://code.launchpad.net/~chasedouglas/lucid/linux-firmware-nonfree
[18:51] <crimsun> smb: do you know when the window for 2.6.32.11 closes? I have possibly two more patches to push to stable (both Jane S's bugs), and I'd like to get them in if feasible.
[18:52] <JFo> I think it is tomorrow morning iirc
[18:52] <JFo> but I defer to smb
[18:52] <smb> crimsun, Not for sure. Normally this amount of activity I would say he might close on Friday
[18:52] <JFo> ah, see I was wrong ;-)
[18:52] <smb> crimsun, But sometimes he is quicker.
[18:52] <crimsun> smb: JFo: ok, thanks
[18:53] <smb> JFo, ITs hard to say. I have not really found a regular schedule in Greg. 
[18:53] <JFo> true, I was thinking of something else entirely I am sure
[18:58] <cnd> apw: ignore my previous bzr branch, I figured out the merge process, so use it instead please
[19:02] <bjf> apw, can you comment on crimsun question ^^
[19:06] <crimsun> (actually I'm awaiting on her ack to submit the first patch :-)
[19:06] <crimsun> awaiting her *
[19:38] <rackerhacker> jjohansen: have you had reports of a microtime issue in linux-ec2?
[19:38] <rackerhacker> i couldn't find a relevant bug
[19:39] <jjohansen> hrmm, not any that I have heard of
[19:39] <jjohansen> what are you seeing?
[19:39] <rackerhacker> lemme slip it into pastie right quick
[19:39] <rackerhacker> http://pastie.org/895689
[19:41] <rackerhacker> jjohansen: here's a normal karmic server (bare metal, not in a VM): http://pastie.org/895692
[19:41] <rackerhacker> which is more of what i'd expect
[19:42] <rackerhacker> if i pop in an old hardy 2.6.24 kernel, all is well
[19:43] <rackerhacker> domU w/2.6.24-23 -> http://pastie.org/895696
[19:44] <rackerhacker> it's not perfect in 2.6.24, but it's worse in linux-ec2 from lucid
[19:44] <rackerhacker> but it could be a silly kernel config on my part
[19:45] <jjohansen> hrmm, well that does look odd, I'll have a look and run a few tests
[19:46] <rackerhacker> i can set you up on one of our environments if that'd help
[19:48] <jjohansen> rackerhacker: sure, that would be worth snooping at
[19:49] <rackerhacker> gimme a second to get one rolling
[20:43] <rackerhacker> jjohansen: want me to pile the details into a launchpad bug?
[20:59] <soren> rackerhacker: Just for giggles, could you try booting a machine with clocksource=acpi_pm and run the same test?
[20:59] <soren> rackerhacker: (A physical machine, that is)
[21:00] <rackerhacker> a physical machine running linux-ec2?
[21:00] <soren> rackerhacker: Running the same as the machine in http://pastie.org/895689 was running.
[21:01] <rackerhacker> soren: that particular example was within a domU
[21:01] <soren> rackerhacker: Sorry, wrong pastie.
[21:01] <soren> rackerhacker: http://pastie.org/895692 this one.
[21:02] <rackerhacker> let me see if i can spare that machine for a moment ;-)
[21:26] <jjohansen> rackerhacker: hrmm, not yet.  I haven't been able to replicate on EC2, I have run through 10 different instance size/kernel combinations and every one was good.  I haven't tried your config on EC2 yet though
[21:32] <rackerhacker> jjohansen: you might be right, soren walked over and gave me a run down
[21:35] <JFo> crimsun, thumbs up from Jane
[21:35] <JFo> crimsun, 
[21:35] <JFo> That's fine - I have no problem with my name and/or email going in there.
[21:35] <JFo> thanks,
[21:35] <JFo> Jane
[21:44] <rackerhacker> jjohansen: call off the search, soren just beat me up with some knowledge
[21:44] <rackerhacker> it turns out i was using clocksource=jiffies
[21:44] <rackerhacker> soren's suggestion of clocksource=acpi_pm fixed it immediately
[21:44] <jjohansen> ah, yeah that can cause so problems
[21:45] <rackerhacker> soren also says hello
[21:45] <jjohansen> yeah, say hi to soren for me too
[21:46] <rackerhacker> can do
[21:46] <rackerhacker> jjohansen: i owe you three cases of beer at this point
[21:46] <rackerhacker> my tab is increasing :/
[21:46] <jjohansen> hehe, not at all
[21:47] <jjohansen> after all soren fixed this problem :D
[21:47] <rackerhacker> other than acpi_pm being a little more expensive than jiffies, should i be worried about anything?
[21:51] <jjohansen> rackerhacker: not really it is consider the best practice to use acpi_pm on more modern kernels
[21:52] <soren> rackerhacker: Just make sure you keep proper time on the host.
[21:55] <rackerhacker> soren: can do
[21:55] <rackerhacker> jjohansen: thanks ;)
[21:56] <jjohansen> np
[21:56] <jjohansen> :-)