public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	hbabu@us.ibm.com, kexec@lists.infradead.org,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: kdump fails to load and crashes [was: mmotm 2009-11-01-10-01 uploaded]
Date: Tue, 03 Nov 2009 16:14:25 +0100	[thread overview]
Message-ID: <4AF048D1.4090402@gmail.com> (raw)
In-Reply-To: <20091103144450.GB4235@redhat.com>

On 11/03/2009 03:44 PM, Vivek Goyal wrote:
> On Tue, Nov 03, 2009 at 12:11:58AM +0100, Jiri Slaby wrote:
>> On 11/01/2009 07:07 PM, akpm@linux-foundation.org wrote:
>>> The mm-of-the-moment snapshot 2009-11-01-10-01 has been uploaded to
>>
>> Hi, kdump loading crashes:
>> BUG: unable to handle kernel paging request at ffff8800010a7000
>> IP: [<ffffffff8101cd8b>] machine_kexec_prepare+0x16b/0x13e0
>> PGD 1806063 PUD 180a063 PMD 10001e1
...
>> ffff8800010a7000 should be OK, as crashkernel=64M@16M was passed to the
>> kernel.
>>
> 
> This is strange. As you said, ffff8800010a7000, should be a valid address
> as you reserved memory from 16M.

Hmm, PMD has not RW bit set and we do store (see below).

> I took above -mm and for me kernel loads fine. I reserved memory 64M@32M
> as by default kernel is loading at address 16M.
> 
> How does your /proc/iomem look like in first kernel?

I'm not any longer on that machine. init_pgtable() overwrites random
memory, so possibly even host's page tables, hence the oops above, I
suppose.

I'm currently chasing it down in the qemu virtual machine, since I
already got a garbage into my ~/.viminfo (some overwritten page got
flushed, I guess).

There /proc/iomem looks like:
00100000-12beffff : System RAM
  01000000-04ffffff : Crash kernel
    01000000-014680c2 : Kernel code
    014680c3-016f39f7 : Kernel data
    0175b000-017d97ab : Kernel bss

I'll keep you informed.

  reply	other threads:[~2009-11-03 15:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-01 18:07 mmotm 2009-11-01-10-01 uploaded akpm
2009-11-01 21:47 ` vga_arb warning [was: mmotm 2009-11-01-10-01 uploaded] Jiri Slaby
2009-11-04  5:48   ` Andrew Morton
2009-11-02  3:48 ` mmotm 2009-11-01-10-01 uploaded (hugetlbfs) Randy Dunlap
2009-11-02 21:50   ` [PATCH] hugetlb: offload per node attribute registrations fix Lee Schermerhorn
2009-11-02 21:59     ` Randy Dunlap
2009-11-02 23:11 ` kdump fails to load and crashes [was: mmotm 2009-11-01-10-01 uploaded] Jiri Slaby
2009-11-03 14:44   ` Vivek Goyal
2009-11-03 15:14     ` Jiri Slaby [this message]
2009-11-03 15:24       ` Vivek Goyal
2009-11-03 15:46         ` Jiri Slaby
2009-11-05 19:13 ` mmotm 2009-11-01-10-01 uploaded Thomas Gleixner
2009-11-06 11:38   ` Balbir Singh
2009-11-06 12:39     ` Emmanuel Benisty
2009-11-06 18:48       ` Randy Dunlap
2009-11-08 13:46         ` Jiri Slaby
2009-11-08 17:41           ` Randy Dunlap
2009-11-12  8:08   ` KOSAKI Motohiro

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=4AF048D1.4090402@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=hbabu@us.ibm.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=vgoyal@redhat.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