Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 981770 - No sound after suspend 82801H HD
Summary: No sound after suspend 82801H HD
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2013-07-05 18:33 UTC by Artyom Kunyov
Modified: 2013-10-08 17:06 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-10-08 17:06:14 UTC
Type: Bug

Attachments (Terms of Use)

Description Artyom Kunyov 2013-07-05 18:33:24 UTC
Description of problem:

Starting with kernel 3.9.0, I no longer have sound after suspend. Worked fine with <3.9 versions.
My laptop is Dell XPS M1530, and the sound card is Intel Corporation 82801H (ICH8 Family) HD Audio Controller.

Version-Release number of selected component (if applicable):
Linux >3.9

Comment 1 Josh Boyer 2013-09-18 20:23:11 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.11.1-200.fc19.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 2 Josh Boyer 2013-10-08 17:06:14 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.

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