On Feb 18, 2008 1:59 PM, Andrew Morton <[EMAIL PROTECTED]> wrote: > On Fri, 15 Feb 2008 14:08:53 +0300 Alexey Dobriyan <[EMAIL PROTECTED]> wrote: > > > Booting without SYSFS fills dmesg like this > > Does the system normally boot without sysfs? Surprised. > > > > ------------[ cut here ]------------ > > WARNING: at lib/kref.c:43 kref_get+0x20/0x30() > > Modules linked in: loop(+) > > Pid: 994, comm: modprobe Tainted: G M 2.6.25-rc1 #6 > > > > Call Trace: > > [<ffffffff802317f4>] warn_on_slowpath+0x64/0x90 > > [<ffffffff8028db08>] init_object+0x88/0xa0 > > [<ffffffff8028f55e>] __slab_alloc+0xbe/0x550 > > [<ffffffff8031aa28>] kvasprintf+0x58/0x90 > > [<ffffffff8031874c>] vsnprintf+0x33c/0x6e0 > > [<ffffffff8031aa41>] kvasprintf+0x71/0x90 > > [<ffffffff8022c597>] hrtick_set+0x77/0x140 > > [<ffffffff80314860>] kref_get+0x20/0x30 > > [<ffffffff80313932>] kobject_get+0x12/0x20 > > [<ffffffff803139f9>] kobject_add_internal+0x49/0xf0 > > [<ffffffff80313bb3>] kobject_add_varg+0x73/0x80 > > [<ffffffff80313fa4>] kobject_add+0x54/0x80 > > [<ffffffff8028ec53>] check_object+0x103/0x230 > > [<ffffffff8028db08>] init_object+0x88/0xa0 > > [<ffffffff80313744>] kobject_create+0x14/0x40 > > [<ffffffff8028fbd3>] kmem_cache_alloc+0xd3/0xe0 > > [<ffffffff803136b4>] kobject_init+0x34/0xb0 > > [<ffffffff8031375b>] kobject_create+0x2b/0x40 > > [<ffffffff8031400c>] kobject_create_and_add+0x3c/0x80 > > [<ffffffff8025e137>] load_module+0x1847/0x1970 > > [<ffffffff80288800>] alloc_pages_current+0x0/0x90 > > [<ffffffff8025e2c2>] sys_init_module+0x62/0x1a0 > > > > Is this a regression?
Alexey, do you always see these messages with every modprobe of a module? Can you enable CONFIG_DEBUG_KOBJECT=y? It might give a hint where we miss to initialization of a kobject when sysfs is not compiled in. Thanks, Kay -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
