Bug 969871

Summary: possible recursive locking detected; MacBookPro 8,2
Product: [Fedora] Fedora Reporter: Chris Murphy <bugzilla>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: ajax, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 11:58:57 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:
Attachments:
Description Flags
dmesg
none
acpidump
none
lspci -nnvv none

Description Chris Murphy 2013-06-02 20:32:19 UTC
Created attachment 756095 [details]
dmesg

Description of problem:
dmesg reports INFO: possible recursive locking detected

Version-Release number of selected component (if applicable):
3.10.0-0.rc3.git0.1.fc20.x86_64.debug
(F19 normally yum updated, plus this kernel manually installed)


How reproducible:
Uncertain.


Steps to Reproduce:
1. Install F19, yum update, install this kernel version, reboot.


Actual results:
dmesg reports INFO: possible recursive locking detected

Expected results:
Not this message.


Additional info:
Seeing this also with 3.10.0-0.rc3.git0.1.fc20.x86_64.debug on Apple Inc. MacBookPro8,2/Mac-94245A3940C91C8 which has both i915 and radeon graphics:

Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126]

Advanced Micro Devices [AMD] nee ATI Whistler [Radeon HD 6600M/6700M/7600M Series] [1002:6741]

Comment 1 Chris Murphy 2013-06-02 20:32:57 UTC
Created attachment 756096 [details]
acpidump

Comment 2 Chris Murphy 2013-06-02 20:33:25 UTC
Created attachment 756097 [details]
lspci -nnvv

Comment 3 Chris Murphy 2013-06-02 20:34:49 UTC
Bug 956314 could be related or a dup.

Comment 4 Fedora End Of Life 2013-09-16 14:03:45 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20

Comment 5 Fedora End Of Life 2015-05-29 09:05:35 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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.

Comment 6 Fedora End Of Life 2015-06-29 11:58:57 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.