Bug#867548: Available for Additional Testing

Bryan Cebuliak bryan.cebuliak at gmail.com
Fri Jul 2 07:30:21 BST 2021


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 at gmail.com>
wrote:

>
> 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 at gmail.com> wrote:.
> > 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).
> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-pulseaudio-devel/attachments/20210702/ff052291/attachment.htm>


More information about the pkg-pulseaudio-devel mailing list