linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: 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
Date: Sun, 23 Sep 2012 13:52:07 -0700	[thread overview]
Message-ID: <CAE9FiQX-R1L-0LDZNTbk-a6SUog+=tTrdwcfr0QUczH_PLMMpw@mail.gmail.com> (raw)
In-Reply-To: <20120923202727.GA28937@mwanda>

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

  reply	other threads:[~2012-09-23 20:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-04 17:32 kexec/kdump kernel fails to start Flavio Leitner
2012-09-04 19:02 ` Yinghai Lu
2012-09-04 19:17   ` Flavio Leitner
2012-09-04 19:20     ` Yinghai Lu
2012-09-04 20:00       ` Flavio Leitner
2012-09-04 20:26       ` Flavio Leitner
2012-09-04 20:45         ` Yinghai Lu
2012-09-04 21:37           ` Flavio Leitner
2012-09-04 22:25             ` Yinghai Lu
2012-09-04 22:40               ` Flavio Leitner
2012-09-05  0:01               ` Flavio Leitner
2012-09-05  1:15                 ` Yinghai Lu
2012-09-05 13:46                   ` Flavio Leitner
2012-09-05 15:34 ` Cong Wang
2012-09-23 20:27   ` Dan Carpenter
2012-09-23 20:52     ` Yinghai Lu [this message]
2012-09-29  7:13       ` Ingo Molnar
2012-10-18  2:16         ` Dave Young
2012-10-18  6:33           ` Dave Young
2012-10-18 13:57             ` Cong Wang
2012-10-18 16:27             ` Flavio Leitner

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='CAE9FiQX-R1L-0LDZNTbk-a6SUog+=tTrdwcfr0QUczH_PLMMpw@mail.gmail.com' \
    --to=yinghai@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=dan.carpenter@oracle.com \
    --cc=fbl@redhat.com \
    --cc=ianfang.cn@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tj@kernel.org \
    --cc=xiyou.wangcong@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).