[02:18] <billybigrigger> anyone here know where i can start filing a bug against the gpsca/sonixj module thats built into the kernel?
[02:18] <billybigrigger> i just compiled a kernel from linus's source today, where there were a bunch of fixes to v4l and gspca, apparently fixing some bad sensor issues for this webcam
[02:18] <billybigrigger> and it's still not working, hasn't worked through the whole 2.6.31 kernel
[02:32] <Seracht> hi
[02:33] <Seracht> does anyone here have experience working with setfsuid
[02:33] <Seracht> it seems to be full of fail
[02:35] <Seracht> is there some known way to get back the current fsuid
[02:35] <Seracht> because I need to check it
[02:35] <Seracht> and if I set it, it seems to set, if my RES UIDs are 0
[02:36] <Seracht> even when I tried things like setfsuid(-5000);  and then did a setfsuid(0); I got -5000 the second time...so it went through, which is very weird
[03:16] <Seracht> um actually
[03:16] <Seracht> anyone know if the setuid invariant bug was fixed
[03:16] <Seracht> after linux 2.4.XXX?
[10:45] <Wellark> hi! what's the current situation with xen support?
[10:46] <Wellark> does jaunty server kernel support xen domu?
[13:36] <tseliot1> apw, mjg59: if I wanted to get rid of some garbage that shows up when resuming from s3 (and which goes away after resume is complete), where should I look at?
[13:58] <apw> tseliot1, the messages should be in the dmesg, so you need to identify them and look at why they are coming out
[14:02] <amitk> jjohansen: a kernel compile leaves behind ubuntu/apparmor/af_names.h and ubuntu/apparmor/capability_names.h. Can they be added to .gitignore?
[14:06] <apw> they are generated files IIRC, where is it leaving them?
[14:08] <jjohansen> amitk: as apw said they are generated files, definitely could be added to .gitignore
[14:08] <amitk> apw: yes, they are generated
[14:09] <apw> i wonder if they are being made in the right place, should they not be made in the O= directory we use in the build
[14:10] <jjohansen> yeah they should I thought I had fixed that
[14:10] <amitk> jjohansen: will you work on this or should I send a patch to add it to .gitignore?
[14:11] <jjohansen> amitk: I will fix
[14:11] <amitk> jjohansen: thanks!
[14:14] <jjohansen> amitk: is this under Karmic? and how are you building?
[14:18] <amitk> jjohansen: Karmic and building using the in-kernel build system. i.e. use a .config and 'make oldconfig;make'
[14:19] <jjohansen> amitk: okay so you are building in place
[14:19] <amitk> yes
[14:20] <amitk> I use it to quickly test my arm flavours
[14:20] <jjohansen> amitk: okay, thanks looks like I just need to add them to .gitignore then
[14:26] <rtg_> tseliot1, have you had reports of the nVidia driver randomly going into power save mode and blanking the screen? It happens to me several times a day.
[14:27] <tseliot1> rtg_: let me check
[14:31] <apw> rtg_, have been looking at the karmic delta, and there are a number of commits which add 5 drivers and others which remove two of those, which makes understanding the delta.  i have been playing with rewriting those commits to split them up so that the add and drop can be paired.  this is with a view to simplifying squashing the redundant delta when we move forward.  does that sound sane?
[14:31] <apw> understanding the delta hard.
[14:34] <rtg_> apw, I've been thinking about LL in that regard, and the amount of noise we carry in the git repo. I'm inclined to start clean and just copy the ubuntu and debian directories and commit them once.
[14:35] <apw> yeah i envision us squashing the entire config thread and all debian stuff as one
[14:35] <tseliot1> rtg_: I can't find anything about that
[14:35] <rtg_> tseliot1, ok, thanks
[14:42] <apw> rtg_, i'll put an email together and push it to the list on this
[14:42] <rtg_> apw, how come 2.6.28-rc1 got rebuilt?
[14:43] <apw> not rebuilt, but built for the first time
[14:43] <rtg_> ah
[14:43] <apw> 2.6.28 was before we started doing them automatically, so we have none for that gap, and smb wanted one for a bisection
[14:43] <apw> so it got requested
[14:44] <gnarl> Just updated the bug report with that
[15:16] <rtg_> amitk, pushed http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-karmic.git;a=commit;h=20268b66870d83d86574d22ee32f654d02996599
[15:17] <amitk> rtg_: sure. ABI and module lists is a don't-care right now.
[15:19] <rtg_> amitk, should I just push an ABI ignore as well?
[15:20] <amitk> rtg_: if armel is the only one causing an ABI bump for the next upload, sure.
[15:21] <rtg_> amitk, I imagine with all of your pending patches, there is bound to be an ARM ABI change
[15:22] <amitk> probably
[15:22] <bjf> rtg_, I'm also close to having a huge pile of Marvell patches to submit for Karmic
[15:23] <rtg_> amitk, bjf - OK, I'll preempt build failures by updating that last push with an ABI ignore
[15:25]  * amitk pictures apw and rtg running to avoid getting buried like in a bad Roland Emmerich movie 
[16:27] <bjf> ****************************************************
[16:27] <bjf> ** What:  Ubuntu Kernel Team Meeting
[16:27] <bjf> ** When:  Today, 17:00 UTC
[16:27] <bjf> ** Where: #ubuntu-meeting
[16:27] <bjf> ** Who:   Everyone is invited
[17:55] <bjf> >
[17:55] <bjf> > Ubunt kernel team meeting starting in 5 minutes in #ubuntu-meeting
[17:55] <bjf> >
[17:55] <bjf> Ubuntu even