* pmu_dev_alloc; warning at at kernel/locking/lockdep.c:3002 lockdep_init_map @ 2015-05-07 13:54 Tvrtko Ursulin 2015-05-07 14:05 ` Peter Zijlstra 0 siblings, 1 reply; 7+ messages in thread From: Tvrtko Ursulin @ 2015-05-07 13:54 UTC (permalink / raw) To: linux-kernel; +Cc: Peter Zijlstra, Ingo Molnar Hi, 4.1.0-rc2 spews the below warning and disables lockdep for me at boot. Any ideas? May 7 11:58:20 skl kernel: [ 6.066696] futex hash table entries: 1024 (order: 5, 131072 bytes) May 7 11:58:20 skl kernel: [ 6.075774] BUG: key ffff88014973b850 not in .data! May 7 11:58:20 skl kernel: [ 6.081369] ------------[ cut here ]------------ May 7 11:58:20 skl kernel: [ 6.086695] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:3002 lockdep_init_map+0x14b/0x5e0() May 7 11:58:20 skl kernel: [ 6.096928] DEBUG_LOCKS_WARN_ON(1) May 7 11:58:20 skl kernel: [ 6.100659] Modules linked in: May 7 11:58:20 skl kernel: [ 6.104433] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.0-rc2-150507+ #3 May 7 11:58:20 skl kernel: [ 6.112284] Hardware name: Intel Corporation Skylake Client platform/Skylake Y LPDDR3 RVP3, BIOS SKLSE2R1.86C.X070.R01.1501282110 01/28/2015 May 7 11:58:20 skl kernel: [ 6.126689] 0000000000000bba ffff880149e1fb88 ffffffff816213f8 ffffffff8109fcc6 May 7 11:58:20 skl kernel: [ 6.135381] ffff880149e1fbd8 ffff880149e1fbc8 ffffffff810528e2 0000000000000000 May 7 11:58:20 skl kernel: [ 6.143992] ffff880146428858 0000000000000000 0000000000000000 ffff88014973b838 May 7 11:58:20 skl kernel: [ 6.152682] Call Trace: May 7 11:58:20 skl kernel: [ 6.155513] [<ffffffff816213f8>] dump_stack+0x4c/0x6e May 7 11:58:20 skl kernel: [ 6.161399] [<ffffffff8109fcc6>] ? console_unlock+0x406/0x440 May 7 11:58:20 skl kernel: [ 6.168075] [<ffffffff810528e2>] warn_slowpath_common+0xb2/0xe0 May 7 11:58:20 skl kernel: [ 6.174946] [<ffffffff810529c6>] warn_slowpath_fmt+0x46/0x50 May 7 11:58:20 skl kernel: [ 6.181525] [<ffffffff81093b6b>] lockdep_init_map+0x14b/0x5e0 May 7 11:58:20 skl kernel: [ 6.188202] [<ffffffff811dc06a>] __kernfs_create_file+0x7a/0xf0 May 7 11:58:20 skl kernel: [ 6.195069] [<ffffffff811dcb4e>] sysfs_add_file_mode_ns+0x16e/0x1b0 May 7 11:58:20 skl kernel: [ 6.202346] [<ffffffff811dd92a>] internal_create_group+0x19a/0x280 May 7 11:58:20 skl kernel: [ 6.209515] [<ffffffff811dda43>] sysfs_create_group+0x13/0x20 May 7 11:58:20 skl kernel: [ 6.216185] [<ffffffff811dda88>] sysfs_create_groups+0x38/0x90 May 7 11:58:20 skl kernel: [ 6.222958] [<ffffffff8145c3d6>] device_add+0x276/0x5d0 May 7 11:58:20 skl kernel: [ 6.229040] [<ffffffff8110a80b>] pmu_dev_alloc+0x8b/0xd0 May 7 11:58:20 skl kernel: [ 6.235215] [<ffffffff81d44c93>] ? perf_workqueue_init+0x61/0x61 May 7 11:58:20 skl kernel: [ 6.242184] [<ffffffff81d44cd9>] perf_event_sysfs_init+0x46/0x95 May 7 11:58:20 skl kernel: [ 6.249144] [<ffffffff81d44c93>] ? perf_workqueue_init+0x61/0x61 May 7 11:58:20 skl kernel: [ 6.256118] [<ffffffff81000352>] do_one_initcall+0x122/0x1f0 May 7 11:58:20 skl kernel: [ 6.262700] [<ffffffff81072e00>] ? parse_args+0x240/0x450 May 7 11:58:20 skl kernel: [ 6.268980] [<ffffffff81d27126>] kernel_init_freeable+0x106/0x19a May 7 11:58:20 skl kernel: [ 6.276045] [<ffffffff81d26878>] ? loglevel+0x31/0x31 May 7 11:58:20 skl kernel: [ 6.281939] [<ffffffff8161a380>] ? rest_init+0x140/0x140 May 7 11:58:20 skl kernel: [ 6.288120] [<ffffffff8161a38e>] kernel_init+0xe/0xf0 May 7 11:58:20 skl kernel: [ 6.294004] [<ffffffff81629e92>] ret_from_fork+0x42/0x70 May 7 11:58:20 skl kernel: [ 6.300186] [<ffffffff8161a380>] ? rest_init+0x140/0x140 May 7 11:58:20 skl kernel: [ 6.306367] ---[ end trace 98f2b03275198a56 ]--- May 7 11:58:20 skl kernel: [ 6.311703] BUG: key ffff88014973b888 not in .data! May 7 11:58:20 skl kernel: [ 6.317300] BUG: key ffff88014973b8c0 not in .data! May 7 11:58:20 skl kernel: [ 6.322895] BUG: key ffff88014973b8f8 not in .data! May 7 11:58:20 skl kernel: [ 6.329549] HugeTLB registered 2 MB page size, pre-allocated 0 pages Regards, Tvrtko P.S. Apologies if my attempt to find suitable people to copy wasn't that great! ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: pmu_dev_alloc; warning at at kernel/locking/lockdep.c:3002 lockdep_init_map 2015-05-07 13:54 pmu_dev_alloc; warning at at kernel/locking/lockdep.c:3002 lockdep_init_map Tvrtko Ursulin @ 2015-05-07 14:05 ` Peter Zijlstra 2015-05-07 16:25 ` Tejun Heo 0 siblings, 1 reply; 7+ messages in thread From: Peter Zijlstra @ 2015-05-07 14:05 UTC (permalink / raw) To: Tvrtko Ursulin Cc: linux-kernel, Ingo Molnar, Greg Kroah-Hartman, Tejun Heo, NeilBrown On Thu, May 07, 2015 at 02:54:00PM +0100, Tvrtko Ursulin wrote: > > Hi, > > 4.1.0-rc2 spews the below warning and disables lockdep for me at boot. > > Any ideas? > > May 7 11:58:20 skl kernel: [ 6.066696] futex hash table entries: 1024 (order: 5, 131072 bytes) > May 7 11:58:20 skl kernel: [ 6.075774] BUG: key ffff88014973b850 not in .data! > May 7 11:58:20 skl kernel: [ 6.081369] ------------[ cut here ]------------ > May 7 11:58:20 skl kernel: [ 6.086695] WARNING: CPU: 0 PID: 1 at kernel/locking/lockdep.c:3002 lockdep_init_map+0x14b/0x5e0() > May 7 11:58:20 skl kernel: [ 6.096928] DEBUG_LOCKS_WARN_ON(1) > May 7 11:58:20 skl kernel: [ 6.100659] Modules linked in: > May 7 11:58:20 skl kernel: [ 6.104433] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.1.0-rc2-150507+ #3 > May 7 11:58:20 skl kernel: [ 6.112284] Hardware name: Intel Corporation Skylake Client platform/Skylake Y LPDDR3 RVP3, BIOS SKLSE2R1.86C.X070.R01.1501282110 01/28/2015 > May 7 11:58:20 skl kernel: [ 6.126689] 0000000000000bba ffff880149e1fb88 ffffffff816213f8 ffffffff8109fcc6 > May 7 11:58:20 skl kernel: [ 6.135381] ffff880149e1fbd8 ffff880149e1fbc8 ffffffff810528e2 0000000000000000 > May 7 11:58:20 skl kernel: [ 6.143992] ffff880146428858 0000000000000000 0000000000000000 ffff88014973b838 > May 7 11:58:20 skl kernel: [ 6.152682] Call Trace: > May 7 11:58:20 skl kernel: [ 6.155513] [<ffffffff816213f8>] dump_stack+0x4c/0x6e > May 7 11:58:20 skl kernel: [ 6.161399] [<ffffffff8109fcc6>] ? console_unlock+0x406/0x440 > May 7 11:58:20 skl kernel: [ 6.168075] [<ffffffff810528e2>] warn_slowpath_common+0xb2/0xe0 > May 7 11:58:20 skl kernel: [ 6.174946] [<ffffffff810529c6>] warn_slowpath_fmt+0x46/0x50 > May 7 11:58:20 skl kernel: [ 6.181525] [<ffffffff81093b6b>] lockdep_init_map+0x14b/0x5e0 > May 7 11:58:20 skl kernel: [ 6.188202] [<ffffffff811dc06a>] __kernfs_create_file+0x7a/0xf0 > May 7 11:58:20 skl kernel: [ 6.195069] [<ffffffff811dcb4e>] sysfs_add_file_mode_ns+0x16e/0x1b0 > May 7 11:58:20 skl kernel: [ 6.202346] [<ffffffff811dd92a>] internal_create_group+0x19a/0x280 > May 7 11:58:20 skl kernel: [ 6.209515] [<ffffffff811dda43>] sysfs_create_group+0x13/0x20 > May 7 11:58:20 skl kernel: [ 6.216185] [<ffffffff811dda88>] sysfs_create_groups+0x38/0x90 > May 7 11:58:20 skl kernel: [ 6.222958] [<ffffffff8145c3d6>] device_add+0x276/0x5d0 > May 7 11:58:20 skl kernel: [ 6.229040] [<ffffffff8110a80b>] pmu_dev_alloc+0x8b/0xd0 > May 7 11:58:20 skl kernel: [ 6.235215] [<ffffffff81d44c93>] ? perf_workqueue_init+0x61/0x61 > May 7 11:58:20 skl kernel: [ 6.242184] [<ffffffff81d44cd9>] perf_event_sysfs_init+0x46/0x95 > May 7 11:58:20 skl kernel: [ 6.249144] [<ffffffff81d44c93>] ? perf_workqueue_init+0x61/0x61 > May 7 11:58:20 skl kernel: [ 6.256118] [<ffffffff81000352>] do_one_initcall+0x122/0x1f0 > May 7 11:58:20 skl kernel: [ 6.262700] [<ffffffff81072e00>] ? parse_args+0x240/0x450 > May 7 11:58:20 skl kernel: [ 6.268980] [<ffffffff81d27126>] kernel_init_freeable+0x106/0x19a > May 7 11:58:20 skl kernel: [ 6.276045] [<ffffffff81d26878>] ? loglevel+0x31/0x31 > May 7 11:58:20 skl kernel: [ 6.281939] [<ffffffff8161a380>] ? rest_init+0x140/0x140 > May 7 11:58:20 skl kernel: [ 6.288120] [<ffffffff8161a38e>] kernel_init+0xe/0xf0 > May 7 11:58:20 skl kernel: [ 6.294004] [<ffffffff81629e92>] ret_from_fork+0x42/0x70 > May 7 11:58:20 skl kernel: [ 6.300186] [<ffffffff8161a380>] ? rest_init+0x140/0x140 > May 7 11:58:20 skl kernel: [ 6.306367] ---[ end trace 98f2b03275198a56 ]--- > May 7 11:58:20 skl kernel: [ 6.311703] BUG: key ffff88014973b888 not in .data! > May 7 11:58:20 skl kernel: [ 6.317300] BUG: key ffff88014973b8c0 not in .data! > May 7 11:58:20 skl kernel: [ 6.322895] BUG: key ffff88014973b8f8 not in .data! > May 7 11:58:20 skl kernel: [ 6.329549] HugeTLB registered 2 MB page size, pre-allocated 0 pages That's in sysfs magic mushroom land, lets Cc people who know about this. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: pmu_dev_alloc; warning at at kernel/locking/lockdep.c:3002 lockdep_init_map 2015-05-07 14:05 ` Peter Zijlstra @ 2015-05-07 16:25 ` Tejun Heo 2015-05-07 16:29 ` Tvrtko Ursulin 0 siblings, 1 reply; 7+ messages in thread From: Tejun Heo @ 2015-05-07 16:25 UTC (permalink / raw) To: Peter Zijlstra Cc: Tvrtko Ursulin, linux-kernel, Ingo Molnar, Greg Kroah-Hartman, NeilBrown Hello, On Thu, May 07, 2015 at 04:05:57PM +0200, Peter Zijlstra wrote: > On Thu, May 07, 2015 at 02:54:00PM +0100, Tvrtko Ursulin wrote: > > > > Hi, > > > > 4.1.0-rc2 spews the below warning and disables lockdep for me at boot. > > > > Any ideas? > > > > May 7 11:58:20 skl kernel: [ 6.066696] futex hash table entries: 1024 (order: 5, 131072 bytes) > > May 7 11:58:20 skl kernel: [ 6.075774] BUG: key ffff88014973b850 not in .data! ... > > May 7 11:58:20 skl kernel: [ 6.188202] [<ffffffff811dc06a>] __kernfs_create_file+0x7a/0xf0 > > May 7 11:58:20 skl kernel: [ 6.195069] [<ffffffff811dcb4e>] sysfs_add_file_mode_ns+0x16e/0x1b0 > > May 7 11:58:20 skl kernel: [ 6.202346] [<ffffffff811dd92a>] internal_create_group+0x19a/0x280 > > May 7 11:58:20 skl kernel: [ 6.209515] [<ffffffff811dda43>] sysfs_create_group+0x13/0x20 > > May 7 11:58:20 skl kernel: [ 6.216185] [<ffffffff811dda88>] sysfs_create_groups+0x38/0x90 > > May 7 11:58:20 skl kernel: [ 6.222958] [<ffffffff8145c3d6>] device_add+0x276/0x5d0 > > May 7 11:58:20 skl kernel: [ 6.229040] [<ffffffff8110a80b>] pmu_dev_alloc+0x8b/0xd0 > > May 7 11:58:20 skl kernel: [ 6.242184] [<ffffffff81d44cd9>] perf_event_sysfs_init+0x46/0x95 > > May 7 11:58:20 skl kernel: [ 6.256118] [<ffffffff81000352>] do_one_initcall+0x122/0x1f0 > > May 7 11:58:20 skl kernel: [ 6.268980] [<ffffffff81d27126>] kernel_init_freeable+0x106/0x19a > > May 7 11:58:20 skl kernel: [ 6.288120] [<ffffffff8161a38e>] kernel_init+0xe/0xf0 > > May 7 11:58:20 skl kernel: [ 6.294004] [<ffffffff81629e92>] ret_from_fork+0x42/0x70 > > May 7 11:58:20 skl kernel: [ 6.306367] ---[ end trace 98f2b03275198a56 ]--- > > May 7 11:58:20 skl kernel: [ 6.311703] BUG: key ffff88014973b888 not in .data! > > May 7 11:58:20 skl kernel: [ 6.317300] BUG: key ffff88014973b8c0 not in .data! > > May 7 11:58:20 skl kernel: [ 6.322895] BUG: key ffff88014973b8f8 not in .data! > > May 7 11:58:20 skl kernel: [ 6.329549] HugeTLB registered 2 MB page size, pre-allocated 0 pages > > That's in sysfs magic mushroom land, lets Cc people who know about this. sysfs by default uses lockdep key embedded in attrs. It looks like somebody is making on-heap copies of attrs and using them as the group attrs. What's the offending pmu type? Thanks. -- tejun ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: pmu_dev_alloc; warning at at kernel/locking/lockdep.c:3002 lockdep_init_map 2015-05-07 16:25 ` Tejun Heo @ 2015-05-07 16:29 ` Tvrtko Ursulin 2015-05-07 17:06 ` Peter Zijlstra 0 siblings, 1 reply; 7+ messages in thread From: Tvrtko Ursulin @ 2015-05-07 16:29 UTC (permalink / raw) To: Tejun Heo, Peter Zijlstra Cc: linux-kernel, Ingo Molnar, Greg Kroah-Hartman, NeilBrown On 05/07/2015 05:25 PM, Tejun Heo wrote: > Hello, > > On Thu, May 07, 2015 at 04:05:57PM +0200, Peter Zijlstra wrote: >> On Thu, May 07, 2015 at 02:54:00PM +0100, Tvrtko Ursulin wrote: >>> >>> Hi, >>> >>> 4.1.0-rc2 spews the below warning and disables lockdep for me at boot. >>> >>> Any ideas? >>> >>> May 7 11:58:20 skl kernel: [ 6.066696] futex hash table entries: 1024 (order: 5, 131072 bytes) >>> May 7 11:58:20 skl kernel: [ 6.075774] BUG: key ffff88014973b850 not in .data! > ... >>> May 7 11:58:20 skl kernel: [ 6.188202] [<ffffffff811dc06a>] __kernfs_create_file+0x7a/0xf0 >>> May 7 11:58:20 skl kernel: [ 6.195069] [<ffffffff811dcb4e>] sysfs_add_file_mode_ns+0x16e/0x1b0 >>> May 7 11:58:20 skl kernel: [ 6.202346] [<ffffffff811dd92a>] internal_create_group+0x19a/0x280 >>> May 7 11:58:20 skl kernel: [ 6.209515] [<ffffffff811dda43>] sysfs_create_group+0x13/0x20 >>> May 7 11:58:20 skl kernel: [ 6.216185] [<ffffffff811dda88>] sysfs_create_groups+0x38/0x90 >>> May 7 11:58:20 skl kernel: [ 6.222958] [<ffffffff8145c3d6>] device_add+0x276/0x5d0 >>> May 7 11:58:20 skl kernel: [ 6.229040] [<ffffffff8110a80b>] pmu_dev_alloc+0x8b/0xd0 >>> May 7 11:58:20 skl kernel: [ 6.242184] [<ffffffff81d44cd9>] perf_event_sysfs_init+0x46/0x95 >>> May 7 11:58:20 skl kernel: [ 6.256118] [<ffffffff81000352>] do_one_initcall+0x122/0x1f0 >>> May 7 11:58:20 skl kernel: [ 6.268980] [<ffffffff81d27126>] kernel_init_freeable+0x106/0x19a >>> May 7 11:58:20 skl kernel: [ 6.288120] [<ffffffff8161a38e>] kernel_init+0xe/0xf0 >>> May 7 11:58:20 skl kernel: [ 6.294004] [<ffffffff81629e92>] ret_from_fork+0x42/0x70 >>> May 7 11:58:20 skl kernel: [ 6.306367] ---[ end trace 98f2b03275198a56 ]--- >>> May 7 11:58:20 skl kernel: [ 6.311703] BUG: key ffff88014973b888 not in .data! >>> May 7 11:58:20 skl kernel: [ 6.317300] BUG: key ffff88014973b8c0 not in .data! >>> May 7 11:58:20 skl kernel: [ 6.322895] BUG: key ffff88014973b8f8 not in .data! >>> May 7 11:58:20 skl kernel: [ 6.329549] HugeTLB registered 2 MB page size, pre-allocated 0 pages >> >> That's in sysfs magic mushroom land, lets Cc people who know about this. > > sysfs by default uses lockdep key embedded in attrs. It looks like > somebody is making on-heap copies of attrs and using them as the group > attrs. What's the offending pmu type? I am not familiar with this area, is this the answer? May 7 11:58:20 skl kernel: [ 0.849877] Performance Events: no PEBS fmt3+, generic architected perfmon, full-width counters, Intel PMU driver. May 7 11:58:20 skl kernel: [ 0.861827] ... version: 4 May 7 11:58:20 skl kernel: [ 0.866406] ... bit width: 48 May 7 11:58:20 skl kernel: [ 0.871083] ... generic registers: 4 May 7 11:58:20 skl kernel: [ 0.875664] ... value mask: 0000ffffffffffff May 7 11:58:20 skl kernel: [ 0.881724] ... max period: 0000ffffffffffff May 7 11:58:20 skl kernel: [ 0.887778] ... fixed-purpose events: 3 May 7 11:58:20 skl kernel: [ 0.892352] ... event mask: 000000070000000f May 7 11:58:20 skl kernel: [ 0.909665] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. Regards, Tvrtko ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: pmu_dev_alloc; warning at at kernel/locking/lockdep.c:3002 lockdep_init_map 2015-05-07 16:29 ` Tvrtko Ursulin @ 2015-05-07 17:06 ` Peter Zijlstra 2015-05-07 17:29 ` Peter Zijlstra 0 siblings, 1 reply; 7+ messages in thread From: Peter Zijlstra @ 2015-05-07 17:06 UTC (permalink / raw) To: Tvrtko Ursulin Cc: Tejun Heo, linux-kernel, Ingo Molnar, Greg Kroah-Hartman, NeilBrown On Thu, May 07, 2015 at 05:29:57PM +0100, Tvrtko Ursulin wrote: > >>> May 7 11:58:20 skl kernel: [ 6.066696] futex hash table entries: 1024 (order: 5, 131072 bytes) > >>> May 7 11:58:20 skl kernel: [ 6.329549] HugeTLB registered 2 MB page size, pre-allocated 0 pages > > sysfs by default uses lockdep key embedded in attrs. It looks like > > somebody is making on-heap copies of attrs and using them as the group > > attrs. What's the offending pmu type? > > I am not familiar with this area, is this the answer? Nope, that's way before you get the fail. initcall_debug might get you the right answer, but I suspect its the intel_uncore driver. I see arch/x86/kernel/cpu/perf_event_intel_uncore.c:uncore_type_init() do exactly what TJ says, its dynamically allocating struct attribute. Now, let me try and trigger that locally, that should not be skylake specific at all. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: pmu_dev_alloc; warning at at kernel/locking/lockdep.c:3002 lockdep_init_map 2015-05-07 17:06 ` Peter Zijlstra @ 2015-05-07 17:29 ` Peter Zijlstra 2015-05-08 14:38 ` Tvrtko Ursulin 0 siblings, 1 reply; 7+ messages in thread From: Peter Zijlstra @ 2015-05-07 17:29 UTC (permalink / raw) To: Tvrtko Ursulin Cc: Tejun Heo, linux-kernel, Ingo Molnar, Greg Kroah-Hartman, NeilBrown On Thu, May 07, 2015 at 07:06:26PM +0200, Peter Zijlstra wrote: > On Thu, May 07, 2015 at 05:29:57PM +0100, Tvrtko Ursulin wrote: > > >>> May 7 11:58:20 skl kernel: [ 6.066696] futex hash table entries: 1024 (order: 5, 131072 bytes) > > > >>> May 7 11:58:20 skl kernel: [ 6.329549] HugeTLB registered 2 MB page size, pre-allocated 0 pages > > > > > sysfs by default uses lockdep key embedded in attrs. It looks like > > > somebody is making on-heap copies of attrs and using them as the group > > > attrs. What's the offending pmu type? > > > > I am not familiar with this area, is this the answer? > > Nope, that's way before you get the fail. initcall_debug might get you > the right answer, but I suspect its the intel_uncore driver. > > I see arch/x86/kernel/cpu/perf_event_intel_uncore.c:uncore_type_init() > do exactly what TJ says, its dynamically allocating struct attribute. > > Now, let me try and trigger that locally, that should not be skylake > specific at all. 4.1-rc2+ with lockdep enabled boots without issue on my ivb-ep, no idea what's going on on your skylake thingy. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: pmu_dev_alloc; warning at at kernel/locking/lockdep.c:3002 lockdep_init_map 2015-05-07 17:29 ` Peter Zijlstra @ 2015-05-08 14:38 ` Tvrtko Ursulin 0 siblings, 0 replies; 7+ messages in thread From: Tvrtko Ursulin @ 2015-05-08 14:38 UTC (permalink / raw) To: Peter Zijlstra Cc: Tejun Heo, linux-kernel, Ingo Molnar, Greg Kroah-Hartman, NeilBrown On 05/07/2015 06:29 PM, Peter Zijlstra wrote: > On Thu, May 07, 2015 at 07:06:26PM +0200, Peter Zijlstra wrote: >> On Thu, May 07, 2015 at 05:29:57PM +0100, Tvrtko Ursulin wrote: >>>>>> May 7 11:58:20 skl kernel: [ 6.066696] futex hash table entries: 1024 (order: 5, 131072 bytes) >> >>>>>> May 7 11:58:20 skl kernel: [ 6.329549] HugeTLB registered 2 MB page size, pre-allocated 0 pages >> >> >>>> sysfs by default uses lockdep key embedded in attrs. It looks like >>>> somebody is making on-heap copies of attrs and using them as the group >>>> attrs. What's the offending pmu type? >>> >>> I am not familiar with this area, is this the answer? >> >> Nope, that's way before you get the fail. initcall_debug might get you >> the right answer, but I suspect its the intel_uncore driver. >> >> I see arch/x86/kernel/cpu/perf_event_intel_uncore.c:uncore_type_init() >> do exactly what TJ says, its dynamically allocating struct attribute. >> >> Now, let me try and trigger that locally, that should not be skylake >> specific at all. > > 4.1-rc2+ with lockdep enabled boots without issue on my ivb-ep, no idea > what's going on on your skylake thingy. Managed to debug it is the intel_pt driver which fails. Which if I see correctly is passing in attr_groups from the data section which should be OK. So I don't know either.. reported offending address is somewhere, terabytes away, before start of kernel. Regards, Tvrtko ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2015-05-08 14:38 UTC | newest] Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2015-05-07 13:54 pmu_dev_alloc; warning at at kernel/locking/lockdep.c:3002 lockdep_init_map Tvrtko Ursulin 2015-05-07 14:05 ` Peter Zijlstra 2015-05-07 16:25 ` Tejun Heo 2015-05-07 16:29 ` Tvrtko Ursulin 2015-05-07 17:06 ` Peter Zijlstra 2015-05-07 17:29 ` Peter Zijlstra 2015-05-08 14:38 ` Tvrtko Ursulin
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).