[03:41] <White_Light> 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] <White_Light> it also appears to not install properly, is this a known issue or am I making some mistake
[08:46] <apw> White_Light, the files have changed names, not installing properly isn't very specific so i cannot comment to that
[12:59] <White_Light> apw, what is the correct order to install them, if say you wanted to install the -generic mainline build?
[13:08] <apw> you need to install linux-image-unsaigned and linux-modules together, and i would expect that to work
[13:08] <apw> 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] <White_Light> hmm, looks like "linux-update-symlinks" isn't found
[13:09] <White_Light> yeah and linux-check-removal isn't found either, so uninstalling this is annoying
[13:09] <White_Light> is this unusual? 16.04 mate doesn't have either installed by default
[13:09] <White_Light> https://askubuntu.com/questions/1028629/kernel-ubuntu-com-kernel-ppa-mainline-v4-16
[13:09] <apw> so that must be in an older release, which needs linux-base to be updated
[13:09] <juergh> White_Light, which release? linux-update-symlinks is provided by base-files.
[13:09] <White_Light> quick google search shows someone else hit this
[13:10] <juergh> maeh linux-base it is.
[13:10] <apw> which is being sru'd to xenial to sort out linux-hwe-edge when it tries to switch to this version
[13:11] <apw> and indeed has made it as far as xenial-proposed
[13:12] <White_Light> ok, so just hang tight until it gets back ported?
[13:16] <apw> or install it from -proposed manually yep
[16:54] <hallyn> so what are the rules for joining this chan?  do you need to be authenticated as ubuntu member?  
[16:54] <tych0> hallyn: i'm here now :)
[16:54] <tych0> seems ok
[16:54] <hallyn> oh ok :)
[16:54] <hallyn> i had *just* checked for you...
[16:54] <tych0> sforshee: apw: hi, so i just filed https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1767443
[16:55] <tych0> i realize that's a terrible bug report
[16:55] <tych0> but hopefully you guys can give me some more sleuthing techniques :)
[17:23] <tyhicks> 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:24] <tych0> tyhicks: cool, thanks
[17:24] <tyhicks> I don't have any other ideas right now :/
[17:24] <tych0> no worries. at some point one of us will have a flash of brilliance :)
[17:37] <bjf> tych0, you have been getting these hard lockups for months and are just now reporting a bug?
[17:38] <tych0> bjf: yes, well, i was hoping to get some more info.
[17:38] <tych0> but nothing has ever really popped out.
[17:49] <tyhicks> 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] <tyhicks> (add "kernel.sysrq = 184" to a file in /etc/sysctl.d/ to make it persistent)
[17:52] <tyhicks> 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] <tyhicks> you'll see the kernel stack traces in the syslog
[18:01] <hallyn> bjf: yeah instead of reporting a bug he's just been kicking a kitten twice a day when it locks up
[20:41] <tych0> i don't like kittens
[20:41] <tych0> tyhicks: thanks, i'll give that a whirl
[21:54] <RadicalEntity> 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