You are not logged in.
I am having frequent crashes on my system. It happens in a few cases that I have seen, but not always in these cases. Sometimes my system will run fine for 5 hours and then crash and sometimes it’ll crash instantly upon launching hyprland. I start hyprland with uwsm
The cases where I have noticed crashes multiple times are
- saving a file (namely my hyprland.conf)
- navigating between workspaces in hyprland (mod 1,2,3, etc)
- immediately upon launching hyprland before I even interact with it at all
My trouble is that I am struggling to find any consistent errors in my journalctl logs. today I have had multiple of these crashes. I’m including a few log dumps here
journalctl —since=today
https://0x0.st/8-3X.txt
journalctl —since=today -p 4
https://0x0.st/8-3K.txt
journalctl —since=today -p 3
https://0x0.st/8-3P.txt
In the full journal since today I noticed weird logging around boot starting with 5ca443c9, where it flipped between that one and bad863a95f…
Also it’s concerning that waybar is dumping its core so frequently. I am not sure how to fix that but waybar has been working fine when I am able to use the system.
I also noticed the errors related to intel_ish_ipc today.
General Info that I think may be relevant
- Laptop - Dell XPS 15 9500
- happens on both Linux 6.6.70-1-lts and 6.12.8.arch1-1
- Hyprland 0.46.2-6
- Wayland 1.23.1-1
- Waybar 0.11.0-5
- bluez 5.79-1
- nvidia-dkms 565.77-3
- dbus 1.16.0-1
- wireplumber 0.5.7-1
- Currently my system is fully updated (Recently ran pacman -Syu and used yay to update AUR packages)
- when in a tty (before I launch hyprland) I have not had any crashes (yet) and it seems much more stable. But I admittedly don’t do much in the tty except launch hyprland and occasionally update the system or view logs.
If I can provide any more information please let me know. Any help is appreciated!
Last edited by jamesh1 (2025-01-22 14:36:15)
Offline
Another example that just happened. Boot e9e1156… crashed, and then I turned the laptop back on (boot e0075…)
I connected to external monitors, closed the lid of my laptop (can be seen at the end of the logs when hyprpaper destroys output to eDP-1, and other logs report Lid Closed)
I used the system for another 30 seconds on my monitors and then it crashed. There is no helpful logs as far as I can tell explaining why the crash happened. Any ideas what I can look into?
Offline
can you post your
pacman -Qm Offline
Output of pacman -Qm
1password 8.10.54-22
aic94xx-firmware 30-10
ast-firmware 501-1
catppuccin-gtk-theme-mocha 1.0.3-1
evdi 1.14.8-1
google-chrome 131.0.6778.264-1
jetbrains-toolbox 2.5.2.35332-1
localsend-bin 1.16.1-1
neovim-git 0.11.0.r1409.g4cbeb6fa3c-1
nvidia-prime-rtd3pm 1.1-1
python-archspec 0.2.5-1
python-boltons 24.1.0-1
python-conda 24.11.3-1
python-conda-libmamba-solver 24.11.1-1
python-conda-package-handling 2.3.0-3
python-conda-package-streaming 0.10.0-4
python-inkscape-figures 1.0.8-3
python-inotify 0.2.10-4
python-libmamba 2.0.5-1
reproc 14.2.5-2
simdjson 1:3.11.5-1
terminus-font-ttf 4.49.3-1
upd72020x-fw 1:1.0.0-2
uwsm 0.20.5-1
way-displays 1.11.0-1
wd719x-firmware 1-7
yay-git 12.4.2.r23.g43567b5d-1
yay-git-debug 12.4.2.r23.g43567b5d-1
zsh-completions-git 0.35.0.r181.gc160d09-1
Offline
try the hyprland session that doesn't have uswm listed
Offline
I originally was running that session, and admittedly can’t remember if it was crashing, so I’ll give it another go. But I think it was having the same issues. If I remember correctly my reason for switching to the uwsm session was in hopes of stopping the crashes.
But it’s my understanding that the uwsm managed session would be more stable
because the processes aren’t direct children of the hyprland session. And I believe hyprlands wiki says it’s the preferred way to start hyprland.
Also it’s encouraged to start programs with “uwsm app — (cmd)” when using the uwsm managed session, so my hyprland config and roti config is currently set to use that method of launching programs. Is there an easier way to switch between the methods of launching programs than for example two config files and swapping which one is in use depending on the session I plan to launch.
Offline
we can't help much if you prefer to stick with the uwsm session as uwsm is not officially supported by Arch.
Offline
That makes sense. I was just curious, I have been trying without the uwsm session as I mentioned I would.
I have been launching Hyprland today.
Here is a full journal from today https://0x0.st/8ozQ.txt.
I have had multiple crashes, most happen immediately after launching, and the others are within 30 seconds or so. Just during normal activity (typing, switching workspaces, etc.)
Offline
https://0x0.st/8o-s.txt
https://0x0.st/8o-r.txt
Here are two hyprland crash reports (from ~/.cache/hyprland)
I have tried accessing the log from
cat $XDG_RUNTIME_DIR/hypr/$(ls -t $XDG_RUNTIME_DIR/hypr/ | head -n 1)/hyprland.log
as encouraged by https://wiki.hyprland.org/Crashes-and-B … ng-the-log, but get the error that the directory does not exist (and of course then the log itself doesn't)
Offline
Here's the error you should be researching
[CRITICAL] m_pAqBackend couldn't start! This usually means aquamarine could not find a GPU or encountered some issues. Make sure you're running either on a tty or on a Wayland session, NOT an X11 one. Offline
I think the following is relevant to that error as well (correct me if wrong). I attempted to explicitly set AQ_DRM_DEVICES=/dev/dri/card2:/dev/dri/card1
[LOG] [AQ] drm: Explicit device list /dev/dri/card2:/dev/dri/card1
[LOG] [AQ] drm: Explicit device /dev/dri/card2 found
[ERR] [AQ] drm: Explicit device /dev/dri/card1 not foundWhen I run
ls -l /dev/dri/by-pathI get that 00:02.0 is card 2 and 01:00.0 is card 1.
00:02.0 VGA compatible controller: Intel Corporation CometLake-H GT2 [UHD Graphics] (rev 05) /dev/dri/card2
01:00.0 3D controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Ti Mobile] (rev a1) /dev/dri/card1So it seems to only be using my intel graphics and not finding my Nvidia Card. Which I am not sure why that is the case. I have my /etc/mkinitcpio.conf modules as
MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)modeset and fbdev are also both enabled. I think all of that is intended to get the nvidia card to load early enough it would be detected, but it doesn't seem to be the case.
Also something I am wondering:
I am running Hyprland from tty1 by simply executing
Hyprland. When the system crashes, my laptop restarts entirely. Should it be kicking me back to the tty (which would allow me to view the current log?)
Last edited by jamesh1 (2025-01-13 19:27:02)
Offline
I see you have a custom nvidia-prime module from aur, can you remove that? Also post your Nvidia prime config, i think this may be the cause of the issue.
Offline
Just removed.
What are the Nvidia prime configs?
/etc/udev/rules.d/80-nvidia-pm.rules
/etc/modprobe.d/nvidia-pm.confI have no file for either of these currently. These files were mentioned in this Wiki https://wiki.archlinux.org/title/PRIME#NVIDIA. The wiki says that the aur package I had provides the files so I didn't have to write them myself.
I also found
/etc/udev/rules.d/60-nvidia.rules
/etc/modprobe.d/nvidia.confWhich are
# Device nodes are created by nvidia-modprobe, which is called by the nvidia DDX.
# In case the DDX is not started, the device nodes are never created, so call
# nvidia-modprobe in the udev rules to cover the Wayland/EGLStream and compute
# case without a started display. In the case where vfio-pci is used
# nvidia-modprobe should not be invoked.
ACTION=="add|bind", ATTR{vendor}=="0x10de", ATTR{class}=="0x03[0-9]*", \
DRIVER=="nvidia", TEST!="/dev/nvidia-uvm", \
RUN+="/usr/bin/nvidia-modprobe", \
RUN+="/usr/bin/nvidia-modprobe -c0 -u"and
options nvidia_drm modeset=1 fbdev=1Respectively.
After removing the AUR package, I am still getting crashes. No crash log to .cache/hyprland or in the XDG_RUNTIME_DIR (because it restarts the computer not crashes to tty)
Last edited by jamesh1 (2025-01-13 19:54:04)
Offline
I also just ran a pacman -Ql nvidia-prime. I only see /usr/bin/prime-run as the files installed by nvidia-prime
The content of that file is
#!/bin/bash
__NV_PRIME_RENDER_OFFLOAD=1 __VK_LAYER_NV_optimus=NVIDIA_only __GLX_VENDOR_LIBRARY_NAME=nvidia "$@"Offline
I will also note, when I have a couple seconds in Hyprland before a crash I have run these couple commands for information on prime
cat /sys/bus/pci/devices/0000:01:00.0/power/runtime_status
cat /sys/bus/pci/devices/0000:01:00.0/power/runtime_suspended_timeThe first gives "active", so I checked the second as the Prime wiki says to do. The suspended time never increments, which leads me to believe there is definitely something wrong with the way prime is setup on my system.
EDIT: https://bbs.archlinux.org/viewtopic.php … 7#p2181317 solved this problem. The GPU now is suspending
Last edited by jamesh1 (2025-01-14 17:17:55)
Offline
In the past couple days I have tested running GNOME (and also Windows). I noticed the same type of crash (much less frequently, but same exact thing happening). This led me to research this specific to my Laptop not the OS/WM.
I found this seems to be a common problem (exact symptoms I am having) with Dell Laptops in general, so I'll close this as it's not an Arch or Hyprland specific problem it doesn't seem like anymore.
https://www.dell.com/community/en/conve … 5fca247538
https://www.dell.com/community/en/conve … 0b019c96bb
https://www.dell.com/community/en/conve … 5897890270
Offline