| Summary: | [abrt] [ INFO: possible recursive locking detected ] [snd_hda_codec_hdmi] | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | George R. Goffe <grgoffe> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 25 | CC: | gansalmon, grgoffe, ichavero, itamar, jonathan, kernel-maint, labbott, madhu.chinakonda, mchehab | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/657152f0915c03d62a017fa07ffd1cb650744d36 | ||||||
| Whiteboard: | abrt_hash:7cec6c3adfbc024a55e80b3f1b231cd18169f82f;VARIANT_ID=workstation; | ||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-02-10 15:41:43 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
Created attachment 1207587 [details]
File: dmesg
If you boot into an older 4.7.x kernel does the warning still appear? Laura, Thank you for looking at this bug I tried the two other kernels I have on this system... Same results. There are several other errors in this system. Shutdown or reboot seems to get stuck right after achieving "Shutdown Target". There are a number of snd_ variables undefined for example. What can be done about them? Regards, George... This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora 'version' of '23'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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. changing version of this bug to 25 since it still exists. Thanks, George... *********** 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 25 kernel bugs. Fedora 25 has now been rebased to 4.9.3-200.fc25. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those. Hi, This problem seems to have been fixed as I haven't seen the message in quite a while. Thanks for all the hard work! George... Thank you for letting us know. |
Description of problem: 1) this kernel was installed in early october, when in became available 2) problem presents at early boot 2) dmesg buffer says it all Additional info: reporter: libreport-2.6.4 [ INFO: possible recursive locking detected ] 4.7.5-100.fc23.x86_64+debug #1 Not tainted --------------------------------------------- kworker/0:1/87 is trying to acquire lock: (&spec->pcm_lock){+.+...}, at: input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input14 [<ffffffffc0898c97>] hdmi_present_sense+0x47/0x3b0 [snd_hda_codec_hdmi]