<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Linux Scheduler on cbugk&#39;s blog</title>
    <link>https://blog.cbugk.com/tags/linux-scheduler/</link>
    <description>Recent content in Linux Scheduler on cbugk&#39;s blog</description>
    <generator>Hugo -- 0.140.2</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 22 Jan 2024 20:51:25 +0300</lastBuildDate>
    <atom:link href="https://blog.cbugk.com/tags/linux-scheduler/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How I made my own R8 5850X (10c/20t)</title>
      <link>https://blog.cbugk.com/post/ryzen-5850x/</link>
      <pubDate>Mon, 22 Jan 2024 20:51:25 +0300</pubDate>
      <guid>https://blog.cbugk.com/post/ryzen-5850x/</guid>
      <description>&lt;h2 id=&#34;tldr-adventure-of-reviving-a-cpu-as-a-hypervisor&#34;&gt;TL;DR: Adventure of reviving a CPU as a hypervisor&lt;/h2&gt;
&lt;p&gt;About few months ago, I found a bargain on a seemingly faulty Ryzen R9 5900X
unit. Stangely enough, it was said to drop internet connectivity while gaming.
Long story short, there are 2 defective physical cores out of the 12 present.
I ended up isolating them with &lt;em&gt;isolcpus=&lt;/em&gt; kernel parameter within boot menu.&lt;/p&gt;
&lt;h2 id=&#34;methodology&#34;&gt;Methodology:&lt;/h2&gt;
&lt;p&gt;Video recording of the process. Includes temporary solution for GRUB2 (see
&lt;code&gt;/etc/default/grub&lt;/code&gt; or &lt;code&gt;/etc/kernel/cmdline&lt;/code&gt; for
&lt;a href=&#34;https://pve.proxmox.com/wiki/Host_Bootloader#sysboot_edit_kernel_cmdline&#34;&gt;proxmox sysboot&lt;/a&gt;
for persistence), an example of OS installation failure without modification,
and a test example.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
