New Linux 4.15-rc2 is out

https://marc.info/?l=linux-kernel&m=151231819021185&w=2

Download from https://www.kernel.org/

2 members found this post helpful.

Oops, aaazen had faster fingers.

Kernels 4.14.4, 4.9.67, 4.4.104 and 3.18.86[EOL] are out:
https://cdn.kernel.org/pub/linux/ker...angeLog-4.14.4
https://cdn.kernel.org/pub/linux/ker...-4.14.4.tar.xz
https://cdn.kernel.org/pub/linux/ker...angeLog-4.9.67
https://cdn.kernel.org/pub/linux/ker...-4.9.67.tar.xz
https://cdn.kernel.org/pub/linux/ker...ngeLog-4.4.104
https://cdn.kernel.org/pub/linux/ker...4.4.104.tar.xz
https://cdn.kernel.org/pub/linux/ker...ngeLog-3.18.86
https://cdn.kernel.org/pub/linux/ker...3.18.86.tar.xz

3 members found this post helpful.

The 4.14.4 kernel is running well here, but now there are other problems which seem to be the result of one package included in today's updates to -current; probably the new icu4c-60.1-x86_64-1.txz.

My understanding is that there are problems with linux 4.14.x either on intel 32bit or Ryzen?
Anyway, I have laptop with Haswell running 64bit so even though I started using 4.14.x as soon as it was first released by kernel.org I never had even single kernel crash. I do use my own config so kernel (I don't use initrd) is streamlined for specific hardware but I doubt that this helped. I assume that I am just lucky with hardware setup.

Regarding latest update: well after I rebooted, I ended up with system that did not recognize basic commands like installpkg or upgradepkg or removepkg. Of course GUI was gone. I am just happy that I never update main system before testing what interesting may happen by running update on virtual guest first, if this will go o.k. then I run update on the host. So this time it cost me just re-creating Slackware virtual guest..

1 members found this post helpful.

The easiest temporary fix to get -current and Alien Bob's November KDE up and running is to install icu4c from 14.2. I used this and I am happy for now: ftp://ftp.osuosl.org/pub/slackware/slackware64/slackware64/l/icu4c-56.1-x86_64-2.txz

1 members found this post helpful.

Problems with custom packages, I suppose, not anything in base Slackware(?)

It was significantly more unstable in 32-bit indeed, but even on 64-bit there were some crashes encountered apparently, not sure about Ryzen. Ivy Bridge here, I never had any problem with 4.14 either.

I think that is likely to break the packages recompiled for the new icu4c in the same update. If you need to have things like that working again in a hurry, I'd advise to quickly point /etc/slackpkg/mirrors to a mirror that hasn't synced yet, and do a slackpkg upgrade-all to trigger downgrades. And consider not tracking -current too closely, or at all.
Example (at the time of posting, of course): https://ftp.heanet.ie/mirrors/ftp.sl...pub/slackware/

1 members found this post helpful.

I have a Ryzen and I'm having kernel issues, but it's not specific to the 4.14 kernel. It originally occurred when I tried the 4.13 (didn't try any earlier than that), so I moved to the RCs of 4.14 and it occurs there. But it isn't the same issues others have been reporting with their kernels from Pat. Mine has no problems booting and will typically run for several days until it just completely locks up. Sometimes it turns the monitor on and leave it in a frozen state on the desktop (when the monitor should be off based on the system blanking the display and putting it to sleep after the 20 or so minutes) and other times the monitors stay off.

I was able to solve my issues by enabling the expert options of RCU configuration and enabling the suboption of "Offload RCU callback processing from boot-selected CPUs". I also had to pass rcu_nocbs=0-15 to the kernel during boot (the 0-15 is based on how many threads your CPU supports, so a 12 thread system would be 0-11). But it sounds like the issues others are having are unrelated to the segfault on boot issue others are having. So, I don't think Ryzen is affected in that matter.

2 members found this post helpful.

Fact is every time I had huge crashes it was after MariaDB it always broke samba unless I reinstalled it. Pat may know this been putting up with it for years freeze. but it is part of my circle now update reinstall.

I have not been able to make these crashes happen unless I upgrade kernel then reboot with grub vmlinuz-huge and a intrd from the previous kernel. Why would I do that because grub is a stupid problem wipes all my work. if you do not understand than do not worry. Wrong modules per kernel will not load and will not cause crash because they they never got entered. Cold start does not cause this problem for me.

Then hard power off then reboot do the same and it boots
this tells me the L2 instructions are stored and not cleared. So I wrote a script that updates the initrid.gz before rebooting with all modules.
If the ram on L2 is not cleared this problem started 18 months ago or more do not say you did not see it. Ok your blind to it.
why are they not cleared ask ask OLD bios. not new stuff.
It is pat's job to look for the bios issue not mine. How does Bios clear ROM. and the RAM.
I am sure there is a .config for the older stuff Hang in There Pat or Patch.

1 members found this post helpful.

Updated kernel 4.1.47 is now available at, https://www.kernel.org/.

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

A change log hasn't been posted (at the moment).

All --

Kernels 4.9.68, 4.4.105 and 3.18.87 are now available.

Handy Links:
No CVE References were found for 4.9.68, 4.4.105 or 3.18.87

As always, do check the ChangeLogs for other security-related fixes.

Check for the Latest Updates at www.kernel.org.

Have Fun All'Y'All !

-- kjh

Dang ... I just got around to booting 4.4.104 this morning

1 members found this post helpful.

Just reverted to the 4.13.16 kernel after the system froze, with the 4.14.4 kernel, for the second time.

I'll have to check the release date on the 4.14.xx series. Halloween would be appropriate, but I think it was later than that.

4.14.5 is ready:

https://www.kernel.org/
https://cdn.kernel.org/pub/linux/ker...-4.14.5.tar.xz
https://cdn.kernel.org/pub/linux/ker...angeLog-4.14.5

3 members found this post helpful.

The 3rd Release Candidate of the 4.15 "mainline" kernel is now available.

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

For all you AMD and AMD/ATi users kernels 4.15.x have 100 KLOC of new and improved support for that hardware

1 members found this post helpful.