[03:41] am I missing something? I see that there is now "linux-image-unsigned" and "linux-modules" packages for the amd64 mainline kernel ppa [03:41] it also appears to not install properly, is this a known issue or am I making some mistake [08:46] White_Light, the files have changed names, not installing properly isn't very specific so i cannot comment to that === JanC is now known as Guest28882 === JanC_ is now known as JanC === aaa_ is now known as Guest27490 [12:59] apw, what is the correct order to install them, if say you wanted to install the -generic mainline build? === Guest27490 is now known as aaa__ [13:08] you need to install linux-image-unsaigned and linux-modules together, and i would expect that to work [13:08] if it does not, you need to be more explicit than "doesn't work" for anyone to know how to help fix it [13:08] hmm, looks like "linux-update-symlinks" isn't found [13:09] yeah and linux-check-removal isn't found either, so uninstalling this is annoying [13:09] is this unusual? 16.04 mate doesn't have either installed by default [13:09] https://askubuntu.com/questions/1028629/kernel-ubuntu-com-kernel-ppa-mainline-v4-16 [13:09] so that must be in an older release, which needs linux-base to be updated [13:09] White_Light, which release? linux-update-symlinks is provided by base-files. [13:09] quick google search shows someone else hit this [13:10] maeh linux-base it is. [13:10] which is being sru'd to xenial to sort out linux-hwe-edge when it tries to switch to this version [13:11] and indeed has made it as far as xenial-proposed [13:12] ok, so just hang tight until it gets back ported? [13:16] or install it from -proposed manually yep === aaa_ is now known as Guest8029 === aaa_ is now known as Guest49979 [16:54] so what are the rules for joining this chan? do you need to be authenticated as ubuntu member? [16:54] hallyn: i'm here now :) [16:54] seems ok [16:54] oh ok :) [16:54] i had *just* checked for you... [16:54] sforshee: apw: hi, so i just filed https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767443 [16:54] Launchpad bug 1767443 in linux-signed (Ubuntu) "regular hard lockup on bionic kernel" [Undecided,New] [16:55] i realize that's a terrible bug report [16:55] but hopefully you guys can give me some more sleuthing techniques :) [17:23] tych0: hey - I took a look to rule out any chance of microcode/kernel issues but everything looks correct there (https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767443/comments/3) [17:23] Launchpad bug 1767443 in linux-signed (Ubuntu) "regular hard lockup on bionic kernel" [Undecided,New] [17:24] tyhicks: cool, thanks [17:24] I don't have any other ideas right now :/ [17:24] no worries. at some point one of us will have a flash of brilliance :) [17:37] tych0, you have been getting these hard lockups for months and are just now reporting a bug? [17:38] bjf: yes, well, i was hoping to get some more info. [17:38] but nothing has ever really popped out. [17:49] tych0: not sure if it'll work with your particular lockup but you might want to write "184" to /proc/sys/kernel/sysrq and then use the "l" magic sysrq on your next lockup to see if a kernel stacktrace can still make it to your screen and/or the system logs [17:51] (add "kernel.sysrq = 184" to a file in /etc/sysctl.d/ to make it persistent) [17:52] that sysrq command is safe to try out now, before you experience a lockup, so that you're confident that you've got all the required finger gymnastics figured out for your specific keyboard [17:53] you'll see the kernel stack traces in the syslog [18:01] bjf: yeah instead of reporting a bug he's just been kicking a kitten twice a day when it locks up === aaa_ is now known as Guest46492 [20:41] i don't like kittens [20:41] tyhicks: thanks, i'll give that a whirl [21:54] Hello guys, anyone have an idea on what's going on with this on 18.04? The hard drives eventually come online, but it slows my boot time. https://pastebin.com/GhgfLjAe