kernel 6.9.12-400.asahi.fc40.aarch64+16k doesn't reach graphical login

[miekg]

Not sure how to fully report this, except this kernel version "does not work", I get bumped in to a VT and can't switch to another VT. This is btw on a GNOME install, not the default KDE

booting 6.9.11-400 fixes things and works like normal. The amount of debugging I can do with .12 seems extremely limited.

this is on a M2

[miekg]

booting with nomodeset doens't seem to help, that just leads to a black screen

[miekg]

and some logs:

Aug 09 14:31:43.535934 miekmac /usr/libexec/gdm-wayland-session[1247]: dbus-daemon[1247]: [session uid=42 pid=1247] Activating service name='ca.desrt.dconf' requested by ':1.2' (uid=42 pid=1248 comm="/usr/libexec/gnome-session-binary --autostart /usr" label="system_u:system_r:xdm_t:s0-s0:c0.c1023")                                                                                                                                           
Aug 09 14:31:43.538914 miekmac /usr/libexec/gdm-wayland-session[1247]: dbus-daemon[1247]: [session uid=42 pid=1247] Successfully activated service 'ca.desrt.dconf'
Aug 09 14:31:43.540000 miekmac audit[1513]: NETFILTER_CFG table=filter:57 family=2 entries=1 op=nft_unregister_rule pid=1513 subj=system_u:system_r:iptables_t:s0 comm="iptables"
Aug 09 14:31:43.545000 miekmac audit: BPF prog-id=67 op=UNLOAD
Aug 09 14:31:43.545000 miekmac audit: BPF prog-id=66 op=UNLOAD
Aug 09 14:31:43.545000 miekmac audit: BPF prog-id=65 op=UNLOAD
Aug 09 14:31:43.549206 miekmac dockerd[1063]: time="2024-08-09T14:31:43.549007642+02:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
Aug 09 14:31:43.559000 miekmac audit[1519]: NETFILTER_CFG table=nat:58 family=2 entries=1 op=nft_register_rule pid=1519 subj=system_u:system_r:iptables_t:s0 comm="iptables"
Aug 09 14:31:43.560388 miekmac gdm-launch-environment][1121]: pam_unix(gdm-launch-environment:session): session closed for user gdm
Aug 09 14:31:43.559000 miekmac audit[1121]: USER_END pid=1121 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_close grantors=pam_keyinit,pam_keyinit,pam_limits,pam_systemd,pam_unix,pam_umask acct="gdm" exe="/usr/libexec/gdm-session-worker" hostname=miekmac addr=? terminal=/dev/tty1 res=success'
Aug 09 14:31:43.559000 miekmac audit[1121]: CRED_DISP pid=1121 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_permit acct="gdm" exe="/usr/libexec/gdm-session-worker" hostname=miekmac addr=? terminal=/dev/tty1 res=success'
Aug 09 14:31:43.562235 miekmac gdm[1054]: Gdm: GdmDisplay: Session never registered, failing
Aug 09 14:31:43.563500 miekmac gdm[1054]: Gdm: Child process -1240 was already dead.
Aug 09 14:31:43.563793 miekmac systemd[1]: session-c1.scope: Deactivated successfully.
Aug 09 14:31:43.563508 miekmac gdm[1054]: Gdm: GdmDisplay: Session never registered, failing
Aug 09 14:31:43.563901 miekmac gdm[1054]: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
Aug 09 14:31:43.563908 miekmac gdm[1054]: Gdm: Child process -1240 was already dead.
Aug 09 14:31:43.564000 miekmac audit[1525]: NETFILTER_CFG table=nat:59 family=2 entries=1 op=nft_register_rule pid=1525 subj=system_u:system_r:iptables_t:s0 comm="iptables"
Aug 09 14:31:43.566101 miekmac systemd-logind[860]: Session c1 logged out. Waiting for processes to exit.
Aug 09 14:31:43.567491 miekmac systemd-logind[860]: Removed session c1.

this seems to try a gdm-x-session instead of gdm-wayland-session, Huh?

[axboe]

Did you update your mesa packages? 6.9.12 (and the 6.10 releases) need a newer version than the one that worked with 6.9.11 and earlier.

[miekg]

ok, weirdly this worked: https://copr.fedorainfracloud.org/coprs/g/asahi/mesa/

complained about having that repo twice in the config, and then proceeded to upgrade the mesa packages.

Thanks for the nudge @axboe

TL:DR: mesa+kernel is tightly synced in asahi, this was a symptom of it not being in sync

[miekg]

More weirdly; doing a simple 'dnf upgrade' on another m2 that I bought later didn't break anything, running .12-401 kernel without problem, wayland running, wifi working. WAT.