[15:38] <tseliot> apw: what is the proper way to request a config change in the kernel? I need DRM_AMD_POWERPLAY=y for my backport
[15:43] <apw> tseliot, at this stage, a bug with the justification would be good, and then a patch as normal
[15:43] <apw> or file the bug, and just tell me the number
[15:43] <apw> tseliot, or are you asking how to apply a change in a big pull request ?
[15:44] <tseliot> apw: that could probably fit the same bug report I filed for my backport (which affects the same code)
[15:44] <tseliot> apw: I was thinking it would be worth doing it myself as part of the pull request
[15:45] <tseliot> since, you know, backporting code just to keep it disabled is probably a little useless :D
[15:45] <tseliot> the thing is, I don't recall doing that before
[15:46] <tseliot> (a config change)
[18:22] <leitao> rtg, hello. It seems that there is an issue with kernel 3.19 on the fixes for 1481357.
[18:23] <rtg> leitao, yeah, I see verification-failed-vivid
[18:23] <leitao> good. I want just to make sure that it does not fly under the radar. Thank you!
[18:25] <rtg> leitao, I'll look at it a bit later this afternoon. gotta wrap up some other stuff first.
[18:26] <leitao> rtg, no worries. As I said, just to make sure that you guys saw the problem.
[18:52] <tych0> hi folks. i'm on the xenial kernel, 4.4.0-8-generic
[18:52] <hallyn> sforshee: apw: hey, tych0 is finding apparmorfs sometimes not loaded 
[18:52] <tych0> and i'm missing my /sys/kernel/security/apparmor is missing
[18:52] <hallyn> but sometimes loaded (and for me it is loaded)
[18:52] <hallyn> tych0: anything in journalctl?
[18:53] <tych0> yeah, for me it is loaded too on other vms but this one
[18:53] <tych0> nothing jumps out at me, but, http://paste.ubuntu.com/15245948/
[18:54] <tyhicks> Feb 29 11:40:56 criu2 kernel: AppArmor: AppArmor disabled by boot time parameter
[18:55] <tyhicks> Feb 29 11:40:56 criu2 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic ... selinux=1 security=selinux ...
[18:55] <hallyn> tsk tsk
[18:55] <tych0> oh
[18:56] <tych0> how did that get there :)
[18:56] <hallyn> gremlins?
[18:57] <tych0> or an extremely elaborate troll
[18:57] <tyhicks> I vaguely remember seeing a xenial bug go by for a package that was depending on selinux-policy-default
[18:58] <tych0> i wonder how i turn it off
[18:58] <tych0> somehow i do have that package installed, let's see what happens if i uninstall it
[18:59] <tyhicks> tych0: do you have the "selinux" binary package installed?
[19:00] <tych0> rc  selinux                             1:0.11                                  all          Security-Enhanced Linux runtime support
[19:00] <tych0> but that might be because i just removed some stuff
[19:01] <tyhicks> tych0: ok, do you have the "apparmor" package installed?
[19:01] <tych0> tyhicks: yes, i have that one
[19:02] <tyhicks> tych0: hmm... I thought that if you had it installed, it would set the right kernel boot params but it has been a while since I've tried switching between apparmor and selinux
[19:03] <tych0> wwell, let me try to --reinstall
[19:03] <tyhicks> that may work
[19:04] <tych0> hm, even that didn't do it
[19:07] <tych0> well never mind, maybe i'll just blow this vm away and start over :)
[19:07] <tyhicks> tych0: the selinux packaging simply modifies /etc/default/grub to add security=selinux selinux=1
[19:08] <tych0> ah, ok
[19:08] <tyhicks> tych0: you should be able to remove those two params and run update-grub2 to return to using apparmor since our kernels are configured to use apparmor by default
[19:08] <tych0> oh
[19:08] <tych0> update-grub2 vs. update-grub :)
[19:08] <tyhicks> either one
[19:08] <tyhicks> I think they're the same
[19:09] <tyhicks> yeah, update-grub2 is a symlink to update-grub
[19:09] <tych0> ok, cool
[19:13] <tych0> tyhicks: \o/ thanks!
[19:13] <tyhicks> tych0: glad that it worked :)
[21:06] <rharper> on Xenial, I've a USB flash drive that shows up when directly connected to x1 carbon gen1; but when plugged in via USB3 hub does not;  other usb devices on hub work (keyboard, nic, mouse) but not mass storage devices;  worked fine in 15.10; thoughts? lsusb does not even list the device when plugged in 
[23:49]  * hallyn at that point in writing a new kernel patch where you wonder 'do i type make for the first time and see where it breaks, or reread the patch to look for obvious errors?'