Skip to content

Acer Nitro V 15 (ANV15-51, 1025:171e) ALC245: Pin 0x19 jack event storm & pcm31 deep buffer IPC failure upon resume #5971

Open

Description

@scriptsledge

[BUG] Acer Nitro V 15 (ANV15-51): ALC245 Pin 0x19 unsolicited jack event storm & pcm31 deep buffer IPC failure on resume

Hardware & Environment

  • Laptop Model: Acer Nitro V 15 (ANV15-51)
  • Motherboard: Sportage_RTH (BIOS V1.60)
  • Audio Controller: Intel Corporation Raptor Lake-P/U/H cAVS [8086:51ca] (rev 01)
    • Subsystem: Acer Incorporated [1025:171e]
    • Driver: sof-audio-pci-intel-tgl / skl_hda_dsp_generic
  • Audio Codec: Realtek ALC245 (10ec:0245)
    • Subsystem ID: 1025:171e
    • Codec Address: 0
  • Kernel: 7.2.5-3-omarchy x86_64
  • SOF Topology: intel/sof-tplg/sof-hda-generic-2ch.tplg
  • SOF Firmware: intel/sof/sof-rpl.ri (version 2:2:0-57864)

Summary of the Problem

On this laptop, after waking from suspend (lid close and open), two distinct audio issues occur:

  1. Intel SOF IPC error on PCM31 (HDA Analog Deep Buffer): The driver fails with IPC -22 (EINVAL).
  2. Infinite Jack Event Storm on Realtek Pin 0x19: The kernel ALC269/ALC245 quirk applies a pin configuration that marks Pin 0x19 as a "Headset Mic Jack". However, the physical hardware has no jack presence detection circuit on this pin (BIOS reports NO_PRESENCE). The floating pin triggers unsolicited events continuously (~200 interrupts/sec), causing irq/197-AudioDSP to spike and WirePlumber/PipeWire event loops to saturate IPC sockets and peg 1 CPU core at 100%.

Diagnostic Details & Evidence

1. Pin 0x19 Quirk Mismatch

Reading /sys/class/sound/hwC1D0/init_pin_configs (from BIOS):

0x19 0x411111f0
  • 0x4 = Not connected / disabled
  • Misc = NO_PRESENCE

Reading /sys/class/sound/hwC1D0/driver_pin_configs (from kernel quirk table):

0x19 0x03a1103c
  • 0x0 = External Jack, 0xa = Mic In, Unsolicited: tag=02, enabled=1

2. Event Storm Reproduction

Running amixer -c 1 events during the issue shows hundreds of rapid toggle events per second:

event value: numid=11,iface=CARD,name='Headset Mic Jack'
event value: numid=11,iface=CARD,name='Headset Mic Jack'
event value: numid=11,iface=CARD,name='Headset Mic Jack'
... (repeats continuously ~200 times/second)

Overriding Pin 0x19 back to 0x411111f0 via sysfs user_pin_configs immediately stops the event storm and drops CPU usage back to 0%.

3. Intel SOF IPC Error on Wake-up

Kernel log (dmesg / journalctl -k):

sof-audio-pci-intel-tgl 0000:00:1f.3: ipc tx error for 0x60010000 (msg/reply size: 108/20): -22
sof-audio-pci-intel-tgl 0000:00:1f.3: sof_ipc3_pcm_hw_params: pcm31 (HDA Analog Deep Buffer), dir 0: STREAM_PCM_PARAMS ipc failed for stream_tag 2
sof-audio-pci-intel-tgl 0000:00:1f.3: ASoC error (-22): at snd_soc_pcm_component_prepare() on 0000:00:1f.3

Steps to Reproduce

  1. Boot system (audio playback through speakers works normally).
  2. Suspend system (close laptop lid or systemctl suspend).
  3. Resume system (open laptop lid).
  4. Run top: observe irq/*-AudioDSP consuming ~20% CPU and wireplumber consuming 100% of 1 CPU core.
  5. Run amixer -c 1 events: observe uninterrupted torrent of Headset Mic Jack events.

Proposed / Tested Fix

  1. For Realtek ALC245: Add a model quirk for Acer Nitro ANV15-51 (1025:171e) ensuring Pin 0x19 remains 0x411111f0 (disabled) without enabling unsolicited jack detection.
  2. For Intel SOF: Address the STREAM_PCM_PARAMS parameter negotiation failure for pcm31 (HDA Analog Deep Buffer) on wake-up.

(Full alsa-info diagnostic output is attached.)

alsa-info.txt

Activity

  1. bardliao commented on Oct 13, 2026

    @bardliao
    Collaborator

    @KailangYang Can you check the ALC245 issue?

  2. 777-200ER commented on Oct 18, 2026

    @777-200ER

    Same issue on Acer Nitro ANV15-51, kernel <7.2.9-arch1-1>, Arch Linux.

    init_pin_configs shows 0x19 0x411111f0 and driver_pin_configs shows 0x19 0x03a1103c, matching the report.

    I tried the live workaround: stopped wireplumber/pipewire/pipewire-pulse, wrote 0x19 0x411111f0 to user_pin_configs, then wrote 1 to reconfig on a fresh boot with zero suspends. The write to reconfig never returned, and tee sat in D state until I force-powered off. So the sysfs reconfig route isn’t a usable workaround on this model, even with PipeWire stopped.

    I’m new to this and used Claude (AI) to help interpret the values and suggest the workaround, but all the output above is from my own machine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions