#867548 playback to HDMI monitor stutters / pauses

Package:
pulseaudio
Source:
pulseaudio
Description:
PulseAudio sound server
Submitter:
Daniel Pocock
Date:
2021-07-18 00:51:03 UTC
Severity:
important
Tags:
#867548#5
Date:
2017-07-07 08:53:07 UTC
From:
To:
When playing audio through the HDMI monitor, I've noticed it
stutters/pauses every few seconds, very briefly, less than a second each
time.  It is very irritating to listen to.

In the middle of playback, I can open the GNOME settings panel for sound
and switch the output to another device (e.g. my USB sound card
connected to an amp with an optical cable) and it works fine.  As soon
as I switch back to the HDMI output the problem comes back.
#867548#10
Date:
2017-07-07 16:07:53 UTC
From:
To:
Control: tags -1 moreinfo

Could you attach a verbose log please?

https://wiki.ubuntu.com/PulseAudio/Log
#867548#17
Date:
2017-07-07 17:05:57 UTC
From:
To:

After following those instructions, I don't hear any playback at all

I notice the killall command doesn't actually kill every pulseaudio
process, there is a process running as user Debian-gdm.  Do I need to do
something to stop that too before logging will work?

Regards,

Daniel
#867548#22
Date:
2017-07-07 17:35:39 UTC
From:
To:
each
sound


After following those instructions, I don't hear any playback at all



Strange. Any errors in the logfile?


I notice the killall command doesn't actually kill every pulseaudio
process, there is a process running as user Debian-gdm.  Do I need to do
something to stop that too before logging will work?



No, that is not necessary.
#867548#27
Date:
2018-02-15 09:26:44 UTC
From:
To:
Laba diena,


Noriu Jus informuoti apie šių metų pasikeitimą dėl atnaujintos visos Lietuvos įmonių bazės 2018 metų sausio vidurio.
Visi juridiniai asmenys pateikti bazėje yra veikiantys, realiai vykdantys veiklą, turintys įdarbintų darbuotojų. Duomenys pagal Sodrą, Registrų centrą.

Bazėje nurodoma ir apyvarta, darbuotojų atlyginimai, darbuotojų skaičius, transporto skaičius ir daug kitų duomenų, kuriuos matysite pavyzdyje.

Duomenis galima filtruoti pagal veiklas, miestus ir kitus duomenis.


Šią bazę verta turėti visoms įmonėms. Pateiksiu priežastis:

1) Kontaktai pateikti bazėje direktorių ir kitų atsakingų asmenų, didelė tikimybė Jums surasti naujų klientų, partnerių, tiekėjų, kai tiesiogiai bendrausite su direktoriais, komercijos vadovais.

2) Konkurentų analizavimas, tiekėjų atsirinkimas pagal Jums reikalingus kriterijus, galite atsifiltruoti pagal įmonės dydį, bazėje nurodoma kiek įmonės skolingos Sodrai.

3) Lengva, greita ir patogu dirbti su šia baze, elektroninius pašto adresus galite importuoti į elektroninių laiškų siuntimo programas ar sistemas iš kurių siunčiate elektroninius laiškus.
Taip pat galite importuoti mobiliųjų telefonų numerius į SMS siuntimo programas.


Išsirinkite iš "Veiklų sąrašo" veiklas kurių Jums reikia.
( Sąrašas prisegtas laiške excel faile )

Parašykite, kurias veiklas išsirinkote
ir atsiųsime pavyzdį ir pasiūlymą su sąlygomis įmonių bazei įsigyti



Pagarbiai,
Tadas Giedraitis
Tel. nr. +37067881041
#867548#32
Date:
2018-02-15 09:26:44 UTC
From:
To:
Laba diena,


Noriu Jus informuoti apie šių metų pasikeitimą dėl atnaujintos visos Lietuvos įmonių bazės 2018 metų sausio vidurio.
Visi juridiniai asmenys pateikti bazėje yra veikiantys, realiai vykdantys veiklą, turintys įdarbintų darbuotojų. Duomenys pagal Sodrą, Registrų centrą.

Bazėje nurodoma ir apyvarta, darbuotojų atlyginimai, darbuotojų skaičius, transporto skaičius ir daug kitų duomenų, kuriuos matysite pavyzdyje.

Duomenis galima filtruoti pagal veiklas, miestus ir kitus duomenis.


Šią bazę verta turėti visoms įmonėms. Pateiksiu priežastis:

1) Kontaktai pateikti bazėje direktorių ir kitų atsakingų asmenų, didelė tikimybė Jums surasti naujų klientų, partnerių, tiekėjų, kai tiesiogiai bendrausite su direktoriais, komercijos vadovais.

2) Konkurentų analizavimas, tiekėjų atsirinkimas pagal Jums reikalingus kriterijus, galite atsifiltruoti pagal įmonės dydį, bazėje nurodoma kiek įmonės skolingos Sodrai.

3) Lengva, greita ir patogu dirbti su šia baze, elektroninius pašto adresus galite importuoti į elektroninių laiškų siuntimo programas ar sistemas iš kurių siunčiate elektroninius laiškus.
Taip pat galite importuoti mobiliųjų telefonų numerius į SMS siuntimo programas.


Išsirinkite iš "Veiklų sąrašo" veiklas kurių Jums reikia.
( Sąrašas prisegtas laiške excel faile )

Parašykite, kurias veiklas išsirinkote
ir atsiųsime pavyzdį ir pasiūlymą su sąlygomis įmonių bazei įsigyti



Pagarbiai,
Tadas Giedraitis
Tel. nr. +37067881041
#867548#37
Date:
2018-12-10 15:12:17 UTC
From:
To:
I would like to confirm this bug exists on several machines tested with
various AMD video card HDMI audio devices in the GCN 1.0 hardware era.
Glitches do not appear to be present using onboard Intel HDMI out. I
have an Nvidia card I can test if someone needs it, but the issue
appears to be AMD specific. Important to note is on the same test
machines loaded with kernel firmware directly from kernel.org (as the
Debian firmware packages are missing modules):

CentOS 7.5 DOES exhibit this same error
Ubuntu 16.04 LTS DOES exhibit this same error
Ubuntu 18.04 LTS DOES NOT exhibit the same errors, playback is error free.

I have four test machines not being used. All HDMI cables and hardware
has been confirmed known working good with Ubuntu 18.04 and Windows 10
Pro for glitch free playback.

There is something "fixed" in Ubuntu 18.04 LTS. I would be happy to test
several hardware configurations to find the root of the problem
(pulseaudio, kernel config, kernel compile, driver, etc.) so we can see
if this can be patched. I've tried several fixes on various wikis (arch,
ubuntu, debian) to no avail.

Thanks.
#867548#42
Date:
2018-12-11 14:55:55 UTC
From:
To:
Also for what it's worth, hw_parms output during playback on the same
device:

On Debian 9 / CentOS 7.5 / Ubuntu 16.04:
	access: MMAP_INTERLEAVED
	format: S16_LE
	subformat: STD
	channels: 2
	rate: 48000 (48000/1)
	period_size: 44096
	buffer_size: 88192

On Ubuntu 18.04:
	access: MMAP_INTERLEAVED
	format: S32_LE
	subformat: STD
	channels: 2
	rate: 48000 (48000/1)
	period_size: 1024
	buffer_size: 16384

I don't know why but...this is the only discernable difference I've been
able to find in all my testing. I've been unable to manually set format,
period_size, or buffer-size parameters in Debian's pulseaudio configuration
files (I am pretty sure its just user error).
#867548#47
Date:
2021-07-02 04:08:25 UTC
From:
To:
Since update  from  Buster to  Bullseye on  hard  disc  and  on  live  USB
  boot  when  using Built-in Audio Digital Stereo(HDMI 2) on  playback for
Youtube  and  other   video streams I  have   noticed variable skipping of
audio and  video ,  audio  out of   sync, video racing   at   fast  forward
pace.  This    does  not   happen    when   playback  is  on Built-in
Audio Analog Stereo.  However  I   would  like  audio  to  come  through
the  HDMI  device [TV].  Using  the  left over old  Debian 10 kernel on
the   Bullseye   system still  shows   same   problem.  Ubuntu 20.04  on
the   same   system has  no  issues.  What  is  the  regression  from
Debian 10  to   11?  I note  the  configuration Analogue  Stereo Duplex
is   unavailable in  the  Bullseye  version  but  available  and  selected
in Buster. Changing  to  and  from  this  in Buster causes no problems  in
playback
Your  bleeding user
Bryan Cebuliak

On Tue, 11 Dec 2018 09:55:55 -0500 "Mike Fuller" <fuller.michael.d@gmail.com>
wrote:.
configuration
#867548#52
Date:
2021-07-02 06:30:21 UTC
From:
To:
This Haswell related bug sounds very similar and possibly relevant to my
Haswell machine:
https://bugzilla.kernel.org/show_bug.cgi?id=60769
https://bugs.freedesktop.org/show_bug.cgi?id=94804

"...
Alexander E. Patrakov 2013-10-08 09:55:09 UTC

I have not tried your patch, but found that intel_iommu=on,igfx_off
snd_hda_intel.align_buffer_size=1 fixes the problem. Should I still
try the patch?..."
..."

and
"...

Alexander E. Patrakov 2016-04-03 06:44:56 UTC
Haswell HDMI audio users are affected by a longstanding kernel IOMMU bug:
https://bugzilla.kernel.org/show_bug.cgi?id=60769 . To make sure that your
report is not a duplicate, please add the following kernel command line
option and reboot: intel_iommu=on,igfx_off If that alone doesn't help,
please try: intel_iommu=on,igfx_off snd_hda_intel.align_buffer_size=1

On Fri, 2 Jul 2021 at 14:08, Bryan Cebuliak <bryan.cebuliak@gmail.com> wrote:
#867548#57
Date:
2021-07-02 07:11:23 UTC
From:
To:
Yep at least  for now  it  works  nicely.
On grub boot I did  the  e  thing  and   added
intel_iommu=on,igfx_off
to  the  end  of  the  line  starting with linux

So  how   does  that  get   fixed on  the   Bullseye  update  and  the
live/install image?

On Fri, 2 Jul 2021 at 16:30, Bryan Cebuliak <bryan.cebuliak@gmail.com> wrote:
#867548#67
Date:
2021-07-03 01:25:27 UTC
From:
To:
more  possibly relevant IOMMU video audio  and  passthrough issue links:
Easy ACS kernel patch guide for Ubuntu 20.04
https://www.youtube.com/watch?v=JBEzshbGPhQ

https://forum.level1techs.com/t/intel-graphics-hdmi-audio-fails-after-enabling-intel-iommu-on/168827

kvm-gpu-passthrough-on-debian-buster.md
https://gist.github.com/davesilva/445276f9157e7cb3a4f6ed2fe852b340
#867548#72
Date:
2021-07-03 02:22:00 UTC
From:
To:
If  igfx_off is  default, how / why is  it  on?
from
https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html
"...

intel_iommu=    [DMAR] Intel IOMMU driver (DMAR) option
                on
                        Enable intel iommu driver.
                off
                        Disable intel iommu driver.
                igfx_off [Default Off]
                        By default, gfx is mapped as normal device. If a gfx
                        device has a dedicated DMAR unit, the DMAR unit is
                        bypassed by not enabling DMAR with this option. In
                        this case, gfx device will use physical address for
                        DMA.
...
#867548#77
Date:
2021-07-03 07:28:27 UTC
From:
To:
bullseye with intel_iommu=on,igfx_off:
sudo dmesg | grep -e DMAR -e IOMMU
[    0.007516] ACPI: DMAR 0x00000000D8FFEAE8 0000B8 (v01 INTEL  HSW
 00000001 INTL 00000001)
[    0.007531] ACPI: Reserving DMAR table memory at [mem
0xd8ffeae8-0xd8ffeb9f]
[    0.019109] DMAR: Disable GFX device mapping
[    0.047926] DMAR: Host address width 39
[    0.047926] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[    0.047930] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap
c0000020660462 ecap f0101a
[    0.047930] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[    0.047932] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap
d2008020660462 ecap f010da
[    0.047933] DMAR: RMRR base: 0x000000dbcf6000 end: 0x000000dbd03fff
[    0.047934] DMAR: RMRR base: 0x000000dd000000 end: 0x000000df1fffff
[    0.047936] DMAR-IR: IOAPIC id 8 under DRHD base  0xfed91000 IOMMU 1
[    0.047937] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[    0.047937] DMAR-IR: Queued invalidation will be enabled to support
x2apic and Intr-remapping.
[    0.048327] DMAR-IR: Enabled IRQ remapping in x2apic mode
[    0.793666] DMAR: No ATSR found
[    0.793696] DMAR: dmar1: Using Queued invalidation
[    0.795240] DMAR: Intel(R) Virtualization Technology for Directed I/O
[    0.799207] AMD-Vi: AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>
[    0.799207] AMD-Vi: AMD IOMMUv2 functionality not available on this
system


bullseye with no intel_iommu command line setting:
dmesg | grep -e DMAR -e IOMMU
[    0.007532] ACPI: DMAR 0x00000000D8FFEAE8 0000B8 (v01 INTEL  HSW
 00000001 INTL 00000001)
[    0.007546] ACPI: Reserving DMAR table memory at [mem
0xd8ffeae8-0xd8ffeb9f]
[    0.048030] DMAR: Host address width 39
[    0.048031] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[    0.048034] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap
c0000020660462 ecap f0101a
[    0.048035] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[    0.048037] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap
d2008020660462 ecap f010da
[    0.048037] DMAR: RMRR base: 0x000000dbcf6000 end: 0x000000dbd03fff
[    0.048038] DMAR: RMRR base: 0x000000dd000000 end: 0x000000df1fffff
[    0.048040] DMAR-IR: IOAPIC id 8 under DRHD base  0xfed91000 IOMMU 1
[    0.048040] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[    0.048041] DMAR-IR: Queued invalidation will be enabled to support
x2apic and Intr-remapping.
[    0.048426] DMAR-IR: Enabled IRQ remapping in x2apic mode
[    0.794120] DMAR: No ATSR found
[    0.794149] DMAR: dmar0: Using Queued invalidation
[    0.794154] DMAR: dmar1: Using Queued invalidation
[    0.863652] DMAR: Intel(R) Virtualization Technology for Directed I/O
[    0.867732] AMD-Vi: AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>

[    0.867733] AMD-Vi: AMD IOMMUv2 functionality not available on this
system
[    1.250394] i915 0000:00:02.0: [drm] DMAR active, disabling use of
stolen memory

buster no intel_iommu setting:
dmesg | grep -e DMAR -e IOMMU
[    0.009193] ACPI: DMAR 0x00000000D8FFEAE8 0000B8 (v01 INTEL  HSW
 00000001 INTL 00000001)
[    0.192242] DMAR: Host address width 39
[    0.192243] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[    0.192246] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap
c0000020660462 ecap f0101a
[    0.192246] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[    0.192248] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap
d2008020660462 ecap f010da
[    0.192249] DMAR: RMRR base: 0x000000dbcf6000 end: 0x000000dbd03fff
[    0.192249] DMAR: RMRR base: 0x000000dd000000 end: 0x000000df1fffff
[    0.192251] DMAR-IR: IOAPIC id 8 under DRHD base  0xfed91000 IOMMU 1
[    0.192251] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[    0.192252] DMAR-IR: Queued invalidation will be enabled to support
x2apic and Intr-remapping.
[    0.192637] DMAR-IR: Enabled IRQ remapping in x2apic mode
[    0.846867] AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>
[    0.846867] AMD IOMMUv2 functionality not available on this system

On Sat, 3 Jul 2021 at 02:22, Bryan Cebuliak <bryan.cebuliak@gmail.com> wrote:
#867548#82
Date:
2021-07-04 01:21:41 UTC
From:
To:
Ubuntu 20.04:
dmesg | grep -e DMAR -e IOMMU
[    0.007620] ACPI: DMAR 0x00000000D8FFEAE8 0000B8 (v01 INTEL  HSW
 00000001 INTL 00000001)
[    0.007633] ACPI: Reserving DMAR table memory at [mem
0xd8ffeae8-0xd8ffeb9f]
[    0.097851] DMAR: Host address width 39
[    0.097852] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[    0.097855] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap
c0000020660462 ecap f0101a
[    0.097856] DMAR: DRHD base: 0x000000fed91000 flags: 0x1
[    0.097858] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap
d2008020660462 ecap f010da
[    0.097858] DMAR: RMRR base: 0x000000dbcf6000 end: 0x000000dbd03fff
[    0.097859] DMAR: RMRR base: 0x000000dd000000 end: 0x000000df1fffff
[    0.097861] DMAR-IR: IOAPIC id 8 under DRHD base  0xfed91000 IOMMU 1
[    0.097861] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[    0.097862] DMAR-IR: Queued invalidation will be enabled to support
x2apic and Intr-remapping.
[    0.098256] DMAR-IR: Enabled IRQ remapping in x2apic mode

On Sat, 3 Jul 2021 at 17:28, Bryan Cebuliak <bryan.cebuliak@gmail.com> wrote:
#867548#87
Date:
2021-07-18 00:48:20 UTC
From:
To:
I  am   still   wondering  which  package   to   register  this   bug.  Is
it  some   kernel  config  issue  since   the   same   recent Buster
kernel   works  well  on Buster  but  not  on   Bullseye?  I   doubt  if
it  is  a  Pulseaudio  issue.
Another  possibly   relevant   link. Takashi Iwai is  the  man:
https://bugzilla.kernel.org/show_bug.cgi?id=74861