Subject : 2.5.30-rc6-git6 -- (fbcon, intelfb, i915?) INFO: possible circular locking dependency detected Submitter : Miles Lane <miles.lane@gmail.com> Date : 2009-05-23 5:08 References : http://marc.info/?l=linux-kernel&m=124305538130702&w=4 This entry is being used for tracking a regression from 2.6.29. Please don't close it until the problem is fixed in the mainline.
This bug is still present in 2.6.30-rc7. I am testing this on an ASUS EEE-PC 1000HE.
Created attachment 21552 [details] My current .config file.
This bug is still present in 2.6.30: [ 5.056504] ======================================================= [ 5.056660] [ INFO: possible circular locking dependency detected ] [ 5.056795] 2.6.30-ep1 #3 [ 5.056849] ------------------------------------------------------- [ 5.056962] udevadm/903 is trying to acquire lock: [ 5.057051] (&mm->mmap_sem){++++++}, at: [<c018a093>] might_fault+0x35/0x72 [ 5.057214] [ 5.057216] but task is already holding lock: [ 5.057326] (sysfs_mutex){+.+.+.}, at: [<c01e1f10>] sysfs_readdir+0xba/0x14b [ 5.057486] [ 5.057488] which lock already depends on the new lock. [ 5.057491] [ 5.057519] [ 5.057519] the existing dependency chain (in reverse order) is: [ 5.057519] [ 5.057519] -> #3 (sysfs_mutex){+.+.+.}: [ 5.057519] [<c014bdc3>] __lock_acquire+0x95b/0xac2 [ 5.057519] [<c014bfda>] lock_acquire+0xb0/0xcd [ 5.057519] [<c04c774c>] __mutex_lock_common+0x3e/0x392 [ 5.057519] [<c04c7ada>] mutex_lock_nested+0x12/0x15 [ 5.057519] [<c01e223a>] sysfs_addrm_start+0x23/0x90 [ 5.057519] [<c01e26d3>] create_dir+0x3a/0x68 [ 5.057519] [<c01e272e>] sysfs_create_dir+0x2d/0x41 [ 5.057519] [<c02ceb86>] kobject_add_internal+0xb7/0x158 [ 5.057519] [<c02cece0>] kobject_add_varg+0x35/0x41 [ 5.057519] [<c02ced51>] kobject_add+0x43/0x49 [ 5.057519] [<c037795c>] device_add+0xa8/0x46e [ 5.057519] [<c0377d34>] device_register+0x12/0x15 [ 5.057519] [<c0377dac>] device_create_vargs+0x75/0x96 [ 5.057519] [<c0377de8>] device_create+0x1b/0x1d [ 5.057519] [<c033b80a>] register_con_driver+0x8f/0xea [ 5.057519] [<c033c857>] take_over_console+0x15/0x35 [ 5.057519] [<c02f8176>] fbcon_takeover+0x63/0x96 [ 5.057519] [<c02f881a>] fbcon_event_notify+0x341/0x6ba [ 5.057519] [<c04cb0d6>] notifier_call_chain+0x2b/0x4a [ 5.057519] [<c0141645>] __blocking_notifier_call_chain+0x37/0x4c [ 5.057519] [<c0141666>] blocking_notifier_call_chain+0xc/0xe [ 5.057519] [<c02ed715>] fb_notifier_call_chain+0x11/0x13 [ 5.057519] [<c02ee548>] register_framebuffer+0x1e9/0x20a [ 5.057519] [<c0367be8>] intelfb_probe+0x49f/0x50b [ 5.057519] [<c0353df3>] drm_helper_initial_config+0x145/0x14f [ 5.057519] [<c0356e22>] i915_driver_load+0x8bd/0x909 [ 5.057519] [<c034ced9>] drm_get_dev+0x301/0x3cd [ 5.057519] [<c04bb68c>] i915_pci_probe+0xd/0xf [ 5.057519] [<c02dffe0>] local_pci_probe+0xe/0x10 [ 5.057519] [<c02e0a0d>] pci_device_probe+0x43/0x66 [ 5.057519] [<c03794b8>] driver_probe_device+0x79/0x105 [ 5.057519] [<c0379587>] __driver_attach+0x43/0x5f [ 5.057519] [<c0378f2a>] bus_for_each_dev+0x3d/0x67 [ 5.057519] [<c037938f>] driver_attach+0x14/0x16 [ 5.057519] [<c03789a6>] bus_add_driver+0xa5/0x1cc [ 5.057519] [<c03797cb>] driver_register+0x8b/0xe8 [ 5.057519] [<c02e0d8c>] __pci_register_driver+0x4c/0xa8 [ 5.057519] [<c0349667>] drm_init+0x59/0xb1 [ 5.057519] [<c070382e>] i915_init+0x46/0x48 [ 5.057519] [<c010113f>] do_one_initcall+0x4a/0x111 [ 5.057519] [<c06e32c6>] kernel_init+0x101/0x152 [ 5.057519] [<c01038c7>] kernel_thread_helper+0x7/0x10 [ 5.057519] [<ffffffff>] 0xffffffff [ 5.057519] [ 5.057519] -> #2 ((fb_notifier_list).rwsem){.+.+.+}: [ 5.057519] [<c014bdc3>] __lock_acquire+0x95b/0xac2 [ 5.057519] [<c014bfda>] lock_acquire+0xb0/0xcd [ 5.057519] [<c04c7d81>] down_read+0x1e/0x5b [ 5.057519] [<c0141632>] __blocking_notifier_call_chain+0x24/0x4c [ 5.057519] [<c0141666>] blocking_notifier_call_chain+0xc/0xe [ 5.057519] [<c02ed715>] fb_notifier_call_chain+0x11/0x13 [ 5.057519] [<c02ee548>] register_framebuffer+0x1e9/0x20a [ 5.057519] [<c0367be8>] intelfb_probe+0x49f/0x50b [ 5.057519] [<c0353df3>] drm_helper_initial_config+0x145/0x14f [ 5.057519] [<c0356e22>] i915_driver_load+0x8bd/0x909 [ 5.057519] [<c034ced9>] drm_get_dev+0x301/0x3cd [ 5.057519] [<c04bb68c>] i915_pci_probe+0xd/0xf [ 5.057519] [<c02dffe0>] local_pci_probe+0xe/0x10 [ 5.057519] [<c02e0a0d>] pci_device_probe+0x43/0x66 [ 5.057519] [<c03794b8>] driver_probe_device+0x79/0x105 [ 5.057519] [<c0379587>] __driver_attach+0x43/0x5f [ 5.057519] [<c0378f2a>] bus_for_each_dev+0x3d/0x67 [ 5.057519] [<c037938f>] driver_attach+0x14/0x16 [ 5.057519] [<c03789a6>] bus_add_driver+0xa5/0x1cc [ 5.057519] [<c03797cb>] driver_register+0x8b/0xe8 [ 5.057519] [<c02e0d8c>] __pci_register_driver+0x4c/0xa8 [ 5.057519] [<c0349667>] drm_init+0x59/0xb1 [ 5.057519] [<c070382e>] i915_init+0x46/0x48 [ 5.057519] [<c010113f>] do_one_initcall+0x4a/0x111 [ 5.057519] [<c06e32c6>] kernel_init+0x101/0x152 [ 5.057519] [<c01038c7>] kernel_thread_helper+0x7/0x10 [ 5.057519] [<ffffffff>] 0xffffffff [ 5.057519] [ 5.057519] -> #1 (&fb_info->lock){+.+.+.}: [ 5.057519] [<c014bdc3>] __lock_acquire+0x95b/0xac2 [ 5.057519] [<c014bfda>] lock_acquire+0xb0/0xcd [ 5.057519] [<c04c774c>] __mutex_lock_common+0x3e/0x392 [ 5.057519] [<c04c7ada>] mutex_lock_nested+0x12/0x15 [ 5.057519] [<c02edc98>] fb_mmap+0x87/0x156 [ 5.057519] [<c018fcc7>] mmap_region+0x23c/0x3f4 [ 5.057519] [<c01900be>] do_mmap_pgoff+0x23f/0x28f [ 5.057519] [<c01060b3>] sys_mmap2+0x5a/0x7b [ 5.057519] [<c0102da5>] syscall_call+0x7/0xb [ 5.057519] [<ffffffff>] 0xffffffff [ 5.057519] [ 5.057519] -> #0 (&mm->mmap_sem){++++++}: [ 5.057519] [<c014bcd3>] __lock_acquire+0x86b/0xac2 [ 5.057519] [<c014bfda>] lock_acquire+0xb0/0xcd [ 5.057519] [<c018a0b0>] might_fault+0x52/0x72 [ 5.057519] [<c02d3fdc>] copy_to_user+0x2c/0xfc [ 5.057519] [<c01acf0b>] filldir64+0x97/0xcd [ 5.057519] [<c01e1f6d>] sysfs_readdir+0x117/0x14b [ 5.057519] [<c01ad11d>] vfs_readdir+0x68/0x94 [ 5.057519] [<c01ad1ab>] sys_getdents64+0x62/0xa1 [ 5.057519] [<c0102da5>] syscall_call+0x7/0xb [ 5.057519] [<ffffffff>] 0xffffffff [ 5.057519] [ 5.057519] other info that might help us debug this: [ 5.057519] [ 5.057519] 2 locks held by udevadm/903: [ 5.057519] #0: (&type->i_mutex_dir_key){+.+.+.}, at: [<c01ad0fb>] vfs_readdir+0x46/0x94 [ 5.057519] #1: (sysfs_mutex){+.+.+.}, at: [<c01e1f10>] sysfs_readdir+0xba/0x14b [ 5.057519] [ 5.057519] stack backtrace: [ 5.057519] Pid: 903, comm: udevadm Not tainted 2.6.30-ep1 #3 [ 5.057519] Call Trace: [ 5.057519] [<c04c6580>] ? printk+0xf/0x11 [ 5.057519] [<c014b1a4>] print_circular_bug_tail+0x5d/0x68 [ 5.057519] [<c014bcd3>] __lock_acquire+0x86b/0xac2 [ 5.057519] [<c014bfda>] lock_acquire+0xb0/0xcd [ 5.057519] [<c018a093>] ? might_fault+0x35/0x72 [ 5.057519] [<c018a0b0>] might_fault+0x52/0x72 [ 5.057519] [<c018a093>] ? might_fault+0x35/0x72 [ 5.057519] [<c02d3fdc>] copy_to_user+0x2c/0xfc [ 5.057519] [<c01acf0b>] filldir64+0x97/0xcd [ 5.057519] [<c01e1f6d>] sysfs_readdir+0x117/0x14b [ 5.057519] [<c01ace74>] ? filldir64+0x0/0xcd [ 5.057519] [<c01ad11d>] vfs_readdir+0x68/0x94 [ 5.057519] [<c01ace74>] ? filldir64+0x0/0xcd [ 5.057519] [<c01ad1ab>] sys_getdents64+0x62/0xa1 [ 5.057519] [<c0102da5>] syscall_call+0x7/0xb
I just reproduced this in 2.6.31-rc1-git5.
I believe this is fixed. I haven't seen this error in recent builds.
OK, closing.