[00:21] who smb` === lag` is now known as lag === amitk is now known as amitk-afk === amitk-afk is now known as amitk [11:40] <_d4vid> when come 3.8.10 to kernel mainline ppa? [11:41] <_d4vid> and 3.9 [11:46] apw: So, linux-lowlatency development release maintenance? How does that work? [11:48] apw: I suppose I'd prepare the source the same way, but how do I keep track of when to do it? [11:49] I'm going to try get some upload rights this cycle. How difficult might that be for linux-lowlatency? I'm focusing on Ubuntu Studio packages first, but I suppose if I were to become a MOTU, I'd be able to upload linux-lowlatency as well [11:50] To begin with, I'm going to focus on getting upload right for the Ubuntu Studio package set first, but -lowlatency is seemingly not a part of that group of packagesd [13:57] apw: do you know whether macvlan/macvtap over wifi is supposed to ever work? (been googling for awhile, and looking at the src, all i know is it doesn't in fact work :) === kentb-out is now known as kentb [14:34] greets... [14:34] I have a kernel bug to report in ubuntu, but it's on a friends comp and he's pretty lost running the reporter on terminal [14:35] I have output from hardinfo and screencaps of the crash [14:35] where to submit? [14:52] DeaconDesperado: https://bugs.launchpad.net/ubuntu/+source/linux/+filebug === chris234 is now known as RAOF [15:39] dobey: thanks === smb` is now known as smb === chuck_ is now known as zul [21:36] What happened to the -extras in the mainline kernel? [21:37] This 3.9 kernel is tiny. [21:44] 42MB is the same size as the old image/extras combo, it just got condensed into one === kentb is now known as kentb-ou === kentb-ou is now known as kentb-out [22:53] apw: The 3.9 kernel appears to fail to autoload overlayfs.ko when I schroot for the first time. [22:53] apw: Manually modprobing it works fine. [23:40] infinity, i would expect that to be modprobe'd by mount ? [23:40] apw: You'd think, right? [23:41] infinity, though ... as you are in a chroot (right?) it would not be there to probe [23:41] apw: No, this is on bare metal. [23:41] "autoload overlayfs.ko when I schroot" [23:41] what does that mean [23:43] apw: It means schroot fails and vomits something about overlayfs being an unknown filesystem type. [23:43] apw: And when I modprobe the module first, it works fine. [23:43] * apw is expecting the schroot to use mount, hmmm [23:43] E: 10mount: mount: unknown filesystem type 'overlayfs' [23:43] It is. [23:44] and the same version booted to the raring kernel works i assume [23:44] Yep. [23:44] infinity: and that's on a nexus or normal desktop?! [23:44] ah, never mind me if it works on raring. [23:51] infinity, very odd ...