| Server IP : 79.136.114.73 / Your IP : 18.191.89.23 Web Server : Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.29 OpenSSL/1.0.1f System : Linux b8009 3.13.0-170-generic #220-Ubuntu SMP Thu May 9 12:40:49 UTC 2019 x86_64 User : www-data ( 33) PHP Version : 5.5.9-1ubuntu4.29 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority, MySQL : ON | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/share/doc/amd64-microcode/ |
Upload File : |
amd64-microcode for Debian -------------------------- Introduction: AMD AMD64 processors are capable of field-upgrading their control program (microcode). These microcode updates correct processor errata, and are often important for safe, correct system operation. While most of the microcode updates fix problems that happen extremely rarely, there are enough updates fixing issues that would cause system lockup, memory corruption, or unpredictable system behavior, to warrant taking it seriously. Microcode updates are ephemeral: they will be lost after a processor hard reset or after the processor is powered off. They must be reapplied at every boot and after the system wakes up from suspend to RAM or disk. Updating the processor microcode is the responsibility of the system firmware (BIOS or EFI). However, not all vendors will release timely updates for their firmware when AMD releases updated microcode, and most users don't update their system firmware in a timely fashion (or at all) anyway. The end result is that, unless some other method of distributing microcode updates is in place, the processor in many systems will be running with outdated microcode, increasing the chances of incorrect system operation. Debian can apply microcode updates to the system processors during the operating system boot. The following configurations are supported for the microcode driver: 1. When an initramfs image is used (Debian default), both modular and built-in configs for the microcode driver will work, and microcode will be updated by the initramfs. You must run "update-initramfs -u" when new microcode is manually installed to /lib/firmware (this will be done automatically when new microcode is installed by a package upgrade). 2. When an initramfs image is not used, only the modular microcode driver is supported. If it doesn't autoload by itself in your kernel version, you should add it to /etc/modules. You must install either the kmod or module-init-tools package, and the root filesystem with /lib/firmware must be available when the modules are loaded. -- Henrique de Moraes Holschuh <hmh@debian.org>, 2012-07-09