[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20131216175651.GA5048@cpaasch-mac>
Date: Mon, 16 Dec 2013 18:56:51 +0100
From: Christoph Paasch <christoph.paasch@...ouvain.be>
To: Cong Wang <xiyou.wangcong@...il.com>
Cc: LKML <linux-kernel@...r.kernel.org>, x86 <x86@...nel.org>,
Yinghai Lu <yinghai@...nel.org>, Tejun Heo <tj@...nel.org>,
Ian Fang <ianfang.cn@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>
Subject: Re: BUG: crashkernel does not boot upon crash from sysrq-trigger
On 16/12/13 - 09:36:52, Cong Wang wrote:
> On Mon, Dec 16, 2013 at 3:35 AM, Christoph Paasch
> <christoph.paasch@...ouvain.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists