MacBook Air 2020 (j313ap): kernel fails to boot when power charger plugged in

[alxdrl]

6.3.0-asahi-7-1-edge-ARCH kernel fails to boot when USB-C charger is plugged in Port 2.

• Was working until kernel upgrade earlier today
• It boots ok when power charger plugged in Port 1 or not plugged at all.
• Failure reproduced with Apple 61W USB-C adapter and some "Port Connect" 60W USB-C adapter
• Same failure occurs when tether-booted the kernel from Asahi package with proxyclient
• Self-compiled non-modular kernel with tag asahi-6.3-7 and half-baked config seems to work (see gist)

Last message on the console is (may not be relevant):

Mounted System ESP /dev/nvme0n1p4 at /run/.system-efi
31588 blocks
[   0.555696] macsmc-rtkit 23e400000,smc: Failed to create device link (0x180)
[   0.556196] macsmc-rtkit 23e400000,smc: Failed to create device link (0x180)
[   0.556699] macsmc-rtkit 23e400000,smc: Failed to create device link (ax180)
[   0.557690] pcie-apple 690000000,pcie: invalid resource

Then either reboots (watchdog timer) or freezes with RCU error messages.

Additional info

• more details: https://gist.github.com/aderuelle/ef62dcd7461699b98613e2273289794b
• IRC logs: https://oftc.irclog.whitequark.org/asahi/2023-06-10#32217995

Collecting system information...
  Product name: MacBook Air (M1, 2020)
  SoC: Apple M1
  Device class: j313ap
  Product type: MacBookAir10,1
  Board ID: 0x26
  Chip ID: 0x8103
  System firmware: iBoot-8422.121.1
  Boot UUID: EDC16493-C9C1-4D33-A0D1-446F30928850
  Boot VGID: EDC16493-C9C1-4D33-A0D1-446F30928850
  Default boot VGID: 6E42B3A4-5667-4964-84FF-BFAD017AA4DC
  Boot mode: macOS
  OS version: 12.6.6 (21G646)
  SFR version: 22.6.66.0.0,0
  System rOS version: 13.4 (22F66)
  No Fallback rOS
  Login user: alexis

Collecting partition information...
  System disk: disk0

Collecting OS information...

Partitions in system disk (disk0):
  1: APFS [Macintosh HD] (183.83 GB, 6 volumes)
    OS: [B ] [Macintosh HD] macOS v12.6.6 [disk4s3s1, EDC16493-C9C1-4D33-A0D1-446F30928850]
  2: APFS [Asahi Linux] (2.50 GB, 4 volumes)
    OS: [ *] [Asahi Linux] m1n1 v1.2.9 (macOS 12.3 stub) [disk3s2, 6E42B3A4-5667-4964-84FF-BFAD017AA4DC]
  3: EFI (500.17 MB)
  4: Linux Filesystem (58.28 GB)
  5: APFS (System Recovery) (5.37 GB, 2 volumes)
    OS: [  ] recoveryOS v13.4 [Primary recoveryOS]

  [B ] = Booted OS, [R ] = Booted recovery, [? ] = Unknown
  [ *] = Default boot volume

Using OS 'Macintosh HD' (disk4s3s1) for machine authentication.

[CobyPear]

~I have been using Asahi on an m1 macmini for awhile with no issues. Recently I noticed I could no longer ssh in, but other things were working fine. Today I plugged in a monitor and I'm not sure exactly what I did but the screen went blank but I could still use the mouse. I restarted and got the same error reported above. I'm not sure how to get back into my machine now :( I can't even login via tty with correct credentials - it always says they are wrong.~

Typing out the portion of the logs that differ here:

macsmc-rtkit 23e4000000.smc: Failed to create device link (0x180) with 23d0d9300.spmi:pmu@f:rtc_nvmem@d000
macsmc-rtkit 23e4000000.smc: Failed to create device link (0x180) with 23d0d9300.spmi:pmu@f:rtc_nvmem@d000
macsmc-rtkit 23e4000000.smc: Failed to create device link (0x180) with 23d0d9300.spmi:pmu@f:legacy_nvme@9f00

Any help would be much appreciated. ty, resolved!

[jannau]

@CobyPear you're issue is almost certainly unrelated to this issue. the Failed to create device link are not fatal and present in working systems. The blank screen might be issue with driver installation. nomodeset in the kernel command line avoids loading the drm/kms display driver which prevents the GPU/OpenGL from being used. If that works you will get a working but slow due to software rendering GUI to investigate.

[CobyPear]

@jannau thanks for the help here and in irc. I was able to resolve my issue, very much a user error 🙃