Now goto the search box in the taskbar and enter in Task Schedule and click on “Run as administrator.” If allowed distrod to set the task your going to have to remove it first.
n "wsl.exe -distribution Arch", 0' > /mnt/to/same/location/of/arch/install/dir/boot-arch-at-logon.vbs Nov 23 09:09:35 XXXX-XXXX systemd-logind: New session c2 of user lightdm.Echo 'set object = createobject("wscript.shell") Nov 23 09:09:35 XXXX-XXXX systemd: Starting User Runtime Directory /run/user/970. Nov 23 09:09:35 XXXX-XXXX systemd: Created slice User Slice of UID 970. Nov 23 09:09:35 XXXX-XXXX lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=970) by (uid=0) Nov 23 09:09:35 XXXX-XXXX lightdm: Error getting user list from : GDBus.Error.ServiceUnknown: The name was no> Nov 23 09:09:33 XXXX-XXXX kernel: ACPI Error: Aborting method \_SB._DSM due to previous error (AE_ALREADY_EXISTS) (20210730/psparse-529) Nov 23 09:09:33 XXXX-XXXX kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20210730/dswload2-477) Nov 23 09:09:33 XXXX-XXXX kernel: ACPI BIOS Error (bug): Failure creating named object, AE_ALREADY_EXISTS (20210730/dsfield-184) Nov 23 09:09:32 XXXX-XXXX polkitd: Unregistered Authentication Agent for unix-session:2 (system bus name :1.42, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)> Nov 23 09:09:32 XXXX-XXXX at-spi-bus-launcher: X connection to :0 broken (explicit kill or server shutdown). Nov 23 09:09:32 XXXX-XXXX systemd-logind: Session 2 logged out. Nov 23 09:09:32 XXXX-XXXX lightdm: pam_unix(lightdm:session): session closed for user Username Nov 23 09:09:32 XXXX-XXXX lightdm: Error opening audit socket: Protocol not supported Nov 23 09:09:32 XXXX-XXXX sudo: pam_unix(sudo:session): session closed for user root Last edited by Dying_Watchdogs ( 22:57:02) the blinking cursor stops blinking and no inputs are shown anymore. I tried to replicate it, but it didn't work, It went back to the original message, but with the watchdog part missing.Īnother thing I noticed in that state is that the monitor freezes after a half a minute or so, i.e. "echo 0 < /proc/sys/kernel/hung_task_timeout_secs"disables this message.Īfter a while, only the "systemd-journald" message gets posted every few minutes. INFO: task kworker/u32:8:385 blocked for more than 122 seconds.
systemd-journald: Failed to send WATCHDOG=1 notification message: Transport endpoint is not connected systemd-journald: Failed to send WATCHDOG=1 notification message: Connection refused INFO: task umount:9784 blocked for more than 368 seconds. "echo 0 < /proc/sys/kernel/hung_task_timeout_secs" disables this message. INFO: task (sd-sync):9654 blocked for more than 491 seconds. Last edited by Dying_Watchdogs ( 17:43:33)
#ARCH LINUX W DOWN DRIVERS#
One thought I had was whether maybe as a work around, it would be possible to somehow stop the Nvidia drivers at an earlier stage during shutdown/reboot? Provided they are the issue in the first place.Īs you can see, I'm a bit lost here. I've read around a bit and this seems to be an issue with quite some people. I know changing drivers to Nouveau might be a solution, but I need the Nvidia drivers for 3d work (Namely Cuda). I tried downgrading the Nvidia drivers, but that lead to the Light Display Manager not starting, so I'm currently preparing a backup before tinkering with earlier systemd or kernel versions. Trying to reboot -f as root resulted in a complete system freeze, which, as written in above text, points towards the kernel being the issue here (apart from the nvidia drivers of course). If either one of the commands does not work, it's more likely to be a kernel, not systemd bug.
0 kommentar(er)
