[00:23] <kees> ogasawara: who is driving the natty kernel?
[00:24] <ogasawara> kees: apw and tgardner
[00:24] <kees> okay, cool. I will subscribe them to my kernel-krack track :)
[00:24] <ogasawara> heh
[00:56] <bjf> ogasawara, my test build of armel has failed the modules check for omap, complaining that smsc911c is missing
[00:57] <ogasawara> bjf: I can't remember, did one of the patches build in that module or maybe disable it?
[00:57] <bjf> ogasawara, i'm trying to determine that, it's builtin now
[00:58] <ogasawara> bjf: I want to say it was changed to being built in.  and I also want to recall I shoved in the file to tell it to then ignore the module check.
[00:59] <ogasawara> commit 6de80403735ba5339a83895ac5591596aacf721e
[00:59] <ogasawara> Author: Leann Ogasawara <leann.ogasawara@canonical.com>
[00:59] <ogasawara> Date:   Tue Oct 5 11:35:37 2010 -0700
[00:59] <ogasawara>     UBUNTU: ARM: Temporarily disable module check for armel
[00:59] <ogasawara> commit a192fd144b602f72caece44ec2ff3dfaedf8d325
[00:59] <ogasawara> Author: Ricardo Salveti de Araujo <ricardo.salveti@canonical.com>
[00:59] <ogasawara> Date:   Thu Sep 23 01:09:08 2010 -0300
[00:59] <ogasawara>     UBUNTU: [Config] Remove CONFIG_FIXED_PHY and move CONFIG_SMSC911X from m to y for omap
[01:01] <ogasawara> bjf: were the correct ABI files included when the next release was started?
[01:01] <bjf> ogasawara, ok, will look at it later, pulled new abi files, probably related, the old abi tree was deleted
[01:02] <bjf> ogasawara, the ignore file is in the abi tree so when I pulled down a new set and deleted the old, i lost the change you'd added
[01:03] <bjf> ogasawara, good thing i did a test build (almost didn't bother)
[01:03] <ogasawara> bjf: ah, makes sense then
[02:08] <proverse> what is drm-intel-next folder / build in the kernel-ppa?
[02:09] <RAOF> proverse: That's a build of the drm-intel-next kernel tree; it's the development tree for the intel drm module.
[02:11] <proverse> drm is direct rendering something, yesno? worth trying with a core i3-350m (integrated graphics), especially since the i915 module is complaining with recent kernels (2.6.35+) ?
[02:14] <RAOF> Yes, that's right.
[02:14] <RAOF> What's the i915 module complaining about for you?
[02:14] <proverse> hang on will get the dmesg lines
[02:15] <proverse> [   13.613936] intel ips 0000:00:1f.6: Warning: CPU TDP doesn't match expected value (found 25, expected 35)
[02:15] <proverse> [   13.613965] intel ips 0000:00:1f.6: PCI INT C -> GSI 18 (level, low) -> IRQ 18
[02:15] <proverse> [   13.614121] intel ips 0000:00:1f.6: failed to get i915 symbols, graphics turbo disabled
[02:15] <proverse> [   13.614290] intel ips 0000:00:1f.6: IPS driver initialized, MCP temp limit 65535
[02:15] <proverse> [   14.000308] agpgart-intel 0000:00:00.0: Intel HD Graphics Chipset
[02:15] <proverse> [   14.001778] agpgart-intel 0000:00:00.0: detected 131068K stolen memory, trimming to 32768K
[02:15] <proverse> [   14.078991] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000
[02:15] <proverse> [   15.303978] fb0: inteldrmfb frame buffer device
[02:15] <proverse> [  998.652812] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
[02:15] <proverse> the "failed to get i915 symbols..." seems to be the most telling line
[02:16] <proverse> maverick beta circa september I was able to get 1400+fps in glxgears, smooth flash video playback, etc.
[02:16] <proverse> recently its been about 60fps in glxgears and stuttering as well
[02:16] <proverse> *stuttering video
[02:18] <psusi> why would the kernel emit a change event for a disk partition?  I thought you got a change event for the disk itself when the partition table was changed, but I'm seeing change events on the partition for no apparently reason when lvm activates logical volumes, and this causes a feeback loop
[02:19] <RAOF> proverse: So, 60fps in glxgears is because intel now has working vsync support - 60fps is exactly the expected value for glxgears FPS on most displays.
[02:20] <RAOF> Secondly: that dmesg is just saying that the ips module won't do the dynamic overclocking thing for your GPU that the core processors can do.
[02:20] <psusi> in udev that is
[08:34] <jk-> smb: hey
[11:12] <Ian_Corne> The latest kernel patch for natty doesn't fix the rds local root exploit
[11:12] <Ian_Corne> just so you know
[11:13] <Ian_Corne> it's fixed on lucid, maverick, karmic but not for natty
[11:13] <lucent> not surprising, good to know as a user though
[11:14] <Ian_Corne> why is it not surprising?
[11:14] <Ian_Corne> it's patched for the other kernels..
[11:14] <Ian_Corne> is there anything holding it back
[11:17] <lucent> natty is not a stable release
[11:17] <lucent> so why would it matter to fix a security bug?
[11:19] <apw> Ian_Corne, yeah we don't generally stress about security issues in the development kernel as it should never be in production anywhere
[11:19] <apw> and all of the fixes come down to us from upstream
[11:19] <Ian_Corne> ok :)
[11:19] <apw> got a pointer to the fix ?
[11:19] <Ian_Corne> Guess I'm booting in 35 for the time being then
[11:20] <Ian_Corne> I'll look it up
[11:20] <apw> cirtainly before the first alpha we do not expect anyone to be really actually running the kernel in anger, especially when its in the -rc1/2 range as we jump between releases
[11:21] <Ian_Corne> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=799c10559d60f159ab2232203f222f18fa3c4a5f
[11:21] <Ian_Corne> Yeah I just upgrade as soon as I can always :)
[11:22]  * lucent eyes the beginning of a facepalm forming subconciously in his own limbs
[11:23] <apw> Ian_Corne, that seems to be in that latest natty tree
[11:23] <apw> and therefore in the latest kernel ?
[11:23] <Ian_Corne> hmm
[11:24] <Ian_Corne> I just tried it on the .36-1 kernel 
[11:24] <Ian_Corne> and the exploit worked
[11:24] <Ian_Corne> I'll try again
[11:24] <apw> which -1 kernel?  whats the full version number
[11:25] <Ian_Corne> I'll check in a second
[11:25] <Ian_Corne> ah there's another kernel update also with -1
[11:26] <apw> yep, wasn't an ABI bumper, and it was very small update, so it wasn't worth the pain
[11:26] <Ian_Corne> ok :)
[11:26] <Ian_Corne> I'll try it asap
[11:26] <apw> yes that fix is between -rc8 and final, so would be in .7 and not .5
[11:27] <Ian_Corne> it was -1.6
[11:27] <Ian_Corne> going to -1.7
[11:33] <Ian_Corne> [*] Exploit failed to get root.
[11:33] <Ian_Corne> :)
[14:20] <BluesKaj> during update dpkg locks my system trying to install a kernel module/linix image that it can't find (2.6.32.24-generic) . Apt just sits there hungup.
[14:20] <eagles0513875> and it seems the kernel he mentions is in lucid 
[14:21] <BluesKaj> actually it's grub trying to regenerate a new .cfg file 
[14:42] <cking> apw, you around?
[14:47] <apw> cking, hi
[15:06] <debarshi> I would like to use a driver present in linux-next.git, but not in the current Ubuntu 10.04 kernel. I would prefer to create a separate package for the module instead of having my own kernel package.
[15:06] <debarshi> I have found out about Module Assistant, but I am not sure how to proceed.	
[15:06] <debarshi> I am trying to extract the driver directory somewhere else and then create a package, but I am having trouble with the kernel make files.
[15:08] <tgardner> debarshi, use dkms. see bcmwl-kernel-source for an example
[15:08] <debarshi> Ok.
[18:28] <jendap__> hi
[18:28] <jendap__> I've read about ppa backporting new kernel to old releases
[18:28] <jendap__> there is ppa:kernel-ppa/ppa repository
[18:29] <jendap__> but it has natty development kernel backported for lucid now
[18:29] <jendap__> so the question is: is there a repository with maverick kernel (2.6.35) backported to lucid (LTS)?
[18:29] <apw>  jendap__ yes that is correct, the maverick kernel has now released and so the backport of that is in the main archive
[18:30] <apw> it _may_ only be in -proposed at the moment as it very soon after maverick release
[18:30] <jendap__> so will it be there later?
[18:30] <apw> where?
[18:31] <jendap__> I need it for servers, so LTS would be nice, but I need 2.6.35 kernel
[18:32] <apw> jendap__, its only supported for servers anyhow
[18:32] <apw> linux-lts-backport-maverick | 2.6.35-22.34~lucid1 | lucid-proposed | source
[18:32] <apw> so yes, it is in -proposed at the moment, so you can enable that if you want to install it
[18:33] <apw> it shoul migrate to -updates shortly when the appopriate bake time has completed
[18:33] <jendap__> how can I enable "-proposed" ?
[18:34] <apw> https://wiki.ubuntu.com/Testing/EnableProposed
[18:35] <jendap__> apw: thanks! that should be it :-)
[18:35] <apw> jendap__, thats the docs i know about, but its a pocket like updates etc so ypu can add it to sources.list manually if yopu don't have a graphical interface
[18:36] <apw> install the meta package to ensure you get updates
[18:36] <jendap__> apw: thanks!
[18:37] <apw> linux-image-server-lts-backport-maverick i think is the one you want to install
[18:45]  * ogasawara bails for appt, back in a bit
[18:53] <jendap__> apw: all servers upgraded, thanks
[19:19] <Leon_Nardella> Hi! What is the possibility of having goo.gl/Gc3a be backported into Maverick?
[20:01] <apw> Leon_Nardella, no idea what that even is ... we don't commonly backport new functionality into released kernels
[20:02] <Leon_Nardella> apw, I wouldn't call it new functionality. It fixed the input audio in some Microsoft webcams.
[20:02] <jendap__> Leon_Nardella: yit was merged to linux 2.6.36 - so netty kernel will work
[20:03] <apw> Leon_Nardella, presumably its never worked before as its new func in .36
[20:04] <apw> but if you want to propose it, emailing the patches to kernel-team list with justification is the normal way forward
[20:04] <apw> that lets us see the extent of the patches and decide from that
[20:06] <Leon_Nardella> apw, ok
[20:06] <apw> the smaller the patches the higher your chances 
[22:34] <greearb> Hello!  I'm trying to put a custom ubuntu-natty kernel on Ubuntu 10.10 live-cd.
[22:34] <greearb> The first problem I'm having is that it seems aufs is not being compiled, so the live-cd will not boot.
[22:35] <greearb> aufs does appear to be in the kernel config file properly, however...any ideas what I might be doing wrong?
[22:46] <greearb> ahhh, makefile has aufs dir commented out..and it won't build in ubuntu-natty kernel..