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 10-31-2017, 05:23 AM   #16
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib."
Posts: 3,633
Blog Entries: 1

Rep: Reputation: 962Reputation: 962Reputation: 962Reputation: 962Reputation: 962Reputation: 962Reputation: 962Reputation: 962

As previously mentioned, it is the kernel.
My "new" box is about 2 months old and running a Ryzen CPU. With the 4.9.xx series it would reboot itself and or shut itself down. With the 4.13.xx series (Thanks to 55020) it runs perfectly, as far as I can tell. That is to say, it has yet to reset itself or shutdown while running the 4.13.xx kernel and it runs 24/7.

Last edited by cwizardone; 10-31-2017 at 12:00 PM.
 
1 members found this post helpful.
Old 11-10-2017, 04:01 PM   #17
mfoley
Senior Member
 
Registered: Oct 2008
Posts: 1,159

Original Poster
Rep: Reputation: 103Reputation: 103
Replacement Ryzen 5 1600 received from AMD today and installed. We'll see ...

November 18, 2017 ...

No halts after 9 days. I'll give this until the end of the month and if no halts I'll consider this closed.

Last edited by mfoley; 11-18-2017 at 01:24 PM.
 
1 members found this post helpful.
Old 11-26-2017, 01:02 AM   #18
mfoley
Senior Member
 
Registered: Oct 2008
Posts: 1,159

Original Poster
Rep: Reputation: 103Reputation: 103
Bad news Machine halted on November 23rd around 6AM. Last messages in /var/log/messages:
Code:
Nov 23 06:08:56 dennis dhcpcd[1169]: eth0: removing default route via 192.168.0.2
Nov 25 14:38:00 dennis syslogd 1.5.1: restart.
I manually restarted the computer on the 25th at 2:38P. It was not powered down, just completely unresponsive.

I guess before handing this system to a Windows user, I'll try the often suggested NEWER KERNEL.

So, where do I get this new kernel? bassmadrigal suggested I "use the SlackBuild for kernel-firmware to grab the latest firmware from kernel.org as that will contain any microcode updates for the processor." I didn't find anything on Slackbuilds, but perhaps I don't know what to search for. kernel.org has stable: 4.14.2. Should I try that with Slackware64 14.2? Should I build it on the prodigal computer?

Last edited by mfoley; 11-26-2017 at 01:24 AM.
 
Old 11-26-2017, 10:30 AM   #19
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 4,551

Rep: Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498
I ended up needing to tweak my kernel to finally prevent restarts on my system. I had to enable enable some custom options in the kernel and then pass rcu_nocbs=0-15 as a kernel parameter (although, the upper number needs to be adjusted to match your number of threads your processor supports minus one... so since my is 16 thread, my is 0-15). It's been up with no instability for 14 days so far, where before, it was usually freezing or restarting every 5 or so days.

https://bugzilla.kernel.org/show_bug.cgi?id=196683

As for the kernel firmware, the SlackBuild is from stock Slackware, so you can find it on your favorite Slackware mirror under source/a/kernel-firmware/.
 
2 members found this post helpful.
Old 11-26-2017, 11:37 AM   #20
mfoley
Senior Member
 
Registered: Oct 2008
Posts: 1,159

Original Poster
Rep: Reputation: 103Reputation: 103
Quote:
Originally Posted by bassmadrigal View Post
As for the kernel firmware, the SlackBuild is from stock Slackware, so you can find it on your favorite Slackware mirror under source/a/kernel-firmware/.
Some clarificaion needed ...

I did find kernel-firmware packages under https://mirrors.slackware.com/slackw...slackware64/a/, but all date from 2016. I understood this RYZEN problem to be more recent than that. Would this older firmware work or did you use something more recent?

I do have a /usr/src/linux/firmware directory that is the most recent 14.2. If you're just using "stock Slackware", could I not just use that?

Are the "stock Slackware" sources what I want and not the files from kernel.org? You mentioned kernel.org in your 10-31-17, 02:31 AM post to this thread. I thought the Slackware kernels pre-dating the RYZEN processor were the heart of the problem.

Last edited by mfoley; 11-26-2017 at 11:39 AM.
 
Old 11-26-2017, 11:51 AM   #21
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 4,551

Rep: Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498
Quote:
Originally Posted by mfoley View Post
Some clarificaion needed ...

I did find kernel-firmware packages under https://mirrors.slackware.com/slackw...slackware64/a/, but all date from 2016. I understood this RYZEN problem to be more recent than that. Would this older firmware work or did you use something more recent?

I do have a /usr/src/linux/firmware directory that is the most recent 14.2. If you're just using "stock Slackware", could I not just use that?

Are the "stock Slackware" sources what I want and not the files from kernel.org? You mentioned kernel.org in your 10-31-17, 02:31 AM post to this thread. I thought the Slackware kernels pre-dating the RYZEN processor were the heart of the problem.
The directory does not contain a tarball, rather the SlackBuild will go and grab the latest firmware from kernel.org and package it into a Slackware package, which you can then use upgradepkg to upgrade the original package.
 
1 members found this post helpful.
Old 11-26-2017, 12:18 PM   #22
mfoley
Senior Member
 
Registered: Oct 2008
Posts: 1,159

Original Poster
Rep: Reputation: 103Reputation: 103
Quote:
Originally Posted by bassmadrigal View Post
The directory does not contain a tarball, rather the SlackBuild will go and grab the latest firmware from kernel.org and package it into a Slackware package, which you can then use upgradepkg to upgrade the original package.
I guess you're going to have to baby-step me through this. I've checked SlackBuilds.org and see no results for "kernel-firmware", nor any results related to "firmware" for the Linux kernel. I don't know what you mean by "SlackBuild will go and grab the latest firmware from kernel.org and package." I've never seen such a mechanism for SlackBuilds. Heretofore, my accessing packages on SlackBuilds has always involved downloading a pre-made tarball.

So, what is my first step here?
 
Old 11-26-2017, 12:26 PM   #23
khronosschoty
Member
 
Registered: Jul 2008
Distribution: Slackware
Posts: 239
Blog Entries: 2

Rep: Reputation: 81
Quote:
Originally Posted by mfoley View Post
I guess you're going to have to baby-step me through this. I've checked SlackBuilds.org and see no results for "kernel-firmware", nor any results related to "firmware" for the Linux kernel. I don't know what you mean by "SlackBuild will go and grab the latest firmware from kernel.org and package." I've never seen such a mechanism for SlackBuilds. Heretofore, my accessing packages on SlackBuilds has always involved downloading a pre-made tarball.

So, what is my first step here?
Here is the SlackBuild you are looking for, I do believe. http://ftp.slackware.com/pub/slackwa...rnel-firmware/
 
Old 11-26-2017, 02:53 PM   #24
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 4,551

Rep: Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498
Quote:
Originally Posted by mfoley View Post
I guess you're going to have to baby-step me through this. I've checked SlackBuilds.org and see no results for "kernel-firmware", nor any results related to "firmware" for the Linux kernel. I don't know what you mean by "SlackBuild will go and grab the latest firmware from kernel.org and package." I've never seen such a mechanism for SlackBuilds. Heretofore, my accessing packages on SlackBuilds has always involved downloading a pre-made tarball.

So, what is my first step here?
SlackBuild is a generic term for a shell script that builds a Slackware package. It can house any number of commands that will ultimately lead it to generating a Slackware package. SBo holds a repo of user-submitted SlackBuilds, but the design of those scripts were based on SlackBuilds used for official Slackware packages, however, per SBo policy, the scripts cannot be used to download sources, where Pat is more relaxed on that. So, some of the SlackBuilds for official Slackware packages will go and grab the latest source automatically, which is the case in the kernel-firmware SlackBuild.

When I say you need to go to your favorite mirror, you're going to an official Slackware mirror, under the source directory, then navigating to a/kernel-firmware/. Download the SlackBuild and slack-desc file and have them in the same directory. Then, as root, run the SlackBuild (you may need to make it executable), which will then get the latest snapshot from the kernel's firmware git page which will then use that to create a new Slackware package.

Since it is normally an official package provided by Pat, you won't find it on SBo.

Hopefully that clears it up.
 
1 members found this post helpful.
Old 11-28-2017, 12:16 PM   #25
mfoley
Senior Member
 
Registered: Oct 2008
Posts: 1,159

Original Poster
Rep: Reputation: 103Reputation: 103
bassmadrigal: Thanks, I wasn't aware of any of that. So, I just did as you instructed going to https://mirrors.slackware.com/slackw...rnel-firmware/ and downloaded kernel-firmware.SlackBuild. I've diff'd this with the one downloaded from khronosschoty's link and they are the same. I ran the slackBuild and it created a package:
Code:
Slackware package /tmp/kernel-firmware-20171128git-noarch-1.txz created.
Before I install this package, can one of you tell me what it actually does? There is no README that I can find in the /tmp package structure. I had expected firmware source to get updated in /usr/src/linux/firmware, and then to have to run `make menuconfig`, compile the kernel, etc. But I'm not sure what the Slackware package is going to do. Will it create a new kernel for me? Will it get installed in /boot? Running `slackpkg --warn kernel-firmware-20171128git-noarch-1.txz` shows only /lib/firmware being updated, so I guess an actual new kernel is not being created, right? Please advise if you can -- I cower before the possibilities!

Also, do I assume correctly that I must blacklist kernel and sources in /etc/slackpkg/blacklist and not upgrade my kernel via `slackpkg upgrade-all` until ... when? (Or maybe just blacklist kernel-firmware)

Lastly, if this doesn't work, will `slackpkg remove kernel-firmware-20171128git-noarch-1` work or will I have to restore from backup?

Sorry for all the questions ...

Last edited by mfoley; 11-28-2017 at 12:40 PM.
 
Old 11-28-2017, 12:58 PM   #26
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 4,551

Rep: Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498
There is no need to recompile the kernel to update the firmware package. The existing kernel will just use the new firmware package (after a reboot). However, if there is new firmware in the package, older kernels may not contain support for them, but it will just sit there harmlessly.

And if you're curious what the new package will do, you can run upgradepkg --dry-run /tmp/kernel-firmware-20171128git-noarch-1.txz to see exactly what it's going to do (which is likely the same output as slackpkg --warn, but I don't use slackpkg for things like that). But it will update the firmware located in /lib/firmware

You should blacklist the kernel-firmware package at least until Pat provides a newer version than what you're running (however, based on the 14.2 changelog, it may not happen since it still has the stock firmware package even though it's gone through several kernel upgrades). You should only blacklist the other kernel packages if you install some other version.

You don't need to use slackpkg to remove this package, in fact, it would probably fail since it is blacklisted. You can use the normal removepkg (which is all that slackpkg calls) script to remove it, or even upgradepkg to "upgrade" to whatever package you specify, even if it is a lower version. So, if you need to restore the stock package, you can either just remove the kernel-firmware package from slackpkg's blacklist or just download it from your favorite mirror and run upgradepkg on it.
 
Old 11-28-2017, 05:03 PM   #27
mfoley
Senior Member
 
Registered: Oct 2008
Posts: 1,159

Original Poster
Rep: Reputation: 103Reputation: 103
OK, package built, installed, machine rebooted (yeah! It came up). I guess I'll now wait and see if it stays up!
 
Old Today, 03:39 PM   #28
mfoley
Senior Member
 
Registered: Oct 2008
Posts: 1,159

Original Poster
Rep: Reputation: 103Reputation: 103
Nope: spontaneously halted again today. I've replaced the processor and installed the new firmware. If it's not the RYZEN processor it must be some other part of the hardware. I'm replacing the whole computer ASAP. The bad thing about this issue is that the office guinea pig is one of the main officers who is highly influential when it comes to computer choices. I was hoping the Linux OS would make a good impression and help us switch away from Windows. But in this case his Linux workstation crashes more often than the Windows workstations. Not making a good impression.
 
Old Today, 05:35 PM   #29
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 4,551

Rep: Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498
If you've got a some time, I'd highly recommend trying what I posted here. My Ryzen system was highly unstable before that, usually only lasting a few days before a lockup. I now have 25 days uptime without so much as a hiccup. Just a quick kernel compile and then passing an option to the kernel during startup.
 
1 members found this post helpful.
Old Today, 09:49 PM   #30
Drakeo
Senior Member
 
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,245
Blog Entries: 3

Rep: Reputation: 348Reputation: 348Reputation: 348Reputation: 348
Quote:
Originally Posted by RadicalDreamer View Post
I dunno but there have been media reports regarding Ryzen CPUs being RMA'd due to instability on Linux: https://duckduckgo.com/?q=ryzen+linu...&t=ffnt&ia=web

What Linux kernel are you using? You might want to try a newer one.
If slackware had been an issue with Ryzen I am sure Eric would have brought something up. His whole new build system is Ryzen 7.
Look around and see what Alien Bob ran into.
 
  


Reply

Tags
crash, kde, ryzen, slackware 14.2


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
Clean Slackware 14.2 install - pauses intermittently Ook Slackware 35 08-13-2016 10:36 AM
Slackware on VMware Workstation andres88_ Slackware 13 04-23-2014 10:13 AM
[SOLVED] VMWare Workstation 7.1.1 on Ubuntu 10.04 crashing vtoal Linux - Virtualization and Cloud 7 09-05-2010 09:48 PM
Slackware 10.1 Crashing dave`2005 Slackware 13 09-08-2005 12:48 AM

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

All times are GMT -5. The time now is 10:31 PM.

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