Updates on latest 64-bit kernel?
Looks like we're sliding further behind for the "latest" 64-bit kernel updates. Last I checked there was references to upstream (uptime output incorrect) bugs (more info here) but that thread seems to have gone quiet.
For us that wants to stay close to upstream but not manually maintain kernel versions it would be great to get an update on the release schedule!
Edit, more references:
- current "latest" is soon 4 months old: https://www.linode.com/kernels/
- original upstream bug in debian bugzilla: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918036 (latest comment notes that it may have been fixed in
4.19.17) - seemed to be in the backport for for
4.19.18(from5.0.0-rc4), which contradicts above comment: https://patchwork.kernel.org/patch/10782557/ - all in all, pathc should live in both LTS (
4.19.x) and current kernels
..can perhaps original authors (@mnordhoff0, @bbigger) confirm so we can get rolling again?
8 Replies
Linode runs "vanilla" kernels AFAIK - whereas Debian etc. often backport patches.
I'm not seeing this fix in 4.19.17 change log, only a (similar?) fix for Xen clock, but that's different.
https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.17
Looking at "vanilla" source on GitHub, it seems that:
1 - The change didn't make it into 5.0:
EDIT: according to this site, the fix is in 5.0.4 onward:
https://elixir.bootlin.com/linux/v5.0.4/source/arch/x86/kernel/kvmclock.c#L105
… including 5.0.8 which is the newest Linode kernel currently available (in the drop-down, not as "latest")
https://elixir.bootlin.com/linux/v5.0.8/source/arch/x86/kernel/kvmclock.c#L105
2 - It was part of 5.1-rc1
https://github.com/torvalds/linux/blob/v5.1-rc1/arch/x86/kernel/kvmclock.c#L105
3 - It is still there in 5.1 "not rc anymore" which was just tagged hours ago:
https://github.com/torvalds/linux/blob/v5.1/arch/x86/kernel/kvmclock.c#L105
Would love to get an update too from someone at Linode:
1 - Can we get a build of 5.1.* in some foreseeable future?
Even if you don't tag it as "latest" (which you probably won't want rush) - it would be a good way to test by people willing to manually pick this kernel.
2 - Maybe 5.0.* can be promoted to "latest" (the current 5.0.* is 5.0.13, probably enough minor releases to mature)?
1 - Can we get a build of 5.1.* in some foreseeable future?
0-day :) Totally agree, happy to test.
5.1.1 is out, doesn't look too interesting compared to 5.1.0 in KVM/XEN-land.
Averaging the frequency in releases at https://www.linode.com/kernels/ seems to indicate this will be the next kernel released. Hopefully this can also turn into latest.
I've been running the 5.1.2 kernel (inc intel fixes) and have had no issues regarding uptime or otherwise.
$ uname -s -r -v
Linux 5.1.2-x86_64-linode124 #1 SMP PREEMPT Wed May 15 15:12:46 UTC 2019
$ uptime
17:39:13 up 3 days, 28 min, 1 user, load average: 0.00, 0.00, 0.00
bbigger
Linode Staff
Thanks for the test reports @jbergstroem. The uptime bug would only manifest under certain host configurations, so user results may vary depending on the host their Linodes are on. Otherwise, we anticipate having this issue completely resolved in the next few weeks, so stay tuned.
We're starting to fall behind again. Any news to share? Thanks!
The kernel listing page at https://www.linode.com/kernels/ now seems taken down. Is there another url to get the same information? Whats going on?
bbigger
Linode Staff
Thanks again for your reports @jbergstroem — we've since restored https://www.linode.com/kernels/