#
✕ nick:dramforever
#asahi-dev · 2025-07-27 02:49
dramforevernevermind i had APPLE_WATCHDOG as m and forgot to put that in my initrd
#asahi-dev · 2025-07-27 02:38
dramforeverearly as in like, in the initrd early
#asahi-dev · 2025-07-27 02:36
dramforeverhow do i / can i disable the watchdog manually to give me time to debug early boot failures?
#asahi-dev · 2025-06-24 14:32
dramforever(i don't know what the proper term is but if e.g. i wake my computer up from idle i get "DP2HDMI HPD irq, connected:0" and then about two seconds later "DP2HDMI HPD irq, connected:1")
#asahi-dev · 2025-06-24 14:31
dramforeveranother possibly relevant idea: when my monitor "activates" it disconnects HPD for like two seconds and reconnects
#asahi-dev · 2025-06-24 13:29
dramforeverah that makes a lot of sense
#asahi-dev · 2025-06-24 13:28
dramforeveri was thinking more like, new firmware or something
#asahi-dev · 2025-06-24 13:27
dramforeverok, thanks, that's one less thing to try
#asahi-dev · 2025-06-24 13:24
dramforeverjust an idea, is there any chance the dcp_hotplug deadlock thing i got earlier is because my macos is really old?
#asahi-dev · 2025-06-22 12:37
dramforeversince this happens just with few kernel modules, i could theoretically try to reproduce it with a "clean" kernel and a busybox initramfs but i'm not doing that today...
#asahi-dev · 2025-06-22 12:34
dramforeverokay this is the "full" stack trace https://fars.ee/DkfT i get when the deadlock happens
#asahi-dev · 2025-06-22 12:07
dramforever(obviously, as in, disconnected_hpd_event which calls drm_kms_helper_connector_hotplug_event deadlocks, so i just removed disconnected_hpd_event)
#asahi-dev · 2025-06-22 12:06
dramforeverso i reverted this and it obviously solves my problem but that doesn't really explain anything https://github.com/AsahiLinux/linux/commit/794a1166e09f0b836b95c13fc7f999c5a08a6260
#asahi-dev · 2025-06-22 11:32
dramforeveryes, if by "second monitor" you're counting the internal display as the first
#asahi-dev · 2025-06-22 11:21
dramforeverNew observation: I can get this (suspected) deadlock without even starting SDDM. It occurs at the module loading stage. Starting SDDM at the right time actually *prevents* the deadlock
#asahi-dev · 2025-06-22 10:31
dramforeveri also bpftrace'd drm_client_dev_hotplug and it's definitely the same device both time, so it's recursing and just deadlocking on itself
#asahi-dev · 2025-06-22 10:30
dramforeverthe thing i'm seeing is systemd-logind blocked in an open syscall on some drm stuff
#asahi-dev · 2025-06-22 10:29
dramforeveryeah sorry, some drm device
#asahi-dev · 2025-06-22 10:27
dramforeveri'm not sure about the logind part but i'm fairly certain that's how systemd works
#asahi-dev · 2025-06-22 10:25
dramforeveron restart sddm asks systemd-logind to open the gpu for it, and then logind joins the team of blocked processes
#asahi-dev · 2025-06-22 10:25
dramforeverjannau: it does not work :(
#asahi-dev · 2025-06-22 09:03
dramforeveri can't believe i've never tried that, but honestly i don't expect it to work with the drm thing just locked
#asahi-dev · 2025-06-22 08:43
dramforever... nope same thing in 6.14.6-1
#asahi-dev · 2025-06-22 08:27
dramforeverjust for the record i'm going back to asahi-6.14.6-1 for now and see for sure if it's just the new update, and then possibly crawl through the git log and see if anything looks like it could be responsible
#asahi-dev · 2025-06-22 04:36
dramforeveris this... supposed to happen? I see drm_client_dev_hotplug twice but I don't know if they're for the same dev
#asahi-dev · 2025-06-22 04:34
dramforeverI hope I copied everything down right
#asahi-dev · 2025-06-22 04:34
dramforeverStack trace is like this https://fars.ee/AH-SPBD-9uv6NFYlpJTSXvT7YzBr
#asahi-dev · 2025-06-22 04:28
dramforeverthis seems to be highly dependent on the timing of loading of a few kernel modules
#asahi-dev · 2025-06-22 04:28
dramforeveri configured it to do that
#asahi-dev · 2025-06-22 04:28
dramforeverno it's kwin_wayland
#asahi-dev · 2025-06-22 04:27
dramforeveroh, it might be weston not kwin_wayland, let me check
#asahi-dev · 2025-06-22 04:26
dramforeverwayland, sddm in fact
#asahi-dev · 2025-06-22 04:20
dramforever(I'm currently trying to copy down the whole stack trace from my photo...)
#asahi-dev · 2025-06-22 04:19
dramforeversysrq "w" tells me dcp_hotplug is blocked and in the stack trace it looks like it's calling apple_crtc_atomic_disable then dcp_poweroff then it tries to mutex_lock which just blocks, so it looks like a deadlock? Is there anything known like that?
#asahi-dev · 2025-06-22 04:18
dramforeverotherwise hung...
#asahi-dev · 2025-06-22 04:18
dramforeverHi, I'm currently using a "custom" built NixOS kernel and I'm trying to figure out what i'm doing wrong. I'm on an "Apple MacBook Pro (14-inch, M1 Pro, 2021)" and asahi-6.14.8-1, and on boot, if I have a monitor plugged into HDMI, there's a chance that it hangs around where graphical interface should be starting with only a cursor on the top left on the laptop screen and nothing on HDMI. At this point the system is responsive to sysrq but