<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="https://dev1galaxy.org/extern.php?action=feed&amp;tid=4916&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / New install with runit and Kernel bug]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=4916</link>
		<description><![CDATA[The most recent posts in New install with runit and Kernel bug.]]></description>
		<lastBuildDate>Fri, 04 Mar 2022 13:41:38 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: New install with runit and Kernel bug]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=35011#p35011</link>
			<description><![CDATA[<p>Thanks for your answer, you help me to better understand the situation.</p><p>I have conclude that there are at least two issues.</p><ul><li><p><a href="https://github.com/openzfs/zfs/issues/12696" rel="nofollow">One related to OpenZFS.</a></p></li><li><p>Another, not yet clearly identified, but probably related to the GPU and how ACPI is handled</p></li></ul><p>For the first issue, this is definitely not what cause the system to hang at resume. Now I have to wait for the fix.</p><p>For the second issue, it remembers the exact same problem I get when I tried to enable Wayland with 470 driver series, but here with Xorg only…</p><p><del>So I have tried the lasted driver (510.54) from Nvidia website. Now I can suspend the system without getting any crash. Moreover, I have now Wayland working.</del></p><p><del><strong>I do not understand how, but before the new install, and with the same drivers, the system worked fine…</strong></del></p><p>Anyway, thanks for your help.</p><p>EDIT</p><p>What a noob… I did not noticed that Nouveau was running, until I used some softwares that are GPU greedy… With the Nvidia 510.54 driver, I have the same bug than before, but not with Nouveau.</p><p>But at least, now I can blame Nvidia driver.</p>]]></description>
			<author><![CDATA[dummy@example.com (zero)]]></author>
			<pubDate>Fri, 04 Mar 2022 13:41:38 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=35011#p35011</guid>
		</item>
		<item>
			<title><![CDATA[Re: New install with runit and Kernel bug]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=34990#p34990</link>
			<description><![CDATA[<p>Here&#039;s an explanation of the error message you got. It&#039;s beyond my understanding.<br /><a href="https://stackoverflow.com/questions/3537252/how-to-solve-bug-scheduling-while-atomic-swapper-0x00000103-0-cpu0-in-ts" rel="nofollow">https://stackoverflow.com/questions/353 … cpu0-in-ts</a></p><p>I have a chimaera xfce with runit, and I can share a few data points. Maybe it will help.</p><p>If I use pm-suspend to put the system to sleep, it wakes normally when I raise the lid.</p><p>If I rely on xfce4-power-manager to put it to sleep when I close the lid, it does not suspend. And the screen is locked when I raise the lid. Both of those behaviors are contrary to the settings in the power manager.</p><p>No nvidia here. It&#039;s all intel. I don&#039;t think runit is the problem, but that&#039;s just a guess. FWIW, I have enabled runit scripts for the following services:</p><div class="codebox"><pre><code>acpid    connman  dbus getty-tty1-6 getty-ttyS0  lightdm
anacron  cron  elogind  irqbalance  mdadm    ssh</code></pre></div>]]></description>
			<author><![CDATA[dummy@example.com (fsmithred)]]></author>
			<pubDate>Wed, 02 Mar 2022 12:17:41 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=34990#p34990</guid>
		</item>
		<item>
			<title><![CDATA[New install with runit and Kernel bug]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=34961#p34961</link>
			<description><![CDATA[<p><a href="https://dev1galaxy.org/viewtopic.php?pid=34960" rel="nofollow">For some context.</a></p><p>Yesterday I have installed Devuan on a pc that used to work perfectly before, but this time I get a suspend issue.</p><p>Maybe I am wrong, but I think it is related to runit, as the same drivers are installed as well as the kernel, only runit is new.</p><p>Now if I suspend the system while being on gdm, or gnome, Devuan crashes at resume, leaving only a black screen, or some message. I have to hard reboot or reset with Alt Gr+Print Scrn+b.</p><p>But if, <strong>before suspend</strong>, I go to any tty, and then push the suspend button on the keyboard, the system resumes without any problem, but now I can get some output from dmesg.</p><p>For each &quot;virual&quot; cpu I get lines like these:</p><ul><li><p>BUG: scheduling while atomic: cpuhp/…</p></li><li><p>Preemption disabled at:</p></li><li><p>the call stack</p></li></ul><p>Could be also related to xserver-xorg-video-nvidia, but I tried almost every combination <strong>that used to work just before the new installation</strong> with Chimaera kernel and drivers, backports kernel and drivers, Ceres…, but since this new installation I get each time the same issue.</p><p>Any idea on how to solve this issue?</p><p>Finally, to who should I report this bug? Devuan only, if it is related to runit? To Linux kernel maintainers?</p>]]></description>
			<author><![CDATA[dummy@example.com (zero)]]></author>
			<pubDate>Tue, 01 Mar 2022 08:35:41 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=34961#p34961</guid>
		</item>
	</channel>
</rss>
