From: Avi Kivity <avi@redhat.com>
To: lkml <linux-kernel@vger.kernel.org>, Yinghai Lu <yinghai@kernel.org>
Subject: CONFIG_NO_BOOTMEM woes, 2.6.34-rc1
Date: Mon, 15 Mar 2010 17:28:17 +0200 [thread overview]
Message-ID: <4B9E5211.9000204@redhat.com> (raw)
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).
--
error compiling committee.c: too many arguments to function
next reply other threads:[~2010-03-15 15:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 15:28 Avi Kivity [this message]
2010-03-15 17:52 ` CONFIG_NO_BOOTMEM woes, 2.6.34-rc1 Yinghai Lu
2010-03-17 10:11 ` Avi Kivity
2010-03-17 10:28 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B9E5211.9000204@redhat.com \
--to=avi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox