SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Yes, i left the sysctl code in my desktop, but as Pat said, the nmi_watchdog has been disabled in the kernel config so it should have no effect on the system.
Looking at RadicalDreamer's screenshot plus that it seems intel machines that have trouble, is there something that has to be set differently with the IOMMU?
There seem to be hangs related to that. I noticed the other day with compiling virtual-box that IOMMU plays a part in virtualisation of I/O stuff and on my box it doesn't do a bit as my hardware does not support that kind of I/O, but this might be different on other machines...
This is the computer in question (I was lucky to get a better processor with it). I also forgot to say I'm using Slackware64-Current on this machine. I am using the Nouveau driver on this machine. Here are the specs: https://www.newegg.com/Product/Produ...82E16834101176
This is the computer in question (I was lucky to get a better processor with it). I also forgot to say I'm using Slackware64-Current on this machine. I am using the Nouveau driver on this machine. Here are the specs: https://www.newegg.com/Product/Produ...82E16834101176
Your laptop computer is similar with my mini-PC, which has a Intel Core2 Duo Mobile P8400 and other laptop-like hardware, but in a very small desktop case.
And in that mini-PC the single stable kernels are the 3.9.x series.
Well, i just got 3 system freeze today with 4.14.3 so i can't work on my desktop at home until i reverted back to 4.9.66. I guess i'll stay on 4.9.xx for a while and follow -current's work. I can keep testing 4.14 on my other x86_64 machines which still works fine there
Linux Kernel 4.14.4 is now out with tons of fixes as well. Hopefully that narrows down our issue
I'll compile it for /testing, but I'd already tested 4.14.4-rc1 and it wasn't any more stable here than 4.14.3. I did try removing all kernel options that depended on CONFIG_DEBUG_KERNEL or CONFIG_EXPERT hoping that might help, but it didn't.
I still suspect the stability will come from figuring out which option(s) are causing the instability and changing them. Or, if I can find the last working kernel a git bisect might shake out the primary bug, assuming there is one.
Sorry if I should start new thread with my question, but it appear with dealing with kernel packages which are the topic of this discussion.
So, when I entered on my Slackware-current (32 bit)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.