public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Paasch <christoph.paasch@uclouvain.be>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>,
	Yinghai Lu <yinghai@kernel.org>, Tejun Heo <tj@kernel.org>,
	Ian Fang <ianfang.cn@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: BUG: crashkernel does not boot upon crash from sysrq-trigger
Date: Mon, 16 Dec 2013 18:56:51 +0100	[thread overview]
Message-ID: <20131216175651.GA5048@cpaasch-mac> (raw)
In-Reply-To: <CAM_iQpUTTNbJLCNDem0xOCGW7XWctEyQ3H2w-1=y0HkhJ4uWhg@mail.gmail.com>

On 16/12/13 - 09:36:52, Cong Wang wrote:
> On Mon, Dec 16, 2013 at 3:35 AM, Christoph Paasch
> <christoph.paasch@uclouvain.be> wrote:
> > Hello,
> >
> > since 3.5, my crashkernel does not boot anymore when triggering an oops with
> > /proc/sysrq-trigger on my HP Elitebook 8540p.
> >
> > I bisected it down to 722bc6b16771ed8 (x86/mm: Fix the size calculation of
> > mapping tables).
> >
> 
> It has been reverted in upstream.

Oh, then something else is causing my bug again, because I tried v3.13-rc3
to see if it has been fixed upstream. And, my Ubuntu runs on v3.11, where
the crashkernel does not work either.

My bisect ended up on 722bc6b16771ed8 because I started bisecting between v3.2
(good) and v3.5 (bad).

So, then I will make again a bisect between v3.7 and v3.11.


Thanks,
Christoph

      reply	other threads:[~2013-12-16 17:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16 11:35 BUG: crashkernel does not boot upon crash from sysrq-trigger Christoph Paasch
2013-12-16 17:36 ` Cong Wang
2013-12-16 17:56   ` Christoph Paasch [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=20131216175651.GA5048@cpaasch-mac \
    --to=christoph.paasch@uclouvain.be \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=ianfang.cn@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=x86@kernel.org \
    --cc=xiyou.wangcong@gmail.com \
    --cc=yinghai@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