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: Sat, 06 Mar 2010 13:09:00 +0530 [thread overview]
Message-ID: <4B920694.7060402@in.ibm.com> (raw)
In-Reply-To: <4B910623.9020707@kernel.org>
Tejun Heo wrote:
>
> I'm having very difficult time imagining how 22b737f4 could have
> affected this as the patch is identical transformation of the previous
> code. Also, 833af842 was released with 2.6.32 and stayed that way, so
> it really looks like a memory overrun / random corruption thing. Can
> you please retry with kmalloc debug stuff turned on?
>
With latest git (2.6.33-git11) the machine boots fine. So as you
mentioned this could be a memory overrun / random corruption issue.
I will try few more boots with latest / old git snapshots, and will
try to collect debug information on recreation.
Thanks
-Sachin
> Thanks.
>
>
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
prev parent reply other threads:[~2010-03-06 7:39 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
2010-03-05 13:24 ` Tejun Heo
2010-03-06 7:39 ` Sachin Sant [this message]
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=4B920694.7060402@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox