[00:38] <kees> jjohansen, arjan: I will now get out of this communication loop.  ;)
[00:39] <arjan> hehe thanks
[00:39] <jjohansen> arjan: I have kicked off a debug kernel build for you, I'll ping you when its done
[00:39] <arjan> all I need is the drivers/acpi/processor-idle.o file
[00:40] <arjan> http://www.kerneloops.org/oneweek31.php
[00:40] <arjan> that is currently mostly ubuntu reports (until Fedora 12 ships I suspect.. then it'll be amix)
[00:40] <arjan> looking at the nr 2 issue
[00:41] <arjan> and failing to make sense out of it without knowing exactly which instruction we're executing
[00:41] <arjan> -> hence the request for vmlinux or drivers/acpi/processor-idle.o
[00:45] <jjohansen> arjan: okay, I just build that then, it will be quicker
[00:57] <jjohansen> arjan: http://kernel.ubuntu.com/~jj/processor_idle.o
[00:58]  * arjan grabs
[00:58] <arjan> thanks a lot!
[00:59] <arjan> ooh fun
[00:59] <arjan> this is in a paravirt hook
[01:00] <arjan> anyway that's good food-for-thought
[01:00] <arjan> thanks again
[01:00]  * arjan will ponder more after dinner ;)
[01:19] <eswenson> Is there an irc channel where I can ask a question about the ubuntu/debian kernel build environment?
[01:42] <rtg> eswenson, this is the right channel, but most folks are about gone. can you post an email to the canonical-kernel-team@lists.canonical.com list?
[01:44] <eswenson> rtg: I could, but I'm not on the kernel team.  I'm just a developer who has a need to update/add modules to a local copy of the kernel.  Can I still send email to canonical-kernel-team list?
[01:44] <rtg> eswenson, yep, I'll moderate it later tonight.
[01:45] <eswenson> rtg: And my question regards the jaunty kernel, not the karmic kernel.  Ok, I'll post the question to the list.  THanks.
[06:42] <indus_> hello
[09:19] <Appiah> On launchpad bugs , should the team be the ones selecting confirmed and priotrity?
[09:19] <Appiah> or the team?
[09:19] <Appiah> or the user* i mean
[10:57] <JanC> Appiah: confirmed is if other people can reproduce the same bug, so it can be another user
[10:57] <JanC> priority is for the developers (or team managers or such)
[10:58] <JanC> never confirm your own bugs though ;)
[11:07] <apw> Appiah, yeah what JanC said ... the priority is covered by our 'policy' so data loss is critical, crashes are high or medium etc
[11:07] <apw> the status implies things about the bug, co
[11:08] <apw> confirmed for more than one user, trigaged for 'having all the data we need' etc
[11:09] <hyperair> does anyone know if there's a difference between the sreadahead and the ureadahead kernel patches?
[11:10] <hyperair> and how come the said patches aren't entering mainline?
[11:20] <apw> hyperair, yes the patches differ.  and as it says in the leader to those patches, we are expecting a more sane common and standard way to trace all syscalls via ftrace which would superceed most of the patch
[11:21] <hyperair> @_@
[11:21] <hyperair> i see
[11:22] <hyperair> you really meant header and not leader, right?
[11:22] <apw> those words mean the same thing to me for patches ... :) ... the description of the patch
[11:23] <hyperair> are you sure "leader" can be used in this context?
[11:23] <hyperair> "leader" applies to a person who leads, right?
[11:23] <apw>     It's not upstream because it will need to be rebased onto the syscall
[11:23] <apw>     trace events whenever that gets merged, and is a stop-gap.
[11:23] <apw> a leader is something or someone who leadsd
[11:23] <apw> the header arrives in your eyes first, so i can be called a leader
[11:23] <apw> english is stupid
[11:24] <apw> you get a similar confusion with rider, a rider can be someone who rides or it can be something which is carried with and is a bout something, like a limitation
[11:25] <hyperair> @_@
[11:25] <hyperair> alright, point taken
[11:25] <apw> hyperair, apparently we have 12 meanings for leader
[11:25]  * hyperair groans
[11:25] <apw> 1. 	a person or thing that leads.
[11:25] <apw> is the one i was using it in
[11:25] <hyperair> ah
[11:26] <apw> you don't need to remind me that english is massivly ambigious even to native speakers and a nightmare for the rest of the world :/
[11:26] <hyperair> so anyway, what does ureadahead require that the sreadahead patch doesn't provide?
[11:26]  * hyperair considers himself to be a native speaker of english
[11:26] <apw> it needs to know which binaries you are running
[11:27] <hyperair> ah i see
[11:28] <hyperair> well then off i go to hack the ureadahead patch to apply ontop of sreadahead's
[11:29] <apw> hyperair, why so?
[11:29] <hyperair> apw: i compile and run the zen kernels. they have the sreadahead patch applied.
[11:29] <hyperair> but not the ureadahead one
[11:30] <hyperair> maybe i'll go suggest to them
[11:30] <apw> well we are expecting to switch out sreadahead for ureadahead at the same time that the kernel updates
[11:30] <apw> and i assume xen is a patch on top of our main branch
[11:30] <apw> so they should switch when they rebase
[11:31] <hyperair> zen, not xen.
[11:31] <apw> ... oh yeah ... no idea :)
[11:31] <hyperair> heh
[11:31] <hyperair> and no, zen isn't a patch..
[11:31] <apw> what the heck is zen
[11:31] <hyperair> it's a tree
[11:31] <hyperair> http://www.zen-kernel.org/
[11:31] <hyperair> it's the mainline with all kinds of unapproved extras applied
[11:32] <hyperair> stuff like phc, bfs, tuxonice
[11:32] <hyperair> and they frequently pull from mainline
[11:32] <apw> gotcha
[11:33] <apw> so you'd want them to have 'both' so you can use that kerenl with ubuntu userspace i assume
[11:33] <hyperair> but of course
[11:33] <apw> sounds like fun for them :)
[11:33] <hyperair> heh
[11:33] <hyperair> well the ureadahead patch isn't much on top of the sreadahead patch, is it?
[11:33] <hyperair> i only had one conflict
[11:34] <hyperair> and that conflict was from stuff already added by sreadahead
[11:34] <apw> i think it produces more data for the existing sreadahead hook iirc
[11:34] <hyperair> yeah it does
[11:34] <apw> dunno how sreadahead would take that change
[11:34] <hyperair> isn't it a different ftrace?
[11:34] <apw> to be honest sreadahead has major issues, like its not aware of hdd ... so it makes things worse there
[11:35] <hyperair> agreed
[11:35] <hyperair> my boot up time is 2m 30s
[11:35] <hyperair> this is ridiculous
[11:35] <hyperair> readahead-list was way better
[11:35] <hyperair> why did we get rid of that?
[11:35] <apw> yeah ... it was ... and ureadahead is fixing that and doing better
[11:36] <apw> was where the majority were going, and probabally was wrong
[11:36] <hyperair> yeah, at least we don't need readahead-list wasting time setting up inotify hooks on every single file on the filesystem >_>
[11:36] <hyperair> there was quite some noise made re readahead-list's removal, but somebody said that sreadahead's packfile was equivalent if not better <_<
[11:37] <hyperair> and conveniently stifled out all the noise by invalidating said bug
[11:37] <hyperair> very elegant.
[11:40] <apw> heh ... sometimes you need to try things, find its wrong, and fix it
[11:40] <apw> i think thats what happened here
[11:42] <hyperair> heh i suppose =\
[11:44] <hyperair> aw damnit it won't compile
[12:14] <Appiah> JanC and apw thanks for the explaination
[12:18]  * hyperair reverted every sreadahead commit on the list and then applied the ureadahead patch
[14:31] <michLinuxGuy> Hi!
[14:31] <apw> s'up
[14:32] <michLinuxGuy> Question: How do I install an older pre-built kernel on Karmic.  (Like the kernel used in Jaunty) ???
[14:32] <michLinuxGuy> I am trying to troubleshoot a failing wireless adapter
[14:32] <apw> older kernels are available in the launchpad librarian, i blieve all of them are there
[14:33] <michLinuxGuy> Do I get to that from synaptic?  Or can you give me a URL?
[14:33] <apw> you can get to the current ones at least here: https://edge.launchpad.net/ubuntu/+source/linux
[14:34] <michLinuxGuy> Thanks!
[14:34] <apw> this link looks to show you _all_ kernels ever: https://edge.launchpad.net/ubuntu/+source/linux/+publishinghistory
[14:36] <michLinuxGuy> I have a Linksys USB wireless adapter that won't connect now that I installed Karmic.  It worked fine with Jaunty.  I'm going to try the Jaunty kernel with my karmic installation.  Does that sound like a good approach to diagnosing this?
[14:36] <apw> michLinuxGuy, yep ... what device is it inside?
[14:37] <michLinuxGuy> ID 13b1:000d Linksys WUSB54G Wireless Adapter
[14:38] <michLinuxGuy> I tried the adapter on another machine with karmic and it did work, but dropped and reconnected once.
[14:38] <apw> odd
[14:39] <michLinuxGuy> Yeah.  This was with a clean install.  I could try reinstalling, but I think I will try the older kernel first.
[14:40] <michLinuxGuy> The problem machine is an older HP laptop: ze4210
[14:44] <michLinuxGuy> apw: Are the links you showed me source only?  Is it possible to get a prebuilt .deb file with the kernel and modules?
[14:46] <apw> michLinuxGuy, binary packages appear to be there if you click trhough the build links for an architecture
[14:53] <michLinuxGuy> I guess I am not as smart as I thought I was.  I can't quite find what I need to install an older kernel from binary.  :(
[14:57] <michLinuxGuy> To install a binary kernel, do I just need an image .deb and a .deb containing the kernel modules?
[15:06] <apw> michLinuxGuy, the linux-image contains the whole kernel, if you have any binary drievers you also nead the linux-headers, and the generic headers the _all package which is only built on i386
[15:10] <michLinuxGuy> apw: Thanks for all your help.
[15:19] <michLinuxGuy> apw: I installed kernel linux-image-2.6.28-16-generic_2.6.28-16.55_i386.deb and my linksys USB wireless adapter started working again.  Do you have advice on what I should do with this information?
[15:21] <apw> file a bug using ubuntu-bug when you are booted on the karmic broken kernel.  include a dmesg from the working kernel
[15:21] <apw> and clearly mark that dmesg, and clearly indicate the version you found it does work 
[15:22] <michLinuxGuy> apw: Thanks, I'll do that.  One note: the symptom is it finds the access pt, but never connects and times out.  I didn't see anything informative in the dmesg output about it.
[15:24] <apw> but having both tells us if the same driver picked up the device and the like
[15:24] <michLinuxGuy> apw: Okay - will do.  Thanks!
[16:51] <michLinuxGuy> apw: I submitted a bug for the problem [Bug 472953].  Thanks again for your help with this.
[16:51] <ubot3> Malone bug 472953 in ubuntu "Linksys WUSB54G won't connect to wireless network with karmic kernel" [Undecided,New] https://launchpad.net/bugs/472953
[18:59] <tormod> is the Mainline Kernel PPA source web-browseable somewhere like with cgit?
[21:59] <cwillu> tormod, it's just the vanilla kernel, so kernel.org
[22:03] <tormod> cwillu, thanks, right, I guess that's the whole point of the PPA :) but there is some Ubuntu building stuff like a debian dir?
[22:05] <cwillu> can't speak to that, sorry :p
[22:05] <tormod> btw there is 2.6.32-rc6 now
[22:07] <tormod> is the daily ppa build exactly like the upstream "snapshot" or is it a pull from linus tree at some time of day?
[22:08] <cwillu> I would guess that it's a package for each tagged upstream release
[22:09] <tormod> yes, but plus the daily builds
[22:09] <cwillu> sorry, missed that
[22:09]  * cwillu clams up
[22:09] <tormod> thanks for answering
[23:45] <_maks> hey
[23:45] <_maks> the gitweb installation on kernel.u.c seems quite old
[23:45] <_maks> what's the refspec to clone http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid.git;a=summary
[23:47] <_maks> git clone git://kernel.ubuntu.com/ubuntu/ubuntu-lucid.git # works
[23:47] <_maks> would be cool to have that on gitweb ;)