From: Sachin Sant <sachinp@in.ibm.com>
To: Tejun Heo <tj@kernel.org>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: -next March 3: Boot failure on x86 (Oops)
Date: Fri, 05 Mar 2010 16:14:10 +0530 [thread overview]
Message-ID: <4B90E07A.5090302@in.ibm.com> (raw)
In-Reply-To: <4B90A031.8090306@kernel.org>
Tejun Heo wrote:
> On 03/05/2010 03:08 PM, Tejun Heo wrote:
>
>> Hmmm... this means that on one of the chunks, chunk->list.next was
>> NULL (BTW, the disassembly is from unlinked object, right?). The main
>> allocation code hasn't seen much change lately. The only changes are,
>>
>> 22b737f4c75197372d64afc6ed1bccd58c00e549 : just refactoring
>> 833af8427be4b217b5bc522f61afdbd3f1d282c2 : possible but isn't very new
>>
>
> Can you also please try reverting the above two commits?
>
> Thanks.
>
>
Reverting both the commits allows the machine to boot.
If i just apply 22b737f4c75197372d64afc6ed1bccd58c00e549 the
box fails to boot with following kobject related traces:
registered taskstats version 1
kobject '' (c11d5fdc): tried to add an uninitialized object, something is seriously wrong.
Pid: 1, comm: swapper Not tainted 2.6.33-autotest-next-20100305 #3
Call Trace:
[<c03a7678>] ? printk+0xf/0x17
[<c028766f>] kobject_add+0x28/0x49
[<c05a1a8e>] memmap_init+0x4f/0x89
[<c05a1a3f>] ? memmap_init+0x0/0x89
[<c0101139>] do_one_initcall+0x4c/0x131
[<c057b352>] kernel_init+0x127/0x1a8
[<c057b22b>] ? kernel_init+0x0/0x1a8
[<c0102db6>] kernel_thread_helper+0x6/0x10
------------[ cut here ]------------
WARNING: at lib/kobject.c:595 kobject_put+0x27/0x3c()
Hardware name: eserver xSeries 235 -[86717AX]-
kobject: '' (c11d5fdc): is not initialized, yet kobject_put() is being called.
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.33-autotest-next-20100305 #3
Call Trace:
[<c012fe66>] warn_slowpath_common+0x60/0x90
[<c012feca>] warn_slowpath_fmt+0x24/0x27
[<c02872c6>] kobject_put+0x27/0x3c
[<c05a1a9c>] memmap_init+0x5d/0x89
[<c05a1a3f>] ? memmap_init+0x0/0x89
[<c0101139>] do_one_initcall+0x4c/0x131
[<c057b352>] kernel_init+0x127/0x1a8
[<c057b22b>] ? kernel_init+0x0/0x1a8
[<c0102db6>] kernel_thread_helper+0x6/0x10
---[ end trace 7b6574301a0037c2 ]---
The results are with today's next, but i think same applies to Linus
tree as well.
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next prev parent reply other threads:[~2010-03-05 10:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 6:46 linux-next: Tree for March 3 Stephen Rothwell
2010-03-03 15:44 ` -next March 3: Boot failure on x86 (Oops) Sachin Sant
2010-03-04 1:28 ` Tejun Heo
2010-03-04 5:23 ` Sachin Sant
2010-03-05 6:08 ` Tejun Heo
2010-03-05 6:09 ` Tejun Heo
2010-03-05 6:17 ` Tejun Heo
2010-03-05 7:47 ` Sachin Sant
2010-03-05 13:25 ` Tejun Heo
2010-03-05 10:44 ` Sachin Sant [this message]
2010-03-05 13:24 ` Tejun Heo
2010-03-06 7:39 ` Sachin Sant
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=4B90E07A.5090302@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.