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
Code: Select all
...4,0773 s, 628 MB/s
Code: Select all
...4,08073 s, 627 MB/s
Code: Select all
...2,45611 s, 1,0 GB/s
Code: Select all
...4,0773 s, 628 MB/s
Code: Select all
...4,08073 s, 627 MB/s
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/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/
Code: Select all
2560000000 bytes (2.6 GB, 2.4 GiB) copied, 11.0231 s, 232 MB/s
Code: Select all
2560000000 bytes (2.6 GB, 2.4 GiB) copied, 12.0607 s, 212 MB/s
According to this https://www.raspberrypi.org/blog/why-ra ... -meltdown/ AMD's are also included, along with ARM.timkb4cq wrote:Glad my machines are AMD.
It's still in flux. 4.14.12 fixes problems discovered for some people with KPTI in 4.14.11, for example.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.
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.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.