Artix Linux => System => Topic started by: nokangaroo on 25 July 2022, 13:33:52
Title: Testing seatd (not to necrobump the previous thread)
Post by: nokangaroo on 25 July 2022, 13:33:52
For me, the reasons for getting rid of elogind were dmesg errors like these (only with kernels later than 5.4, and regardless of kernel config, kernel commandline or BIOS settings):
[112632.955495] Asynchronous wait on fence 0000:00:02.0:elogind[1165]:4f482 timed out (hint:intel_atomic_commit_ready [i915]) [112636.925429] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:878aaff9, in elogind [1165] ... [ 3680.505752] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out [ 3680.505778] i915 0000:00:02.0: [drm] elogind[1171] context reset due to GPU hang [ 3680.510459] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:86dfaff9, in elogind [1171]
Turns out it didn't stop the freezes, but here's my experience with seatd FWIW.
seatd, dbus and polkit just need libelogind to run (elogind is only a buildtime dependency; the headers could be packaged with libelogind, or separately (an "elogind-headers" package would be nice, see below). I tested libelogind-249-pre, though the binary package also works. I've already been using custom-built dbus (no audit) and polkit (with duktape, which fortunately is the default now). For suspend, shutdown and reboot I added the following to /etc/sudoers:
#include <stdio.h> #include <stdlib.h> int main(void) { FILE *state; state = fopen("/sys/power/state", "r+"); if (state == NULL) { exit(EXIT_FAILURE); } fprintf(state, "%s", "mem"); fclose(state); exit(EXIT_SUCCESS); }
I put it in /usr/local/lib because I don't want it on my path. This program could of course be expanded to handle shutdown and reboot as well (not currently needed). Who needs loginctl? For XDG_RUNTIME_DIR, I tested adding
to .bash_profile, which works perfectly well. There is also a pam_rundir package, which I also tested (it creates the usual /run/user/$UID). The elogind-git package needed a hack to build (here's a working PKGBUILD):
package_elogind-headers() { mkdir -p ${pkgdir}/usr/include/elogind cp -R --no-preserve='ownership' ${srcdir}/elogind/src/systemd ${pkgdir}/usr/include/elogind cd ${pkgdir}/usr/include/elogind for file in systemd/*.h; do ln -s $file ./${file/systemd//}; done }
I tested {,lib}elogind-249-pre built with this PKGBUILD, see below. Does seatd actually do anything on a system with a single logged-in user? "ps axo seat" came up empty except for a column of dashes. (Even when I logged in again on a different tty, which incidentally took very long, and I didn't get graphics - it turned out to be a libelogind-249-pre issue, works with {,lib}elogind-246-10, including the one built against elogind-headers. Maybe polkit and dbus also need to be rebuilt, but since seatd doesn't do anything for me, I'm done testing).
Title: Re: Testing seatd (not to necrobump the previous thread)
Post by: Dudemanguy on 25 July 2022, 16:15:34
Yeah it makes it possible to run graphics as a non-root user. You wouldn't have been able to start xorg in the first place.
tried using seatd on my mate dinit system and could not run graphics as a non root user. i only got a working desktop running as root.
Title: Re: Testing seatd (not to necrobump the previous thread)
Post by: nokangaroo on 25 July 2022, 17:05:14
I just uninstalled elogind and kexec-tools and rebooted, and I'm in the graphics (rootless xorg). What I can't do is login to another tty and get graphics, same as with seatd. Still not convinced that seatd does anything. Rebooting now with elogind, will try rebuilding dbus and polkit with elogind-git.
Title: Re: Testing seatd (not to necrobump the previous thread)
Post by: Dudemanguy on 25 July 2022, 17:15:18
I just uninstalled elogind and kexec-tools and rebooted, and I'm in the graphics (rootless xorg).
In theory, this shouldn't have worked at all. You should have had a permissions error when trying to access /dev/dri/card0 (or whatever your gpu card number is) if you really removed elogind completely from your system.
Title: Re: Testing seatd (not to necrobump the previous thread)
Post by: cat herders of linux on 25 July 2022, 17:22:38
You need to actually run the daemon and add the your user to the correct group.
In theory, this shouldn't have worked at all. You should have had a permissions error when trying to access /dev/dri/card0 (or whatever your gpu card number is) if you really removed elogind completely from your system.
gui() { if [[ -z "${WINDOWPATH}" ]]; then local WIN=$(pidof Xorg | wc -w) rm -f /tmp/.gui${WIN}-${UID}* local LOG="$(mktemp -q /tmp/.gui${WIN}-${UID}-`date +%a%d%b%Y-%T`.log.XXXXXXXXXX)" local ERR="$(mktemp -q /tmp/.gui${WIN}-${UID}-`date +%a%d%b%Y-%T`-error.log.XXXXXXXXXX)" startx :${WIN} 1>${LOG} 2>${ERR} else echo 'To be run from the console - Aborting.' fi }
Then typing "gui" at the console will log you in (on as many ttys as you want, works with elogind). And I started seatd-openrc when testing seatd. Did you mean I have to add myself to the "seat" group? seatd was started with "-g video" by default (which I'm a member of), if I recall correctly.
Title: Re: Testing seatd (not to necrobump the previous thread)
Post by: Dudemanguy on 25 July 2022, 20:05:50
The init scripts are currently a bit dated. They should run with the "seat" group. Currently some run with "video" and others with "seatd". That said, if you were in the video group and seatd was running as the video group, then this should have worked.
Title: Re: Testing seatd (not to necrobump the previous thread)
Post by: pluto on 25 July 2022, 20:08:48
A little bit more information would be nice.
So far i can see here, you using the openrc version. Wich DE?
Quote
For suspend, shutdown and reboot I added the following to /etc/sudoers:
This sadly dont readd the Shutdown and Restart Buttons back to KDE. Tried is already too.
Quote
seatd, dbus and polkit just need libelogind to run (elogind is only a buildtime dependency; the headers could be packaged with libelogind, or separately (an "elogind-headers" package would be nice, see below). I tested libelogind-249-pre, though the binary package also works. I've already been using custom-built dbus (no audit) and polkit (with duktape, which fortunately is the default now)
Everything from AUR? why?
Quote
Who needs loginctl? For XDG_RUNTIME_DIR, I tested adding
The init scripts are currently a bit dated. They should run with the "seat" group. Currently some run with "video" and others with "seatd".
Im since two days testing seatd in a VM. The seatd group even didnt exist. So i only added me to the two groups audio and input like in the post https://forum.artixlinux.org/index.php/topic,3050.0.html mentioned. And everything works.
Should i add me to seat?
Title: Re: Testing seatd (not to necrobump the previous thread)
Post by: cat herders of linux on 25 July 2022, 22:29:27
The init scripts are currently a bit dated. They should run with the "seat" group. Currently some run with "video" and others with "seatd". That said, if you were in the video group and seatd was running as the video group, then this should have worked.
i am capable of following written instructions. i added myself to all the groups listed as well as the ones recommended in the arch link you posted about groups. I wouldn't waste your time if i could get it to work. I see that it works for many and that is awesome. There are a few though, me and nokangaroo at least for who it appears to not be working. If it worked, i would def use it. I thank you for your hard work on this project. I look forward to the day it is part of the iso builds from community live usbs.
Title: Re: Testing seatd (not to necrobump the previous thread)
Post by: nokangaroo on 26 July 2022, 12:21:27
pluto: My DE is MATE with openbox as window manager (which can handle my keyboard shortcuts, so I'm not using mate-settings-daemon or mate-panel, I use tint2 instead. I use mate-session-manager, which is actually smaller than lxde-session and works better). As for the AUR packages an all the other modifications, I am plagued by this i915 interface freeze (with kernels later than 5.4), and I was trying to find out if it had anything to do with userspace applications, see the above dmesg code (apparently it's a pure kernel issue, but I like my modified DE and will keep it). If you can't get shutdown and restart buttons, try defining keyboard shortcuts (that's what I did; for openbox that means adding code to rc.xml, for KDE I can't tell you, but there will be documentation). You may need to press the power button after shutting down. The XDG_RUNTIME_DIR is used by dbus, dconf and gvfs (and xorg puts a cookie there). Adding lines to .bash_profile is just one possible way to get it, the canonical way would be installing pam_rundir (only if you use seatd, elogind creates XDG_RUNTIME_DIR automatically)
The posted PKGBUILD is still not quite correct, it creates a corrupt libelogind.pc (which is trivial to fix but elogind-249-pre seems to be hopelessly broken, and I don't recommend using it).
Title: Re: Testing seatd (not to necrobump the previous thread)
Post by: pluto on 26 July 2022, 15:02:13
pluto: My DE is MATE with openbox as window manager (which can handle my keyboard shortcuts, so I'm not using mate-settings-daemon or mate-panel, I use tint2 instead. I use mate-session-manager, which is actually smaller than lxde-session and works better). As for the AUR packages an all the other modifications, I am plagued by this i915 interface freeze (with kernels later than 5.4), and I was trying to find out if it had anything to do with userspace applications, see the above dmesg code (apparently it's a pure kernel issue, but I like my modified DE and will keep it). If you can't get shutdown and restart buttons, try defining keyboard shortcuts (that's what I did; for openbox that means adding code to rc.xml, for KDE I can't tell you, but there will be documentation). You may need to press the power button after shutting down. The XDG_RUNTIME_DIR is used by dbus, dconf and gvfs (and xorg puts a cookie there). Adding lines to .bash_profile is just one possible way to get it, the canonical way would be installing pam_rundir (only if you use seatd, elogind creates XDG_RUNTIME_DIR automatically)
The posted PKGBUILD is still not quite correct, it creates a corrupt libelogind.pc (which is trivial to fix but elogind-249-pre seems to be hopelessly broken, and I don't recommend using it).
Ah ok. Did you tried this? https://wiki.archlinux.org/title/Intel_graphics#Kernel_crashing_w/kernels_4.0+_on_Broadwell/Core-M_chips
sure i could make keyboard shortcuts wich start "sudo poweroff" for example. Or simple Desktopicons wich does this. But that only a workaround :-)
Now i simply shutdown/restart with konsole and sudo poweroff/sudo reboot. But would be nice if i could use KDE native for that. And it should be possible how i already found out. But i only found solution for dinit, initd and 66. But sadly not with openrc.
And im to stupid to implement the found solutions to openrc :-)
Title: Re: Testing seatd (not to necrobump the previous thread)
Post by: artoo on 26 July 2022, 18:58:08
Not gonna happen, unless seatd becomes a full logind replacement.
this is possibly a stupid question because i am not familiar with it, but what is missing until now?
im investing much time the last few days with researching because i switched to seatd and collecting a bunch information. I tried few wide spread DEs already (KDE, GNOME, Cinnamon), at all it seems to work without problems (after fresh install, openrc). The only Problem all have common is that all lose the ability to reboot/shutdown over the Desktop.
Edit: and with all i had to manually add a variable to make nano as standard editor for user, root and sudo. Dont know if this wouldnt be needed with elogind.
Title: Re: Testing seatd (not to necrobump the previous thread)
Post by: capezotte on 26 July 2022, 20:48:24
this is possibly a stupid question because i am not familiar with it, but what is missing until now?
im investing much time the last few days with researching because i switched to seatd and collecting a bunch information. I tried few wide spread DEs already (KDE, GNOME, Cinnamon), at all it seems to work without problems (after fresh install, openrc). The only Problem all have common is that all lose the ability to reboot/shutdown over the Desktop.
Power management is one of these features. GNOME, KDE, etc. use logind to suspend, poweroff and reboot.
Seatd also doesn't implement logind-stlye user access control lists (https://enotty.pipebreaker.pl/2012/05/23/linux-automatic-user-acl-management/).
Title: Re: Testing seatd (not to necrobump the previous thread)
Post by: gripped on 26 July 2022, 21:13:16
The only Problem all have common is that all lose the ability to reboot/shutdown over the Desktop.
This may be of interest to you ? Creating a a replacement loginctl. https://forum.artixlinux.org/index.php/topic,3050.msg23032.html#msg23032 I've never tried it but something like this could work if replicated in a binary and set SUID. Scripts can't be set SUID AFAIK. At least sh / bash can't.
Title: Re: Testing seatd (not to necrobump the previous thread)
Post by: pluto on 26 July 2022, 21:40:12
This may be of interest to you ? Creating a a replacement loginctl. https://forum.artixlinux.org/index.php/topic,3050.msg23032.html#msg23032 I've never tried it but something like this could work if replicated in a binary and set SUID. Scripts can't be set SUID AFAIK. At least sh / bash can't.
Yeah, already read that. But like already said in this Thread:
Quote
Sadly, i dont quite understand this and how to implement this for openrc: https://forum.artixlinux.org/index.php/topic,3050.msg23032.html#msg23032
case $1 in halt)openrc-shutdown -H 0;; reboot)openrc-shutdown -r 0;; poweroff)openrc-shutdown -p 0;; *)show_usage esac
;; *)show_usage esac
But it would not work from a GUI as it needs root privileges. Hence needing to convert to a compiled binary that can be set SUID. And that's assuming loginctl is called by your desktop of choice. But if strajder believes so I expect it usually is ? Also the result would be that any user can poweroff the machine but on a single user PC that's not a biggie imho
I can't program really but you can find small C tutorials and convert them to serve a tiny purpose such as this.
For example suspend and hibernate do not work for me from the KDE GUI. System comes back up but screen never does. However writing directly to the kernel does work
Ah ok. Did you tried this? https://wiki.archlinux.org/title/Intel_graphics#Kernel_crashing_w/kernels_4.0+_on_Broadwell/Core-M_chips
sure i could make keyboard shortcuts wich start "sudo poweroff" for example. Or simple Desktopicons wich does this. But that only a workaround :-)
Now i simply shutdown/restart with konsole and sudo poweroff/sudo reboot. But would be nice if i could use KDE native for that. And it should be possible how i already found out. But i only found solution for dinit, initd and 66. But sadly not with openrc.
And im to stupid to implement the found solutions to openrc :-)
pluto: I tried everything I could find, and then some more. Nothing worked so far. The problem seems to be forced preemption, which cannot be safely disabled (DRM_I915_PREEMPT_TIMEOUT=0 does not work, and if you unset the various timeouts, kconfig asks for them; they cannot be unset). Here is the outcome of "git show 3a7a92aba8fb77162e1e9963360fd81fc15c39a5" in linux-mainline, which seems to be the relevant commit:
commit 3a7a92aba8fb77162e1e9963360fd81fc15c39a5 Author: Chris Wilson <[email protected]> Date: Wed Oct 23 14:31:05 2019 +0100
drm/i915/execlists: Force preemption
If the preempted context takes too long to relinquish control, e.g. it is stuck inside a shader with arbitration disabled, evict that context with an engine reset. This ensures that preemptions are reasonably responsive, providing a tighter QoS for the more important context at the cost of flagging unresponsive contexts more frequently (i.e. instead of using an ~10s hangcheck, we now evict at ~100ms). The challenge of lies in picking a timeout that can be reasonably serviced by HW for typical workloads, balancing the existing clients against the needs for responsiveness.
Note that coupled with timeslicing, this will lead to rapid GPU "hang" detection with multiple active contexts vying for GPU time.
The forced preemption mechanism can be compiled out with
diff --git a/drivers/gpu/drm/i915/Kconfig.profile b/drivers/gpu/drm/i915/Kconfig.profile index 3a3881d5e44b..b071b6024152 100644 --- a/drivers/gpu/drm/i915/Kconfig.profile +++ b/drivers/gpu/drm/i915/Kconfig.profile @@ -12,6 +12,18 @@ config DRM_I915_USERFAULT_AUTOSUSPEND May be 0 to disable the extra delay and solely use the device level runtime pm autosuspend delay tunable.
+config DRM_I915_PREEMPT_TIMEOUT +int "Preempt timeout (ms, jiffy granularity)" +default 100 # milliseconds +help + How long to wait (in milliseconds) for a preemption event to occur + when submitting a new context via execlists. If the current context + does not hit an arbitration point and yield to HW before the timer + expires, the HW will be reset to allow the more important context + to execute. + + May be 0 to disable the timeout. + config DRM_I915_SPIN_REQUEST int "Busywait for request completion (us)" default 5 # microseconds diff --git a/drivers/gpu/drm/i915/gt/intel_engine.h b/drivers/gpu/drm/i915/gt/intel_engine.h index c2d9d67c63d9..9409b7856299 100644 --- a/drivers/gpu/drm/i915/gt/intel_engine.h +++ b/drivers/gpu/drm/i915/gt/intel_engine.h @@ -527,4 +527,13 @@ void intel_engine_init_active(struct intel_engine_cs *engine, #define ENGINE_MOCK1 #define ENGINE_VIRTUAL2
+/** + * @preempt: reset the current context if it fails to give way + */ +struct timer_list preempt; + /** * @default_priolist: priority list for I915_PRIORITY_NORMAL */ @@ -544,6 +549,7 @@ struct intel_engine_cs { } stats;
#endif + +void cancel_timer(struct timer_list *t) +{ +if (!READ_ONCE(t->expires)) +return; + +del_timer(t); +WRITE_ONCE(t->expires, 0); +} + +void set_timer_ms(struct timer_list *t, unsigned long timeout) +{ +if (!timeout) { +cancel_timer(t); +return; +} + +timeout = msecs_to_jiffies_timeout(timeout); + +/* + * Paranoia to make sure the compiler computes the timeout before + * loading 'jiffies' as jiffies is volatile and may be updated in + * the background by a timer tick. All to reduce the complexity + * of the addition and reduce the risk of losing a jiffie. + */ +barrier(); + +mod_timer(t, jiffies + timeout); +} diff --git a/drivers/gpu/drm/i915/i915_utils.h b/drivers/gpu/drm/i915/i915_utils.h index 562f756da421..94f136d8a5fd 100644 --- a/drivers/gpu/drm/i915/i915_utils.h +++ b/drivers/gpu/drm/i915/i915_utils.h @@ -32,6 +32,7 @@ #include <linux/workqueue.h>
struct drm_i915_private; +struct timer_list;
#undef WARN_ON /* Many gcc seem to no see through this and fall over :( */ @@ -421,4 +422,12 @@ static inline void add_taint_for_CI(unsigned int taint) add_taint(taint, LOCKDEP_STILL_OK); }
to my linux-mainline PKGBUILD (before make oldconfig), but all it does is set CONFIG_DRM_I915_PREEMPT_TIMEOUT to 0, which I already tried. I am currently testing "i915.enable_dc=0 processor.max_cstate=1 intel_idle.max_cstate=0" added to my kernel commandline, and disabling timeslicing (CONFIG_DRM_I915_TIMESLICE_DURATION=0). If that doesn't work, I'm out of options, unless the kernel guys come to their senses and provide a way to disable forced preemption safely on hardware that doesn't support it. Timeslicing can also be disabled at runtime (as root; the actual names of the engines may differ):
case $1 in halt)openrc-shutdown -H 0;; reboot)openrc-shutdown -r 0;; poweroff)openrc-shutdown -p 0;; *)show_usage esac
;; *)show_usage esac
But it would not work from a GUI as it needs root privileges. Hence needing to convert to a compiled binary that can be set SUID. And that's assuming loginctl is called by your desktop of choice. But if strajder believes so I expect it usually is ? Also the result would be that any user can poweroff the machine but on a single user PC that's not a biggie imho
I can't program really but you can find small C tutorials and convert them to serve a tiny purpose such as this.
For example suspend and hibernate do not work for me from the KDE GUI. System comes back up but screen never does. However writing directly to the kernel does work