Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1485645 - Disable var_periodsize as default
Disable var_periodsize as default
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: alsa-lib (Show other bugs)
7.4
Unspecified Unspecified
unspecified Severity medium
: rc
: ---
Assigned To: Jaroslav Kysela
Ken Benoit
:
Depends On:
Blocks: 1442258
  Show dependency treegraph
 
Reported: 2017-08-26 11:55 EDT by GV
Modified: 2018-04-10 13:09 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2018-04-10 13:09:00 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0928 None None None 2018-04-10 13:09 EDT

  None (edit)
Description GV 2017-08-26 11:55:20 EDT
Description of problem:

Please consider disabling var_periodsize as default. See:
https://www.spinics.net/lists/alsa-devel/msg61714.html

"The recently added variable period-size feature for dmix & co seems
causing a regression on some old applications; e.g. Audacious aborts
with an error:

  ALSA error: snd_pcm_hw_params_set_buffer_time_near failed: Invalid argument.

As a quick fix, disable the feature as default.  One can still enable
it via asoundrc.

Bugzilla: https://bugzilla.opensuse.org/show_bug.cgi?id=1033179
Signed-off-by: Takashi Iwai <tiwai@xxxxxxx>"
Comment 3 Ken Benoit 2017-11-30 13:39:52 EST
Installed RHEL-7.5-20171129.n.4 different test systems and audio is working fine. Verified the patch is in place in the source of alsa-lib-1.1.4.1-2.el7.src.rpm. Marking as verified.
Comment 6 errata-xmlrpc 2018-04-10 13:09:00 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0928

Note You need to log in before you can comment on or make changes to this bug.