#
…

2025-06-22

01:42pb17 has quit [Ping timeout: 480 seconds]
01:47pb17 has joined #asahi-dev
02:15tobhe has joined #asahi-dev
02:20hexdump01 has joined #asahi-dev
02:22hexdump0815 has quit [Ping timeout: 480 seconds]
02:22tobhe_ has quit [Ping timeout: 480 seconds]
03:58nora has joined #asahi-dev
04:00nora_ has quit [Ping timeout: 480 seconds]
04:04___nick___ has joined #asahi-dev
04:08___nick___ has quit []
04:09dramforever has joined #asahi-dev
04:10___nick___ has joined #asahi-dev
04:11___nick___ has quit []
04:14___nick___ has joined #asahi-dev
04:18dramforeverHi, 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
04:18dramforeverotherwise hung...
04:19dramforeversysrq "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?
04:20dramforever(I'm currently trying to copy down the whole stack trace from my photo...)
04:26chadmedwayland or x11?
04:26dramforeverwayland, sddm in fact
04:26chadmedis sddm being launched in kwin_wayland? iirc it still doesnt do this by default
04:27dramforeveroh, it might be weston not kwin_wayland, let me check
04:28dramforeverno it's kwin_wayland
04:28dramforeveri configured it to do that
04:28chadmedwe did have issues at some point with something similar but i thought the issue was fixed
04:28chadmedthat was related to planes though and wasnt an issue with crtc ops
04:28dramforeverthis seems to be highly dependent on the timing of loading of a few kernel modules
04:29chadmedlikely a race or deadlock then
04:34dramforeverI hope I copied everything down right
04:36dramforeveris this... supposed to happen? I see drm_client_dev_hotplug twice but I don't know if they're for the same dev
04:39chadmed has quit [Quit: Konversation terminated!]
04:40chadmed has joined #asahi-dev
04:46dramforever has quit [Quit: Leaving]
04:53dramforever has joined #asahi-dev
04:59dramforever has quit [Remote host closed the connection]
05:18ddxtanx has quit [Remote host closed the connection]
05:20ddxtanx has joined #asahi-dev
05:31Calandracas_ has quit [Ping timeout: 480 seconds]
06:52mattia013_ has joined #asahi-dev
06:57mattia013 has quit [Ping timeout: 480 seconds]
06:57mattia013_ is now known as mattia013
07:46flokli has quit [Quit: WeeChat 4.6.2]
07:46flokli has joined #asahi-dev
07:48pb17 has quit [Ping timeout: 480 seconds]
07:50pb17 has joined #asahi-dev
08:23dramforever has joined #asahi-dev
08:27dramforeverjust 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
08:32dramforever has quit [Quit: Leaving]
08:41dramforever has joined #asahi-dev
08:43dramforever... nope same thing in 6.14.6-1
08:48psykose has quit [Remote host closed the connection]
08:51psykose has joined #asahi-dev
09:03jannaudramforever: can ssh in and restart sddm?
09:03dramforeveri can't believe i've never tried that, but honestly i don't expect it to work with the drm thing just locked
09:05jannauif it does work, I can reproduce it. Since restarting sddm worked I never blamed it on the driver
09:06dramforever has quit [Quit: Leaving]
09:28pb17 has quit [Remote host closed the connection]
09:28pb17 has joined #asahi-dev
10:24chadmedlmfao i spent almost all day chasing an off-by-one
10:24dramforever has joined #asahi-dev
10:25chadmed(of my own making of course)
10:25dramforeverjannau: it does not work :(
10:25dramforeveron restart sddm asks systemd-logind to open the gpu for it, and then logind joins the team of blocked processes
10:26chadmedthat sounds like something very wrong with your system. sddm should not need to ask to open the gpu
10:27dramforeveri'm not sure about the logind part but i'm fairly certain that's how systemd works
10:28chadmedoh yes i misunderstood
10:29chadmedi thought logind was asking _you_ for permission to open the gpu
10:29jannauI assume gpu means the display controllers drm device. not sure if it is sddm itself or if that's deferred to kwin though
10:29dramforeveryeah sorry, some drm device
10:30dramforeverthe thing i'm seeing is systemd-logind blocked in an open syscall on some drm stuff
10:31dramforeveri 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
10:35dramforever has quit [Remote host closed the connection]
11:09pb17 has quit [Ping timeout: 480 seconds]
11:15pb17 has joined #asahi-dev
11:19dramforever has joined #asahi-dev
11:21dramforeverNew 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
11:21ravikant_ has joined #asahi-dev
11:29chadmedis it _only_ with a second monitor plugged in?
11:32dramforeveryes, if by "second monitor" you're counting the internal display as the first
11:38ravikant__ has joined #asahi-dev
11:38ravikant__ has quit []
11:52dramforever has quit [Remote host closed the connection]
12:04dramforever has joined #asahi-dev
12:06dramforeverso i reverted this and it obviously solves my problem but that doesn't really explain anything https://github.com/AsahiLinux/linux/commit/794a1166e09f0b836b95c13fc7f999c5a08a6260
12:07dramforever(obviously, as in, disconnected_hpd_event which calls drm_kms_helper_connector_hotplug_event deadlocks, so i just removed disconnected_hpd_event)
12:34dramforeverokay this is the "full" stack trace https://fars.ee/DkfT i get when the deadlock happens
12:37dramforeversince 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...
14:19Calandracas has joined #asahi-dev
14:36ravikant_ has quit [Ping timeout: 480 seconds]
14:58mattia013 has quit [Remote host closed the connection]
14:59dramforever has quit [Remote host closed the connection]
15:00mattia013 has joined #asahi-dev
16:21Ansh has joined #asahi-dev
16:21Ansh has quit []
16:32chadmed has quit [Quit: Konversation terminated!]
16:33chadmed has joined #asahi-dev
16:33chadmed has quit []
16:33chadmed has joined #asahi-dev
16:33chadmed has quit []
16:34chadmed has joined #asahi-dev
16:35chadmed has quit []
16:35chadmed has joined #asahi-dev
16:35chadmed has quit []
16:37chadmed has joined #asahi-dev
16:41cow123_ has quit [Remote host closed the connection]
16:42cow123 has joined #asahi-dev
17:35chadmed has quit [Quit: Konversation terminated!]
17:35chadmed has joined #asahi-dev
17:36chadmed has quit []
17:36chadmed has joined #asahi-dev
17:36chadmed has quit []
17:37chadmed has joined #asahi-dev
17:37chadmed has quit []
17:38chadmed has joined #asahi-dev
17:38chadmed has quit []
17:38chadmed has joined #asahi-dev
17:38chadmed has quit []
17:38chadmed has joined #asahi-dev
18:36___nick___ has quit [Ping timeout: 480 seconds]
20:44pb17 has quit [Ping timeout: 480 seconds]
20:48pb17 has joined #asahi-dev
20:57okb has quit [Read error: Connection reset by peer]
22:10pb17 has quit [Ping timeout: 480 seconds]
22:15pb17 has joined #asahi-dev
…