* Frederic Weisbecker <fweisbec@xxxxxxxxx> wrote: > The first one, a lockdep warning: > > [ 2.975320] [<ffffffff8077c7f5>] rt_spin_lock+0x85/0xb0 > [ 2.975320] [<ffffffff802f6823>] ? kfree+0x43/0xc0 > [ 2.975320] [<ffffffff802f6823>] kfree+0x43/0xc0 > [ 2.975320] [<ffffffff8027f2fd>] ? trace_hardirqs_off+0xd/0x10 > [ 2.975320] [<ffffffff8028a156>] generic_smp_call_function_single_interrupt+0x106/0x110 > [ 2.975320] [<ffffffff80227144>] smp_call_function_single_interrupt+0x24/0x40 > [ 2.975320] [<ffffffff80213223>] call_function_single_interrupt+0x13/0x20 > [ 2.975320] <EOI> [<ffffffff8022df7b>] ? native_safe_halt+0xb/0x10 > [ 2.975320] [<ffffffff8022df79>] ? native_safe_halt+0x9/0x10 > [ 2.975320] [<ffffffff8021a93a>] ? default_idle+0x5a/0x60 > [ 2.975320] [<ffffffff8021136e>] ? cpu_idle+0x7e/0x100 > [ 2.975320] [<ffffffff80775b6c>] ? start_secondary+0x197/0x1eb hm, that's a complex one - we do kfree() from IPI context, dunno why this never triggered in our testing of -rt1. > The second, a sysfs warning: > > [ 8.042459] ------------[ cut here ]------------ > [ 8.054763] WARNING: at fs/sysfs/dir.c:462 sysfs_add_one+0x51/0x60() > [ 8.066777] Hardware name: AMILO Li 2727 > [ 8.078555] sysfs: duplicate filename '14:4' can not be created that should be harmless - unless you only get it under -rt1. Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
