tas2764 2-003c: fault: over current

[jvoisin]

I recently got some worrying tas2764-related logs in my dmesg:

[58905.633152] macsmc-rtkit 23e400000.smc: RTKit: syslog message: charger.cpp:2420: Not charging:400001
[64729.753379] macsmc-power macsmc-power: Charging: 0
[64729.762817] macsmc-power macsmc-power: Port 1 state change (charge port: 1)
[64729.770272] macsmc-rtkit 23e400000.smc: RTKit: syslog message: aceElec.cpp:703: 	Elec: Elec Cause 0x0
[64990.658905] tas2764 2-003c: fault: over current
[64990.658910] tas2764 2-003c: other context to the fault: 02,19,00,00,00
[64992.152151] tas2764 2-003c: fault: over current
[64992.152163] tas2764 2-003c: other context to the fault: 02,19,00,00,00
[65455.808133] input: WH-1000XM3 (AVRCP) as /devices/virtual/input/input7
[65508.174031] macsmc-rtkit 23e400000.smc: RTKit: syslog message: aceElec.cpp:703: 	Elec: Elec Cause 0x0
[65508.272872] macsmc-power macsmc-power: Port 1 state change (charge port: 1)
[65508.272947] macsmc-power macsmc-power: Port 1 state change (charge port: 1)
[65508.275358] macsmc-power macsmc-power: Charging: 1

$ asahi-diagnose
# Asahi Linux System Diagnostic Dump

    Collected at:   Fri  9 Aug 22:07:59 PDT 2024 (2024-08-09T22:07:59-07:00)
    Username:       jvoisin
    Hostname:       chernabog

## Device information
    Model:          Apple MacBook Air (13-inch, M2, 2022)
    Compatible:     apple,j413 apple,t8112 apple,arm-platform

## Firmware versions
    iBoot1:         iBoot-10151.140.19
    iBoot2:         iBoot-8422.141.2
    SFR:            unknown
    OS firmware:    13.5
    m1n1 stage 2:   v1.4.14
    U-Boot:         2024.04

## Boot information
    ESP UUID:       f0f3e299-07aa-4db9-a3fe-965e5969237a
    EFI:            available

## System information
    Distro:         Fedora Linux Asahi Remix 40 (Workstation Edition)
    Kernel:         6.9.12-401.asahi.fc40.aarch64+16k
    Kernel build:   #1 SMP PREEMPT_DYNAMIC Sat Aug  3 22:26:24 UTC 2024
    Uptime:          22:07:59 up 1 day,  5:41,  1 user,  load average: 0.81, 1.07, 1.33
    Kernel cmdline: BOOT_IMAGE=(hd0,gpt5)/vmlinuz-6.9.12-401.asahi.fc40.aarch64+16k root=UUID=6b7fba8b-c7ab-48fe-b5b2-a3ce1dc9476f ro rootflags=subvol=root rhgb quiet rootflags=subvol=root rd.luks.uuid=2cae1ea9-2f69-4e31-9b28-d0d236fe3d5c brcmfmac.feature_disable=0x82000

## Audio Configuration:
    Default profile: 
    Pro Audio profile detected: no
    Old configuration files in `/etc/`: no
    File conflicts in `/usr/share/`: no
    Speaker detonation requested: no
    TAS2764 quirks applied: yes


## Package versions

alsa-ucm-asahi-5-3.fc40.noarch
asahi-audio-2.2-1.fc40.noarch
asahi-platform-metapackage-0-12.fc40.aarch64
asahi-repos-1-13.fc40.noarch
dracut-asahi-20240429-1.fc40.noarch
fedora-asahi-remix-scripts-20240722-1.fc40.noarch
kernel-16k-6.9.11-400.asahi.fc40.aarch64
kernel-16k-6.9.12-400.asahi.fc40.aarch64
kernel-16k-6.9.12-401.asahi.fc40.aarch64
kernel-16k-modules-extra-6.9.11-400.asahi.fc40.aarch64
kernel-16k-modules-extra-6.9.12-400.asahi.fc40.aarch64
kernel-16k-modules-extra-6.9.12-401.asahi.fc40.aarch64
m1n1-1.4.14-3.fc40.aarch64
package asahi-fwextract is not installed
package mesa is not installed
pipewire-1.0.7-2.fc40.aarch64
speakersafetyd-0.1.9-3.fc40.aarch64
tiny-dfr-0.2.0-5.fc40.aarch64
uboot-images-armv8-2024.04-4.fc40.noarch
update-m1n1-20240429-1.fc40.noarch
wireplumber-0.5.5-1.fc40.aarch64

$

[marcan]

Did the speakers stop working or functioning properly? If not, this might just be working as intended. There are issues with the overcurrent alert on the speaker amps due to what we believe is a hardware bug/errata. It doesn't mean the OS did anything wrong or the speakers are in danger.

[jvoisin]

They keep functioning properly.