Bug 956314 - possible recursive locking detected; Macmini1,1 intel 945GM
Summary: possible recursive locking detected; Macmini1,1 intel 945GM
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 19
Hardware: i686
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-24 16:35 UTC by John Reiser
Modified: 2015-02-17 15:03 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 15:03:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg output (70.69 KB, text/plain)
2013-04-24 17:01 UTC, John Reiser
no flags Details

Description John Reiser 2013-04-24 16:35:57 UTC
Description of problem: kernel complains of "possible recursive locking detected"


Version-Release number of selected component (if applicable):
kernel-3.9.0-0.rc5.git1.301.fc19.i686
(running graphics testday-2013-04-23-i686.iso)

How reproducible: every time


Steps to Reproduce:
1. boot testday-2013-04-23-i686.iso to single-user mode (append " single" to kernel boot command line) on Macmini1,1 i686 only (Intel Core Duo [not Core*2* Duo])
2. pm-suspend  # on VGA console
3. resume (use main Power button)
  
Actual results:
[   75.751519] PM: resume of devices complete after 1707.909 msecs
[   75.754200] PM: resume devices took 1.711 seconds
[   75.804648] PM: Finishing wakeup.
[   75.804653] Restarting tasks ... done.
[   75.825608] video LNXVIDEO:00: Restoring backlight state

[   84.233106] =============================================
[   84.233106] [ INFO: possible recursive locking detected ]
[   84.233106] 3.9.0-0.rc5.git1.301.fc19.i686 #1 Not tainted
[   84.233106] ---------------------------------------------
[   84.233106] kworker/0:1/26 is trying to acquire lock:
[   84.233106]  (&crtc->mutex){+.+.+.}, at: [<f7e9e81c>] intel_get_load_detect_pipe+0x15c/0x3b0 [i915]
[   84.233106]
but task is already holding lock:
[   84.233106]  (&crtc->mutex){+.+.+.}, at: [<f7d54822>] drm_modeset_lock_all+0x42/0x60 [drm]
[   84.233106]
other info that might help us debug this:
[   84.233106]  Possible unsafe locking scenario:

[   84.233106]        CPU0
[   84.233106]        ----
[   84.233106]   lock(&crtc->mutex);
[   84.233106]   lock(&crtc->mutex);
[   84.233106]
 *** DEADLOCK ***

[   84.233106]  May be due to missing lock nesting notation

[   84.233106] 4 locks held by kworker/0:1/26:
[   84.233106]  #0:  (events){.+.+.+}, at: [<c04627be>] process_one_work+0x12e/0x590
[   84.233106]  #1:  ((&(&dev->mode_config.output_poll_work)->work)){+.+.+.}, at: [<c04627be>] process_one_work+0x12e/0x590
[   84.233106]  #2:  (&dev->mode_config.mutex){+.+.+.}, at: [<f7d547fa>] drm_modeset_lock_all+0x1a/0x60 [drm]
[   84.233106]  #3:  (&crtc->mutex){+.+.+.}, at: [<f7d54822>] drm_modeset_lock_all+0x42/0x60 [drm]
[   84.233106]
stack backtrace:
[   84.233106] Pid: 26, comm: kworker/0:1 Not tainted 3.9.0-0.rc5.git1.301.fc19.i686 #1
[   84.233106] Call Trace:
[   84.233106]  [<c04aa8f7>] __lock_acquire+0x1487/0x1630
[   84.233106]  [<c04a6840>] ? __lock_is_held+0x40/0x70
[   84.233106]  [<c04ab0bb>] lock_acquire+0x8b/0x1b0
[   84.233106]  [<f7e9e81c>] ? intel_get_load_detect_pipe+0x15c/0x3b0 [i915]
[   84.233106]  [<c0a2ed2e>] mutex_lock_nested+0x6e/0x330
[   84.233106]  [<f7e9e81c>] ? intel_get_load_detect_pipe+0x15c/0x3b0 [i915]
[   84.233106]  [<f7e9e81c>] ? intel_get_load_detect_pipe+0x15c/0x3b0 [i915]
[   84.233106]  [<f7d54925>] ? drm_get_connector_name+0x45/0x50 [drm]
[   84.233106]  [<f7e9e81c>] intel_get_load_detect_pipe+0x15c/0x3b0 [i915]
[   84.233106]  [<c047df9f>] ? sched_clock_cpu+0xdf/0x150
[   84.233106]  [<c040e420>] ? save_stack_trace+0x30/0x50
[   84.233106]  [<c04a61db>] ? trace_hardirqs_off+0xb/0x10
[   84.233106]  [<f7eb9e07>] intel_tv_detect+0xe7/0x4a0 [i915]
[   84.233106]  [<c04a8fc3>] ? mark_held_locks+0x83/0xe0
[   84.233106]  [<c0a31c8f>] ? _raw_spin_unlock_irqrestore+0x2f/0x70
[   84.233106]  [<c0a29311>] ? __slab_free+0x16a/0x332
[   84.233106]  [<c04a910c>] ? trace_hardirqs_on_caller+0xec/0x170
[   84.233106]  [<f7d042a8>] drm_helper_probe_single_connector_modes+0x1b8/0x330 [drm_kms_helper]
[   84.233106]  [<f7d01d91>] drm_fb_helper_probe_connector_modes.isra.3+0x41/0x60 [drm_kms_helper]
[   84.233106]  [<f7d02c92>] drm_fb_helper_hotplug_event+0xc2/0xf0 [drm_kms_helper]
[   84.233106]  [<f7eb9079>] intel_fb_output_poll_changed+0x19/0x20 [i915]
[   84.233106]  [<f7d03e91>] drm_kms_helper_hotplug_event+0x21/0x30 [drm_kms_helper]
[   84.233106]  [<f7d04055>] output_poll_execute+0x155/0x170 [drm_kms_helper]
[   84.233106]  [<c046283a>] process_one_work+0x1aa/0x590
[   84.233106]  [<c04627be>] ? process_one_work+0x12e/0x590
[   84.233106]  [<c0462fc6>] ? worker_thread+0x196/0x350
[   84.233106]  [<c0462f25>] worker_thread+0xf5/0x350
[   84.233106]  [<c0462e30>] ? rescuer_thread+0x210/0x210
[   84.233106]  [<c0467c88>] kthread+0xa8/0xb0
[   84.233106]  [<c04a919b>] ? trace_hardirqs_on+0xb/0x10
[   84.233106]  [<c0a39eb7>] ret_from_kernel_thread+0x1b/0x28
[   84.233106]  [<c0467be0>] ? insert_kthread_work+0x70/0x70
[   84.511942] VFS: busy inodes on changed media or resized disk sr0


Expected results: no complaint


Additional info:

Comment 1 John Reiser 2013-04-24 17:01:20 UTC
Created attachment 739544 [details]
dmesg output

Comment 2 Chris Murphy 2013-06-02 20:34:29 UTC
Bug 969871 could be related or a dup.

Comment 3 Fedora End Of Life 2015-01-09 17:57:38 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 4 Fedora End Of Life 2015-02-17 15:03:27 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.


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