#
#asahi-dev · 2025-06-22 04:26
chadmedwayland or x11?
#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
#asahi-dev · 2025-06-21 17:59
nickchanand i can't do that from linux
#asahi-dev · 2025-06-21 17:59
nickchanit's also very annoying to put t8012 into dfu mode without macvdmtool
#asahi-dev · 2025-06-21 17:42
svenit's either a bug in mfd or it's expected behavior
#asahi-dev · 2025-06-21 17:42
svenofc it does, the reboot driver isn't special in that case
#asahi-dev · 2025-06-21 17:42
nickchanthe gpio driver also probes without a node btw
#asahi-dev · 2025-06-21 17:41
nickchanwell that's after disabled wdt in device tree
#asahi-dev · 2025-06-21 17:41
svenweird
#asahi-dev · 2025-06-21 17:41
nickchanthen it does not restart
#asahi-dev · 2025-06-21 17:40
nickchansven: says reboot: Restarting system
#asahi-dev · 2025-06-21 17:32
svenso does t8015 support smc-reboot then?
#asahi-dev · 2025-06-21 17:31
nickchanno mbse on t8012
#asahi-dev · 2025-06-21 17:31
svenso the key exists but reboot doesn't?
#asahi-dev · 2025-06-21 17:31
nickchansven: on t8015: #401: MBSE = (hex_, 0xd4) 2f 00 00 00
#asahi-dev · 2025-06-21 16:55
svennickchan: also, does the key MBSE exist there?
#asahi-dev · 2025-06-21 16:54
fl0_idinteresting :)
#asahi-dev · 2025-06-21 16:53
amarioguy2fl0_id: yes that's sorta been the reason i sometimes ask questions here
#asahi-dev · 2025-06-21 16:53
svennickchan: what device doesn't have smc-reboot btw.? was that really only introduced later?
#asahi-dev · 2025-06-21 16:47
fl0_idor do I misunderstand windows bootloader
#asahi-dev · 2025-06-21 16:47
fl0_idamarioguy2 so you're loading windows on arm with m1n1 hv?
#asahi-dev · 2025-06-21 16:46
fl0_idnickchan yeah that's what I assumed, but just wanted to make sure
#asahi-dev · 2025-06-21 16:31
amarioguy2also had a quirk a couple times where sometimes a few instructions before an exception is hit it will "speculate" to the exception directly - which was *so* annoying when trying to debug why exceptions happened
#asahi-dev · 2025-06-21 16:30
amarioguy2i don't think it's a foundational m1n1 debugger problem? but at the same time wanted to point the weird behavior out in case anyone else had that behavior (it usually tends to happen when the Windows first-stage bootloader hits an exception and enters the branch loop)
#asahi-dev · 2025-06-21 16:28
amarioguy2btw one note on the backtrace thing in m1n1 - more of an aside i wanted to note than anything else - i've had certain situations during my debugging where the hv debugger backtrace is just infinitely spamming the same two addresses when it tries to print the backtrace
#asahi-dev · 2025-06-21 16:26
nickchanxnu is running but those output are not from it
#asahi-dev · 2025-06-21 16:25
nickchan*not from xnu
#asahi-dev · 2025-06-21 16:25
nickchanand the output after jumping to entrypoint is from the m1n1 hypervisor not from m1n1
#asahi-dev · 2025-06-21 16:21
nickchans3_0_c15_c2_3 and s3_0_c15_c2_4 should be HID30 and HID31 respectively
#asahi-dev · 2025-06-21 16:19
nickchanso yeah it's starting on cpu4
#asahi-dev · 2025-06-21 16:19
nickchanoops, meant > > CPU init (MIDR: 0x611f0492 smp_id:0x4)...
#asahi-dev · 2025-06-21 16:19
nickchan> and during booting you might want to add cpus=1
#asahi-dev · 2025-06-21 16:19
nickchanI think so
#asahi-dev · 2025-06-21 15:28
fl0_idoh and as it has so much output about the cpu4 at the end, I assume that's the one it's starting on?
#asahi-dev · 2025-06-21 15:18
fl0_idthanks for the feedback
#asahi-dev · 2025-06-21 15:18
fl0_idjannau ok cool. might get to try this evening
#asahi-dev · 2025-06-21 15:17
fl0_idsven ah k
#asahi-dev · 2025-06-21 15:02
jannauon the current cpu and the hypervisor can switch CPUs
#asahi-dev · 2025-06-21 15:01
jannaufl0_id: bt should provide a backtrace
#asahi-dev · 2025-06-21 15:01
jannauchicken bits in xnu are sone on the boot CPU
#asahi-dev · 2025-06-21 15:00
sventhat's expected, usb-pd no longer uses i2c
#asahi-dev · 2025-06-21 15:00
fl0_idbut not sure if that matters
#asahi-dev · 2025-06-21 15:00
fl0_idthere is also TTY> i2c: Error getting /arm-io/i2c0 node TTY> usb: i2c init failed.
#asahi-dev · 2025-06-21 14:59
fl0_idjannau you would have to explain a bit more. ctrl-c the hv and then?
#asahi-dev · 2025-06-21 14:59
fl0_idsven k
#asahi-dev · 2025-06-21 14:58
svenshould be xnu already after "Jumping to entrypoint at 0x1001b800660"
#asahi-dev · 2025-06-21 14:58
jannauhave interrupted the HV and `bt`s each CPU?

plus ›