From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mx1.redhat.com ([209.132.183.28]) by merlin.infradead.org with esmtp (Exim 4.76 #1 (Red Hat Linux)) id 1RQwG7-0002ow-1C for kexec@lists.infradead.org; Thu, 17 Nov 2011 07:19:44 +0000 Message-ID: <4EC4B60C.3030706@redhat.com> Date: Thu, 17 Nov 2011 15:21:48 +0800 From: Dave Young MIME-Version: 1.0 Subject: Re: Crash during vmcore_init References: <1318376345.2050.20.camel@boudreau> <1321296650.2066.17.camel@boudreau> <4EC21F67.10905@redhat.com> <1321396371.4198.5.camel@boudreau> <4EC31E55.6040809@redhat.com> <1321467647.2137.4.camel@boudreau> <4EC47FCA.5090908@redhat.com> <4EC491B3.705@redhat.com> In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: kexec-bounces@lists.infradead.org Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Tim Hartrick Cc: Tejun Heo , WANG Cong , kexec@lists.infradead.org, linux-kernel@vger.kernel.org On 11/17/2011 01:22 PM, Tim Hartrick wrote: > Tejun, Dave, > > I will be happy to answer any questions about our environment or test > debug or other patches. Just tell me what you need. Thank you. Can you share your kernel config? > > tim > > On Nov 16, 2011 8:44 PM, "Dave Young" > wrote: > > On 11/17/2011 12:34 PM, Tejun Heo wrote: > > > Hello, > > > > On Wed, Nov 16, 2011 at 7:30 PM, Dave Young > wrote: > >> This addr is converted to an invalid phys address, > > > > I'm a bit lost on the context here. Who's calling > per_cpu_ptr_to_phys()? > > > It's drivers/base/cpu.c : show_crash_notes() > > > > >> looking the code below: > >> if (in_first_chunk) { > >> if (!is_vmalloc_addr(addr)) > >> return __pa(addr); > >> else > >> return page_to_phys(vmalloc_to_page(addr)); > >> } else > >> return page_to_phys(pcpu_addr_to_page(addr)); > >> > >> I dont understand per cpu allocation well, if addr is not in > first chunk > >> then it should be in vmalloc area? > > > > Yes, it is. First chunk can be embedded in the kernel linear address > > space but from the second one, it's always set up from the top of the > > vmalloc area with the same offset layout as the first chunk. > > > in this case ffff880667c19ad0 fall out of vmalloc area and it's not in > first chunk also. > > > > >> Tejun, do you have any idea about this? > > > > Can you please tell me how to reproduce the problem? I'll try to find > > out what's going on. > > > make sure kernel support CRASH DUMP, then cat > /sys/devices/system/cpu/cpu[x]/crash_notes > > Tim Hartrick > reported > the problem when test kdump. > But I can not reproduce this. I think tim can help to test > > > > > Thanks. > > > > > > -- > Thanks > Dave > -- Thanks Dave _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec