[02:35] <taihsiang> henrix,  I am testing proposed kernels for certification this cycle. there is no lucid kernel update, isn't it? thanks.
[04:51] <infinity> taihsiang: No lucid this cycle, no.  You can get the full overview here: http://kernel.ubuntu.com/sru/kernel-sru-workflow.html
[06:18] <taihsiang> infinity, thanks, got it.
[14:36] <exebat> Hi all
[14:37] <exebat> I have a problem with Ubuntu 14.04 USB devices not being available on boot until repluged
[14:39] <exebat> What might I do to fix it ? It worked just fine on 12.04
[14:43] <apw> exebat, the normal thing is to check for dmesg errors, if there are osme then there may be hope of figureing it out from those, so you'd file a bug against linux after the failed boot
[14:45] <smoser> hey. random curious thing...
[14:45] <apw> exebat, if there is no obvious clue then it becomes a hunt for when it stopped working, a bisect as it were, and for that we normally suggest again filing a bug against linux and somene can help talk you through the how of it
[14:45] <smoser> is there any way to query "how long has hardware been up" or "when was hardware turned on".
[14:45] <apw> exebat, either way a bug is needed, file using "ubuntu-bug linux"
[14:45] <smoser> i'm aware of issues with clock changing, so that 'date' wouldnt be always relevant, but just curious.
[14:46] <apw> isn't that uptime ?
[14:46] <smoser> /proc/uptime tells me when kernel started running
[14:46] <smoser> which is after bios + after grub + after grub loaded kernel and initramfs ..
[14:46] <smoser> which is ages :)
[14:46] <apw> efi does give you some information
[14:46] <apw> if you have efi then systemd-analyse gives you some breakdown before kernel
[14:47] <smoser> hm.
[14:48] <apw> not that i have a clue how it gets that information
[14:48] <apw> other than it is efi informaiton
[14:49] <smoser> dont have thta on the 2 systems i'm looking at (which are not efi :)
[14:49] <smoser> but that is really nice. i didn't know about that.
[14:49] <shirgall> I was tihnking it was in dmidecode somewhere, but I didn't find it. :/
[14:50] <smoser> yeah, well, dmi data is notterribly consistent in my experience
[14:51] <shirgall> Aye
[14:51] <smoser> but yeah, i kind of thought it might be there too
[14:52] <shirgall> 'facter' tells a lot, but only the OS uptime.
[17:28] <bjf> stgraber, i'm still getting the failure in lxc-test-apparmor. is that correct?
[17:29] <bjf> stgraber, that's for vivid
[17:36] <stgraber> bjf: yep
[17:37] <stgraber> bjf: hallyn pushed a fix to cgmanager which unblocked lxcfs and some other test failures for LXC, but the apparmor testcase still hangs or fail, it's next up on the list
[17:37] <bjf> stgraber, ok, thanks for the info
[20:47] <studio_> hi
[20:47] <studio_> anybody here?