[10:32] <mamarley> apw: I just tried the 4.6.2 mainline kernel and it boots now (yay!), but ACPI CPU frequency scaling doesn't work.  I filed a bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590371
[14:16] <rtg> cyphermox, have you encountered any UEFI issues with the kernels in ppa:canonical-kernel-team/unstable ?
[14:17] <apw> rtg, bug: #1590371 might (though mainline was tested) indicate an issue with your 4.6/7 config
[14:18] <rtg> apw, there has to be a better way then building in those drivers
[14:19] <apw> rtg, yeah i know your feeling
[14:22] <mamarley> Indeed, though the bug report is still valid.  (I was able to work around the issue by modprobing cpufreq_ondemand and then manually changing governors.)
[14:22] <mamarley> Also, that only affects my one system that is too old to use the intel_pstate driver, which works fine.
[14:23] <apw> mamarley, yep he wasn't saying the bug was invalid, that reverting the change which likely introduced it might not be the best soln.
[14:23] <mamarley> Agreed.
[14:23] <rtg> perhaps /etc/init.d/ondemand could do the modprobe
[14:24] <apw> rtg, but we only need it if acpi supports it right?  shouldn't it be autoloadable with acpi anyhow ?
[14:26] <rtg> apw, not sure. these CPU frequency governors are also built for arches that don't have ACPI (like armhf)
[14:26] <mamarley> I do know that those governors do nothing with intel_pstate.
[14:28] <rtg> bug #1584124 has interesting info in that regard
[15:03] <cyphermox> rtg: not done verifying, have you?
[15:06] <cyphermox> rtg: everything is already in place for xenial, or do you still have something to land as kernel there? there isn't a xenial kernel in the PPA
[15:07] <rtg> cyphermox, xenial in the archive is feature complete wrt UEFI and MOK
[15:07] <cyphermox> ack
[17:46] <mowthegrass> Hi 
[17:46] <mowthegrass> Anyone out there to help me with boot issues 
[17:47] <mowthegrass> My Ubuntu 14.04 doesnt boot with 3.16.0-67 Kernel , But the same machine is able to boot from the latest kernel 
[17:47] <mowthegrass> Booting from 3.16.0-67 kernel freezes with the below error 
[17:48] <mowthegrass> [    2.402903] random: lvm urandom read with 61 bits of entropy available
[17:48] <mowthegrass> random: Non blocking pool initialzed 
[17:49] <mowthegrass> booting to recovery , just drops me to initramfs "Gave up waiting for root device" 
[17:50] <mowthegrass> I have updated the ramfs of the all the kernels by booting to latest kernel 
[17:50] <mowthegrass> anyone have any pointers on where the issue could be 
[17:50] <mowthegrass> appreciate your time and help 
[17:50] <apw> "latest kernel"?
[17:51] <mowthegrass> 4.2.0-36
[17:54] <mowthegrass> issues seem to be strange 
[18:58] <ali1234> jsalisbury/anyone else: here are my notes on bisection: http://paste.ubuntu.com/17126664/
[20:45] <mjg59> apw: Any idea what the status of https://launchpadlibrarian.net/149319334/overlayfs_inotify.patch was?
[20:48] <apw> mjg59, that is a good question ... i've not rebased that for ages, i really should
[20:50] <mjg59> apw: Was anyone working on pushing that upstream? It's something that seems to be biting a bunch of docker users (and we've got customers complaining, so I do have somewhat selfish reasons to be interested)
[20:50] <apw> mjg59, i will try and get that rebased 
[20:52] <mjg59> apw: Sweet. Let me know if I can help in any way