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.
Gah, I had a lock up in 4.19.42 yesterday and was waiting for a more 'stable' 4.19.4x, doesn't look like that's going to be happening any time soon. Just as well I still have 4.19.34, I think I'll stick with that one until this blows over.
EDIT: The headers are from 4.19.42 but I don't know if this makes any difference.
EDIT2: apparently not.
Last edited by Lysander666; 05-15-2019 at 02:43 PM.
Thanks! MDS mitigations are available in the changelog there. Need to wait now for the official release of 4.4.180, meanwhile preparing the systems - updating the microcode.
Wondering what the performance penalties would be with these kernel+microcode mitigations for MDS.
So, after 5.5 months, a vulnerability assigned a CVE in late 2018 is now being mitigated (I note that Windows 10 has also had an update to address this). Yet Intel claims it was previously aware.
From https://www.intel.com/content/www/us...ology/mds.html
Quote:
First identified by Intel's internal researchers and partners, and independently reported to Intel by external researchers...
At least the CEO at Volkswagen had the decency to resign when the company was caught cheating emission testing. Sadly, Intel is not displaying corporate accountability.
PS - And people wonder why a stable Slackware release is being delayed.
So, after 5.5 months, a vulnerability assigned a CVE in late 2018 is now being mitigated (I note that Windows 10 has also had an update to address this). Yet Intel claims it was previously aware.
From https://www.intel.com/content/www/us...ology/mds.html
At least the CEO at Volkswagen had the decency to resign when the company was caught cheating emission testing. Sadly, Intel is not displaying corporate accountability.
PS - And people wonder why a stable Slackware release is being delayed.
I noticed that statement myself and wondered, why on earth haven't they patched it earlier if they already knew about it...
Related to the corporate responsibility, they already lost a CEO and I have a more practical suggestion, they should refund the performance loss (percentage) out of their "Recommended Customer Price" for all these vulnerabilities (Meltdown&co). This recommended price looks to be present for all their CPUs: https://ark.intel.com/content/www/us...ml#@Processors
Last edited by abga; 05-16-2019 at 04:23 PM.
Reason: typo
Another round of updates has been scheduled for release just before Noon on Wednesday morning, GMT.
If no problems are found while testing the release candidates, they might be available sometime on Tuesday or early Wednesday morning (depending on your time zone).
Last edited by cwizardone; 05-20-2019 at 07:45 AM.
At least the CEO at Volkswagen had the decency to resign when the company was caught cheating emission testing. Sadly, Intel is not displaying corporate accountability.
PS - And people wonder why a stable Slackware release is being delayed.
Slackware can't afford resignation at CEO level - that's why the delay
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
), Jackie Gleason, "And Away We Go."
