From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sachin Sant Subject: Re: -next March 3: Boot failure on x86 (Oops) Date: Sat, 06 Mar 2010 13:09:00 +0530 Message-ID: <4B920694.7060402@in.ibm.com> References: <20100303174603.5be197ba.sfr@canb.auug.org.au> <4B8E83D4.6090507@in.ibm.com> <4B8F0CD0.1040507@kernel.org> <4B8F43DD.10002@in.ibm.com> <4B909FC5.8020800@kernel.org> <4B90A031.8090306@kernel.org> <4B90E07A.5090302@in.ibm.com> <4B910623.9020707@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from e23smtp06.au.ibm.com ([202.81.31.148]:37367 "EHLO e23smtp06.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751381Ab0CFHjF (ORCPT ); Sat, 6 Mar 2010 02:39:05 -0500 In-Reply-To: <4B910623.9020707@kernel.org> Sender: linux-next-owner@vger.kernel.org List-ID: To: Tejun Heo Cc: linux-next@vger.kernel.org, LKML 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 ---------------------------------