All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: CAI Qian <caiqian@redhat.com>
Cc: graff.yang@gmail.com, Marcelo Tosatti <mtosatti@redhat.com>,
	kexec <kexec@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	dhowells@redhat.com, sonic.adi@gmail.com,
	Avi Kivity <avi@redhat.com>
Subject: Re: kvm kdump regression
Date: Tue, 14 Sep 2010 10:26:17 +0200	[thread overview]
Message-ID: <4C8F31A9.7070507@kernel.org> (raw)
In-Reply-To: <149379123.860951284433779554.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>

On 09/14/2010 05:09 AM, CAI Qian wrote:
> This commit introduced a regression that an empty vmcore was generated on a kvm guest.
> ioremap: invalid physical address db74000000000000
> ------------[ cut here ]------------
> WARNING: at arch/x86/mm/ioremap.c:83 __ioremap_caller+0x307/0x380()
> Hardware name: KVM
> Modules linked in:
> Pid: 1, comm: swapper Not tainted 2.6.36-rc2-mm1+ #2
> Call Trace:
>  [<ffffffff8105f48f>] warn_slowpath_common+0x7f/0xc0
>  [<ffffffff8103052e>] ? copy_oldmem_page+0x4e/0xc0
>  [<ffffffff8105f4ea>] warn_slowpath_null+0x1a/0x20
>  [<ffffffff8103f0a7>] __ioremap_caller+0x307/0x380
>  [<ffffffff8103f1f7>] ioremap_nocache+0x17/0x20
>  [<ffffffff8103052e>] copy_oldmem_page+0x4e/0xc0
>  [<ffffffff811af4ca>] read_from_oldmem+0x7a/0xb0
>  [<ffffffff81c4f70b>] merge_note_headers_elf64.clone.1+0x6c/0x21f
>  [<ffffffff8103056e>] ? copy_oldmem_page+0x8e/0xc0
>  [<ffffffff811af4ca>] ? read_from_oldmem+0x7a/0xb0
>  [<ffffffff81c4fa5b>] vmcore_init+0x19d/0x396
>  [<ffffffff81c4f8be>] ? vmcore_init+0x0/0x396
>  [<ffffffff81002053>] do_one_initcall+0x43/0x190
>  [<ffffffff81c278ab>] kernel_init+0x2a0/0x330
>  [<ffffffff8100be84>] kernel_thread_helper+0x4/0x10
>  [<ffffffff81c2760b>] ? kernel_init+0x0/0x330
>  [<ffffffff8100be80>] ? kernel_thread_helper+0x0/0x10
> ---[ end trace 93d72a36b9146f22 ]---
> Kdump: vmcore not initialized
> 
> commit 020ec6537aa65c18e9084c568d7b94727f2026fd
> Author: Tejun Heo <tj@kernel.org>
> Date:   Fri Apr 9 18:57:00 2010 +0900
> 
>     percpu: factor out pcpu_addr_in_first/reserved_chunk() and update per_cpu_ptr_to_phys()

Hmm... I'm confused.  Isn't this the one fixed by commit 9983b6f0
(percpu: fix first chunk match in per_cpu_ptr_to_phys())?

Thanks.

-- 
tejun

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org>
To: CAI Qian <caiqian@redhat.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Avi Kivity <avi@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	dhowells@redhat.com, graff.yang@gmail.com, sonic.adi@gmail.com,
	kexec <kexec@lists.infradead.org>
Subject: Re: kvm kdump regression
Date: Tue, 14 Sep 2010 10:26:17 +0200	[thread overview]
Message-ID: <4C8F31A9.7070507@kernel.org> (raw)
In-Reply-To: <149379123.860951284433779554.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>

On 09/14/2010 05:09 AM, CAI Qian wrote:
> This commit introduced a regression that an empty vmcore was generated on a kvm guest.
> ioremap: invalid physical address db74000000000000
> ------------[ cut here ]------------
> WARNING: at arch/x86/mm/ioremap.c:83 __ioremap_caller+0x307/0x380()
> Hardware name: KVM
> Modules linked in:
> Pid: 1, comm: swapper Not tainted 2.6.36-rc2-mm1+ #2
> Call Trace:
>  [<ffffffff8105f48f>] warn_slowpath_common+0x7f/0xc0
>  [<ffffffff8103052e>] ? copy_oldmem_page+0x4e/0xc0
>  [<ffffffff8105f4ea>] warn_slowpath_null+0x1a/0x20
>  [<ffffffff8103f0a7>] __ioremap_caller+0x307/0x380
>  [<ffffffff8103f1f7>] ioremap_nocache+0x17/0x20
>  [<ffffffff8103052e>] copy_oldmem_page+0x4e/0xc0
>  [<ffffffff811af4ca>] read_from_oldmem+0x7a/0xb0
>  [<ffffffff81c4f70b>] merge_note_headers_elf64.clone.1+0x6c/0x21f
>  [<ffffffff8103056e>] ? copy_oldmem_page+0x8e/0xc0
>  [<ffffffff811af4ca>] ? read_from_oldmem+0x7a/0xb0
>  [<ffffffff81c4fa5b>] vmcore_init+0x19d/0x396
>  [<ffffffff81c4f8be>] ? vmcore_init+0x0/0x396
>  [<ffffffff81002053>] do_one_initcall+0x43/0x190
>  [<ffffffff81c278ab>] kernel_init+0x2a0/0x330
>  [<ffffffff8100be84>] kernel_thread_helper+0x4/0x10
>  [<ffffffff81c2760b>] ? kernel_init+0x0/0x330
>  [<ffffffff8100be80>] ? kernel_thread_helper+0x0/0x10
> ---[ end trace 93d72a36b9146f22 ]---
> Kdump: vmcore not initialized
> 
> commit 020ec6537aa65c18e9084c568d7b94727f2026fd
> Author: Tejun Heo <tj@kernel.org>
> Date:   Fri Apr 9 18:57:00 2010 +0900
> 
>     percpu: factor out pcpu_addr_in_first/reserved_chunk() and update per_cpu_ptr_to_phys()

Hmm... I'm confused.  Isn't this the one fixed by commit 9983b6f0
(percpu: fix first chunk match in per_cpu_ptr_to_phys())?

Thanks.

-- 
tejun

  reply	other threads:[~2010-09-14  8:26 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-14  3:09 kvm kdump regression CAI Qian
2010-09-14  3:09 ` CAI Qian
2010-09-14  8:26 ` Tejun Heo [this message]
2010-09-14  8:26   ` Tejun Heo
2010-09-14  8:29   ` CAI Qian
2010-09-14  8:29     ` CAI Qian
2010-09-17 15:22     ` Tejun Heo
2010-09-17 15:22       ` Tejun Heo
2010-09-18 12:36       ` CAI Qian
2010-09-18 12:36         ` CAI Qian
2010-09-19 15:02         ` Tejun Heo
2010-09-19 15:02           ` Tejun Heo
2010-09-20  8:00           ` CAI Qian
2010-09-20  8:00             ` CAI Qian
2010-09-20  9:12             ` Tejun Heo
2010-09-20  9:12               ` Tejun Heo
2010-09-20  9:44               ` CAI Qian
2010-09-20  9:44                 ` CAI Qian
2010-09-20  9:49                 ` CAI Qian
2010-09-20  9:49                   ` CAI Qian
     [not found] <1888861854.1349971284977836487.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-09-20 10:17 ` caiqian
2010-09-20 10:17   ` caiqian
2010-09-20 23:09   ` Tejun Heo
2010-09-20 23:09     ` Tejun Heo
2010-09-21  0:40     ` CAI Qian
2010-09-21  0:40       ` CAI Qian

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=4C8F31A9.7070507@kernel.org \
    --to=tj@kernel.org \
    --cc=avi@redhat.com \
    --cc=caiqian@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=graff.yang@gmail.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=sonic.adi@gmail.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.