A na sta se odnosi ovo upozorenje?
Recommendations:
Updated Jan. 22
We have now identified the root cause of the reboot issue impacting Broadwell and Haswell platforms, and made good progress in developing a solution to address it. Based on this, we are updating our guidance for customers and partners:
We recommend that OEMs, Cloud service providers, system manufacturers, software vendors and end users stop deployment of current versions on the below platforms, as they may introduce higher than expected reboots and other unpredictable system behavior.
We also ask that our industry partners focus efforts on testing early versions of the updated solution for Broadwell and Haswell we started rolling out this weekend, so we can accelerate its release. We expect to share more details on timing later this week.
For those concerned about system stability while we finalize the updated solutions, we are also working with our OEM partners on the option to utilize a previous version of microcode that does not display these issues, but removes the Variant 2 (Spectre) mitigations. This would be delivered via a BIOS update, and would not impact mitigations for Variant 1 (Spectre) and Variant 3 (Meltdown).
We believe it is important for OEMs and our customers to follow this guidance for all of the specified platforms listed below, as they may demonstrate higher than expected reboots and unpredictable system behavior. The progress we have made in identifying a root cause for Haswell and Broadwell will help us address issues on other platforms. Please be assured we are working quickly to address these issues.
For a list of products associated with this updated guidance go here
Taj "novi" bios, možeš da zaboraviš, po pitanju ove teme. Samo pogledaj datum.
ispegla
konacno resenje
Nisam programer,
verovatno sto vise programera manje sijalica.
Stvarno ne znam sta sam lose rekao,
do juce se nije znalo da taj problem i postoji pa se zivelo bez toga
Izgleda da nisi shvatio poentuToliko je normalan, da posle svega, svi treba da budemo male bezbrižne bebe, ušukane u male krevetiće, kojima samo baldahin fali.
Znaci u pitanju je hardware-ski problem, kao takav resenje je kupovina novog hardware-a, a svaka software-ska intervencija je drz vodu dok....
Iz istog razloga zbog postoji hiljadu bagova i rupa u svakom velikom hardverskom i softverskom projektu, iako se krpe godinama. Samo što se na ovom radi ubrzano i naći će odgovarajuće rešenje, jer su pogođeni veliki sistemi a ne CoD igračiPa što ga ne okrpe kad mogu?
i sta ako se ipak nadje prava zakrpa i ispostavi se da ipak utice i na taj segment???
In order to provide more detail, Red Hat’s performance team is sharing the performance results measured for Red Hat Enterprise Linux 7, (with similar behavior on Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 5), on a wide variety of benchmarks based on performance impact:
Measureable: 8-19% - Highly cached random memory, with buffered I/O, OLTP database workloads, and benchmarks with high kernel-to-user space transitions were measured to be impacted between 8-19%. Examples include OLTP Workloads (tpc), sysbench, pgbench, netperf (< 256 byte), and fio (random I/O to NvME).
Modest: 3-7% - Database analytics, Decision Support System (DSS), and Java VMs were measured to be impacted less than the “Measurable” category. These applications may have significant sequential disk or network traffic, but kernel/device drivers are able to aggregate requests to moderate level of kernel-to-user transitions. Examples include SPECjbb2005, Queries/Hour and overall analytic timing (sec).
Small: 2-5% - HPC (High Performance Computing) CPU-intensive workloads that spend little time in the kernel were measured to have 2-5% performance impact. This is with jobs that run mostly in user space and are scheduled using cpu-pinning or numa-control. Examples include Linpack NxN on x86 and SPECcpu2006.
Minimal: Linux accelerator technologies that generally bypass the kernel in favor of user direct access were measured to have the least impact, with less than 2% overhead measured. Examples tested include DPDK (VsPERF at 64 byte) and OpenOnload (STAC-N). Userspace accesses to VDSO like gettimeofday were not measured to be impacted. We expect similar minimal impact for other offloads that bypass the kernel.
NOTE: Because microbenchmarks like netperf/uperf, iozone, and fio are designed to stress a specific hardware component or operation, their results may not be generally representative of customer workload. Some microbenchmarks have shown a larger performance impact, related to the specific area they stress.
Due to containerized applications being implemented as generic Linux processes, applications deployed in containers incur the same performance impact as those deployed on bare metal. We expect the impact on applications deployed in virtual guests to be higher than bare metal due to the increased frequency of user-to-kernel transitions. Those results will be available soon in an updated version of this document.
Nećemo instalirati zakrpu, barem ja :d
Follow along with the video below to see how to install our site as a web app on your home screen.
Napomena: this_feature_currently_requires_accessing_site_using_safari