=== JanC_ is now known as JanC [04:27] so I've already filed a bug for my issue (regarding ohci_pci dropping 2 specific USB ports) but I'm mainly here to see if I can at least help find a temporary workaround for the issue since booting isn't of help since the issue happens roughly a minute after boot every boot now, I wonder if unloading and reloading the ohci_pci module would help at all and is reasonably safe [07:56] c_smith, normally dropping a module is meant to be safe, worth trying. if you let us know the bug number we might be able to suggest something more === sts_ is now known as sts [13:02] hey. [13:02] i'm looking for some education [13:03] https://pastebin.canonical.com/166997/ [13:03] http://paste.ubuntu.com/23274982/ [13:04] that runs in a chroot of one ubuntu release that is not necessarily the same as the host [13:04] the chroot doesn't have /lib/modules/$(uname -r). so 'modprobe' will fail to load overlayfs or overlay if you did that. [13:04] but somehow 'mount -t overlayfs' gets it mounted [13:04] smoser, the kernel can load things too [13:05] the mount abi call must just ask the kernel to mount of that type, and then the kernel loads it by the fs-NAME alias ? [13:05] fs/filesystems.c: if (!fs && (request_module("fs-%.*s", len, name) == 0)) [13:06] hm.. that sucks. [13:07] means that my code that says "can i use overlay" is needing fixing as it relies on being able to load the module or have it in /proc/filesystems already. :-( [13:08] apw, so other places i have done in the past 'modprobe nbd' is there any way to get similar behavior for that ? [13:09] from inside a container, not to my knowledge [13:09] snapd seems to have to hand it out to snapd itself for execution so i assume not [13:09] i assume they have found no way to do it [13:10] smoser, but why do you care? can you not literally mount -t overlay || mount -t overlayfs [13:11] smoser, or just assume based on version number ? [13:11] smoser, https://github.com/snapcore/snapd/blob/master/docs/interfaces.md#kernel-module-control ... ? [13:11] (in case you want to load a module from a snapped up thing) [13:13] smoser: The only reliable way to determine whether the kernel can do something is to try to do it and see what error you get back [13:18] i'd rather not loop over attempts to mount something. [13:18] then use the kernel version number [13:59] infinity: where is tim? [14:00] one|2, which tim [14:00] apw: tim working on the kernel [14:14] * ogra_ guesses tim is at home [14:14] (if he doesnt travel that is) [14:17] one|2, are you asking his timezone or if he is here now, he is here now [14:36] tim the nascar video is still running [14:37] this looks like the oracle kernel [15:12] PaulW2U: hello [16:56] jsalisbury, Hi! re: bug 1627108 the first debs that you gave me contain the regression. [16:56] bug 1627108 in linux (Ubuntu Yakkety) "X1Carbon comes to a crawl during high CPU usage tasks" [High,In progress] https://launchpad.net/bugs/1627108 [16:57] om26er, ack, thanks for testing. I'll build the next kernel and post when it's ready. [17:21] hi, the lts-yakkety kernel (-20) from the dev ppa can't mount my lvm raid1 devices do to unknown compatibility flags, is this a known issue?