Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

The latest bad news.

Feel free to talk about anything and everything in this board. Just don't post offensive topics that are meant to cause trouble with other members or are derogatory towards people of different genders, race, color, minors (this includes nudity and sex), politics or religion. Let's try to keep peace among the community and for visitors.

No spam on this or any other forums please! If you post advertisements on these forums, your account may be deleted.

Do not copy and paste entire or even up to half of someone else's words or articles into posts. Post only a few sentences or a paragraph and make sure to include a link back to original words or article. Otherwise it's copyright infringement.

You can talk about other distros here, but no MX bashing. You can email the developers of MX if you just want to say you dislike or hate MX.
Message
Author
dr-kart
Forum Regular
Forum Regular
Posts: 122
Joined: Sun Oct 22, 2017 8:12 pm

Re: The latest bad news.

#41 Post by dr-kart » Thu Jan 04, 2018 7:37 pm

:sad: sandy bridge core i5
dd if=/dev/zero of=/tmp/testfile bs=512 count=5000000

4.9.0-4-amd64 #1 SMP Debian 4.9.65-3+deb9u1 (2017-12-23)

Code: Select all

...2,45611 s, 1,0 GB/s
4.9.0-5-amd64 #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04)

Code: Select all

...4,0773 s, 628 MB/s
:bawling: 4.14.0-3-amd64 #1 SMP Debian 4.14.12-2~mx17+1 (2018-01-06)

Code: Select all

...4,08073 s, 627 MB/s
seems like PCID didn't help so far with 4.14 kernel https://groups.google.com/forum/m/#!top ... 9mHTbeQLNU
Last edited by dr-kart on Tue Jan 09, 2018 7:05 am, edited 2 times in total.

User avatar
bwich12
Forum Regular
Forum Regular
Posts: 182
Joined: Tue Jul 12, 2016 9:14 am

Re: The latest bad news.

#42 Post by bwich12 » Fri Jan 05, 2018 4:56 am

dr-kart wrote:As far as I'm concerned

meltdown - (intel CPUs are vulnerable. AMD owners can ignore)
patch for debian kernel (4.9.65-3+deb9u2) is in sources already
https://security-tracker.debian.org/tra ... -2017-5754

spectre - 100% resolution is in future hardware. So would never get fixed via soft only.
Still hoping for new updated microcode to arrive anyway ).
And imho it's too much fuss here. Amazon cloud etc. should be nervous for sure. Not us. Btw spectre is much harder to exploit in real life.

PS (easy explanation of the story)
https://arstechnica.com/gadgets/2018/01 ... ity-flaws/
This is probably the best and most concise elaboration in this whole thread spilling over with misinformation and FUD. Meltdown is basically dealt with, and Spectre (especially variant 1), though there are mitigation measures, is ultimately unfixable. Another readable article is here: https://www.theregister.co.uk/2018/01/0 ... explained/

If architects built bridges and airplane designers built planes like hardware and software "engineers" build CPUs and applications, nobody would walk over a bridge and nobody would ever use an airplane.

User avatar
v3g4n
Forum Guide
Forum Guide
Posts: 1783
Joined: Sat Jan 16, 2016 8:20 pm

Re: The latest bad news.

#43 Post by v3g4n » Fri Jan 05, 2018 9:46 am

Thanks for enlightening us all with your words of wisdom taken from an article posted today.

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15965
Joined: Fri Dec 15, 2006 8:07 pm

Re: The latest bad news.

#44 Post by Stevo » Fri Jan 05, 2018 2:25 pm

Slowdown not as bad for my machine on the ported Liquorix 4.14-11 kernel. Intel Core i5-6200U

Booted with "nopti":

Code: Select all

2560000000 bytes (2.6 GB, 2.4 GiB) copied, 11.0231 s, 232 MB/s
Standard boot:

Code: Select all

2560000000 bytes (2.6 GB, 2.4 GiB) copied, 12.0607 s, 212 MB/s

User avatar
smilliken
Forum Guide
Forum Guide
Posts: 2116
Joined: Tue Feb 06, 2007 11:47 pm

Re: The latest bad news.

#45 Post by smilliken » Fri Jan 05, 2018 2:27 pm

timkb4cq wrote:Glad my machines are AMD.
According to this https://www.raspberrypi.org/blog/why-ra ... -meltdown/ AMD's are also included, along with ARM.
There is no "Ctrl+Z" in life!
Panasonic Toughpad FZ-G1 - MX-17
Acer 7551G MX-17 | Dell 1525, MX17 & Win 10
HP DV4-1118 Mx17 & Win 10
HP CP1215/Brother DCP-7065DN
Linux User# 4523410

User avatar
timkb4cq
Forum Veteran
Forum Veteran
Posts: 4304
Joined: Wed Jul 12, 2006 4:05 pm

Re: The latest bad news.

#46 Post by timkb4cq » Fri Jan 05, 2018 2:42 pm

Spectre affects AMD. Meltdown does not. Meltdown is the what the KAISER patches fix, and they are what slows down execution of calls to the kernel.
They still don't know how to completely fix Spectre since its leaking is primarily between different user processes - which includes between a VM & its Hypervisor. It does this primarily through shared libraries, since their address space is accessible to all users.

We live in interesting times...
MSI 970A-G43 MB, AMD FX-6300 (six core), 16GB RAM, GeForce 730, Samsung 850 EVO 250GB SSD, Seagate Barracuda XT 3TB

User avatar
smilliken
Forum Guide
Forum Guide
Posts: 2116
Joined: Tue Feb 06, 2007 11:47 pm

Re: The latest bad news.

#47 Post by smilliken » Fri Jan 05, 2018 3:10 pm

Sounds very ugly. Is MX waiting to see what comes down from Debian, or how do you deal with it?

Excuse me if this was answered prior to this post. Might be worth adding a sticky if it hasn't been done already.

Thanks Tim.
There is no "Ctrl+Z" in life!
Panasonic Toughpad FZ-G1 - MX-17
Acer 7551G MX-17 | Dell 1525, MX17 & Win 10
HP DV4-1118 Mx17 & Win 10
HP CP1215/Brother DCP-7065DN
Linux User# 4523410

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 15965
Joined: Fri Dec 15, 2006 8:07 pm

Re: The latest bad news.

#48 Post by Stevo » Fri Jan 05, 2018 3:33 pm

smilliken wrote:Sounds very ugly. Is MX waiting to see what comes down from Debian, or how do you deal with it?

Excuse me if this was answered prior to this post. Might be worth adding a sticky if it hasn't been done already.

Thanks Tim.
It's still in flux. 4.14.12 fixes problems discovered for some people with KPTI in 4.14.11, for example.

User avatar
uncle mark
Forum Veteran
Forum Veteran
Posts: 4966
Joined: Sat Nov 11, 2006 10:42 pm

Re: The latest bad news.

#49 Post by uncle mark » Mon Jan 08, 2018 6:35 pm

And the hits just keep on coming:

https://betanews.com/2018/01/08/microso ... s-amd-pcs/

<q>
Details of the problem have been gradually emerging through reports posted by users on Microsoft Answers. People with AMD Athlon-powered computers say that following the installation of the patch, it is impossible to boot into Windows leaving a full reinstallation as the only option -- although some users report that even this does not fix the problem.
</q>
Desktop: Custom build Asus/AMD/nVidia -- MEPIS 11
Laptop: Acer Aspire 5250 -- MX-15
Assorted junk: assorted Linuxes

User avatar
j2mcgreg
Forum Regular
Forum Regular
Posts: 363
Joined: Tue Oct 23, 2007 12:04 pm

Re: The latest bad news.

#50 Post by j2mcgreg » Fri Feb 02, 2018 12:14 pm

Details of the problem have been gradually emerging through reports posted by users on Microsoft Answers. People with AMD Athlon-powered computers say that following the installation of the patch, it is impossible to boot into Windows leaving a full reinstallation as the only option -- although some users report that even this does not fix the problem.
The article only says that only users with older AMD kit are having this problem, but it doesn't say what versions of Windows are involved. When Microsoft initially released Win 10, video cards with Win 8.1 supported drivers worked fine. Not anymore. Coincidental to the widespread exposure of the cpu flaws, Microsoft now requires video cards to be fully supported in Win 10. I have a number of clients who experienced this problem and who had their problem solved by switching out their existing video card for a known good one.

In fairness the the article's author(s), the average Windows user is going to equate a black screen with a complete failure to boot. And they won't understand that, since updates in Win 10 can not be turned off, re-installation is a fool's errand because Win 10 will continue to fail to locate an appropriate driver.

in short blame Microsoft for slipping this in under the radar, and blame AMD for not updating their legacy drivers after the fact.
Acer Aspire 5742: Intel i3 M370, Intel HD graphics, 4 GB ram, 500 GB hdd, Broadcom wireless n adapter

Post Reply

Return to “General”