LGA2011 combo dalla Cina

[Jena Plisskin]

Prima e dopo il lockdown ho ricevuto in regalo una xbox360 e questa PS3 slim la 2004a, quest'ultima ci ho fatto un paio di partite questa estate. La riaccendo l'altra settimana e si spegne dopo nemmeno 10 secondi, nemmeno il tempo di entrare nella dash. Ho come al solito lurkato per internet ed ho fatto una manutenzione generale smontando tutta la PS3, pulendola dalla polvere (poca per la verità), pulendo i due processori e mettendo una artic mx4. Non pago ho pulito la lente del laser ed ho giocato con i trimmer dell'alimentatore.
Ora si accende e la maggior parte dei giochi parte e non si spegne, al contrario del primo Uncharted (che precedentemente nemmeno caricava, ora si carica ma appena dentro il gioco spegnimento della console) e Gods of war ascension. Quando si spegne fà i tre bip ed il led rosso resta a lamepggiare. Dovrebbe essere surriscaldamento ma la ventola non gira al massimo e sentendo la scocca è tiepido, non caldo. Mah misteri.
Se interessa però meglio aprire un altro topic.

[ragen-fio]

Aprilo se ti va, magari ne parliamo meglio perché anche io ne ho sistemate alcune recentemente.

[Jena Plisskin]

Eccolo

viewtopic.php?f=12&t=19161

e grazie

[Jena Plisskin]

Update sul fronte Xeon:

Windows 10 ha proposto una serie di update opzionali, quasi tutti con la descrizione driver xeon blah blha blah. Li ho installati e magicamente tutti i punti di sospensione nella gestione driver sono spariti, eccetto l'Intel Storage Management o simile, abilitandolo mi ritarda l'avvio del desktop. Disabilitandolo nessun problema.

Fronte Bios, ho rotto le scatole al venditore e mi ha inviato il bios, ovviamente senza specificare data, changelog o altro. Controllandolo con un editor esadecimale ho scoperto essere un boot con il turbo unlock, l'ho installato ed in effetti ora il turbo va a 3200 per tutti i core. Speravo in un cambiamento del SATA, ma niente purtroppo.

Fronte Sleep. Su Windows niente da fare, dovrei provare a forzare almeno l'ibernazione. Su Fedora ho scornato e parecchio. Il problema dello sleep è dovuto ai driver amdgpu e con vulkan attivo, ho una GCN1.0 e per attivarla bisogna inserire delle opzioni nel kernel, tolte queste lo sleep ha funzionato, ma lasciando accesa la ventola della cpu.

A presto spero di postare i bench con l'unlock attivato.

[Il nabbo di turno]

Beh ottima notizia, almeno hai un boost decente, per il resto sulle sata e sull'ibernazione ci chiuderei un occhio, se il sistema è stabile e prestante per quello che l'hai pagato non ci baderei troppo.

[Jena Plisskin]

Guarda ho ripreso a fare qualche conversione con handbrake, la differenza si vede tutta, direi 4x. Per 120€ scarse al momento non ci prendi nemmeno un 3200G, mi accontento alla grande. Le VM sotto kvm vanno alla grande, sto pensando di fare la spesa e prednere un NVME da 512GB, l'attuale SSD da 240G lo affiancherei ad un 120G che ho per i dati condivisi, home ecc. Il dubbio però è: funzionerà l'NVME ?

[speedyant]

Io l'ibernazione la disabilito sempre, fin dai tempi di xp.

[Scaveon]

C'è modo di sapere se in quel bios sono state applicate le patch per tutte le falle di sicurezza delle cpu Intel che sono saltate fuori negli ultimi tre anni?

[Jena Plisskin]

@Scaveon, ti allego l'ouput dello script linux per rilevare le vulnerabilità. E' un pò verboso, ma ad una prima occhiata direi di no. Qui non si vede, ma sulla console colora in rosso le vulnerabilità aperte, sono i CVE con
:KO alla fine dell'ouput.

Codice: Seleziona tutto

[jena@localhost ~]$ sudo spectre-meltdown-checker 
[sudo] password di jena: 
Spectre and Meltdown mitigation detection tool v0.44

Checking for vulnerabilities on current system
Kernel is Linux 5.9.12-100.fc32.x86_64 #1 SMP Wed Dec 2 15:58:24 UTC 2020 x86_64
CPU is Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz

Hardware check
* Hardware support (CPU microcode) for mitigation techniques
  * Indirect Branch Restricted Speculation (IBRS)
    * SPEC_CTRL MSR is available:  NO 
    * CPU indicates IBRS capability:  NO 
  * Indirect Branch Prediction Barrier (IBPB)
    * PRED_CMD MSR is available:  NO 
    * CPU indicates IBPB capability:  NO 
  * Single Thread Indirect Branch Predictors (STIBP)
    * SPEC_CTRL MSR is available:  NO 
    * CPU indicates STIBP capability:  NO 
  * Speculative Store Bypass Disable (SSBD)
    * CPU indicates SSBD capability:  NO 
  * L1 data cache invalidation
    * FLUSH_CMD MSR is available:  NO 
    * CPU indicates L1D flush capability:  NO 
  * Microarchitectural Data Sampling
    * VERW instruction is available:  NO 
  * Enhanced IBRS (IBRS_ALL)
    * CPU indicates ARCH_CAPABILITIES MSR availability:  NO 
    * ARCH_CAPABILITIES MSR advertises IBRS_ALL capability:  NO 
  * CPU explicitly indicates not being vulnerable to Meltdown/L1TF (RDCL_NO):  NO 
  * CPU explicitly indicates not being vulnerable to Variant 4 (SSB_NO):  NO 
  * CPU/Hypervisor indicates L1D flushing is not necessary on this system:  NO 
  * Hypervisor indicates host CPU might be vulnerable to RSB underflow (RSBA):  NO 
  * CPU explicitly indicates not being vulnerable to Microarchitectural Data Sampling (MDS_NO):  NO 
  * CPU explicitly indicates not being vulnerable to TSX Asynchronous Abort (TAA_NO):  NO 
  * CPU explicitly indicates not being vulnerable to iTLB Multihit (PSCHANGE_MSC_NO):  NO 
  * CPU explicitly indicates having MSR for TSX control (TSX_CTRL_MSR):  NO 
  * CPU supports Transactional Synchronization Extensions (TSX):  YES  (RTM feature bit)
  * CPU supports Software Guard Extensions (SGX):  NO 
  * CPU supports Special Register Buffer Data Sampling (SRBDS):  NO 
  * CPU microcode is known to cause stability problems:  NO  (family 0x6 model 0x3f stepping 0x2 ucode 0x0 cpuid 0x306f2)
  * CPU microcode is the latest known available version:  NO  (latest version is 0x44 dated 2020/05/27 according to builtin firmwares DB v165.20201021+i20200616)
* CPU vulnerability to the speculative execution attack variants
  * Vulnerable to CVE-2017-5753 (Spectre Variant 1, bounds check bypass):  YES 
  * Vulnerable to CVE-2017-5715 (Spectre Variant 2, branch target injection):  YES 
  * Vulnerable to CVE-2017-5754 (Variant 3, Meltdown, rogue data cache load):  YES 
  * Vulnerable to CVE-2018-3640 (Variant 3a, rogue system register read):  YES 
  * Vulnerable to CVE-2018-3639 (Variant 4, speculative store bypass):  YES 
  * Vulnerable to CVE-2018-3615 (Foreshadow (SGX), L1 terminal fault):  NO 
  * Vulnerable to CVE-2018-3620 (Foreshadow-NG (OS), L1 terminal fault):  YES 
  * Vulnerable to CVE-2018-3646 (Foreshadow-NG (VMM), L1 terminal fault):  YES 
  * Vulnerable to CVE-2018-12126 (Fallout, microarchitectural store buffer data sampling (MSBDS)):  YES 
  * Vulnerable to CVE-2018-12130 (ZombieLoad, microarchitectural fill buffer data sampling (MFBDS)):  YES 
  * Vulnerable to CVE-2018-12127 (RIDL, microarchitectural load port data sampling (MLPDS)):  YES 
  * Vulnerable to CVE-2019-11091 (RIDL, microarchitectural data sampling uncacheable memory (MDSUM)):  YES 
  * Vulnerable to CVE-2019-11135 (ZombieLoad V2, TSX Asynchronous Abort (TAA)):  YES 
  * Vulnerable to CVE-2018-12207 (No eXcuses, iTLB Multihit, machine check exception on page size changes (MCEPSC)):  YES 
  * Vulnerable to CVE-2020-0543 (Special Register Buffer Data Sampling (SRBDS)):  NO 

CVE-2017-5753 aka 'Spectre Variant 1, bounds check bypass'
* Mitigated according to the /sys interface:  YES  (Mitigation: usercopy/swapgs barriers and __user pointer sanitization)
* Kernel has array_index_mask_nospec:  UNKNOWN  (couldn't check (kernel compression format is unknown or image is invalid))
* Kernel has the Red Hat/Ubuntu patch:  UNKNOWN  (couldn't check (kernel compression format is unknown or image is invalid))
* Kernel has mask_nospec64 (arm64):  UNKNOWN  (couldn't check (kernel compression format is unknown or image is invalid))
* Kernel has array_index_nospec (arm64):  UNKNOWN  (couldn't check (kernel compression format is unknown or image is invalid))
* Checking count of LFENCE instructions following a jump in kernel...  UNKNOWN  (couldn't check (kernel compression format is unknown or image is invalid))
> STATUS:  NOT VULNERABLE  (Mitigation: usercopy/swapgs barriers and __user pointer sanitization)

CVE-2017-5715 aka 'Spectre Variant 2, branch target injection'
* Mitigated according to the /sys interface:  YES  (Mitigation: Full generic retpoline, STIBP: disabled, RSB filling)
* Mitigation 1
  * Kernel is compiled with IBRS support:  YES 
    * IBRS enabled and active:  NO 
  * Kernel is compiled with IBPB support:  UNKNOWN  (in offline mode, we need the kernel image to be able to tell)
    * IBPB enabled and active:  NO 
* Mitigation 2
  * Kernel has branch predictor hardening (arm):  NO 
  * Kernel compiled with retpoline option:  YES 
    * Kernel compiled with a retpoline-aware compiler:  YES  (kernel reports full retpoline compilation)
> STATUS:  NOT VULNERABLE  (Full retpoline is mitigating the vulnerability)
IBPB is considered as a good addition to retpoline for Variant 2 mitigation, but your CPU microcode doesn't support it

CVE-2017-5754 aka 'Variant 3, Meltdown, rogue data cache load'
* Mitigated according to the /sys interface:  YES  (Mitigation: PTI)
* Kernel supports Page Table Isolation (PTI):  YES 
  * PTI enabled and active:  YES 
  * Reduced performance impact of PTI:  YES  (CPU supports INVPCID, performance impact of PTI will be greatly reduced)
* Running as a Xen PV DomU:  NO 
> STATUS:  NOT VULNERABLE  (Mitigation: PTI)

CVE-2018-3640 aka 'Variant 3a, rogue system register read'
* CPU microcode mitigates the vulnerability:  NO 
> STATUS:  VULNERABLE  (an up-to-date CPU microcode is needed to mitigate this vulnerability)

CVE-2018-3639 aka 'Variant 4, speculative store bypass'
* Mitigated according to the /sys interface:  NO  (Vulnerable)
* Kernel supports disabling speculative store bypass (SSB):  YES  (found in /proc/self/status)
* SSB mitigation is enabled and active:  NO 
> STATUS:  VULNERABLE  (Your CPU doesn't support SSBD)

CVE-2018-3615 aka 'Foreshadow (SGX), L1 terminal fault'
* CPU microcode mitigates the vulnerability:  N/A 
> STATUS:  NOT VULNERABLE  (your CPU vendor reported your CPU model as not vulnerable)

CVE-2018-3620 aka 'Foreshadow-NG (OS), L1 terminal fault'
* Mitigated according to the /sys interface:  YES  (Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable)
* Kernel supports PTE inversion:  UNKNOWN  (kernel compression format is unknown or image is invalid)
* PTE inversion enabled and active:  YES 
> STATUS:  NOT VULNERABLE  (Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable)

CVE-2018-3646 aka 'Foreshadow-NG (VMM), L1 terminal fault'
* Information from the /sys interface: Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
* This system is a host running a hypervisor:  NO 
* Mitigation 1 (KVM)
  * EPT is disabled:  NO 
* Mitigation 2
  * L1D flush is supported by kernel:  UNKNOWN  (kernel compression format is unknown or image is invalid)
  * L1D flush enabled:  YES  (conditional flushes)
  * Hardware-backed L1D flush supported:  NO  (flush will be done in software, this is slower)
  * Hyper-Threading (SMT) is enabled:  YES 
> STATUS:  NOT VULNERABLE  (this system is not running a hypervisor)

CVE-2018-12126 aka 'Fallout, microarchitectural store buffer data sampling (MSBDS)'
* Mitigated according to the /sys interface:  NO  (Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable)
* Kernel supports using MD_CLEAR mitigation:  UNKNOWN 
* Kernel mitigation is enabled and active:  NO 
* SMT is either mitigated or disabled:  NO 
> STATUS:  VULNERABLE  (Neither your kernel or your microcode support mitigation, upgrade both to mitigate the vulnerability)

CVE-2018-12130 aka 'ZombieLoad, microarchitectural fill buffer data sampling (MFBDS)'
* Mitigated according to the /sys interface:  NO  (Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable)
* Kernel supports using MD_CLEAR mitigation:  UNKNOWN 
* Kernel mitigation is enabled and active:  NO 
* SMT is either mitigated or disabled:  NO 
> STATUS:  VULNERABLE  (Neither your kernel or your microcode support mitigation, upgrade both to mitigate the vulnerability)

CVE-2018-12127 aka 'RIDL, microarchitectural load port data sampling (MLPDS)'
* Mitigated according to the /sys interface:  NO  (Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable)
* Kernel supports using MD_CLEAR mitigation:  UNKNOWN 
* Kernel mitigation is enabled and active:  NO 
* SMT is either mitigated or disabled:  NO 
> STATUS:  VULNERABLE  (Neither your kernel or your microcode support mitigation, upgrade both to mitigate the vulnerability)

CVE-2019-11091 aka 'RIDL, microarchitectural data sampling uncacheable memory (MDSUM)'
* Mitigated according to the /sys interface:  NO  (Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable)
* Kernel supports using MD_CLEAR mitigation:  UNKNOWN 
* Kernel mitigation is enabled and active:  NO 
* SMT is either mitigated or disabled:  NO 
> STATUS:  VULNERABLE  (Neither your kernel or your microcode support mitigation, upgrade both to mitigate the vulnerability)

CVE-2019-11135 aka 'ZombieLoad V2, TSX Asynchronous Abort (TAA)'
* Mitigated according to the /sys interface:  NO  (Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable)
* TAA mitigation is supported by kernel:  UNKNOWN  (kernel compression format is unknown or image is invalid)
* TAA mitigation enabled and active:  NO 
> STATUS:  VULNERABLE  (Vulnerable: Clear CPU buffers attempted, no microcode; SMT vulnerable)

CVE-2018-12207 aka 'No eXcuses, iTLB Multihit, machine check exception on page size changes (MCEPSC)'
* Mitigated according to the /sys interface:  YES  (KVM: Mitigation: VMX disabled)
* This system is a host running a hypervisor:  NO 
* iTLB Multihit mitigation is supported by kernel:  UNKNOWN  (kernel compression format is unknown or image is invalid)
* iTLB Multihit mitigation enabled and active:  YES  (KVM: Mitigation: VMX disabled)
> STATUS:  NOT VULNERABLE  (this system is not running a hypervisor)

CVE-2020-0543 aka 'Special Register Buffer Data Sampling (SRBDS)'
* Mitigated according to the /sys interface:  YES  (Not affected)
* SRBDS mitigation control is supported by the kernel:  UNKNOWN  (kernel compression format is unknown or image is invalid)
* SRBDS mitigation control is enabled and active:  NO 
> STATUS:  NOT VULNERABLE  (your CPU vendor reported your CPU model as not vulnerable)

> SUMMARY: CVE-2017-5753:OK CVE-2017-5715:OK CVE-2017-5754:OK CVE-2018-3640:KO CVE-2018-3639:KO CVE-2018-3615:OK CVE-2018-3620:OK CVE-2018-3646:OK CVE-2018-12126:KO CVE-2018-12130:KO CVE-2018-12127:KO CVE-2019-11091:KO CVE-2019-11135:KO CVE-2018-12207:OK CVE-2020-0543:OK

Need more detailed information about mitigation options? Use --explain
A false sense of security is worse than no security at all, see --disclaimer

Edit: aggiornato con l'output da utente root.

[Jena Plisskin]

Finalmente i bench con il turbo sbloccato. Ora lo xeon riesce ad arrivare ai 3200MHz su tutti i core, queste le differenze:


2.4GHz


Turbo unlocked


2.4GHz


Turbo unlocked


2.4GHz


Turbo unlocked


Il miglioramento c'è stato, tranne per 3D Mark. Complessivamente funziona bene, nonostante i difetti elencati nel corso del thread, alla fine ci posso convivere ed adattarmi. Cmq per il prezzo di una cpu di medio basso livello, mi son fatto un sistema più prestante ai prezzi gonfiati di oggi. Se mi dura un paio di anni e non ho motivi da credere che non lo faccia, potrò poi passare ad un usato più recente. Per ora è ok.