[09:37] <Kano> apw: is rc3 compiling already?
[09:41] <apw> Kano, very likely, they are completly automated, i don't start them
[09:42] <Kano> well the tag was 6h ago...
[09:42] <apw> yep and they are built daily at about 9am UTC
[09:42] <apw> that is when build resources are available
[09:43] <Kano> ah
[09:43] <Kano> is the build script available?
[09:44] <apw> yep in the kteam-tools git repository on zinc
[09:44] <Kano> zinc?
[09:45] <apw> kernel.ubuntu.com
[09:45] <Kano> http://kernel.ubuntu.com/git?p=ubuntu/kteam-tools.git;a=summary
[09:45] <Kano> those then
[09:45] <apw> quite why you need them so urgently however is beyond me
[10:19] <darren> g'day people, I think I have a kernel bug, and reading the kernel bug reporting process it says to test the "latest development Ubuntu kernel version", but I'm not sure what and where that is, anyone able to help?
[10:21] <smb> darren, That would currently mean, is that bug still in the Natty kernel. 
[10:22] <smb> Which is a 2.6.38 based one. If it is simple to reproduce/test you may use a life cd or usb stick
[10:23] <darren> yes but what is it, is it a package I can find somewhere is it a tag in a git tree somewhere ?
[10:24] <darren> or is a snapshot of the latest live cd the only way to get it ?
[10:25] <smb> The kernel on its own is a package: So you can get it from the archive, launchpad (https://launchpad.net/ubuntu/+source/linux/+publishinghistory) or the right git tree (git://kernel.ubuntu.com/ubuntu/ubuntu-natty.git)
[10:26] <smb> Currently the latest Natty kernel is: https://launchpad.net/ubuntu/natty/+source/linux/2.6.38-1.28
[10:26] <darren> Cool thanks.
[10:27] <darren> also will I have any problems running a Natty kernel on Maverick ?
[10:29] <smb> One cannot completely say no, but afaik there are people doing that already. But I would not say that you will not have any problems.
[10:31] <darren> ok so it can work but might not.
[10:32] <smb> right. I don't know of any problems yet but there might be. X could have some dependencies unknown or there have been LVM userspace problems in the past with Hardy
[10:37] <smb> darren, One thing to keep in mind is to install linux-headers*all*, linux-headers-*<your flavour (like generic)>* and linux-image-*<your flavour>* together. That way you have the headers required for any dkms packages (for example the ati or nvidia binary drviers)
[10:37] <darren> hmm ok
[10:39] <darren> also before I spend too much time playing with this. When I got the latest maveric kernel my network card stopped working, but when I boot into the older 2.6.35-24 kernel it seems to work fine. Is there anything else that changes when I choose a different kernel from the grub list that I should look at ? or is the kernel the only thing that will be different?
[10:41] <smb> darren, Mainly the kernel. But there are a few things depending on it: like the initrd or if you have installed backports modules those need to go along
[10:42] <smb> one things to check would be whether your network card's module came from backports. "modinfo <module>" shows the path it comes from
[10:45] <darren> so if it is a backport the filename: will have backports somewhere in the path ?
[10:46] <smb> Unfortunately not but it will have an "update(s)" in it instead of "kernel"
[10:46]  * smb cannot remember whether it was update or updates
[10:47] <darren> well I can't see either, so I guess it is not a backport
[10:49] <smb> right, so it sounds like this is a regression in the last update. 
[10:49] <apw> for regressions in updates we are most keen to know which version you had before
[10:49] <smb> (in the bug report)
[10:50] <apw> darren, sounds like we need a bug against 'linux' and when answering say its a 'regression-update'
[10:50] <apw> run ubuntu-bug linux, that will ask you about the issue including if it is a regression
[10:52] <darren> should I try the natty daily build before submitting a bug ?
[10:52] <apw> darren, i would get the bug filed as you want to be running the broken kernel if possible
[10:54] <darren> "want to be running the broken kernel" well I can run it, but can't submit the bug from it because I can't network
[10:54] <apw> darren, well indeed depends if you have another option, for example i have wireless and wired on most of mine
[10:55] <apw> if you can't you can't
[10:55] <apw> then file it aginst the last working one, and add dmesg at least from the broken one
[10:55] <apw> and say very clearly you are in the working one
[11:00] <bdrung> was v4l removed from the natty kernel?
[11:04] <darren> ok thanks for the help guys
[11:05] <RAOF> bdrung: Yes.
[11:05] <RAOF> bdrung: Or, rather, it's removed upstream, so it's removed in the natty kernel.
[11:05] <bdrung> RAOF: that explains why the v4l plugin of vlc wasn't build
[11:06] <RAOF> Indeed it does.  Also, why xserver-xorg-video-geode FTBFS.
[12:11] <boban_> im having problems with PAE kernels
[12:11] <boban_> anyone to help me reporting bugs?
[12:12] <boban_> I have HP Probook 4520s with 4GB of RAM
[12:13] <boban_> System normaly goes to suspend to ram
[12:13] <boban_> but when i try to power it up, it starts up as it was powered off
[12:13] <boban_> any sugestions?
[12:16] <boban_> any1?
[12:33] <diwic> boban_, for reporting bugs, try the "ubuntu-bug linux" terminal command
[12:33] <boban_> i see
[12:33] <diwic> boban_, is it only happening with the PAE kernel?
[12:34] <boban_> but the isue is only for .37 and .38 PAE kernels
[12:34] <diwic> boban_, I have a 4520s with 3GB here and haven't experienced the problem you're described.
[12:34] <boban_> i see
[12:34] <diwic> boban_, but then I haven't tried the PAE kernel, only i386-generic and amd64
[12:34] <boban_> Issue is only with .37 PAE kernel
[12:34] <boban_> i386 and amd64 works just fine
[12:35] <diwic> boban_, see https://wiki.ubuntu.com/DebuggingKernelSuspend for some initial instructions 
[12:35] <boban_> i have read those pages
[12:35] <diwic> and see if you get something fun out of it
[12:35] <diwic> ok
[12:35] <boban_> i might just fill bug
[12:35] <diwic> ok
[12:35] <boban_> thank u anyway
[12:42] <Kano> has anybody a fix for fglrx + 38rc3?
[14:23] <apw> herton, yay ... 
[14:23] <herton> hello guys
[14:24] <JFo> hi herton :)
[14:37] <apw> commit 5ef41308f94dcbb3b7afc56cdef1c2ba53fa5d2f
[14:37] <apw> Author: Dan Rosenberg <drosenberg@vsecurity.com>
[14:37] <apw> Date:   Fri Nov 12 12:44:42 2010 -0800
[14:37] <apw>     x25: Prevent crashing when parsing bad X.25 facilities
[14:46] <charlie-tca> JFo: any bugs in particular for the KernelBugDay?
[14:47] <JFo> charlie-tca, looking at bugs in the New state today
[14:47] <charlie-tca> Okay, I will look too, then
[14:47] <JFo> mainly interested in making sure they reflect the apropriate status
[14:47] <JFo> Thank you sir :)
[14:47] <charlie-tca> Thank you
[14:50] <tgardner> herton, what is you Launchpad ID. I need to add you to some teams.
[15:00] <herton> tgardner: herton
[15:23] <sforshee> bzr branch lp:~utouch-team/utouch/ntrig-calibrator
[15:23] <sforshee> apw: ^
[15:24] <apw> apw@dm$ bzr push lp:~apw/utouch/ntrig-calibrator
[15:24] <apw> Created new branch.                                    
[15:50] <bjf> herton, welcome
[15:59] <herton> thanks brad
[16:00] <bjf> ##
[16:00] <bjf> ## Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[16:00] <bjf> ##      agenda: https://wiki.ubuntu.com/KernelTeam/Meeting
[16:00] <bjf> ##
[16:09] <sconklin> https://kernel-tools.canonical.com/srus.html
[16:26] <quup> hi, when I try to follow this tutorial: https://help.ubuntu.com/community/Kernel/Compile I get 
[16:26] <quup> $ debian/rules updateconfigs
[16:26] <quup> dh_testdir;
[16:26] <quup> dh_testdir: cannot read debian/control: No such file or directory
[16:27] <quup> is there some way to fix this?
[16:28] <tgardner> quup, do 'debian/rules clean' first
[16:30] <bjf> quup, you could try: https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
[16:31] <quup> bjf: oh that looks a bit more up to date
[16:32] <bjf> JFo, you will be attending the meeting ?
[16:32] <JFo> yessir
[16:34] <JFo> bjf, need me to do anything special?
[16:34] <bjf> JFo, nope
[16:34] <JFo> k
[16:51] <bjf> ##
[16:51] <bjf> ## Kernel team meeting in 10 minutes
[16:51] <bjf> ##
[16:52]  * JFo is ready
[17:26] <bjf> JFo, your meeting report "Release Metrics", the "Lucid Updates Bugs" line is missing the trailing "[17:26] <JFo> gah, sorry about that bjf
[17:26]  * JFo fixes
[17:26] <bjf> np
[17:28] <bjf> http://www.amazon.com/gp/product/B0037H9P4A/ref=oss_product   the essential kernel team debugging tool !
[17:28] <JFo> oooh
[17:28] <JFo> I was thinking it was a pitcher :)
[17:33] <JFo> bjf, we need one of these http://www.kegclub.com/
[17:33] <bjf> HEHE
[17:41] <rtdos> just curious: is there a reason there has been more of a significant increase in system requirements in recent releases of ubuntu than in previous versions?
[17:43] <apw> kees, how often do you merge back the kernel cve traacker?  all my pages seem to be at least days out of date
[17:43] <kees> apw: I can do it now, one sec.
[17:45] <tgardner> apw, http://people.canonical.com/~ubuntu-security/cve/pkg/linux.html
[17:45] <kees> active/CVE-2010-3699: bad line '	The vulnerability described by CVE-2010-3699 probably exists, but I've' (need more than 1 value to unpack)
[17:45] <ubot2> kees: The backend driver in Xen 3.x allows guest OS users to cause a denial of service via a kernel thread leak, which prevents the device and guest OS from being shut down or create a zombie domain, causes a hang in zenwatch, or prevents unspecified xm commands from working properly, related to (1) netback, (2) blkback, or (3) blktap. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3699)
[17:45] <ubot2> kees: The backend driver in Xen 3.x allows guest OS users to cause a denial of service via a kernel thread leak, which prevents the device and guest OS from being shut down or create a zombie domain, causes a hang in zenwatch, or prevents unspecified xm commands from working properly, related to (1) netback, (2) blkback, or (3) blktap. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3699)
[17:45] <kees> you can't use tabs. :P
[17:45] <kees> it's a single space there...
[17:46] <kees> (do you use "check-syntax" before committing?)
[17:46] <kees> also, "Ubuntu-Description" is literally for the USN. anything else should go in Notes
[17:47] <kees> tgardner: ^^
[17:47] <tgardner> kees, egads
[17:48] <apw> tgardner, but it is so easy to use
[17:48] <tgardner> apw, indeed
[17:50] <kees> http://people.canonical.com/~ubuntu-security/cve/pkg/linux.html should be updated
[18:11] <JFo> <-need food
[18:59]  * tgardner --> lunch
[19:16] <bjf> JFo, the script that generates: http://reports.qa.ubuntu.com/reports/jfo/kernel-buglist-by-team.html is that checked in somewhere ?
[19:18] <JFo> yessir
[19:19] <JFo> one sec
[19:19] <JFo> bjf https://code.launchpad.net/~canonical-qa/canonical-qa-tracking/main
[19:19] <JFo> it is in the misc-scripts dir
[19:23] <bjf> JFo, which script is it in that directory ?
[19:24] <JFo> it is a pair of them
[19:24] <JFo> KernelBugListByTeam.py and kernel-buglist-by-team.py
[19:25] <JFo> they are mainly copies of Leann's script changed to create this current list
[19:25] <JFo> script/scripts
[19:26] <bjf> JFo, thanks
[19:26] <JFo> my pleasure
[19:36] <kees> tgardner: since we're not doing security updates of the arm flavors, can I mark all the arm flavors on https://wiki.ubuntu.com/Kernel/Dev/ABIPackages as "abandoned"? I'm trying to find a way to represent reality, etc.
[19:37] <tgardner> kees, works for me. I'm not gonna bother with ARM unless someone hollers.
[19:37] <kees> okay, cool
[19:38] <kees> tgardner: can we move ti-omap4 into universe for natty?
[19:38] <tgardner> kees, in fact, we ought to since its not directly supported by the kernel team.
[19:39] <tgardner> I also don't think anyone is making images from it, but I'd have to ask ogra for sure
[19:39] <ogra> huh ?
[19:39] <tgardner> ogra, kees wants to move ti-omap4 into universe
[19:39] <kees> tgardner: oh, and should I do this for linux-lts-backport-maverick too? it's not been published for -security either
[19:39] <ogra> we surely make omap4 images
[19:40] <ogra> thats our omap4 kernel, yeah
[19:40] <tgardner> kees, linux-lts-backport-maverick is officially supported and is on the 10.04.2 point release
[19:40] <ogra> what makes you want to move it to universe ?
[19:40] <ogra> its the official omap4 kernel
[19:40] <tgardner> ogra, its not getting any security updates.
[19:41] <ogra> why ?
[19:41] <kees> tgardner: ah, when will it be respun for security updates?
[19:41] <ogra> we are paid for providing them
[19:41] <tgardner> kees, as soon as maverick gets promoted it'll have all the goodness in it.
[19:41] <kees> tgardner: 2.6.35-25.44 ? it's in -security now.
[19:41] <ogra> omap4 is 18 months fully supported
[19:42] <tgardner> ogra, why is it nobody tells me this stuff?
[19:42] <ogra> tgardner, no idea
[19:42] <ogra> i thought pete knew about that
[19:42] <tgardner> ogra, cooleney has been doing the ti-omap4 maintenence
[19:43] <ogra> that didnt change
[19:43] <tgardner> ogra, well, _he_ hasn'
[19:43] <ogra> he still does it for natty
[19:43] <tgardner> ogra, he hasn't been doing security updates.
[19:43] <ogra> he is responsible for getting the ubuntu sauce on top of the linaro tree we will get now 
[19:44] <ogra> since that task was moved away from the kernel team
[19:44] <tgardner> kees, well, I guess ti-omap4 stays in main.
[19:44] <ogra> tgardner, well, i dont know who should do them but i'm sure we have to do them
[19:44] <ogra> i guess thats something pete and david should discuss somehow ;)
[19:45] <kees> tgardner: ah, so, then, what about CVEs on the maverick ti-omap4?
[19:45] <tgardner> ogra, yep. if you want security support, then it needs to get on our list of things to do
[19:45] <ogra> kees, i guess easiest would be if cooloney added the patches 
[19:45] <kees> tgardner, ogra: okay, so you guys will get that branch included in the cadence process?
[19:45] <ogra> since he maintained the packages 
[19:46] <ogra> but that needs to be sorted out on management level
[19:46] <tgardner> kees, lemme take it up with pgraner. we're pretty short staffed.
[19:47] <ogra> i think cooloney is the right person but i dont think where thats located resource wise 
[19:47] <ogra> so needs top level discussion first 
[19:47] <tgardner> cooloney is out for a couple of weeks
[19:47] <ogra> i really dont get why that hasnt heppened already
[19:47] <tgardner> ogra, too much to do, not enough people
[19:48] <Q-FUNK> hi! what was the URL to the team's repository of stock vanilla kernels, again?  I need to test a 2.6.38 against what's in natty, just to make sure we don't have a regression.
[19:48] <ogra> tgardner, i mean the assignment of the work
[19:49] <ogra> to one of the teams
[19:55] <tgardner> kees, the LTS maverick backport is built in the c-k-t PPA. its ready to be copied to -security
[19:55] <kees> tgardner: doesn't it have to go through QA?
[19:55] <tgardner> kees, they don't test anything but Maverick and Natty.
[19:56] <tgardner> and occaisionally Lucid when we ask real nice
[19:56] <kees> tgardner: pitti won't pocket-copy without QA sign off. they need to do the testing...
[19:56] <tgardner> then thas gonna be a real problem.
[19:57] <JFo> Q-FUNK, http://kernel.ubuntu.com/~kernel-ppa/mainline/
[19:57] <kees> this is my point from last friday. :P
[20:13]  * jjohansen -> lunch
[20:34] <apw> skaet, forgot to mention i did the updates to the release page for kernel
[20:34] <skaet> Thanks apw!
[20:38] <JFo> apw, tgardner pgraner what packages do you want duplicate detection turned off for per bdmurray's e-mail?
[20:41] <pgraner> JFo, didn't get an email
[20:42] <JFo> went to kernel-team
[20:42] <tgardner> JFo, likely just linux for now. lets see how well it works.
[20:42] <JFo> sorry should have specified
[20:42] <JFo> tgardner, my thinking as well
[20:42] <pgraner> JFo, +1
[20:43] <JFo> k
[20:47]  * apw concurs for what it is worth
[20:48] <JFo> k, thanks apw
[21:05]  * apw_ notes that upgrading right now is a huge mistake ... unity core dumps
[21:09] <JFo> :-/
[21:38] <apw_> sounds like they may have just found it
[21:45] <kamal> what's the tool that submits email pull-requests to the kernel-team list?  the thing that creates messages e.g. "The following changes since commit ... are available in the git repository at ..." ?
[21:49] <jjohansen> git request-pull
[21:49] <kamal> answer: git request-pull
[21:49] <kamal> jjohansen: :-) thanks ;-)
[21:49] <jjohansen> hehe :)
[21:52] <bdmurray> JFo: I can update bugs tagged regression-proposed to regression-update for you
[21:54] <JFo> well, not all of them will be bdmurray 
[21:58] <JFo> sorry, got pulled away on a phone call