All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Stanislaw Gruszka <sgruszka@redhat.com>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	Maxim Uvarov <muvarov@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Neil Horman <nhorman@redhat.com>
Subject: Re: kdump broken on 2.6.37-rc4
Date: Fri, 17 Dec 2010 12:06:23 -0800	[thread overview]
Message-ID: <4D0BC2BF.5010400@kernel.org> (raw)
In-Reply-To: <20101217200139.GF14502@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2014 bytes --]

On 12/17/2010 12:01 PM, Vivek Goyal wrote:
> On Fri, Dec 17, 2010 at 11:52:11AM -0800, Yinghai Lu wrote:
>> On 12/17/2010 11:50 AM, Vivek Goyal wrote:
>>> On Fri, Dec 17, 2010 at 11:46:08AM -0800, Yinghai Lu wrote:
>>>> On 12/17/2010 11:39 AM, H. Peter Anvin wrote:
>>>>> On 12/17/2010 10:21 AM, Yinghai Lu wrote:
>>>>>>>>
>>>>>>>> Do we have actual testing for how high the 64-bit kernel will load?
>>>>>>>
>>>>>>> I will do some experiments on my box today and let you know.
>>>>>>
>>>>>> if bzImage is used, it is 896M.
>>>>>>
>>>>>
>>>>> Why?  896 MiB is a 32-bit kernel limitation which doesn't have anything
>>>>> to do with the bzImage format.
>>>>>
>>>>> So unless there is something going on here, I suspect you're just plain
>>>>> flat wrong.
>>>>
>>>> kexec-tools have some checking when it loads bzImage.
>>>>
>>>
>>> Yinghai,
>>>
>>> I think x86_64 might have just inherited the settings of 32bit without
>>> giving it too much of thought. At that point of time nobody bothered
>>> to load the kernel from high addresses. So these might be artificial
>>> limits.
>>
>> good point.  will check that.
> 
> Yinghai,
> 
> On x86_64, I am not seeing "Crash kernel" entry in /proc/iomem.
> 
> I see following in dmesg.
> 
> "[    0.000000] Reserving 128MB of memory at 64MB for crashkernel (System
> RAM: 5120MB)"
> 
> Following is my /proc/iomem.
> 
> # cat /proc/iomem 
> 00000100-0000ffff : reserved
> 00010000-00096fff : System RAM
> 00097000-0009ffff : reserved
> 000c0000-000e7fff : pnp 00:0f
> 000e8000-000fffff : reserved
> 00100000-bffc283f : System RAM
>   01000000-015d1378 : Kernel code
>   015d1379-01aee00f : Kernel data
>   01bc8000-024b4c4f : Kernel bss
> bffc2840-bfffffff : reserved
> 
> So there is RAM available at the requested address still no entry for
> "Crash Kernel". This is both with 2.6.36 as well as 37-rc6 kernel. I am 
> wondering if insert_resource() is failing here?
> 

also could be memblock_x86_reserve() fail ...

Please check attached debug patch...

Thanks

	Yinghai

[-- Attachment #2: mb_debug.patches.tar.bz2 --]
[-- Type: application/x-bzip, Size: 11774 bytes --]

  reply	other threads:[~2010-12-17 20:07 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03 11:16 kdump broken on 2.6.37-rc4 Stanislaw Gruszka
2010-12-03 11:16 ` Stanislaw Gruszka
2010-12-03 15:46 ` Maxim Uvarov
2010-12-03 15:46   ` Maxim Uvarov
2010-12-03 17:11   ` Stanislaw Gruszka
2010-12-03 17:11     ` Stanislaw Gruszka
2010-12-03 17:54     ` Neil Horman
2010-12-03 17:54       ` Neil Horman
2010-12-07 10:50       ` Stanislaw Gruszka
2010-12-07 10:50         ` Stanislaw Gruszka
2010-12-07 19:24         ` Yinghai Lu
2010-12-07 19:24           ` Yinghai Lu
2010-12-08 14:19           ` Stanislaw Gruszka
2010-12-08 14:19             ` Stanislaw Gruszka
2010-12-09  7:16             ` Yinghai Lu
2010-12-09  7:16               ` Yinghai Lu
2010-12-09 12:41               ` Stanislaw Gruszka
2010-12-09 12:41                 ` Stanislaw Gruszka
2010-12-09 20:09                 ` Yinghai Lu
2010-12-09 20:09                   ` Yinghai Lu
2010-12-13 10:08                   ` Stanislaw Gruszka
2010-12-13 10:08                     ` Stanislaw Gruszka
2010-12-13 18:20                     ` Yinghai Lu
2010-12-13 19:47                       ` H. Peter Anvin
2010-12-14 22:41                         ` Vivek Goyal
2010-12-15 10:39                           ` Stanislaw Gruszka
2010-12-15 22:41                             ` Yinghai Lu
2010-12-16  4:29                             ` Yinghai Lu
2010-12-16 10:00                               ` Stanislaw Gruszka
2010-12-16 16:16                                 ` H. Peter Anvin
2010-12-16 16:22                                   ` Vivek Goyal
2010-12-16 16:53                                     ` H. Peter Anvin
2010-12-18 21:50                                 ` Yinghai Lu
2010-12-16 14:39                               ` Vivek Goyal
2010-12-16 16:28                                 ` H. Peter Anvin
2010-12-16 17:28                                   ` Yinghai Lu
2010-12-16 19:58                                     ` H. Peter Anvin
2010-12-16 22:57                                       ` Yinghai Lu
2010-12-16 23:30                                       ` Yinghai Lu
2010-12-16 23:49                                         ` Yinghai Lu
2010-12-17  0:39                                           ` Yinghai Lu
2010-12-17  1:06                                             ` H. Peter Anvin
2010-12-17  1:21                                             ` H. Peter Anvin
2010-12-17  1:51                                             ` H. Peter Anvin
2010-12-17  3:05                                               ` Yinghai Lu
2010-12-17  3:07                                               ` Yinghai Lu
2010-12-17  3:19                                                 ` [tip:x86/urgent] x86-32: Make sure we can map all of lowmem if we need to tip-bot for H. Peter Anvin
2010-12-17 14:33                                                   ` Stanislaw Gruszka
2010-12-16 22:01                                     ` kdump broken on 2.6.37-rc4 Vivek Goyal
2010-12-16 22:58                                       ` Yinghai Lu
2010-12-17 16:15                                         ` Vivek Goyal
2010-12-17  1:15                                       ` H. Peter Anvin
2010-12-17  3:31                               ` H. Peter Anvin
2010-12-17  3:58                                 ` Yinghai
2010-12-17  4:08                                   ` H. Peter Anvin
2010-12-17  4:46                                     ` Yinghai Lu
2010-12-17  5:16                                       ` H. Peter Anvin
2010-12-17 17:01                                   ` Vivek Goyal
2010-12-17 17:56                                     ` H. Peter Anvin
2010-12-17 18:02                                       ` Vivek Goyal
2010-12-17 18:21                                         ` Yinghai Lu
2010-12-17 18:35                                           ` Vivek Goyal
2010-12-17 19:39                                           ` H. Peter Anvin
2010-12-17 19:46                                             ` Yinghai Lu
2010-12-17 19:50                                               ` Vivek Goyal
2010-12-17 19:52                                                 ` Yinghai Lu
2010-12-17 20:01                                                   ` Vivek Goyal
2010-12-17 20:06                                                     ` Yinghai Lu [this message]
2010-12-17 20:34                                                       ` Vivek Goyal
2010-12-17 23:51                                                         ` Vivek Goyal
2010-12-17 19:56                                                 ` H. Peter Anvin
2010-12-17 20:11                                                   ` Vivek Goyal
2010-12-17 20:59                                                     ` H. Peter Anvin
2010-12-17 21:13                                                       ` Vivek Goyal
2010-12-20 16:31                                                   ` Stanislaw Gruszka
2010-12-18  4:34                                                 ` [tip:x86/urgent] x86, kexec: Limit the crashkernel address appropriately tip-bot for H. Peter Anvin
2010-12-17 19:50                                               ` kdump broken on 2.6.37-rc4 H. Peter Anvin
2010-12-13 10:25                   ` Américo Wang
2010-12-13 10:25                     ` Américo Wang
2010-12-05 14:35 ` Maciej Rutecki
2010-12-05 14:35   ` Maciej Rutecki

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=4D0BC2BF.5010400@kernel.org \
    --to=yinghai@kernel.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=muvarov@gmail.com \
    --cc=nhorman@redhat.com \
    --cc=sgruszka@redhat.com \
    --cc=tglx@linutronix.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.