From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754467Ab2IWUwL (ORCPT ); Sun, 23 Sep 2012 16:52:11 -0400 Received: from mail-bk0-f46.google.com ([209.85.214.46]:35210 "EHLO mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754371Ab2IWUwJ (ORCPT ); Sun, 23 Sep 2012 16:52:09 -0400 MIME-Version: 1.0 In-Reply-To: <20120923202727.GA28937@mwanda> References: <20120904143215.5bbbb2a4@obelix.rh> <20120923202727.GA28937@mwanda> Date: Sun, 23 Sep 2012 13:52:07 -0700 X-Google-Sender-Auth: 6x_fQKdpOc_XWh4sVV9sgJluqI0 Message-ID: Subject: Re: kexec/kdump kernel fails to start From: Yinghai Lu To: Dan Carpenter Cc: Cong Wang , Flavio Leitner , lkml , Ingo Molnar , Tejun Heo , ianfang.cn@gmail.com, Andrew Morton Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Sep 23, 2012 at 1:27 PM, Dan Carpenter 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 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 2012-03-05 20:05:13 >> > Committer: Ingo Molnar 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