2023-05-01
00:00steven has quit [Quit: ZNC 1.8.2 - https://znc.in]
00:01steven has joined #asahi-dev
00:02nicolas17 has joined #asahi-dev
00:12martinr1 has quit [Ping timeout: 480 seconds]
00:35abd has joined #asahi-dev
00:40martinr1 has joined #asahi-dev
00:48martinr1 has quit [Ping timeout: 480 seconds]
00:53nsklaus has quit [Ping timeout: 480 seconds]
01:14martinr1 has joined #asahi-dev
01:29martinr1 has quit [Ping timeout: 480 seconds]
01:43hightower3 has joined #asahi-dev
01:50hightower2 has quit [Ping timeout: 480 seconds]
01:53martinr1 has joined #asahi-dev
02:00gabuscus has quit []
02:01martinr1 has quit [Ping timeout: 480 seconds]
02:13martinr1 has joined #asahi-dev
02:14gabuscus has joined #asahi-dev
02:17stipa is now known as Guest143
02:17stipa has joined #asahi-dev
02:23Guest143 has quit [Ping timeout: 480 seconds]
02:29martinr1 has quit [Ping timeout: 480 seconds]
02:55martinr1 has joined #asahi-dev
02:58nicolas17 has quit [Read error: Connection reset by peer]
03:00nicolas17 has joined #asahi-dev
03:03martinr1 has quit [Ping timeout: 480 seconds]
03:27martinr1 has joined #asahi-dev
03:35martinr1 has quit [Ping timeout: 480 seconds]
03:55nicolas17 has quit [Read error: Connection reset by peer]
03:58nicolas17 has joined #asahi-dev
04:00martinr1 has joined #asahi-dev
04:08martinr1 has quit [Ping timeout: 480 seconds]
04:34martinr1 has joined #asahi-dev
04:42martinr1 has quit [Ping timeout: 480 seconds]
04:44marcanthat usually means some UART power domain is getting turned off, though the HV should disallow that
04:48martinr1 has joined #asahi-dev
05:08martinr1 has quit [Ping timeout: 480 seconds]
05:33martinr1 has joined #asahi-dev
05:43martinr1 has quit [Ping timeout: 480 seconds]
05:43martinr1 has joined #asahi-dev
05:54martinr1 has quit [Ping timeout: 480 seconds]
05:55nicolas17 has quit [Quit: zzZ]
06:17martinr1 has joined #asahi-dev
06:25martinr1 has quit [Ping timeout: 480 seconds]
06:27abd has quit [Remote host closed the connection]
06:49martinr1 has joined #asahi-dev
06:54benpoulson has joined #asahi-dev
06:57martinr1 has quit [Ping timeout: 480 seconds]
07:02benpoulson has quit [Ping timeout: 480 seconds]
07:12martinr1 has joined #asahi-dev
07:20martinr1 has quit [Ping timeout: 480 seconds]
07:24zalyx0 has quit [Read error: Connection reset by peer]
07:24zalyx0 has joined #asahi-dev
07:36richyliu2 has quit [Remote host closed the connection]
07:36richyliu2 has joined #asahi-dev
07:42martinr1 has joined #asahi-dev
08:02jannau has quit [Quit: leaving]
08:08_jannau_ has quit [Quit: ZNC - http://znc.in]
08:18nyilas has joined #asahi-dev
08:18bps2 has joined #asahi-dev
08:19nyilas has quit [Remote host closed the connection]
08:19nyilas has joined #asahi-dev
08:21nyilas has quit [Remote host closed the connection]
08:26Deewiant has quit [Remote host closed the connection]
08:29Deewiant has joined #asahi-dev
08:56mazdoes anyone remember which bit of the kernel is responsible for resetting the boot count that invalidates the m1n1 install after 10 or so failed boots?
08:57roxfan2 has joined #asahi-dev
09:01roxfan has quit [Ping timeout: 480 seconds]
09:34nsklaus has joined #asahi-dev
09:43jannau has joined #asahi-dev
09:49mazyeah, figured out that it is way easier to add this to my chainload script and forget about it.
09:54mazagreed. this is more specific to my own use case where I'm not quite in a position to boot the OS yet, and having to fish for keyboard/mouse every 20 minutes is driving me potty.
10:00jannauone could argue that chainload.py should reset the counter. when chainload runs the system obviously booted successfully to m1n1's proxymode
10:32marcanmaz: m1n1.setup already does the PMU counter reset, so almost all m1n1 scripts automatically do it, including chainload.py
10:35marcanprobably means m1n1 is panicking which means you should be getting a message over the vUART
10:35mazmarcan: my scripts are based on a m1n1 version that is about 2 year old... that might explain why.
10:36chadmedodd, nothing in the console except that same exception after trying to jump to the kernel
10:36marcanremember we don't guarantee ABI compat for the uart protocol, I only actively try to keep chainload.py working
10:37chadmedit's the m1n1 at the front of the guest payload throwing it before the kernel starts printing at all
10:44marcanthere are very few commits to the good commit so it should be very obvious what is wrong from the guest exception
10:45marcanbut probably in the kernel before it installs its own exception handlers, so it goes back to m1n1
10:47mx08 has quit [Quit: WeeChat 3.0]
10:47mx08 has joined #asahi-dev
10:51chadmedtheres nothing special about it, just m1n1 at HEAD, earlycon and debug in chosen.bootargs, the j474s dtb from asahi-wip, the debian netinstaller, then Image from asahi-wip with everything built in
10:52marcanokay but I need the binary if I'm going to try to disassemble it to figure out what it's doing :p
10:59marcanso I guess the last few commits just made m1n1 slightly larger enough that the kernel lost something more critical :p
11:02benpoulson has joined #asahi-dev
11:06chadmedif you search the logs you can find me bumbling around with a 300mb initramfs that decompresses to like a few bytes above 1gb, which broke payload.c and the hypervisor's default heap
11:28kettenismarcan: when we change the installer to produce a .cpio with just the firmwares that u-boot cares about, it will still have pauths that start with vendorfw/ ?
11:37kettenismaybe I should introduce a tiny abstraction layer in u-boot that prepends vendorfw/ such that the firmware name in the driver matches what Linux has
12:24cylm has joined #asahi-dev
12:26benpoulson has quit [Remote host closed the connection]
12:29DarkShadow44 has quit [Quit: ZNC - https://znc.in]
12:29DarkShadow44 has joined #asahi-dev
12:45korreckj328__ has quit [Read error: Connection reset by peer]
12:45korreckj328__ has joined #asahi-dev
13:32korreckj328 has joined #asahi-dev
13:37korreckj328__ has quit [Ping timeout: 480 seconds]
13:45korreckj328 has quit [Remote host closed the connection]
13:46marcanthere's a reddit post about bad interactivity on an 8-core j314 and now I'm wondering if we're doing something wrong with the AIC2 or cpustart setup...
13:46marcansince that kind of thing could be explained by IRQs getting delivered to nonexistent CPUs first (AIC2 will fallback to all CPUs after a timeout if no CPU acks the IRQ)
13:47rcombs has quit [Quit: ZNC - http://znc.in/ZNC]
13:49korreckj328 has joined #asahi-dev
13:51rcombs has joined #asahi-dev
14:25kettenisloading the firmware directly from the ESP would make updating u-boot easier and I suspect it would result in less resistence upstream
14:34marcankettenis: works for me, but then we need the magic ESP selection stuff upstream too, and all that has to run before PCIe/USB init which means NVMe has to come first
14:36marcan(hope we never have to deal with the complex firmware trees in uboot, those need hard/symlinks :p)
14:37amarioguy has joined #asahi-dev
14:38Tomdownsouth has joined #asahi-dev
14:48marcanmaz: so I saw this on reddit and I'm wondering whether it rings any bells: https://www.reddit.com/r/AsahiLinux/comments/134g00u/strange_scheduling_latency_on_the_host_when_kvm/
14:49marcanI *think* those symptoms could be explained by some kind of pathological IRQ routing in KVM, like as if host IRQs don't get handled when they arrive at CPUs that are in the guest
14:50marcanreason being that I believe AIC2 will always try to deliver IRQs to CPUs that are alive instead of waking up CPUs that are asleep, and then will prefer e-clusters by default or if all CPUs are asleep, and it has a fallback where if the IRQ is not acked in a while it broadcasts to all CPUs, which would explain lag if a guest is busy but its CPUs are not properly handling host IRQs
14:52marcancould also be we screwed something up in lower core machines, though I haven't found anything yet
15:01thomas has joined #asahi-dev
15:01Tomdownsouth has quit [Read error: Connection reset by peer]
15:12ChaosPrincessthe rust for linux crowd really needs to work on kernel build ux. just too many things that can cause a random "you aren't getting gpu drivers this kernel build"
15:24korreckj328_ has joined #asahi-dev
15:24korreckj328_ has quit []
15:27jannauTom Rini pointed me to https://lists.denx.de/pipermail/u-boot-custodians/2023-May/001004.html w.r.t the ESP selection problem but I think it is mostly unrelated
15:58mazmarcan: it'd be good to have some details. I'm running my desktop in a VM on the Studio, and otherwise compiling on the host. the host definitely doesn't feel sluggish...
16:00mazeven if an IRQ ends up on the "wrong" core, we can service the interrupt in about 1000 cycles, which wouldn't register at all, so something else must be at odds.
16:07amarioguy has quit [Remote host closed the connection]
16:08mazmarcan: in any case, I'd love the person with the problem to show up on the list. if they are experiencing issues, they probable aren't the only ones (and there's a long list of details I need to know about...)
16:10gladiac has joined #asahi-dev
16:31bps2 has quit [Ping timeout: 480 seconds]
16:34gladiac is now known as Guest191
16:34gladiac has joined #asahi-dev
16:40Guest191 has quit [Ping timeout: 480 seconds]
16:43rhysmdnz has quit [Quit: Bridge terminating on SIGTERM]
16:43Guest12533 has quit [Quit: Bridge terminating on SIGTERM]
16:46Jamie has joined #asahi-dev
16:47rhysmdnz has joined #asahi-dev
16:47Jamie is now known as Guest192
16:49thomas has quit [Remote host closed the connection]
16:51drubrkletern has joined #asahi-dev
17:04brolin has joined #asahi-dev
17:07roxfan has joined #asahi-dev
17:11roxfan2 has quit [Ping timeout: 480 seconds]
17:39brolin has quit [Ping timeout: 480 seconds]
17:42brolin has joined #asahi-dev
17:45mazdoes someone have the part numbers of M2 max CPUs? I'm adding the -pro versions to the vgic SError shit-list, and I might as well do the full M2 range, since it is likely to be the same old story.
17:52roxfan has quit [Ping timeout: 480 seconds]
17:53brolin has quit [Ping timeout: 480 seconds]
17:57roxfan has joined #asahi-dev
17:58brolin has joined #asahi-dev
18:09brolin has quit [Ping timeout: 480 seconds]
18:43nsklaus has quit [Quit: WeeChat 3.8]
18:46nsklaus has joined #asahi-dev
18:50korreckj328_ has joined #asahi-dev
18:55korreckj328 has quit [Ping timeout: 480 seconds]
19:19gladiac has quit [Quit: k thx bye]
19:33brolin has joined #asahi-dev
19:54brolin has quit [Ping timeout: 480 seconds]
19:57korreckj328_ has quit [Remote host closed the connection]
19:58korreckj328_ has joined #asahi-dev
20:08bps2 has joined #asahi-dev
20:31tired has quit [Quit: /]
20:31benpoulson has joined #asahi-dev
20:33tired has joined #asahi-dev
20:33jlco has joined #asahi-dev
20:36jannaumarcan: both plasma and gnome ignore touchbar (display/mt) with non-desktop and the udev rule in https://github.com/AsahiLinux/PKGBUILDs/pull/35
20:41ChaosPrincessprobably not rebased
20:43ChaosPrincesshavent fixed that one yet
20:43benpoulson has quit [Ping timeout: 480 seconds]
20:48ChaosPrincessrebased
21:03korreckj328_ has quit [Remote host closed the connection]
21:04korreckj328_ has joined #asahi-dev
21:05martinr1 has quit [Ping timeout: 480 seconds]
21:11martinr1 has joined #asahi-dev
21:18brolin has joined #asahi-dev
21:44tired has quit [Quit: /]
21:45tired has joined #asahi-dev
22:05jannauChaosPrincess: review as fixups and j493 device nodes https://github.com/jannau/linux/tree/touchbar-touch-fixes
22:08ChaosPrincesshave you tested it on j293
22:09ChaosPrincessi see that its devicetree is missing all the delay and cs gpio stuff
22:10nicolas17 has joined #asahi-dev
22:17martinr1 has quit [Ping timeout: 480 seconds]
22:19ki has joined #asahi-dev
22:39martinr1 has joined #asahi-dev
22:47martinr1 has quit [Ping timeout: 480 seconds]
23:02martinr1 has joined #asahi-dev
23:09bps2 has quit [Ping timeout: 480 seconds]
23:10martinr1 has quit [Ping timeout: 480 seconds]
23:15bluetail has joined #asahi-dev
23:16nsklaus has quit [Ping timeout: 480 seconds]
23:25kit_ty_kate has quit [Quit: WeeChat 3.6]
23:25kit_ty_kate has joined #asahi-dev
23:26korreckj328_ has quit [Quit: Leaving]
23:34martinr1 has joined #asahi-dev
23:48martinr1 has quit [Ping timeout: 480 seconds]