Bug 87799 - (SOUND VIA82CXXX_AUDIO)Sound problems with Gigabyte GA-7VAXP onboard sound chip (8235)
Summary: (SOUND VIA82CXXX_AUDIO)Sound problems with Gigabyte GA-7VAXP onboard sound ch...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 9
Hardware: athlon
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-04-02 17:10 UTC by James Boulton
Modified: 2007-04-18 16:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-09-30 15:40:44 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description James Boulton 2003-04-02 17:10:31 UTC 
Description of problem:
Sound plays very briefly then (<1 second) the application (xmms, gnome sound
events..) locks. 

Version-Release number of selected component (if applicable):
Redhat 9

How reproducible:
Every time

Steps to Reproduce:
1.Enable Sounds for events under Preferences->sound
2.Play music thru' XMMS
3.
    
Actual results:
Gnome lockup for sound events (can CTRL+ALT+Backspace to restart X - so it's not
a kernel lockup). If sound events is disabled and I play music thru XMMS it locks up

Expected results:
Sound 

Additional info:
The installation of RH9 correctly identified the sound driver (via82cxxx_audio)
and successfully played the test sound.
Comment 1 Alan Cox 2003-06-27 21:31:29 UTC 
Ok fixed in current -ac now. Finally found the bug
Comment 2 Bugzilla owner 2004-09-30 15:40:44 UTC 
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/
Note You need to log in before you can comment on or make changes to this bug.