Bug 1351738
| Summary: | Broadwell sound no longer workin in 4.6 kernels | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Oleg Drokin <green> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 24 | CC: | delyan.kratunov, fedora, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | kernel-4.6.4-301.fc24 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-07-20 00:23:39 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Oleg Drokin
2016-06-30 17:07:11 UTC
Should be fixed in the next build. With the rebase I accidentally dropped CONFIG_DW_DMAC_CORE=y (because it's actually a terrible hack but upstream made a poor choice requiring that for sound on these platforms). Any ETA on a new build of the kernel with this config option (In reply to charles profitt from comment #2) > Any ETA on a new build of the kernel with this config option Later this week. The Fedora updates system will leave comments when it's filed. @Josh - the week is over yet no comment from the updates system and I'm still experiencing this with the latest kernel from @updates - 4.6.3-300.fc24. I see that you kicked off a build on July 5 for 4.6.3-200 - was that the build with the fix? Is it possible that someone beat you to bumping the version number? :) (In reply to Delyan Kratunov from comment #4) > @Josh - the week is over yet no comment from the updates system and I'm > still experiencing this with the latest kernel from @updates - > 4.6.3-300.fc24. I see that you kicked off a build on July 5 for 4.6.3-200 - > was that the build with the fix? Is it possible that someone beat you to > bumping the version number? :) No. 4.6.4 was queued upstream and we're waiting for that release. kernel-4.6.4-301.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-9a16b2e14e kernel-4.6.4-301.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-9a16b2e14e kernel-4.6.4-301.fc24 fixes the issue for me. kernel-4.6.4-301.fc24 fixes the issue for me as well. kernel-4.6.4-301.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report. |