Garbled HDMI audio. Transfer failed: File descriptor in bad state
I have a TV connected to the HDMI port of my A770, the detected properties are:
andrew@andrew-gentoo-pc card2 % cat /proc/asound/card2/eld\#2.0
monitor_present 1
eld_valid 1
codec_pin_nid 0x4
codec_dev_id 0x0
codec_cvt_nid 0x3
monitor_name HKC-TV
connection_type DisplayPort
eld_version [0x2] CEA-861D or below
edid_version [0x3] CEA-861-B, C or D
manufacture_id 0x6321
product_id 0x0
port_id 0x0
support_hdcp 0
support_ai 0
audio_sync_delay 0
speakers [0x1] FL/FR
sad_count 3
sad0_coding_type [0x1] LPCM
sad0_channels 2
sad0_rates [0xe0] 32000 44100 48000
sad0_bits [0x60000] 16 20
sad1_coding_type [0xa] E-AC-3/DD+ (Dolby Digital Plus)
sad1_channels 8
sad1_rates [0xe0] 32000 44100 48000
sad2_coding_type [0x2] AC-3
sad2_channels 6
sad2_rates [0xe0] 32000 44100 48000
sad2_max_bitrate 640000Sending audio to the TV results in this mess: 3106__2023-05-15_21_23_28_ This is KDE Plasma's speaker testing utility, we can only hear front left (but audio is garbled), front right does not do anything at all.
- There is also a monitor connected using DisplayPort, this audio connection works fine.
- The HDMI connection to the TV works fine under Windows, so this cannot be a hardware problem.
- The HDMI connection is listed as a DisplayPort connection in the eld info, whether this is actually a problem and if it is related to the audio issue I don't know.
- Sending ac3 audio (which is listed as supported and also works under Windows) results in no sound at all.
- Happens both with kernel version 6.3.2 and the latest drm-tip.
Activity
added Community feature: display/audio platform: DG2 labels
@AndrewAmmerlaan
Please try with latest drmtip kernel and provide the i915 logs as in below instructions: drm.debug=0x1e log_buf_len=4M https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugsI had already tried with the drm-tip branch. I did indeed forget to attach a log. Here's one: dmesg.log
Cc : @uma_mnnit @vsyrjala
The speaker-test command comes back with an error, again only front left is audible:
speaker-test -c2 -twav -Dhdmi:CARD=PCH_1,DEV=0 -l 10 speaker-test 1.2.9 Playback device is hdmi:CARD=PCH_1,DEV=0 Stream parameters are 48000Hz, S16_LE, 2 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 64 to 1048576 Period size range from 32 to 524288 Using max buffer size 1048576 Periods = 4 was set period_size = 262144 was set buffer_size = 1048576 0 - Front Left 1 - Front Right Write error: -77,File descriptor in bad state xrun_recovery failed: -77,File descriptor in bad state Transfer failed: File descriptor in bad statespeaker-test -c2 -twav -Dplughw:CARD=PCH_1,DEV=3 -l 10 speaker-test 1.2.9 Playback device is plughw:CARD=PCH_1,DEV=3 Stream parameters are 48000Hz, S16_LE, 2 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 64 to 1048576 Period size range from 32 to 524288 Using max buffer size 1048576 Periods = 4 was set period_size = 262144 was set buffer_size = 1048576 0 - Front Left 1 - Front Right Write error: -77,File descriptor in bad state xrun_recovery failed: -77,File descriptor in bad state Transfer failed: File descriptor in bad state@kaivehmanenintel @ckborah Please have a look.
Edited by Suresh@AndrewAmmerlaan can you share output of alsa-info tool (preferably when the garbled audio is output). And can you try "speaker-test -c2 -twav -Dhw:1,3 -l 10"? The errors look like the some ALSA plugin would be used here (giving the EBADFD/77 errors), but could be issue with the hardware as well.
Here's my alsa-info: alsa-info.txt.9uE6eElm3n
And the speaker-test output:
speaker-test -c2 -twav -Dhw:1,3 -l 10 speaker-test 1.2.9 Playback device is hw:1,3 Stream parameters are 48000Hz, S16_LE, 2 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 64 to 1048576 Period size range from 32 to 524288 Using max buffer size 1048576 Periods = 4 was set period_size = 262144 was set buffer_size = 1048576 0 - Unknown 1 - Unknown Write error: -77,File descriptor in bad state xrun_recovery failed: -77,File descriptor in bad state Transfer failed: File descriptor in bad stateI do have the alsa-plugins and dcaenc packages installed, but I already tried removing these and this made no difference.
Here's the contents of my alsa conf.d:
andrew@andrew-gentoo-pc ~ % ls /etc/alsa/conf.d 10-rate-lav.conf 50-pulseaudio.conf 60-speex.conf 98-usb-stream.conf dca.conf 10-speexrate.conf 51-pulseaudio-probe.conf 60-upmix.conf 99-pipewire-default-hook.conf 50-pipewire.conf 60-a52-encoder.conf 60-vdownmix.conf 99-pulseaudio-default.conf.exampleThese packages are the owners of those files (I already tried without dcaenc and alsa-plugins):
andrew@andrew-gentoo-pc ~ % equery b /etc/alsa/conf.d * Searching for /etc/alsa/conf.d ... media-plugins/alsa-plugins-1.2.7.1-r1 (/etc/alsa/conf.d) media-sound/dcaenc-3-r1 (/etc/alsa/conf.d) media-video/pipewire-0.3.71-r2 (/etc/alsa/conf.d)I used to have a hdmi-audio splitter between the tv and the computer, this used to work. I replaced the splitter with a usb audio s/pdif device (which also works if the tv is off). Now that the tv is connected directly to the computer I have this garbled audio problem.
@AndrewAmmerlaan ALSA configuration seems fine and there is nothing suspicious in alsa-info. Have you tried with different resolution -- does that impact?
The error seems to definitely come from kernel (not ALSA plugins). To debug this, you could put following to /etc/modprobe.d/hda-debug.conf
options snd_hda_core dyndbg=+p options snd_hda_codec dyndbg=+p options snd_hda_codec_hdmi dyndbg=+p options snd_hda_intel dyndbg=+pAnd capture dmesg while running the speaker-test that ends to the error.
Have you tried with different resolution -- does that impact?
Video resolutions? I just tried some different display resolutions and refresh rates. None of them fix the issue though some of them change how the distortion sounds. I still only get front left though, front right is silent.
Here's the dmesg log with those debug options enabled: audio-debug.log With these options enabled no audible sound is produced at all. The speaker-test command returns with the same error as before.
I should mention this motherboard is a MSI z370-a pro which is a pci-e version 3 platform. So the link speed is slower then usual/expected (maybe that is somehow relevant). Here's the lspci info (note that
LnkStasays(downgraded):01:00.0 PCI bridge: Intel Corporation Device 4fa0 (rev 01) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 16 Region 0: Memory at 2c00000000 (64-bit, prefetchable) [size=8M] Bus: primary=01, secondary=02, subordinate=04, sec-latency=0 I/O behind bridge: [disabled] [32-bit] Memory behind bridge: de000000-df3fffff [size=20M] [32-bit] Prefetchable memory behind bridge: 2800000000-2bffffffff [size=16G] [32-bit] Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR- BridgeCtl: Parity- SERR+ NoISA- VGA+ VGA16+ MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+ Address: 0000000000000000 Data: 0000 Masking: 00000000 Pending: 00000000 Capabilities: [70] Express (v2) Upstream Port, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ SlotPowerLimit 75W DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+ RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr+ TransPend- LnkCap: Port #0, Speed 16GT/s, Width x16, ASPM L1, Exit Latency L1 <64us ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 8GT/s (downgraded), Width x16 TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP+ LTR+ 10BitTagComp+ 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS+ AtomicOpsCap: Routing+ 32bit+ 64bit+ 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ 10BitTagReq- OBFF Disabled, AtomicOpsCtl: EgressBlck- LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS+ LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance Preset/De-emphasis: -6dB de-emphasis, 0dB preshoot LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+ EqualizationPhase1+ EqualizationPhase2+ EqualizationPhase3+ LinkEqualizationRequest- Retimer- 2Retimers- CrosslinkRes: Upstream Port Capabilities: [100 v2] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+ AERCap: First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn- MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- HeaderLog: 00000000 00000000 00000000 00000000 Capabilities: [158 v1] Secondary PCI Express LnkCtl3: LnkEquIntrruptEn- PerformEqu- LaneErrStat: 0 Capabilities: [188 v1] Physical Layer 16.0 GT/s <?> Capabilities: [1b8 v1] Lane Margining at the Receiver <?> Capabilities: [20c v1] Latency Tolerance Reporting Max snoop latency: 71680ns Max no snoop latency: 71680ns Capabilities: [214 v1] L1 PM Substates L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+ PortCommonModeRestoreTime=10us PortTPowerOnTime=14us L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1- T_CommonMode=0us LTR1.2_Threshold=0ns L1SubCtl2: T_PwrOn=10us Capabilities: [230 v1] Vendor Specific Information: ID=0002 Rev=4 Len=100 <?> Capabilities: [330 v1] Vendor Specific Information: ID=0001 Rev=1 Len=038 <?> Capabilities: [368 v1] Data Link Feature <?> Kernel driver in use: pcieport 02:01.0 PCI bridge: Intel Corporation Device 4fa4 (prog-if 00 [Normal decode]) Subsystem: Intel Corporation Device 4fa4 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=02, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: [disabled] [16-bit] Memory behind bridge: de000000-df1fffff [size=18M] [32-bit] Prefetchable memory behind bridge: 2800000000-2bffffffff [size=16G] [32-bit] Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR- BridgeCtl: Parity- SERR+ NoISA- VGA+ VGA16+ MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Downstream Port (Slot-), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+ RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr- TransPend- LnkCap: Port #8, Speed 2.5GT/s, Width x1, ASPM L1, Exit Latency L1 <1us ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1 TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR+ 10BitTagComp+ 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- ARIFwd+ AtomicOpsCap: Routing- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ 10BitTagReq- OBFF Disabled, ARIFwd+ AtomicOpsCtl: EgressBlck- LnkCap2: Supported Link Speeds: 2.5GT/s, Crosslink- Retimer+ 2Retimers+ DRS- LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance Preset/De-emphasis: -6dB de-emphasis, 0dB preshoot LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- EqualizationPhase1- EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest- Retimer- 2Retimers- CrosslinkRes: unsupported Capabilities: [a0] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [7c] Subsystem: Intel Corporation Device 4fa4 Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+ AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn- MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- HeaderLog: 00000000 00000000 00000000 00000000 Capabilities: [148 v1] Access Control Services ACSCap: SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd+ EgressCtrl- DirectTrans+ ACSCtl: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans- Kernel driver in use: pcieport 02:04.0 PCI bridge: Intel Corporation Device 4fa4 (prog-if 00 [Normal decode]) Subsystem: Intel Corporation Device 0000 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=02, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: [disabled] [16-bit] Memory behind bridge: df300000-df3fffff [size=1M] [32-bit] Prefetchable memory behind bridge: [disabled] [64-bit] Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR- BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16+ MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Downstream Port (Slot-), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag+ RBE+ DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+ RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr- TransPend- LnkCap: Port #8, Speed 2.5GT/s, Width x1, ASPM L1, Exit Latency L1 <1us ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1 TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR+ 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- ARIFwd+ AtomicOpsCap: Routing- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ 10BitTagReq- OBFF Disabled, ARIFwd- AtomicOpsCtl: EgressBlck- LnkCap2: Supported Link Speeds: 2.5GT/s, Crosslink- Retimer+ 2Retimers+ DRS- LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance Preset/De-emphasis: -6dB de-emphasis, 0dB preshoot LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- EqualizationPhase1- EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest- Retimer- 2Retimers- CrosslinkRes: unsupported Capabilities: [a0] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [7c] Subsystem: Intel Corporation Device 0000 Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+ AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn- MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- HeaderLog: 00000000 00000000 00000000 00000000 Capabilities: [148 v1] Access Control Services ACSCap: SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd+ EgressCtrl- DirectTrans+ ACSCtl: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans- Kernel driver in use: pcieport 03:00.0 VGA compatible controller: Intel Corporation DG2 [Arc A770] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation DG2 [Arc A770] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin ? routed to IRQ 167 Region 0: Memory at de000000 (64-bit, non-prefetchable) [size=16M] Region 2: Memory at 2800000000 (64-bit, prefetchable) [size=16G] Expansion ROM at df000000 [disabled] [size=2M] Capabilities: [40] Vendor Specific Information: Len=0c <?> Capabilities: [70] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0W DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ FLReset- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq+ AuxPwr- TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1 TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Range B, TimeoutDis+ NROPrPrP- LTR+ 10BitTagComp+ 10BitTagReq+ OBFF Not Supported, ExtFmt+ EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- TPHComp- ExtTPHComp- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ 10BitTagReq- OBFF Disabled, AtomicOpsCtl: ReqEn- LnkCap2: Supported Link Speeds: 2.5GT/s, Crosslink- Retimer- 2Retimers- DRS- LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance Preset/De-emphasis: -6dB de-emphasis, 0dB preshoot LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- EqualizationPhase1- EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest- Retimer- 2Retimers- CrosslinkRes: unsupported Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit+ Address: 00000000fee007b8 Data: 0000 Masking: 00000000 Pending: 00000000 Capabilities: [d0] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Alternative Routing-ID Interpretation (ARI) ARICap: MFVC- ACS-, Next Function: 0 ARICtl: MFVC- ACS-, Function Group: 0 Capabilities: [420 v1] Physical Resizable BAR BAR 2: current size: 16GB, supported: 256MB 512MB 1GB 2GB 4GB 8GB 16GB Capabilities: [400 v1] Latency Tolerance Reporting Max snoop latency: 71680ns Max no snoop latency: 71680ns Kernel driver in use: i915 Kernel modules: i915 04:00.0 Audio device: Intel Corporation DG2 Audio Controller Subsystem: Intel Corporation DG2 Audio Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin ? routed to IRQ 172 Region 0: Memory at df300000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: 00000000fee00818 Data: 0000 Capabilities: [70] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 <64us ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0W DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag+ PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes, Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1 TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis+ NROPrPrP- LTR+ 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- TPHComp- ExtTPHComp- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ 10BitTagReq- OBFF Disabled, AtomicOpsCtl: ReqEn- LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance Preset/De-emphasis: -6dB de-emphasis, 0dB preshoot LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- EqualizationPhase1- EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest- Retimer- 2Retimers- CrosslinkRes: unsupported Capabilities: [100 v1] Latency Tolerance Reporting Max snoop latency: 71680ns Max no snoop latency: 71680ns Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intelAdditionally due to an unrelated issue the Arc GPU is not the boot gpu, instead posting etc is done of the iGPU. This effects the order in which the kernel initializes the audio and video devices. Not sure why that should matter but might as well mention it just in case.
@kaivehmanenintel If I connect the tv using a DisplayPort to HDMI adapter then front left plays without any distortion! Front right is still silent and still results in this error:
Write error: -77,File descriptor in bad state xrun_recovery failed: -77,File descriptor in bad state Transfer failed: File descriptor in bad stateIf I use the DisplayPort connection on the motherboard instead of the on on the GPU then I have the same problem (no distortion, front left works, front right is silent). The issue (or part of it at least) is therefore not specific to DG2. The CPU is a Intel i9-9900KS (Coffee Lake) with UHD Graphics 630.
@AndrewAmmerlaan The audio_debug.log suprisingly did not have any errors, which is really quite surprising. Is this now specific to your HKC-TV TV? If yo just switch another to another HDMI receiver, will the problem still happen? @suresh_kurmi Can you have someone look at the display setup in the logs. Given negotiated resolution affectes the artifacts, this hints at something with the display setup.
One audio side thing is to still try with silent streaming disabled ("options snd_hda_codec_hdmi enable_silent_stream=N" to some file under /etc/modprobe.d/ ). Pretty unlikely this will have effect, but pretty much the only audio-side thing to try out.
Is this now specific to your HKC-TV TV?
Very likely. As I said in my previous comments, it works if I put a HDMI audio splitter in between. The audio of the main display connected with DisplayPort also works (unplugging this does not help). Unfortunately I do not have a second HDMI display device available to test, but as I said this works fine under windows so there is not a hardware problem with the TV, cable or HDMI port.
One audio side thing is to still try with silent streaming disabled ("options snd_hda_codec_hdmi enable_silent_stream=N" to some file under /etc/modprobe.d/ ). Pretty unlikely this will have effect, but pretty much the only audio-side thing to try out.
Unfortunately this does not fix my problem. I had a different issue with silent_stream=Y that was also unreproducible on Intel's side, this however was worked around since it also effected others: #8307
Can you have someone look at the display setup in the logs. Given negotiated resolution affectes the artifacts, this hints at something with the display setup.
If I run speaker-test in a tty before logging in (i.e. SDDM is running in an X server) there is no audio corruption. Once I log in and start the KDE Plasma wayland session the audio is messed up again. Perhaps this is somehow specific to wayland/kwin, or perhaps it is related to pipewire not running when I run speaker-test in a tty?
Even in the tty I still only have front left though, front right remains silent. This is for me a bigger issue since the audio corruption I can work around with the DisplayPort to HDMI adapter.
The audio_debug.log suprisingly did not have any errors, which is really quite surprising.
@kaivehmanenintel I just realized that the ordering of the audio devices sometimes changes, specifically rebooting flips the order of the internal audio card and the one on the GPU. Last time I tested with those debug flags you mentioned I didn't actually hear any audio from the same speaker-test command, probably the reason was because I was running the wrong speaker-test command since the order of the devices had changed.
I tried this again, taking special care that the ids in the speaker-test command actually matched the output of alsa-info. This time I hear (ungarbled) front left, but again no front right. Here's the new log: audio-debug_2_.log
Compared to the previous log it shows some of these lines which to me look suspicious:
[ 120.710452] snd_hda_codec_hdmi hdaudioC0D2: invalid CONNECT_LIST verb 5[1]:0 [ 120.711138] snd_hda_codec_hdmi hdaudioC0D2: invalid CONNECT_LIST verb 5[1]:0 [ 120.711408] snd_hda_codec_hdmi hdaudioC0D2: invalid CONNECT_LIST verb 6[1]:0 [ 120.712098] snd_hda_codec_hdmi hdaudioC0D2: invalid CONNECT_LIST verb 6[1]:0 [ 120.712347] snd_hda_codec_hdmi hdaudioC0D2: invalid CONNECT_LIST verb 7[1]:0 [ 120.713036] snd_hda_codec_hdmi hdaudioC0D2: invalid CONNECT_LIST verb 7[1]:0 [ 120.716126] snd_hda_codec_hdmi hdaudioC1D2: invalid CONNECT_LIST verb 6[1]:0 [ 120.716814] snd_hda_codec_hdmi hdaudioC1D2: invalid CONNECT_LIST verb 6[1]:0 [ 120.719002] snd_hda_codec_hdmi hdaudioC1D2: invalid CONNECT_LIST verb a[1]:0 [ 120.719688] snd_hda_codec_hdmi hdaudioC1D2: invalid CONNECT_LIST verb a[1]:0 [ 120.719938] snd_hda_codec_hdmi hdaudioC1D2: invalid CONNECT_LIST verb b[1]:0 [ 120.720626] snd_hda_codec_hdmi hdaudioC1D2: invalid CONNECT_LIST verb b[1]:0 [ 120.720876] snd_hda_codec_hdmi hdaudioC1D2: invalid CONNECT_LIST verb c[1]:0 [ 120.721564] snd_hda_codec_hdmi hdaudioC1D2: invalid CONNECT_LIST verb c[1]:0 [ 120.721814] snd_hda_codec_hdmi hdaudioC1D2: invalid CONNECT_LIST verb d[1]:0 [ 120.722501] snd_hda_codec_hdmi hdaudioC1D2: invalid CONNECT_LIST verb d[1]:0 [ 120.722751] snd_hda_codec_hdmi hdaudioC1D2: invalid CONNECT_LIST verb e[1]:0 [ 120.723439] snd_hda_codec_hdmi hdaudioC1D2: invalid CONNECT_LIST verb e[1]:0 [ 120.723689] snd_hda_codec_hdmi hdaudioC1D2: invalid CONNECT_LIST verb f[1]:0 [ 120.724376] snd_hda_codec_hdmi hdaudioC1D2: invalid CONNECT_LIST verb f[1]:0 [ 120.726773] snd_hda_codec_hdmi hdaudioC1D2: invalid CONNECT_LIST verb 6[1]:0 [ 120.729273] snd_hda_codec_hdmi hdaudioC1D2: invalid CONNECT_LIST verb a[1]:0 [ 120.730023] snd_hda_codec_hdmi hdaudioC1D2: invalid CONNECT_LIST verb b[1]:0 [ 120.730773] snd_hda_codec_hdmi hdaudioC1D2: invalid CONNECT_LIST verb c[1]:0 [ 120.731523] snd_hda_codec_hdmi hdaudioC1D2: invalid CONNECT_LIST verb d[1]:0 [ 120.732273] snd_hda_codec_hdmi hdaudioC1D2: invalid CONNECT_LIST verb e[1]:0 [ 120.733023] snd_hda_codec_hdmi hdaudioC1D2: invalid CONNECT_LIST verb f[1]:100:The CONNECT_LIST is likely from pipewire (or some other user-space entity) going through the ALSA sysfs entries and this will result in invalid CONNECT_LIST debug logs.
The actual playback part seems completely fine: [ 275.332682] snd_hda_codec_hdmi hdaudioC1D2: hdmi_pin_hbr_setup: NID=0x4, pinctl=0x40 [ 275.332825] snd_hda_codec_hdmi hdaudioC1D2: hda_codec_setup_stream: NID=0x3, stream=0x1, channel=0, format=0x11 [ 280.802897] snd_hda_codec_hdmi hdaudioC1D2: hda_codec_cleanup_stream: NID=0x3
... this looks completely fine for 48khz 16bit stereo playback. This is likely some interoperability issue with your TV. When you launch KDE desktop, the display resolution changes, so it's a new situation in terms of sending audio data over HDMI.
@mgolani Can you please share the audio bw calculation patches with some extra logs to find out if we are running out of bandwidth?
Please find attached debug patch, This patch checks and print debug logs for required audio bandwidth and available blank bandwidth for current mode. Based on it calculate possible combination of channel and frequency. Please try on latest drm-tip, try with different resolution and please share logs.
0001-Debug-patch-to-check-required-BW.patch
Thanks, Mitul
Edited by Mitul GolaniPlease try on latest drm-tip, try with different resolution and please share logs.
I pulled drm-tip again, applied the patch and recompiled. Here's the new log: audio-debug_3_.log
I cycled through the available display resolutions, starting low and going higher. There are a couple where the distortion is noticeably less, there is no clear pattern unfortunately. Even when the distortion is less the audio quality is far from what I would consider decent, and again there is only audio from front left.
I am able to see,
i915_debug intel_hdmi_audio_compute_config: Matching Config Found!!
Required Audio BW: 24576000 Available Blank BW: 28800000 Max freq Supported: 96000 Max channel supported: 8could not find below log line in your attached debug log file,
pr_err("\n\ni915_debug %s: \nsad_count: %d \nmask= %x crtc_state->audio.max_freq: %d\nsink supported channels: %d crtc_state->audio.max_channel: %d \nShould prune this SAD ?? :: %s \nsad[%d][0]: %d sad[%d][1]: %d \n", func, drm_eld_sad_count(eld), mask, crtc_state->audio.max_frequency, sad_to_channels(temp_sad), crtc_state->audio.max_channel, crtc_state->audio.max_channel <= sad_to_channels(temp_sad)? "yes":"not applicable, as sink support is already lesser", index, temp_sad[0] & 0x7, index,temp_sad[1] & 0xf);
As above log help to check supported sink rate and supported channel by sink. Can you please help and check if we get this log by increasing log level ?
Thanks Mitul
Edited by Mitul GolaniCan you please help and check if we get this log by increasing log level ?
Can you elaborate on how I do that? I already have these debug options that @kaivehmanenintel mentioned in modprobe.d:
options snd_hda_core dyndbg=+p options snd_hda_codec dyndbg=+p options snd_hda_codec_hdmi dyndbg=+p options snd_hda_intel dyndbg=+p
Thanks!
I'm not using grub (systemd-boot with uki's) but I applied the kernel parameters you mentioned, here's the new (longer) log: audio-debug_4_.log
Possibly related: It is not possible to use pavucontrol advanced settings to enable the E-AC3 format for the tv (even though it is listed as supported). I can click the checkbox but
pactlshows that the setting is not being applied and after restarting pavucontrol this is also reflected there. The settings for AC3 and other formats do work, but when using passthrough still no sound is produced. E-AC3 can be enabled as a supported format on the other sinks.If I put this audio-splitter that I mentioned earlier back between the computer and the tv all audio works as it should. The ELD info changes to:
monitor_present 1 eld_valid 1 codec_pin_nid 0x4 codec_dev_id 0x0 codec_cvt_nid 0x3 monitor_name HKC-TV connection_type DisplayPort eld_version [0x2] CEA-861D or below edid_version [0x3] CEA-861-B, C or D manufacture_id 0x6321 product_id 0x0 port_id 0x0 support_hdcp 0 support_ai 1 audio_sync_delay 0 speakers [0xf] FL/FR LFE FC RL/RR sad_count 4 sad0_coding_type [0x1] LPCM sad0_channels 2 sad0_rates [0x1ee0] 32000 44100 48000 88200 96000 176400 192000 sad0_bits [0xe0000] 16 20 24 sad1_coding_type [0x1] LPCM sad1_channels 6 sad1_rates [0x1ee0] 32000 44100 48000 88200 96000 176400 192000 sad1_bits [0xe0000] 16 20 24 sad2_coding_type [0x2] AC-3 sad2_channels 6 sad2_rates [0x1ee0] 32000 44100 48000 88200 96000 176400 192000 sad2_max_bitrate 640000 sad3_coding_type [0x7] DTS sad3_channels 6 sad3_rates [0x1ee0] 32000 44100 48000 88200 96000 176400 192000 sad3_max_bitrate 1536000Note that E-AC3 is no longer listed as a supported format, and DTS is added. This makes sense since the audio-splitter has an optical output which of course only supports PCM, AC3 and DTS. This reduces the maximum number of channels from 8 to 6. Other differences are: higher rates (88200 to 192000) and bit depth (24) are allowed and
support_ai(whatever that means) is now enabled.@kaivehmanenintel @mgolani I suspect one of these differences is the reason why it works with audio-splitter but not without. Is there anyway I can control or manipulate the ELD info to see which property (if any) is responsible?
Hi @AndrewAmmerlaan,
There are few ways we can go about it.
-
We can dump the "working" edid into a bin file.
cat /sys/class/drm/<output-name>/edid > hkc-tv-edid.bin e.g. cat /sys/class/drm/card0-DP-3/edid > hkc-tv-edid.binIn the last log shared, the TV was connected to DP-3. You can confirm this by checking the output of
cat /sys/kernel/debug/dri/<device number>/i915_display_infoPlace the bin file in
/usr/lib/firmware/edidThen you can force the connector to use the edid by adding a kernel command line parameter
drm.edid_firmware=<connector-name>:edid/hkc-tv-edid.bin e.g. drm.edid_firmware=DP-3:edid/hkc-tv-edid.bin -
You can also apply the following patch to disable E-AC3
0001-Testpatch-Prune-E-AC3.patch
- We can use method 1 to manually change the SAD (Short Audio Descriptor) bytes in the edid and then overriding the edid but this would be bit gnarly.
Regarding your query of the monitor being connected to a DP port even though you are connecting it to a HDMI port. It seems your device has DP dual mode port(DP++). This should explain the observation as DP in dual mode can output HDMI signals.
[ 2.302493] i915 0000:00:02.0: [drm:intel_bios_init [i915]] Port B VBT info: CRT:0 DVI:1 HDMI:1 DP:1 eDP:0 DSI:0 DP++:1 LSPCON:0 USB-Type-C:0 TBT:0 DSC:0 [ 2.302604] i915 0000:00:02.0: [drm:intel_bios_init [i915]] Port B VBT HDMI level shift: 10However, this means the patch shared by Mitul won't be of much help as it is for native HDMI ports. We are currently working on a similar patch for the DP path. That should be shared with you soon.
In the meantime, please check if the steps above helps. Also, please share the edid file once you retrieve it.
Edited by Chaitanya Kumar Borah-
@ckborah Thanks for the extensive information!
- If I force apply the EDID of the splitter audio works as it should, without the splitter actually being connected!
- If I connect the splitter again, and then force apply the EDID of the TV (without splitter) the issue comes back.
So the issue is definitely somehow related to the EDID of the TV.
Your patch successfully disables E-AC3 (verified in
/proc/asound/card2/eld\#2.0) but unfortunately does not fix the issue. So the issue is most likely not related to E-AC3 and the problem I was having with enabling this is probably a separate issue (maybe in pipewire).Here are both EDID files:
By the way, I also tested this with a laptop (Dynabook Satellite Pro L50-G-188 with i7-10510U iGPU) and found the same problem there. The distortion on front left sounds different though.
@AndrewAmmerlaan Thank you for the feedback. I am trying to find a comparable set up to reproduce the issue. Haven't been successful yet. I will keep looking. Do you see any difference in parameters between working and non-working scenario?
speaker-test -c2 -twav -Dhw:1,3 -l 10 speaker-test 1.2.9 Playback device is hw:1,3 Stream parameters are 48000Hz, S16_LE, 2 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 64 to 1048576 Period size range from 32 to 524288 Using max buffer size 1048576 Periods = 4 was set period_size = 262144 was set buffer_size = 1048576@kaivehmanenintel Let us know if you see anything unusual in the edid that can cause us some problems.
Do you see any difference in parameters between working and non-working scenario?
Actually, the plot is thickening, the output from speaker-test is identical. And..... I somehow even get the same error:
Without EDID override:
andrew@andrew-gentoo-pc ~ % speaker-test -c2 -twav -Dhw:1,3 -l 10 speaker-test 1.2.9 Playback device is hw:1,3 Stream parameters are 48000Hz, S16_LE, 2 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 64 to 1048576 Period size range from 32 to 524288 Using max buffer size 1048576 Periods = 4 was set period_size = 262144 was set buffer_size = 1048576 0 - Front Left 1 - Front Right Write error: -77,File descriptor in bad state xrun_recovery failed: -77,File descriptor in bad state Transfer failed: File descriptor in bad stateWith EDID override:
andrew@andrew-gentoo-pc ~ % speaker-test -c2 -twav -Dhw:2,3 -l 10 speaker-test 1.2.9 Playback device is hw:2,3 Stream parameters are 48000Hz, S16_LE, 2 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 64 to 1048576 Period size range from 32 to 524288 Using max buffer size 1048576 Periods = 4 was set period_size = 262144 was set buffer_size = 1048576 0 - Front Left 1 - Front Right Write error: -77,File descriptor in bad state xrun_recovery failed: -77,File descriptor in bad state Transfer failed: File descriptor in bad state andrew@andrew-gentoo-pc ~ % speaker-test -c2 -twav -Dhw:2,3 speaker-test -c2 -twav -Dhdmi:CARD=PCH,DEV=0 -l 10 speaker-test 1.2.9 Playback device is hdmi:CARD=PCH,DEV=0 Stream parameters are 48000Hz, S16_LE, 2 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 64 to 1048576 Period size range from 32 to 524288 Using max buffer size 1048576 Periods = 4 was set period_size = 262144 was set buffer_size = 1048576 0 - Front Left 1 - Front Right Write error: -77,File descriptor in bad state xrun_recovery failed: -77,File descriptor in bad state Transfer failed: File descriptor in bad stateAnd with speaker-test there is again no front right (front left sounds fine though, no distortion). Yet somehow if I use the KDE Plasma speaker testing utility (which was the one I was using before) everything works just fine (provided I override the EDID). I can also play regular audio to the TV just fine if I override the EDID.
Yet somehow speaker-test still throws this error. Speaker-test must be doing something slightly different then the KDE Plasma speaker testing utility, though they sound the same. Overriding the EDID "fixes" things in the sense that it works for regular desktop things, but speaker-test exposes that there is still some underlying problem. Could it be that speaker-test somehow ignores the EDID override?
I am trying to find a comparable set up to reproduce the issue. Haven't been successful yet.
Maybe using the "broken" EDID on some similar display is enough to break the audio? I have the same issue with 9th gen iGPU, 10th gen iGPU and DG2 so I suspect the model of (i)GPU is not a factor.
Edited by Nowa Ammerlaan
I've been playing with this for a bit and I can somehow make this work with the
--bufferoption:andrew@andrew-gentoo-pc ~ % speaker-test -c2 -twav -Dhw:2,3 -l10 -b0 speaker-test 1.2.9 Playback device is hw:2,3 Stream parameters are 48000Hz, S16_LE, 2 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 64 to 1048576 Period size range from 32 to 524288 Using max buffer size 1048576 Periods = 4 was set period_size = 262144 was set buffer_size = 1048576 0 - Front Left 1 - Front Right Write error: -77,File descriptor in bad state xrun_recovery failed: -77,File descriptor in bad state Transfer failed: File descriptor in bad state andrew@andrew-gentoo-pc ~ % speaker-test -c2 -twav -Dhw:2,3 -l10 -b1 speaker-test 1.2.9 Playback device is hw:2,3 Stream parameters are 48000Hz, S16_LE, 2 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 64 to 1048576 Period size range from 32 to 524288 Requested buffer time 1 us Periods = 4 was set period_size = 32 was set buffer_size = 64 0 - Front Left 1 - Front Right Time per period = 3.498292 0 - Front Left 1 - Front Right Time per period = 3.909544 0 - Front Left 1 - Front Right Time per period = 3.295454 0 - Front Left 1 - Front Right Time per period = 3.430737 0 - Front Left Write error: -32,Broken pipe 1 - Front Right Time per period = 3.858279 0 - Front Left 1 - Front Right Time per period = 3.498950 0 - Front Left 1 - Front Right Write error: -32,Broken pipe Time per period = 3.678546 0 - Front Left 1 - Front Right Time per period = 3.545487 0 - Front Left 1 - Front Right Time per period = 3.591726 0 - Front Left 1 - Front Right Time per period = 3.460506Even a value as tiny as 1us is enough to 'fix' the problem, however with tiny values there is some weird noise when it switches from front left to front right, this goes away for values higher then 10ms (with EDID override).
If I don't override the EDID I can still get rid of the error with
-b1. However this weird switching noise I mentioned is worse, again values above 10ms make this weird noise go away. "Normal" desktop audio is still messed up if I don't override the EDID.@ckborah @kaivehmanenintel I think the root of my problem here is a too small buffer. That it works with the EDID override is still a bit confusing to me, maybe the other EDID somehow makes pipewire/alsa/kernel use a larger buffer size? Is there any information on buffers in the EDID?
[EDIT] Now it becomes even more interesting. Note that if I don't specify the
--bufferparameter or set it to zero, I get:Using max buffer size 1048576Now if I explicitly set the buffer size to the value speaker-test claims it is using:
andrew@andrew-gentoo-pc ~ % speaker-test -c2 -twav -Dhw:1,3 -l1 -b1048576 speaker-test 1.2.9 Playback device is hw:1,3 Stream parameters are 48000Hz, S16_LE, 2 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 64 to 1048576 Period size range from 32 to 524288 Requested buffer time 1000000 us Periods = 4 was set period_size = 12000 was set buffer_size = 48000 0 - Front Left 1 - Front Right Time per period = 2.250610Note that now we have
Requested buffer time 1000000 uswhich is less then what I set it to on the command line (what it was claiming to be the maximum).Even if I set the buffer to
1000001speaker-test actually tells me it is using1000000. So clearly1000000is the maximum! Yet, if I don't specify this parameter speaker-test uses a larger value (1048576). So probably the problem is that the buffer is too large, not too small. And that something somewhere is using a buffer larger then the maximum if it is not explicitly told to use a different size.Edited by Nowa AmmerlaanExplicitly setting
--periodto values lower then 740031 also makes theWrite error: -77go away:andrew@andrew-gentoo-pc ~ % speaker-test -c2 -twav -Dplughw:CARD=PCH,DEV=3 -l1 -p 740031 speaker-test 1.2.9 Playback device is plughw:CARD=PCH,DEV=3 Stream parameters are 48000Hz, S16_LE, 2 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 64 to 1048576 Period size range from 32 to 524288 Requested period time 740031 us Periods = 4 was set period_size = 35522 was set buffer_size = 142088 0 - Front Left 1 - Front Right Write error: -77,File descriptor in bad state xrun_recovery failed: -77,File descriptor in bad state Transfer failed: File descriptor in bad state andrew@andrew-gentoo-pc ~ % speaker-test -c2 -twav -Dplughw:CARD=PCH,DEV=3 -l1 -p 740030 speaker-test 1.2.9 Playback device is plughw:CARD=PCH,DEV=3 Stream parameters are 48000Hz, S16_LE, 2 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 64 to 1048576 Period size range from 32 to 524288 Requested period time 740030 us Periods = 4 was set period_size = 35521 was set buffer_size = 142084 0 - Front Left 1 - Front Right Time per period = 0.743841@kaivehmanenintel Does these observations point to something?
Maybe using the "broken" EDID on some similar display is enough to break the audio? I have the same issue with 9th gen iGPU, 10th gen iGPU and DG2 so I suspect the model of (i)GPU is not a factor.
That is the idea, I haven't found a similar display yet. I will keep you updated.
Note that now we have
Requested buffer time 1000000 uswhich is less then what I set it to on the command line (what it was claiming to be the maximum).Important to distinguish here between buffer time and buffer size.
Using max buffer size 1048576Requested buffer time 1000000 usI tried reproducing this issue in some monitors and a tv that we have. I can never reproduce the original issue.
Write error: -77,File descriptor in bad state xrun_recovery failed: -77,File descriptor in bad state Transfer failed: File descriptor in bad stateHowever, with the default parameters[1], parts of the audio prompt are muted. Mostly the word "Front". I am not sure if the issues are related. However, the parameters for which @AndrewAmmerlaan's problem gets healed also seem to work on the problem I find. @kaivehmanenintel Your inputs?
[1]
speaker-test -Dplughw:CARD=PCH,DEV=3 -twav -c2The underlying issue preventing
speaker-testfrom explicitly using the maximum--buffertime has been fixed: https://github.com/alsa-project/alsa-utils/issues/224@ckborah as you pointed out I got the units confused here. According to @perexg over at the alsa-utils github a maximum buffer size of 1048576 means a maximum buffer time of 1048576 / 48000 seconds. After applying the patch I can successfully set this buffer time, and as expected this makes
speaker-testerror out again:andrew@andrew-gentoo-pc alsa-utils % speaker-test -c2 -twav -Dplughw:CARD=PCH,DEV=7 --buffer 21845333 speaker-test 1.2.9 Playback device is plughw:CARD=PCH,DEV=7 Stream parameters are 48000Hz, S16_LE, 2 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 64 to 1048576 Period size range from 32 to 524288 Requested buffer time 21845333 us Periods = 4 was set period_size = 262144 was set buffer_size = 1048576 0 - Front Left 1 - Front Right Write error: -77,File descriptor in bad state xrun_recovery failed: -77,File descriptor in bad state Transfer failed: File descriptor in bad stateUsing trial and error I have determined that the maximum buffer time for which speaker-test works is 2960093 us:
andrew@andrew-gentoo-pc alsa-utils % speaker-test -c2 -twav -Dplughw:CARD=PCH,DEV=7 --buffer 2960093 speaker-test 1.2.9 Playback device is plughw:CARD=PCH,DEV=7 Stream parameters are 48000Hz, S16_LE, 2 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 64 to 1048576 Period size range from 32 to 524288 Requested buffer time 2960093 us Periods = 4 was set period_size = 35521 was set buffer_size = 142084 0 - Front Left 1 - Front Right Time per period = 0.743704If the buffer time is 1 us larger,
speaker-testfails with error -77 again:andrew@andrew-gentoo-pc alsa-utils % speaker-test -c2 -twav -Dplughw:CARD=PCH,DEV=7 --buffer 2960094 speaker-test 1.2.9 Playback device is plughw:CARD=PCH,DEV=7 Stream parameters are 48000Hz, S16_LE, 2 channels WAV file(s) Rate set to 48000Hz (requested 48000Hz) Buffer size range from 64 to 1048576 Period size range from 32 to 524288 Requested buffer time 2960094 us Periods = 4 was set period_size = 28417 was set buffer_size = 142085 0 - Front Left 1 - Front Right Write error: -77,File descriptor in bad state xrun_recovery failed: -77,File descriptor in bad state Transfer failed: File descriptor in bad stateAs I understand it, the maximum buffer size (1048576) is communicated by the driver. What I would like to try is to instruct/patch the driver to communicate a lower maximum buffer size to see if this fixes my issue without overriding the TV's EDID. But I'm not sure how to do this, could you give me some pointers?
[EDIT] According to this article, on Windows 10+ the driver is also responsible for communicating the buffer constraints. I would be curious to know what these constraints are for the Intel driver on Windows, perhaps these are different on the different platforms, and this might be the root cause of why audio playback works fine for me on Windows but fails on Linux.
Edited by Nowa Ammerlaan@ckborah @kaivehmanenintel Any pointers on the above query.
I compared the edids again and it doesn't help that the edid that is working for you adds things (like higher sampling rates). So there is nothing in the TVs edid that we can try removing. I will try looking in other directions.
In the mean time, @kaivehmanenintel anything we can do here from audio driver's perspective? What really causes the error code -77 (EBADFD)?
@mgolani May be we can share a patch to check what is happening with the bandwidth?
