LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-05-2019, 07:23 PM   #1216
abga
Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 945

Rep: Reputation: 493Reputation: 493Reputation: 493Reputation: 493Reputation: 493

Michael Larabel (phoronix) just did some interesting overhead benchmarking for the current (out of the box) Spectre&Meltdown mitigations on the newly released 5.0 kernel:

https://www.phoronix.com/scan.php?pa...meltdown&num=1
Quote:
Of 57 benchmarks tested on these three systems with the Linux 5.0 kernel, the Core i9 7980XE performance was down by about 13% based upon the geometric mean of all the test results. The Intel Core i7 8086K performance was down by 17% with these out-of-the-box protections for Spectre and Meltdown.
 
2 members found this post helpful.
Old 03-10-2019, 06:46 AM   #1217
mats_b_tegner
Member
 
Registered: Nov 2009
Location: Gothenburg, Sweden
Distribution: Slackware64
Posts: 488

Rep: Reputation: 277Reputation: 277Reputation: 277
Linux kernels 5.0.1, 4.20.15 and 4.19.28 are out:
https://cdn.kernel.org/pub/linux/ker...hangeLog-5.0.1
https://cdn.kernel.org/pub/linux/ker...ngeLog-4.20.15
https://cdn.kernel.org/pub/linux/ker...ngeLog-4.19.28
 
4 members found this post helpful.
Old 03-13-2019, 04:43 PM   #1218
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,523

Original Poster
Blog Entries: 1

Rep: Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825
Kernel updates 5.0.2, 4.20.16, 4.19.29, 4.14.106 and 4.9.163 are now available at

https://www.kernel.org/

The change logs,

https://cdn.kernel.org/pub/linux/ker...hangeLog-5.0.2

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

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

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

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

The change logs for kernels 5.0.2, 4.20.16 and 4.19.29 are showing three or
four reverts each.

The changes logs for 4.14.106 and 4.9.163 are showing the following Spectre fix,
Quote:
commit 3001a9c2d9349cd4eef5043126a55a5365719034
Author: Gustavo A. R. Silva <gustavo@embeddedor.com>
Date: Wed Jan 9 16:05:10 2019 -0600

applicom: Fix potential Spectre v1 vulnerabilities

commit d7ac3c6ef5d8ce14b6381d52eb7adafdd6c8bb3c upstream.

IndexCard is indirectly controlled by user-space, hence leading to
a potential exploitation of the Spectre variant 1 vulnerability.

This issue was detected with the help of Smatch:

drivers/char/applicom.c:418 ac_write() warn: potential spectre issue 'apbs' [r]
drivers/char/applicom.c:728 ac_ioctl() warn: potential spectre issue 'apbs' [r] (local cap)

Fix this by sanitizing IndexCard before using it to index apbs.

Notice that given that speculation windows are large, the policy is
to kill the speculation on the first load and not worry if it can be
completed with a dependent load/store [1].

[1] https://lore.kernel.org/lkml/2018042...hcp22.suse.cz/

Cc: stable@vger.kernel.org
Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Last edited by cwizardone; 03-13-2019 at 05:39 PM.
 
3 members found this post helpful.
Old 03-14-2019, 04:23 PM   #1219
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,523

Original Poster
Blog Entries: 1

Rep: Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825
There is a regression in 5.0.2:

http://lkml.iu.edu/hypermail/linux/k...3.1/06457.html

Quote:
Re: [Regression] Re: Linux 5.0.2
From: Alan J. Wylie
Date: Thu Mar 14 2019 - 16:43:20 EST

In reply to: Greg KH: "Re: [Regression] Re: Linux 5.0.2"

(Adding Linus, since his tree is also broken)

Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> writes:

> On Thu, Mar 14, 2019 at 07:59:00PM +0000, Alan J. Wylie wrote:
>> Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> writes:
>>
>> > I'm announcing the release of the 5.0.2 kernel.
>>
>> There is a regression for AMD-only builds.
>
> Adding the stable list, which people should do...
>
>>
>> See also Alec Ari's report:
>> https://lkml.org/lkml/2019/3/13/1113
>>
>> > If CONFIG_CPU_SUP_INTEL is disabled with either the 5.0.2 or 4.20.16
>> > kernel, it errors out right away:
>>
>> $ grep "CONFIG_CPU_SUP_" .config
>> # CONFIG_CPU_SUP_INTEL is not set
>> CONFIG_CPU_SUP_AMD=y
>> # CONFIG_CPU_SUP_HYGON is not set
>> # CONFIG_CPU_SUP_CENTAUR is not set
>>
>> CC arch/x86/events/core.o
>> In file included from arch/x86/events/core.c:44:
>> arch/x86/events/perf_event.h:1035:45: warning: ‚struct cpu_hw_event‚ declared inside parameter list will not be visible outside of this definition or declaration
>> static inline int intel_cpuc_prepare(struct cpu_hw_event *cpuc, int cpu)
>> ^~~~~~~~~~~~
>> arch/x86/events/perf_event.h:1040:45: warning: ‚struct cpu_hw_event‚ declared inside parameter list will not be visible outside of this definition or declaration
>> static inline void intel_cpuc_finish(struct cpu_hw_event *cpuc)
>> ^~~~~~~~~~~~
>> arch/x86/events/core.c: In function ‚free_fake_cpuc‚:
>> arch/x86/events/core.c:1998:20: error: passing argument 1 of ‚intel_cpuc_finish‚ from incompatible pointer type [-Werror=incompatible-pointer-types]
>> intel_cpuc_finish(cpuc);
>> ^~~~
>> In file included from arch/x86/events/core.c:44:
>> arch/x86/events/perf_event.h:1040:59: note: expected ‚struct cpu_hw_event *‚ but argument is of type ‚struct cpu_hw_events *‚
>> static inline void intel_cpuc_finish(struct cpu_hw_event *cpuc)
>> ~~~~~~~~~~~~~~~~~~~~~^~~~

>> arch/x86/events/core.c: In function ‚allocate_fake_cpuc‚:
>> arch/x86/events/core.c:2012:25: error: passing argument 1 of
>> ‚intel_cpuc_prepare‚ from incompatible pointer type
>> [-Werror=incompatible-pointer-types] if (intel_cpuc_prepare(cpuc,
>> cpu)) ^~~~ In file included from arch/x86/events/core.c:44:
>> arch/x86/events/perf_event.h:1035:59: note: expected ‚struct
>> cpu_hw_event *‚ but argument is of type ‚struct cpu_hw_events *‚
>> static inline int intel_cpuc_prepare(struct cpu_hw_event *cpuc, int
>> cpu) ~~~~~~~~~~~~~~~~~~~~~^~~~ cc1: some warnings being treated as
>> errors
>
> Is this a regression?

5.0.1 was fine, git pulled, then "make oldconfig" just answering the default "N"s

> If so, what commit caused this?

It looks as if it's

commit 3ad8e57560d7652a66da12b41c668a593509f3ad
Author: Peter Zijlstra (Intel) <peterz@xxxxxxxxxxxxx>
Date: Tue Mar 5 22:23:15 2019 +0100

perf/x86/intel: Make cpuc allocations consistent

The cpuc data structure allocation is different between fake and
real cpuc's; use the same code to init/free both.

which is the commit which introduces the function:

+static inline int intel_cpuc_prepare(struct cpu_hw_event *cpuc, int cpu)

> Is this also an issue in Linus's tree right now?

Yes, as of 3b319ee220a8795406852a897299dbdfc1b09911

CC arch/x86/entry/common.o
arch/x86/events/core.c: In function ‚free_fake_cpuc‚:
arch/x86/events/core.c:1998:20: error: passing argument 1 of ‚intel_cpuc_finish‚ from incompatible pointer type [-Werror=incompatible-pointer-types]
intel_cpuc_finish(cpuc);
^~~~
Thanks
Alan

--
Alan J. Wylie https://www.wylie.me.uk/

Dance like no-one's watching. / Encrypt like everyone is.
Security is inversely proportional to convenience

Last edited by cwizardone; 03-14-2019 at 04:28 PM.
 
3 members found this post helpful.
Old 03-14-2019, 04:38 PM   #1220
GazL
Senior Member
 
Registered: May 2008
Posts: 4,951
Blog Entries: 15

Rep: Reputation: 2555Reputation: 2555Reputation: 2555Reputation: 2555Reputation: 2555Reputation: 2555Reputation: 2555Reputation: 2555Reputation: 2555Reputation: 2555Reputation: 2555
Phew! Looks like I dodged that one (intel box).
 
1 members found this post helpful.
Old 03-16-2019, 11:44 PM   #1221
rogan
Member
 
Registered: Aug 2004
Distribution: Slackware
Posts: 126

Rep: Reputation: 37
This occurs if you chose a build for AMD _only_.
5.0.2 works fine on my box ( AMD 9590 + Vega64 ).
 
1 members found this post helpful.
Old 03-17-2019, 04:41 PM   #1222
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,523

Original Poster
Blog Entries: 1

Rep: Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825
5.1-rc1

The newest "mainline" development kernel, version 5.1-rc1, has been been made available for testing.

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

Mr. Torvalds' comments,

http://lkml.iu.edu/hypermail/linux/k...3.2/00495.html

Quote:
Re: [GIT PULL] PCI changes for v5.1
From: Linus Torvalds
Date: Sun Mar 17 2019 - 17:19:26 EST

On Fri, Mar 8, 2019 at 9:31 AM Bjorn Helgaas <helgaas@xxxxxxxxxx> wrote:
>
> - Report PCIe links that become degraded at run-time (Alexandru Gagniuc)

Gaah. Only now as I'm about to do the rc1 release am I looking at new
runtime warnings, and noticing that this causes

genirq: Threaded irq requested with handler=NULL and !ONESHOT for irq 16
pcie_bw_notification: probe of 0000:00:1b.0cie010 failed with error -22

because you can't have a NULL handler for a level-triggered interrupt
(you need something to shut the interrupt off so that it doesn't keep
screaming!).

Happens on both my desktop and my laptop, regular intel CPU and
chipset, nothing odd in either case.

Everything else works, but the new BW notification obviously will
never work this way.

This is not holding up rc1, obviously, but I thought I'd mention it
since I noticed it as part of my "let's see that nothing regressed"
checks..

Linus
Mr. Torvalds' announcement,

http://lkml.iu.edu/hypermail/linux/k...3.2/00496.html

Quote:
Linux 5.1-rc1
From: Linus Torvalds
Date: Sun Mar 17 2019 - 17:51:09 EST

It's Sunday, and two weeks have passed, and everything is normal. You
all know the drill by now - the merge window is closed, and things are
supposed to calm down.

The merge window felt fairly normal to me. And looking at the stats,
nothing really odd stands out either. It's a regular sized release
(which obviously means "big" - , but it's not bigger than usual) and
the bulk of it (just over 60%) is drivers. All kinds of drivers, the
one that stands out for being different is the habanalabs AI
accelerator chip driver, but I suspect we'll be starting to see more
of that kind of stuff. But there are all the usual suspects too - gpu,
networking, block devices etc etc.

A somewhat recent development is how the tools/testing/ updates have
been quite noticeable lately. That's not new to the 5.1 merge window,
it's been going on for a while, but it's maybe just worth a mention
that we have more new selftest changes than we have architecture
updates, for example. The documentation subdirectory is also quite
noticeable.

But on the whole, there's really stuff all over, including core VFS
updates (in addition to all the usual low-level filesystem updates
too, of course).

And as always, the shortlog is much too big to post with 11k+ commits
(12k+ if counting merges). So below is my usual "mergelog" listing
submaintainers and a summary of the git pulls I've done from them..

Go forth and test,

Linus

---

Last edited by cwizardone; 03-17-2019 at 05:31 PM.
 
Old 03-18-2019, 09:26 AM   #1223
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,523

Original Poster
Blog Entries: 1

Rep: Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825
Another round of kernel updates has been scheduled for release Wednesday morning, GMT/UTC.
If there are no problems testing the release candidates they should be available sometime
Tuesday.
 
Old 03-19-2019, 08:33 AM   #1224
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,523

Original Poster
Blog Entries: 1

Rep: Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825
Kernel updates 5.0.3, 4.20.17 [EOL], 4.19.30, 4.14.107 and 4.9.164 are now available at

https://www.kernel.org/

The change logs,

https://cdn.kernel.org/pub/linux/ker...hangeLog-5.0.3

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

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

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

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


The 4.20.y series has been designated, End Of Life.
Quote:
From: Greg Kroah-Hartman
Date: Mon Mar 18 2019 - 05:29:00 EST
------------------
NOTE, this is going to be the LAST 4.20.y release. After this one, 4.20
will be end-of-life. Please move to the 5.0.y tree at this point in
time, or let me know why that is not possible.
------------------
All five changelogs report the same revert,
Quote:
commit c4bec922def2285707cd3be3a80be46467ad8cde
Author: YueHaibing <yuehaibing@huawei.com>
Date: Thu Feb 21 22:42:01 2019 +0800

mdio_bus: Fix use-after-free on device_register fails

[ Upstream commit 6ff7b060535e87c2ae14dd8548512abfdda528fb ]

KASAN has found use-after-free in fixed_mdio_bus_init,
commit 0c692d07842a ("drivers/net/phy/mdio_bus.c: call
put_device on device_register() failure") call put_device()
while device_register() fails,give up the last reference
to the device and allow mdiobus_release to be executed
,kfreeing the bus. However in most drives, mdiobus_free
be called to free the bus while mdiobus_register fails.
use-after-free occurs when access bus again, this patch
revert it to let mdiobus_free free the bus.......
Please see the change logs if you need more information.

Last edited by cwizardone; 03-20-2019 at 08:42 AM.
 
Old 03-19-2019, 04:47 PM   #1225
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,523

Original Poster
Blog Entries: 1

Rep: Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825
Went to install the 4.19.30 kernel and found the generic kernel is not finding its way to the /boot directory.

Quote:
bash-5.0$ ls
README.initrd coffee.dat elilo-x86_64.efi onlyblue.bmp vmlinuz-generic-4.19.28
System.map config grub onlyblue.dat vmlinuz-generic-4.19.29
System.map-generic-4.19.28 config-generic-4.19.28.x64 initrd-4.19.28.gz slack.bmp vmlinuz-huge
System.map-generic-4.19.29 config-generic-4.19.29.x64 initrd-4.19.29.gz slack14.0.2012.bmp vmlinuz-huge-4.19.28
System.map-huge-4.19.28 config-huge-4.19.28.x64 initrd-4.19.30.gz slackware64.bmp vmlinuz-huge-4.19.29
System.map-huge-4.19.29 config-huge-4.19.29.x64 initrd-tree tuxlogo.bmp vmlinuz-huge-4.19.30
System.map-huge-4.19.30 config-huge-4.19.30.x64 inside.bmp tuxlogo.dat
boot.0800 efi inside.dat vmlinuz
boot_message.txt elilo-ia32.efi map vmlinuz-generic
But, here is what is in /var/lib/pkgtools/packages,
Quote:
bash-5.0$ ls kernel*
kernel-firmware-20190314_7bc2464-noarch-1 kernel-headers-4.19.30-x86-1 kernel-modules-4.19.30-x86_64-1
kernel-generic-4.19.28-x86_64-1 kernel-huge-4.19.28-x86_64-1 kernel-source-4.19.28-noarch-1
kernel-generic-4.19.29-x86_64-1 kernel-huge-4.19.29-x86_64-1 kernel-source-4.19.29-noarch-1
kernel-generic-4.19.30-x86_64-1 kernel-huge-4.19.30-x86_64-1 kernel-source-4.19.30-noarch-1
kernel-headers-4.19.28-x86-1 kernel-modules-4.19.28-x86_64-1
kernel-headers-4.19.29-x86-1 kernel-modules-4.19.29-x86_64-1
 
Old 03-19-2019, 07:00 PM   #1226
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,753

Rep: Reputation: Disabled
No issue here (system based on Slackware64-14.2 with kernels 4.19.29 installed, then installpkg kernel-generic-4.19.30-x86_64-1.txz ):
Code:
oot[/home/didier/Tťlťchargements]# ls -ltr /boot/
total 34200
drwxr-xr-x 3 root root   16384 janv.  1  1970 efi
-rwxr-xr-x 1 root root  242346 mars  29  2013 elilo-x86_64.efi
-rwxr-xr-x 1 root root  214120 mars  29  2013 elilo-ia32.efi
-rw-r--r-- 1 root root  153718 mai    2  2016 image.bmp
-rw-r--r-- 1 root root     423 oct.   3  2017 tuxlogo.dat
-rw-r--r-- 1 root root   33192 oct.   3  2017 tuxlogo.bmp
-rw-r--r-- 1 root root     424 oct.   3  2017 onlyblue.dat
-rw-r--r-- 1 root root    6878 oct.   3  2017 onlyblue.bmp
-rw-r--r-- 1 root root     432 oct.   3  2017 inside.dat
-rw-r--r-- 1 root root   22578 oct.   3  2017 inside.bmp
-rw-r--r-- 1 root root     426 oct.   3  2017 coffee.dat
-rwxr-xr-x 1 root root    2245 nov.  26  2017 message.msg
-rwxr-xr-x 1 root root    1980 nov.  26  2017 help.msg
-rwxr-xr-x 1 root root    2158 nov.  26  2017 customization.msg
-rw-r--r-- 1 root root  185247 mars  14 03:26 config-huge-4.19.29.x64
-rw-r--r-- 1 root root 4940383 mars  14 03:28 System.map-huge-4.19.29
-rw-r--r-- 1 root root 9516928 mars  14 03:29 vmlinuz-huge-4.19.29
-rw-r--r-- 1 root root  185247 mars  14 03:29 config-generic-4.19.29.x64
-rw-r--r-- 1 root root 3531789 mars  14 03:29 System.map-generic-4.19.29
-rw-r--r-- 1 root root 6088576 mars  14 03:30 vmlinuz-generic-4.19.29
lrwxrwxrwx 1 root root      38 mars  18 23:58 README.initrd -> /usr/doc/mkinitrd-1.4.10/README.initrd
-rw-r--r-- 1 root root  185247 mars  19 19:10 config-generic-4.19.30.x64
-rw-r--r-- 1 root root 3531789 mars  19 19:10 System.map-generic-4.19.30
-rw-r--r-- 1 root root 6092672 mars  19 19:10 vmlinuz-generic-4.19.30
lrwxrwxrwx 1 root root      20 mars  20 00:21 vmlinuz-huge -> vmlinuz-huge-4.19.29
drwxr-xr-x 7 root root    4096 mars  20 00:37 grub
lrwxrwxrwx 1 root root      26 mars  20 00:55 System.map -> System.map-generic-4.19.30
lrwxrwxrwx 1 root root      26 mars  20 00:55 config -> config-generic-4.19.30.x64
lrwxrwxrwx 1 root root      23 mars  20 00:55 vmlinuz -> vmlinuz-generic-4.19.30
lrwxrwxrwx 1 root root      23 mars  20 00:55 vmlinuz-generic -> vmlinuz-generic-4.19.30
root[/home/didier/Tťlťchargements]#
 
2 members found this post helpful.
Old 03-20-2019, 01:05 AM   #1227
teoberi
Member
 
Registered: Jan 2018
Location: Romania
Distribution: Slackware64-current (servers) / Ubuntu (workstations)
Posts: 76

Rep: Reputation: 18
Upgrade 4.19.29 --> 4.19.30 on my test server and so no problem here.
 
1 members found this post helpful.
Old 03-22-2019, 09:37 AM   #1228
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,523

Original Poster
Blog Entries: 1

Rep: Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825
Another round of kernel updates has been scheduled for release just before Noon Sunday, GMT/UTC.
If no problems are found while testing the release candidates, they should be available sometime Saturday.

5.04, will have 238 patches.

4.19.31, will contain 280 patches.

4.14.108, will include 183 patches.

4.9.165, will incorporate 118 patches.

4.4.177, will assimilate 230 patches.

3.18.137, will integrate 134 patches.

Last edited by cwizardone; 03-22-2019 at 12:25 PM.
 
Old 03-23-2019, 08:40 AM   #1229
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,523

Original Poster
Blog Entries: 1

Rep: Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825
Kernel updates 4.14.108, 4.9.165, 4.4.177 and 3.18.137 are now available at

https://www.kernel.org/

The change logs,

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

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

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

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

Last edited by cwizardone; 03-24-2019 at 10:30 AM.
 
1 members found this post helpful.
Old 03-23-2019, 02:40 PM   #1230
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,523

Original Poster
Blog Entries: 1

Rep: Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825Reputation: 1825
Kernel updates 5.0.4 and 4.19.31 are now available at

https://www.kernel.org/

The change logs,

https://cdn.kernel.org/pub/linux/ker...hangeLog-5.0.4

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


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Linux.conf.au: Latest Linux kernel release due early March DragonSlayer48DX Linux - News 0 01-18-2010 10:43 PM
No video on latest kernel release Tralce Linux - Kernel 3 11-30-2006 07:48 AM
What is the latest Redhat release TILEMANN Linux - Software 5 11-20-2006 10:48 PM
LXer: News: OpenVZ To Release Support, Patches for Latest Kernel LXer Syndicated Linux News 0 11-01-2006 10:54 PM
latest debian release? doralsoral Linux - Software 5 12-25-2004 12:40 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:00 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration