Bug 505464

Summary: Audio playback is sped up while using F11 LiveCD
Product: [Fedora] Fedora Reporter: Jon <7stringjon>
Component: kernelAssignee: Jaroslav Kysela <jkysela>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 11CC: awilliam, itamar, james, kernel-maint, mwc
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-28 12:54:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 513462    
Attachments:
Description Flags
First Boot into F11 LiveCD
none
Second Boot into F11 LiveCD
none
Third Boot into F11 LiveCD
none
alsa-info.sh ouput from working system (Arch) on same hardware none

Description Jon 2009-06-12 01:07:14 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b4) Gecko/20090427 Fedora/3.5-0.20.beta4.fc11 Firefox/3.5b4

All audio playback (using Totem, Rhythmbox, mouse-over preview, etc.) is sped up slightly and also higher in pitch while running the F11 LiveCD.

Reproducible: Always

Steps to Reproduce:
1.Boot from F11 LiveCD
2.Play any audio file (*.wav, *.flac, or *.ogg)
3.
Actual Results:  
Increased playback speed and higher pitch.

Expected Results:  
Normal playback speed and normal pitch.

The sampling rate must be being set incorrectly at boot. Attached is the output for "alsa-info.sh" for 3 separate trials of booting into the LiveCD. Also attached is the same output but from Arch Linux running on the same hardware, with correctly working audio playback.

The biggest clue (IMHO, but my alsa knowledge is limited) is that the "PCM front DAC" and "PCM ADC" values are greater than 44100 when the playback is not working correctly (sped up).

Comment 1 Jon 2009-06-12 01:08:25 UTC
Created attachment 347501 [details]
First Boot into F11 LiveCD

Comment 2 Jon 2009-06-12 01:09:24 UTC
Created attachment 347502 [details]
Second Boot into F11 LiveCD

Comment 3 Jon 2009-06-12 01:09:52 UTC
Created attachment 347503 [details]
Third Boot into F11 LiveCD

Comment 4 Jon 2009-06-12 01:10:46 UTC
Created attachment 347504 [details]
alsa-info.sh ouput from working system (Arch) on same hardware

Comment 5 Adam Williamson 2009-06-12 22:50:20 UTC
I'm almost certain it's the values mentioned in the final paragraph of the initial report. They match the described symptoms very well. I don't know where those get set or if it's possible to override them, though.

jaroslav, over to you!

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 6 Jon 2009-06-14 16:15:55 UTC
Update: I'm also getting the same results after using the installation DVD to install, so the issue is not specific to the LiveCD.

Comment 7 Jaroslav Kysela 2009-07-27 12:26:12 UTC
It looks like an another ac97_clock measure problem.

Any sound related messages in output from dmesg after boot (working and not working initialization)?

Comment 8 Jon 2009-07-27 19:04:22 UTC
Booted the Live CD twice.

1st boot, with an incorrectly set DAC/ADC (47113Hz)

[liveuser@localhost ~]$ dmesg | grep ac97
ALSA sound/pci/ac97/ac97_codec.c:2127: AC'97 0 analog subsections not ready
intel8x0_measure_ac97_clock: measured 51258 usecs
[liveuser@localhost ~]$ dmesg | grep intel8x0
intel8x0_measure_ac97_clock: measured 51258 usecs
intel8x0: clocking to 51280
[liveuser@localhost ~]$

2nd boot, with a correctly set DAC/ADC (44100Hz)

[liveuser@localhost ~]$ dmesg | grep ac97
ALSA sound/pci/ac97/ac97_codec.c:2127: AC'97 0 analog subsections not ready
intel8x0_measure_ac97_clock: measured 50999 usecs
[liveuser@localhost ~]$ dmesg | grep intel8x0
intel8x0_measure_ac97_clock: measured 50999 usecs
intel8x0: measured clock 215 rejected
intel8x0: clocking to 48000
[liveuser@localhost ~]$

Comment 9 Michael Carney 2009-08-03 19:35:25 UTC
Fedora 11 installed from DVD, all updates, DAC/ADC always set incorrectly on boot:

627> r 621
dmesg | grep intel8x0
intel8x0_measure_ac97_clock: measured 50800 usecs
intel8x0: measured clock 78 rejected
intel8x0: clocking to 48000
628>

Comment 10 Bug Zapper 2010-04-27 14:47:58 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 11 Bug Zapper 2010-06-28 12:54:58 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.