Re: CONFIG_NO_BOOTMEM woes, 2.6.34-rc1

[Yinghai Lu]

On 03/15/2010 08:28 AM, Avi Kivity wrote:
> With CONFIG_NO_BOOTMEM=y, I get:
> 
> kobject '' (c252bfdc): tried to add an uninitialized object, something
> is seriously wrong.
> Pid: 1, comm: swapper Not tainted 2.6.34-rc1 #121
> Call Trace:
>  [<c07803f5>] ? printk+0x14/0x17
>  [<c05a4cea>] kobject_add+0x28/0x49
>  [<c06e65c1>] add_sysfs_fw_map_entry+0x5b/0x74
>  [<c09fa56f>] memmap_init+0x13/0x2d
>  [<c040305b>] do_one_initcall+0x51/0x13f
>  [<c09ca376>] kernel_init+0x122/0x1a3
>  [<c09ca254>] ? kernel_init+0x0/0x1a3
>  [<c0408ffe>] kernel_thread_helper+0x6/0x10
> ------------[ cut here ]------------
> WARNING: at lib/kobject.c:595 kobject_put+0x27/0x3c()
> 
> a bit after which the kernel dies.  Inspection of memmap_init() and
> related code appears to call kobject_init() correctly.
> 
> With CONFIG_NO_BOOTMEM, the kernel hangs in early boot before displaying
> anything.
> 
> 2.6.34-rc1, i386 (x86_64 works fine).
> 

can you send out
.config and boot log for old kernel ...

Thanks

Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/