The Latest Kernel Release.

nobodino · 07-28-2018, 06:07 AM

nearly a new kernel every day: 4.14.59, 4.17.11, 4.9.116 and 4.4.145, it's hard to follow the good rythm!

cwizardone · 07-28-2018, 06:47 AM

And, not to be left out, 3.18.117.
For a kernel that has been designated EOL, it certainly gets a lot of updates.

https://www.kernel.org/

The change log, https://cdn.kernel.org/pub/linux/ker...geLog-3.18.117

The DUSK-4.4.145 and 4.17.11 kernels are now available at,
https://dusk.idlemoor.tk/

Poprocks · 07-29-2018, 12:58 PM

Damnit, that reminds me, I need to upgrade 3.2.83 on my server to something newer. No point in upgrading to 3.2.102 since it's the last release of that kernel and EOL as of June 2018.

I'm tempted to upgrade to 3.16 since Ben Hutchings is also its maintainer, but its projected EOL is 2020 whereas 4.4's is 2022. So I'll likely upgrade to 4.4.

I guess I could just accomplish that by upgrading to Slackware 14.2 on that server... But meh.

cwizardone · 07-29-2018, 05:13 PM

4.18-rc-7

The seventh release candidate of the mainline 4.18 series is now available for testing.

The tarball, https://git.kernel.org/torvalds/t/linux-4.18-rc7.tar.gz

Mr. Torvalds' announcement, http://lkml.iu.edu/hypermail/linux/k...7.3/04774.html

Quote:

Linux 4.18-rc7
From: Linus Torvalds
Date: Sun Jul 29 2018 - 18:09:21 EST

So unless something odd happens, this should be the last rc for 4.18.

Nothing particularly odd happened this last week - we got the usual
random set of various minor fixes all over. About two thirds of it is
drivers - networking, staging and usb stands out, but there's a little
bit of stuff all over (clk, block, gpu, nvme..).

Outside of drivers, the bulk is some core networking stuff, with
random changes elsewhere (minor arch updates, filesystems, core
kernel, test scripts).

The appended shortlog gives a flavor of the details.

Linus

---

MarcT · 07-30-2018, 07:39 AM

Has anyone been able to use 4.17 or 4.18-rc (possibly anything 4.15 upwards) with the amdgpu driver and the new DC/"display core"/DAL code?

For me it emits a load of warnings during boot; eg for 4.18-rc6:

[ 9.167769] WARNING: CPU: 4 PID: 1133 at drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_base.c:64 dal_gpio_open_ex+0xc/0x30 [amdgpu]
[ 9.184735] WARNING: CPU: 4 PID: 1133 at drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:488 dal_ddc_open+0x31/0xe0 [amdgpu]
[ 9.246097] WARNING: CPU: 10 PID: 1134 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:88 dm_dp_aux_transfer+0xa5/0xb0 [amdgpu]
[ 9.411094] WARNING: CPU: 4 PID: 1133 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:88 dm_dp_aux_transfer+0xa5/0xb0 [amdgpu]

(Slackware-current, AMD Ryzen 2700x, Radeon RX 480)

Another slacker filed a bug: https://bugs.freedesktop.org/show_bug.cgi?id=105725
...but no progress.

I'm thinking it may be something to do with Slackware's kernel config, but I don't know for sure.

cwizardone · 08-03-2018, 05:18 AM

Kernel updates 4.17.12, 4.14.60 and 4.9.117 are now available at, https://www.kernel.org/

The change logs,

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.17.12

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.14.60

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.9.117

The DUSK-4.17.12 kernel is now available at,
https://dusk.idlemoor.tk/

cwizardone · 08-05-2018, 05:34 PM

4.18-rc-8

The eighth and what should be the final release candidate of the mainline 4.18 series, is now available for testing.

The tarball, https://git.kernel.org/torvalds/t/linux-4.18-rc8.tar.gz

Mr. Torvalds' announcement, http://lkml.iu.edu/hypermail/linux/k...8.0/04294.html

cwizardone · 08-06-2018, 11:47 AM

Kernel updates 4.17.13, 4.14.61, 4.9.118 and 4.4.146 are now available at, https://www.kernel.org/

The change logs,

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.17.13

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.14.61

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.9.118

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.4.146

The dusk-4.17.13 and 4.4.146 kernels are now available at,
https://dusk.idlemoor.tk/

cwizardone · 08-09-2018, 05:56 AM

Kernel updates 4.17.14, 4.14.62, 4.9.119, 4.4.147 and 3.18.118 [EOL] are now available at, https://www.kernel.org/

The change logs,

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.17.14

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.14.62

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.9.119

https://cdn.kernel.org/pub/linux/ker...ngeLog-4.4.147

https://cdn.kernel.org/pub/linux/ker...geLog-3.18.118

cwizardone · 08-09-2018, 01:37 PM

The dusk-4.4.147 and 4.17.14 kernels are now available at,
https://dusk.idlemoor.tk/

FWIW, the dusk-4.17.14 kernel is installed on this box and is running fine with -current and the Nvidia-390.77 driver.

cwizardone · 08-12-2018, 04:17 PM

The Stable 4.18 kernel has been released.

The tarball, https://cdn.kernel.org/pub/linux/ker...ux-4.18.tar.xz

Mr. Torvalds announcement,
http://lkml.iu.edu/hypermail/linux/k...8.1/02806.html

Quote:

Linux 4.18
From: Linus Torvalds
Date: Sun Aug 12 2018 - 17:08:16 EST

One week late(r) and here we are - 4.18 is out there.

It was a very calm week, and arguably I could just have released on
schedule last week, but we did have some minor updates. Mostly
networking, but some vfs race fixes (mentioned in the rc8 announment
as "pending") and a couple of driver fixes (scsi, networking, i2c).
Some other minor random things (arm crypto fix, parisc memory ordering
fix). Shortlog appended for the (few) details.

Some of these I was almost ready to just delay to until the next merge
window, but they were marked for stable anyway, so it would just have
caused more backporting. The vfs fixes are for old races that are
really hard to hit (which is obviously why they are old and weren't
noticed earlier). Some of them _have_ been seen in real life, some of
them probably need explicit help to ever trigger (ie artificial delays
just to show that "yes, this can actually happen in theory").

Anyway, with this, the merge window for 4.19 is obviously open, and
I'll start pulling tomorrow. I already have a couple of dozen pull
requests pending due to the one-week delay of 4.18, but keep them
coming.

Linus

---

Lysander666 · 08-12-2018, 04:32 PM

Anyone still keeping an eye on how things are going with their system kernel and meltdown/spectre? Here is how it's shaping up on 4.4.144 [64-bit]:

Code:

lysander@psychopig-xxxiv:~$ gawk '{ print FILENAME ":\t" $0 }' /sys/devices/system/cpu/vulnerabilities/*
/sys/devices/system/cpu/vulnerabilities/meltdown:	Mitigation: PTI
/sys/devices/system/cpu/vulnerabilities/spec_store_bypass:	Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v1:	Mitigation: __user pointer sanitization
/sys/devices/system/cpu/vulnerabilities/spectre_v2:	Mitigation: Full generic retpoline

That second line wasn't always there. I completely missed any information on this fourth variant.

smaclennan · 08-12-2018, 04:55 PM

Quote:

Originally Posted by Lysander666

Anyone still keeping an eye on how things are going with their system kernel and meltdown/spectre? Here is how it's shaping up on 4.4.144 [64-bit]:

Code:

lysander@psychopig-xxxiv:~$ gawk '{ print FILENAME ":\t" $0 }' /sys/devices/system/cpu/vulnerabilities/*
/sys/devices/system/cpu/vulnerabilities/meltdown:	Mitigation: PTI
/sys/devices/system/cpu/vulnerabilities/spec_store_bypass:	Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v1:	Mitigation: __user pointer sanitization
/sys/devices/system/cpu/vulnerabilities/spectre_v2:	Mitigation: Full generic retpoline

That second line wasn't always there. I completely missed any information on this fourth variant.

IIRC you need a microcode update that allows you to disable the speculative store bypass. However, there is a noticeable performance penalty to doing this.

AlleyTrotter · 08-12-2018, 05:16 PM

[QUOTE=cwizardone;5891001]The Stable 4.18 kernel has been released.

The tarball, https://cdn.kernel.org/pub/linux/ker...ux-4.18.tar.xz
]

up and running
john