<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.8.5">Jekyll</generator><link href="https://5long.github.io/is-arch-broken/feed.xml" rel="self" type="application/atom+xml" /><link href="https://5long.github.io/is-arch-broken/" rel="alternate" type="text/html" /><updated>2020-01-03T15:56:20+00:00</updated><id>https://5long.github.io/is-arch-broken/feed.xml</id><title type="html">Is Arch Broken?</title><subtitle>Is Arch Linux broken or just me?</subtitle><entry><title type="html">i915 GPU hangs with 5.4 Kernel</title><link href="https://5long.github.io/is-arch-broken/kernel-5.4-i915.html" rel="alternate" type="text/html" title="i915 GPU hangs with 5.4 Kernel" /><published>2019-12-20T00:00:00+00:00</published><updated>2019-12-20T00:00:00+00:00</updated><id>https://5long.github.io/is-arch-broken/kernel-5.4-i915</id><content type="html" xml:base="https://5long.github.io/is-arch-broken/kernel-5.4-i915.html">&lt;p&gt;Another oopsie from Intel with 5.4 kernel: Intel iGPU could hang for no clear reason, leaving user a frozen computer.&lt;/p&gt;

&lt;p&gt;The issue seems to be affecting 5.3 kernel as well. But it’s a lot easier to reproduce since 5.4.&lt;/p&gt;

&lt;h2 id=&quot;state&quot;&gt;State&lt;/h2&gt;

&lt;p&gt;Broken.&lt;/p&gt;

&lt;p&gt;A fixing patch has been applied on mainline kernel, version 5.5rc. But the patch has not been backported to 5.4 yet. And the patch can’t be cleanly backported to 5.4 according to Arch Linux developers.&lt;/p&gt;

&lt;h2 id=&quot;workaround&quot;&gt;Workaround&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;Downgrade kernel to &amp;lt; 5.4&lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;tracked-elsewhere&quot;&gt;Tracked elsewhere&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;drm/intel: &lt;a href=&quot;http://gitlab.freedesktop.org/drm/intel/issues/673&quot;&gt;http://gitlab.freedesktop.org/drm/intel/issues/673&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;Arch Linux: &lt;a href=&quot;https://bugs.archlinux.org/task/64725&quot;&gt;FS#64725&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</content><author><name></name></author><summary type="html">Another oopsie from Intel with 5.4 kernel: Intel iGPU could hang for no clear reason, leaving user a frozen computer.</summary></entry><entry><title type="html">iwlwifi with 5.4 Kernel</title><link href="https://5long.github.io/is-arch-broken/kernel-5.4-iwlwifi.html" rel="alternate" type="text/html" title="iwlwifi with 5.4 Kernel" /><published>2019-12-20T00:00:00+00:00</published><updated>2019-12-20T00:00:00+00:00</updated><id>https://5long.github.io/is-arch-broken/kernel-5.4-iwlwifi</id><content type="html" xml:base="https://5long.github.io/is-arch-broken/kernel-5.4-iwlwifi.html">&lt;p&gt;Kernel 5.4 makes iwlwifi module crash for various models of Intel WiFi NIC. The WiFi NIC is missing from &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;ip link&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Some users are lucky enough not to experience any issues. You may or may not be a lucky one.&lt;/p&gt;

&lt;h2 id=&quot;state&quot;&gt;State&lt;/h2&gt;

&lt;p&gt;Broken.&lt;/p&gt;

&lt;h2 id=&quot;workarounds&quot;&gt;Workarounds&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;Remove the &lt;code class=&quot;language-plaintext highlighter-rouge&quot;&gt;lar_disable=1&lt;/code&gt; module parameter if it is present&lt;/li&gt;
  &lt;li&gt;Downgrade kernel to &amp;lt; 5.4&lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;tracked-elsewhere&quot;&gt;Tracked elsewhere&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;Kernel.org: &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=205749&quot;&gt;#205749&lt;/a&gt;, &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=205695&quot;&gt;#205695&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;Arch Linux: &lt;a href=&quot;https://bugs.archlinux.org/task/64703&quot;&gt;FS#64703&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</content><author><name></name></author><summary type="html">Kernel 5.4 makes iwlwifi module crash for various models of Intel WiFi NIC. The WiFi NIC is missing from ip link.</summary></entry><entry><title type="html">Kernel 5.4 Can’t Read NVMe Partitions</title><link href="https://5long.github.io/is-arch-broken/kernel-5.4-nvme.html" rel="alternate" type="text/html" title="Kernel 5.4 Can't Read NVMe Partitions" /><published>2019-12-20T00:00:00+00:00</published><updated>2019-12-20T00:00:00+00:00</updated><id>https://5long.github.io/is-arch-broken/kernel-5.4-nvme</id><content type="html" xml:base="https://5long.github.io/is-arch-broken/kernel-5.4-nvme.html">&lt;p&gt;Strike three for Kernel 5.4: it won’t read the partitions of some NVMe drives that do not strictly adhere to the NVMe specification.&lt;/p&gt;

&lt;h2 id=&quot;state&quot;&gt;State&lt;/h2&gt;

&lt;p&gt;Broken.&lt;/p&gt;

&lt;p&gt;A fixing patch has landed in 5.5-rc2 and will be backported to 5.4. Just wait.&lt;/p&gt;

&lt;h2 id=&quot;workarounds&quot;&gt;Workarounds&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;Downgrade kernel to &amp;lt; 5.4&lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;tracked-elsewhere&quot;&gt;Tracked elsewhere&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;Kernel.org: &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=205679&quot;&gt;https://bugzilla.kernel.org/show_bug.cgi?id=205679&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</content><author><name></name></author><summary type="html">Strike three for Kernel 5.4: it won’t read the partitions of some NVMe drives that do not strictly adhere to the NVMe specification.</summary></entry><entry><title type="html">NetworkManager 1.22</title><link href="https://5long.github.io/is-arch-broken/networkmanager-1.22.html" rel="alternate" type="text/html" title="NetworkManager 1.22" /><published>2019-12-20T00:00:00+00:00</published><updated>2019-12-20T00:00:00+00:00</updated><id>https://5long.github.io/is-arch-broken/networkmanager-1.22</id><content type="html" xml:base="https://5long.github.io/is-arch-broken/networkmanager-1.22.html">&lt;p&gt;After upgrading NetworkManager to 1.22, some users can no longer connect to the network. NICs managed by NetworkManager would constantly switch between the states of connected and disconnected, or simply refuse to connect.&lt;/p&gt;

&lt;p&gt;As seen on Reddit: &lt;a href=&quot;https://redd.it/ecjiqb&quot;&gt;https://redd.it/ecjiqb&lt;/a&gt;.&lt;/p&gt;

&lt;h2 id=&quot;state&quot;&gt;State&lt;/h2&gt;

&lt;p&gt;Should be fixed since 1.22.2.&lt;/p&gt;

&lt;h2 id=&quot;workarounds&quot;&gt;Workarounds&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;Switch to &lt;a href=&quot;https://wiki.archlinux.org/index.php/Network_configuration#Network_managers&quot;&gt;a different network manager&lt;/a&gt; (e.g. systemd-networkd)&lt;/li&gt;
  &lt;li&gt;Downgrade NetworkManager to 1.20&lt;/li&gt;
  &lt;li&gt;Downgrade kernel to &amp;lt; 5.4&lt;/li&gt;
&lt;/ul&gt;

&lt;h2 id=&quot;tracked-elsewhere&quot;&gt;Tracked elsewhere&lt;/h2&gt;

&lt;ul&gt;
  &lt;li&gt;Arch Linux: &lt;a href=&quot;https://bugs.archlinux.org/task/64880&quot;&gt;FS#64880&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</content><author><name></name></author><summary type="html">After upgrading NetworkManager to 1.22, some users can no longer connect to the network. NICs managed by NetworkManager would constantly switch between the states of connected and disconnected, or simply refuse to connect.</summary></entry></feed>