abrt-dump-oops: Found oopses: 1 Version: 2.6.33.1-19.fc13.x86_64 [ INFO: possible recursive locking detected ] 2.6.33.1-19.fc13.x86_64 #1 --------------------------------------------- 94cpufreq/3017 is trying to acquire lock: (s_active){++++.+}, at: [] sysfs_addrm_finish+0x36/0x55 but task is already holding lock: (s_active){++++.+}, at: [] sysfs_get_active_two+0x24/0x48 other info that might help us debug this: 4 locks held by 94cpufreq/3017: #0: (&buffer->mutex){+.+.+.}, at: [] sysfs_write_file+0x3c/0x144 #1: (s_active){++++.+}, at: [] sysfs_get_active_two+0x24/0x48 #2: (s_active){++++.+}, at: [] sysfs_get_active_two+0x31/0x48 #3: (dbs_mutex){+.+.+.}, at: [] cpufreq_governor_dbs+0x2a0/0x352 [cpufreq_ondemand] stack backtrace: Pid: 3017, comm: 94cpufreq Not tainted 2.6.33.1-19.fc13.x86_64 #1 Call Trace: [] __lock_acquire+0xcb5/0xd2c [] ? mark_held_locks+0x52/0x70 [] ? debug_check_no_locks_freed+0x12e/0x145 [] ? trace_hardirqs_on_caller+0x111/0x135 [] lock_acquire+0xdc/0x102 [] ? sysfs_addrm_finish+0x36/0x55 [] ? lockdep_init_map+0x9e/0x113 [] sysfs_deactivate+0x9a/0x103 [] ? sysfs_addrm_finish+0x36/0x55 [] ? sched_clock_cpu+0xc3/0xce [] ? __mutex_unlock_slowpath+0x120/0x132 [] sysfs_addrm_finish+0x36/0x55 [] sysfs_hash_and_remove+0x53/0x6a [] sysfs_remove_group+0x91/0xca [] cpufreq_governor_dbs+0x2b4/0x352 [cpufreq_ondemand] [] ? trace_hardirqs_on+0xd/0xf [] __cpufreq_governor+0x9b/0xde [] __cpufreq_set_policy+0x1ce/0x275 [] store_scaling_governor+0x1a7/0x1fb [] ? handle_update+0x0/0x39 [] ? down_write+0x7a/0x81 [] store+0x61/0x86 [] sysfs_write_file+0x108/0x144 [] vfs_write+0xae/0x10b [] ? trace_hardirqs_on_caller+0x111/0x135 [] sys_write+0x4a/0x6e [] system_call_fastpath+0x16/0x1b