Description of problem: The ethernet card stops working while playing any audio. The problem even occurs on small duration sounds like message sounds in Gaim. Another aspect of this problem is: sometimes the audio repeats, and the audio program (e.g. Rhythmbox) stops responding. The sound repeats even when the program is forcefully quited. Version-Release number of selected component (if applicable): kernel-2.6.17-1.2142_FC4.i686 How reproducible: just play any song Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I have MSI K8NGM2 motherboard with Nforce 410 chipset.
[This comment added as part of a mass-update to all open FC4 kernel bugs] FC4 has now transitioned to the Fedora legacy project, which will continue to release security related updates for the kernel. As this bug is not security related, it is unlikely to be fixed in an update for FC4, and has been migrated to FC5. Please retest with Fedora Core 5. Thank you.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you.