From: takahiro.akashi@linaro.org (AKASHI Takahiro) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v26 0/7] arm64: add kdump support Date: Wed, 5 Oct 2016 14:48:51 +0900 [thread overview] Message-ID: <20161005054849.GB19531@linaro.org> (raw) In-Reply-To: <70ca1b97-8de4-921f-0cef-e02a88691ccd@caviumnetworks.com> Manish, On Tue, Oct 04, 2016 at 06:53:28PM +0530, Manish Jaggi wrote: > > On 10/04/2016 04:23 PM, James Morse wrote: > > Hi Manish, > > > > On 04/10/16 11:05, Manish Jaggi wrote: > >> On 10/04/2016 03:16 PM, James Morse wrote: > >>> On 03/10/16 13:41, Manish Jaggi wrote: > >>>> On 10/03/2016 04:34 PM, AKASHI Takahiro wrote: > >>>>> On Mon, Oct 03, 2016 at 01:24:34PM +0530, Manish Jaggi wrote: > >>>>>> First kernel is booted with mem=2G crashkernel=1G command line option. > >>>>>> While the system has 64G memory. > >>> > >>>>> Are you saying that "mem=..." doesn't have any effect? > >>>> What I am saying it that If the first kernel is booted using mem= option and crashkernel= option > >>>> the memory for second kernel has to be withing the crashkernel size. > >>>> As per /proc/iomem System RAM the information is correct, but the /proc/meminfo is showing total memory > >>>> much more than the first kernel had in first place. > >>> > >>> So your second crashkernel has 63G of memory? Unless you provide the same 'mem=' > >>> to the kdump kernel, this is the expected behaviour. The > >>> DT:/reserved-memory/crash_dump describes the memory not to use. > >>> > >>> On your first boot with 'mem=2G' memblock_mem_limit_remove_map() called from > >>> arm64_memblock_init() removed the top 62G of memory. Neither the first kernel > >>> nor kexec-tools know about the top 62G. > >>> When you run kexec-tools, it describes what it sees in /proc/iomem in the > >>> DT:/reserved-memory/crash_dump, which is just the remaining 1G of memory. > >>> > >>> When we crash and reboot, the crash kernel discovers all 64G of memory from the > >>> EFI memory map. > > > >> So the iomem and meminfo should be same or different for the second kernel? > >> Also i assumed that crashkernel=1G should restrict the second kernels to 1G. > > > > Not with v26 of this series. What should it do with the 62G of memory that was > > removed by booting with 'mem=2G'? It isn't part of the crashkernel reserved > > area, and it isn't part of the vmcore described in elfcorehdr either... > > > > > >> This is my understanding from the description. It should not require a second mem= option > > > >>> kexec-tools described the 1G of memory that the first kernel was using in the > >>> DT:/reserved-memory/crash_dump node, so early_init_fdt_scan_reserved_mem() > >>> reserves the 1G of memory the first kernel used. This leaves us with 63G of memory. > >>> > >>> This may change with the next version of kdump if it switches back to using > >>> DT:/chosen/linux,usable-memory-range. > >>> If you need v26 to avoid the top 62G of memory, you need to provide the same > >>> 'mem=' to the first and second kernel. > > > >> If I provide for second kernel, I dont see any prints after Bye. > >> Have you tired this anytime? > > > > Yes, on juno-r1 passing 'mem=2G' to both the first and second kernel causes only > > the first 2G of memory to be used with this pattern: > > first kernel: [1G used for linux] [1G reserved for Crash kernel] [6G memory > > hidden] > > kdump kernel: [1G vmcore] [1G used for linux] [6G memory hidden] > > > > > Oh, ok! > I was giving mem=1G to crashkernel to test. with mem=2G it works. I didn't know that you specified "mem=1G" in our local discussions ... > >>>>>> 1.2 Live crash dump fails with error > >>> > >>> ... do we expect this to work? I don't think it has anything to do with this > >>> series... > >>> > >> Why it should not? > >> I saved the vmcore file while in second kernel. Since crash without vmcore file didnt run, > >> Tried with vmcore file and it worked. Its just that if you want to boot a second kernel > >> with read only file system without network live crash dump analysis is handy. > > > > Ah, you want to run /usr/bin/crash with the kdump boot of linux. You still need > > to tell it where to find the memory image: "crash /path/to/vmlinux /proc/vmcore" > > should do the trick. > > > We should fix the documentation of kdump them. > Since it is not supported, it should be removed. Remove what? And can you please double-check if you still have any problem on a live system or with a saved core file? (except for "mem=" stuff) -Takahiro AKASHI > > Thanks, > > > > James > >
WARNING: multiple messages have this Message-ID (diff)
From: AKASHI Takahiro <takahiro.akashi@linaro.org> To: Manish Jaggi <mjaggi@caviumnetworks.com> Cc: mark.rutland@arm.com, geoff@infradead.org, catalin.marinas@arm.com, kexec@lists.infradead.org, will.deacon@arm.com, "Kapoor, Prasun" <Prasun.Kapoor@caviumnetworks.com>, James Morse <james.morse@arm.com>, bauerman@linux.vnet.ibm.com, dyoung@redhat.com, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v26 0/7] arm64: add kdump support Date: Wed, 5 Oct 2016 14:48:51 +0900 [thread overview] Message-ID: <20161005054849.GB19531@linaro.org> (raw) In-Reply-To: <70ca1b97-8de4-921f-0cef-e02a88691ccd@caviumnetworks.com> Manish, On Tue, Oct 04, 2016 at 06:53:28PM +0530, Manish Jaggi wrote: > > On 10/04/2016 04:23 PM, James Morse wrote: > > Hi Manish, > > > > On 04/10/16 11:05, Manish Jaggi wrote: > >> On 10/04/2016 03:16 PM, James Morse wrote: > >>> On 03/10/16 13:41, Manish Jaggi wrote: > >>>> On 10/03/2016 04:34 PM, AKASHI Takahiro wrote: > >>>>> On Mon, Oct 03, 2016 at 01:24:34PM +0530, Manish Jaggi wrote: > >>>>>> First kernel is booted with mem=2G crashkernel=1G command line option. > >>>>>> While the system has 64G memory. > >>> > >>>>> Are you saying that "mem=..." doesn't have any effect? > >>>> What I am saying it that If the first kernel is booted using mem= option and crashkernel= option > >>>> the memory for second kernel has to be withing the crashkernel size. > >>>> As per /proc/iomem System RAM the information is correct, but the /proc/meminfo is showing total memory > >>>> much more than the first kernel had in first place. > >>> > >>> So your second crashkernel has 63G of memory? Unless you provide the same 'mem=' > >>> to the kdump kernel, this is the expected behaviour. The > >>> DT:/reserved-memory/crash_dump describes the memory not to use. > >>> > >>> On your first boot with 'mem=2G' memblock_mem_limit_remove_map() called from > >>> arm64_memblock_init() removed the top 62G of memory. Neither the first kernel > >>> nor kexec-tools know about the top 62G. > >>> When you run kexec-tools, it describes what it sees in /proc/iomem in the > >>> DT:/reserved-memory/crash_dump, which is just the remaining 1G of memory. > >>> > >>> When we crash and reboot, the crash kernel discovers all 64G of memory from the > >>> EFI memory map. > > > >> So the iomem and meminfo should be same or different for the second kernel? > >> Also i assumed that crashkernel=1G should restrict the second kernels to 1G. > > > > Not with v26 of this series. What should it do with the 62G of memory that was > > removed by booting with 'mem=2G'? It isn't part of the crashkernel reserved > > area, and it isn't part of the vmcore described in elfcorehdr either... > > > > > >> This is my understanding from the description. It should not require a second mem= option > > > >>> kexec-tools described the 1G of memory that the first kernel was using in the > >>> DT:/reserved-memory/crash_dump node, so early_init_fdt_scan_reserved_mem() > >>> reserves the 1G of memory the first kernel used. This leaves us with 63G of memory. > >>> > >>> This may change with the next version of kdump if it switches back to using > >>> DT:/chosen/linux,usable-memory-range. > >>> If you need v26 to avoid the top 62G of memory, you need to provide the same > >>> 'mem=' to the first and second kernel. > > > >> If I provide for second kernel, I dont see any prints after Bye. > >> Have you tired this anytime? > > > > Yes, on juno-r1 passing 'mem=2G' to both the first and second kernel causes only > > the first 2G of memory to be used with this pattern: > > first kernel: [1G used for linux] [1G reserved for Crash kernel] [6G memory > > hidden] > > kdump kernel: [1G vmcore] [1G used for linux] [6G memory hidden] > > > > > Oh, ok! > I was giving mem=1G to crashkernel to test. with mem=2G it works. I didn't know that you specified "mem=1G" in our local discussions ... > >>>>>> 1.2 Live crash dump fails with error > >>> > >>> ... do we expect this to work? I don't think it has anything to do with this > >>> series... > >>> > >> Why it should not? > >> I saved the vmcore file while in second kernel. Since crash without vmcore file didnt run, > >> Tried with vmcore file and it worked. Its just that if you want to boot a second kernel > >> with read only file system without network live crash dump analysis is handy. > > > > Ah, you want to run /usr/bin/crash with the kdump boot of linux. You still need > > to tell it where to find the memory image: "crash /path/to/vmlinux /proc/vmcore" > > should do the trick. > > > We should fix the documentation of kdump them. > Since it is not supported, it should be removed. Remove what? And can you please double-check if you still have any problem on a live system or with a saved core file? (except for "mem=" stuff) -Takahiro AKASHI > > Thanks, > > > > James > > _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2016-10-05 5:48 UTC|newest] Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-09-07 4:29 [PATCH v26 0/7] arm64: add kdump support AKASHI Takahiro 2016-09-07 4:29 ` AKASHI Takahiro 2016-09-07 4:29 ` [PATCH v26 1/7] arm64: kdump: reserve memory for crash dump kernel AKASHI Takahiro 2016-09-07 4:29 ` AKASHI Takahiro 2016-09-22 10:23 ` Matthias Bruger 2016-09-22 10:23 ` Matthias Bruger 2016-09-23 8:37 ` AKASHI Takahiro 2016-09-23 8:37 ` AKASHI Takahiro 2016-09-07 4:29 ` [PATCH v26 2/7] arm64: kdump: implement machine_crash_shutdown() AKASHI Takahiro 2016-09-07 4:29 ` AKASHI Takahiro 2016-09-14 18:09 ` James Morse 2016-09-14 18:09 ` James Morse 2016-09-15 8:13 ` Marc Zyngier 2016-09-15 8:13 ` Marc Zyngier 2016-09-16 3:21 ` AKASHI Takahiro 2016-09-16 3:21 ` AKASHI Takahiro 2016-09-16 14:49 ` James Morse 2016-09-16 14:49 ` James Morse 2016-09-20 7:36 ` AKASHI Takahiro 2016-09-20 7:36 ` AKASHI Takahiro 2016-09-07 4:29 ` [PATCH v26 3/7] arm64: kdump: add kdump support AKASHI Takahiro 2016-09-07 4:29 ` AKASHI Takahiro 2016-09-16 14:50 ` James Morse 2016-09-16 14:50 ` James Morse 2016-09-20 7:46 ` AKASHI Takahiro 2016-09-20 7:46 ` AKASHI Takahiro 2016-09-22 15:50 ` Matthias Brugger 2016-09-22 15:50 ` Matthias Brugger 2016-09-07 4:29 ` [PATCH v26 4/7] arm64: kdump: add VMCOREINFO's for user-space coredump tools AKASHI Takahiro 2016-09-07 4:29 ` AKASHI Takahiro 2016-09-16 16:04 ` James Morse 2016-09-16 16:04 ` James Morse 2016-09-07 4:29 ` [PATCH v26 5/7] arm64: kdump: enable kdump in the arm64 defconfig AKASHI Takahiro 2016-09-07 4:29 ` AKASHI Takahiro 2016-09-07 4:29 ` [PATCH v26 6/7] arm64: kdump: update a kernel doc AKASHI Takahiro 2016-09-07 4:29 ` AKASHI Takahiro 2016-09-16 16:08 ` James Morse 2016-09-16 16:08 ` James Morse 2016-09-20 8:27 ` AKASHI Takahiro 2016-09-20 8:27 ` AKASHI Takahiro 2016-09-26 17:21 ` Matthias Brugger 2016-09-26 17:21 ` Matthias Brugger [not found] ` <20160907042908.6232-1-takahiro.akashi-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> 2016-09-07 4:32 ` [PATCH v26 7/7] Documentation: dt: chosen properties for arm64 kdump AKASHI Takahiro 2016-09-07 4:32 ` AKASHI Takahiro 2016-09-07 4:32 ` AKASHI Takahiro [not found] ` <20160907043203.6309-1-takahiro.akashi-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> 2016-09-16 13:03 ` Rob Herring 2016-09-16 13:03 ` Rob Herring 2016-09-16 13:03 ` Rob Herring 2016-09-07 4:37 ` [PATCH v26 0/7] arm64: add kdump support AKASHI Takahiro 2016-09-07 4:37 ` AKASHI Takahiro 2016-09-16 16:04 ` James Morse 2016-09-16 16:04 ` James Morse 2016-09-16 20:17 ` Ard Biesheuvel 2016-09-16 20:17 ` Ard Biesheuvel 2016-09-19 16:05 ` James Morse 2016-09-19 16:05 ` James Morse 2016-09-19 16:10 ` Ard Biesheuvel 2016-09-19 16:10 ` Ard Biesheuvel 2016-09-21 7:42 ` AKASHI Takahiro 2016-09-21 7:42 ` AKASHI Takahiro 2016-09-21 7:33 ` AKASHI Takahiro 2016-09-21 7:33 ` AKASHI Takahiro 2016-10-03 7:54 ` Manish Jaggi 2016-10-03 7:54 ` Manish Jaggi 2016-10-03 11:04 ` AKASHI Takahiro 2016-10-03 11:04 ` AKASHI Takahiro 2016-10-03 12:41 ` Manish Jaggi 2016-10-03 12:41 ` Manish Jaggi 2016-10-04 2:56 ` AKASHI Takahiro 2016-10-04 2:56 ` AKASHI Takahiro 2016-10-04 9:46 ` James Morse 2016-10-04 9:46 ` James Morse 2016-10-04 10:05 ` Manish Jaggi 2016-10-04 10:05 ` Manish Jaggi 2016-10-04 10:53 ` James Morse 2016-10-04 10:53 ` James Morse 2016-10-04 13:23 ` Manish Jaggi 2016-10-04 13:23 ` Manish Jaggi 2016-10-05 5:48 ` AKASHI Takahiro [this message] 2016-10-05 5:48 ` AKASHI Takahiro 2016-10-05 5:41 ` AKASHI Takahiro 2016-10-05 5:41 ` AKASHI Takahiro 2016-10-04 10:18 ` Mark Rutland 2016-10-04 10:18 ` Mark Rutland 2016-10-17 15:41 ` Ruslan Bilovol 2016-10-17 15:41 ` Ruslan Bilovol 2016-10-18 6:26 ` AKASHI Takahiro 2016-10-18 6:26 ` AKASHI Takahiro 2016-11-01 12:19 ` Ruslan Bilovol 2016-11-01 12:19 ` Ruslan Bilovol
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=20161005054849.GB19531@linaro.org \ --to=takahiro.akashi@linaro.org \ --cc=linux-arm-kernel@lists.infradead.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: linkBe 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.