From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932158Ab2I2HN0 (ORCPT <rfc822;w@1wt.eu>);
	Sat, 29 Sep 2012 03:13:26 -0400
Received: from mail-wi0-f178.google.com ([209.85.212.178]:64013 "EHLO
	mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1755080Ab2I2HNX (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Sat, 29 Sep 2012 03:13:23 -0400
Date: Sat, 29 Sep 2012 09:13:18 +0200
From: Ingo Molnar <mingo@kernel.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
        Cong Wang <xiyou.wangcong@gmail.com>, Flavio Leitner <fbl@redhat.com>,
        lkml <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
        Tejun Heo <tj@kernel.org>, ianfang.cn@gmail.com,
        Andrew Morton <akpm@linux-foundation.org>
Subject: Re: kexec/kdump kernel fails to start
Message-ID: <20120929071318.GA7444@gmail.com>
References: <20120904143215.5bbbb2a4@obelix.rh>
 <CAM_iQpVVCjJ0Bde9RS9Rm-0RJ=CtTyX3eUH45+oaaepvdAvAmQ@mail.gmail.com>
 <20120923202727.GA28937@mwanda>
 <CAE9FiQX-R1L-0LDZNTbk-a6SUog+=tTrdwcfr0QUczH_PLMMpw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAE9FiQX-R1L-0LDZNTbk-a6SUog+=tTrdwcfr0QUczH_PLMMpw@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


* Yinghai Lu <yinghai@kernel.org> wrote:

> On Sun, Sep 23, 2012 at 1:27 PM, Dan Carpenter <dan.carpenter@oracle.com> wrote:
> > On Wed, Sep 05, 2012 at 11:34:25PM +0800, Cong Wang wrote:
> >> On Wed, Sep 5, 2012 at 1:32 AM, Flavio Leitner <fbl@redhat.com> wrote:
> >> > Hi folks,
> >> >
> >> > I have system that no longer boots kdump kernel. Basically,
> >> >
> >> > # echo c > /proc/sysrq-trigger
> >> >
> >> > to dump a vmcore doesn't work. It just hangs after showing the usual
> >> > panic messages. I've bisected the problem and the commit introducing
> >> > the issue is the one below.
> >> >
> >> > Any idea?
> >> >
> >> > commit 722bc6b16771ed80871e1fd81c86d3627dda2ac8
> >> > Author: WANG Cong <xiyou.wangcong@gmail.com>  2012-03-05 20:05:13
> >> > Committer: Ingo Molnar <mingo@elte.hu>  2012-03-06 05:38:26
> >> > Parent: 550cf00dbc8ee402bef71628cb71246493dd4500 (Merge tag 'mmc-fixes-for-3.3' of git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc)
> >> > Child:  a6fca40f1d7f3e232c9de27c1cebbb9f787fbc4f (x86, tlb: Switch cr3 in leave_mm() only when needed)
> >> > Branches: master, remotes/origin/master
> >> > Follows: v3.3-rc6
> >> > Precedes: v3.5-rc1
> >> >
> >> >     x86/mm: Fix the size calculation of mapping tables
> >>
> >> There was some attempt to fix this:
> >> https://patchwork.kernel.org/patch/1195751/
> >>
> >> but for some reason it is not accepted.
> >
> > I filed a bug for this:
> > https://bugzilla.kernel.org/show_bug.cgi?id=47881
> >
> > Is it fixed now?
> 
> that offending patch should be reverted...
> 
> 722bc6b16771ed80871e1fd81c86d3627dda2ac8

It does not revert cleanly - could someone send a (kexec 
tested!) patch with a proper description?

Thanks,

	Ingo