All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Edge <bruce.edge@gmail.com>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [Question] Has anyone tried kexec/kdump
Date: Tue, 7 Sep 2010 15:38:05 -0700	[thread overview]
Message-ID: <AANLkTikPu2owF_P=Ht5zqpV+seWSeR_=5zcDEUahkc-Z@mail.gmail.com> (raw)
In-Reply-To: <789F9655DD1B8F43B48D77C5D30659731D8B3BED@shsmsx501.ccr.corp.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 4960 bytes --]

On Wed, Apr 28, 2010 at 2:07 AM, Jiang, Yunhong <yunhong.jiang@intel.com>wrote:

> I tried kexec on xen environment and get followed error. Does anyone meet
> similar issues? Does anyone try kexec/kdump recendly?
>

Did you ever get this working?

I noticed that the kdump docs state that you have to have CONFIG_SMP=n
(Documentation/kdump/kdump.txt), this seems like a huge limitation in this
era of multicore machines.

-Bruce


> Xen Changeset: 21230:c87ec146229a and Dom0 is pvops dom0.
>
> Thanks
> --jyh
>
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.491275] BUG: unable to handle
> kernel NULL pointer dereference at (null)
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] IP: [<ffffffff8102c39a>]
> xen_page_pinned+0x1d/0x3c
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] PGD 11006067 PUD
> 11078067 PMD 0
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] Oops: 0000 [#1] SMP
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] last sysfs file:
> /sys/module/libata/version
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] CPU 0
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] Modules linked in: igb
> sg sr_mod cdrom ata_generic pata_acpi ahci ide_gd_mod ide_core usb_storage
> ata_piix libata sd_mod scsi_mod ehci_hcd ohci_hcd uhci_hcd
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] Pid: 3591, comm: kexec
> Not tainted 2.6.31.13 #1 To Be Filled By O.E.M.
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] RIP:
> e030:[<ffffffff8102c39a>]  [<ffffffff8102c39a>] xen_page_pinned+0x1d/0x3c
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] RSP:
> e02b:ffff880011011e18  EFLAGS: 00010246
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] RAX: 0000000000000000
> RBX: 0000000780000000 RCX: ffff880011011e38
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] RDX: 0000000000000000
> RSI: 000000002dbb4063 RDI: 00000000000f0000
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] RBP: ffff880011011e28
> R08: 0000000000000003 R09: ffff880011011e38
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] R10: ffff880011011e38
> R11: 0000000000000002 R12: ffff880011004000
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] R13: 0000000000000001
> R14: 000000002dbb4063 R15: ffff88001104f000
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] FS:
>  00007f0311e606f0(0000) GS:ffffc90000000000(0000) knlGS:0000000000000000
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] CS:  e033 DS: 0000 ES:
> 0000 CR0: 000000008005003b
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] CR2: 0000000000000000
> CR3: 00000000110a1000 CR4: 0000000000002660
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] DR0: 0000000000000000
> DR1: 0000000000000000 DR2: 0000000000000000
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] DR3: 0000000000000000
> DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] Process kexec (pid:
> 3591, threadinfo ffff880011010000, task ffff880011893c80)
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] Stack:
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003]  ffff880011004000
> ffff880011004000 ffff880011011e58 ffffffff8102d58d
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] <0> ffff880011004000
> 0000000040000000 ffff880011039000 0000008000000000
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] <0> ffff880011011e68
> ffffffff8104ab25 ffff880011011ee8 ffffffff8104b1ea
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] Call Trace:
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003]  [<ffffffff8102d58d>]
> xen_set_pgd+0x41/0xba
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003]  [<ffffffff8104ab25>]
> set_pgd+0x17/0x1b
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003]  [<ffffffff8104b1ea>]
> machine_kexec_prepare+0x56b/0x60b
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003]  [<ffffffff81097110>]
> sys_kexec_load+0x27d/0x561
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003]  [<ffffffff81525bd0>] ?
> thread_return+0x7e/0x95
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003]  [<ffffffff810a6a68>] ?
> audit_syscall_entry+0xfe/0x12a
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003]  [<ffffffff81032c82>]
> system_call_fastpath+0x16/0x1b
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] Code: 48 89 c7 74 07 31
> f6 e8 c5 06 0a 00 c9 c3 55 48 89 e5 53 48 83 ec 08 e8 a9 a4 02 00 48 89 c3
> 48 c1 eb 0c 48 89 df e8 1a f6 ff ff <48> 8b 38 48 6b c3 38 48 83 e7 fc 48 01
> c7 e8 22 f6 ff ff 5a 5b
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] RIP
>  [<ffffffff8102c39a>] xen_page_pinned+0x1d/0x3c
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003]  RSP <ffff880011011e18>
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] CR2: 0000000000000000
> Apr 29 00:57:36 vt_wb_jimmy kernel: [   60.492003] ---[ end trace
> 4c3a1aad9172f2c6 ]---
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

[-- Attachment #1.2: Type: text/html, Size: 5680 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-09-07 22:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AcrmsjWgU23BSz2DQd2VwQ+UjdWZmg==>
2010-04-28  9:07 ` [Question] Has anyone tried kexec/kdump Jiang, Yunhong
2010-09-07 22:38   ` Bruce Edge [this message]
2010-09-08 14:42     ` Jiang, Yunhong
2010-09-08 16:18       ` Bruce Edge

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='AANLkTikPu2owF_P=Ht5zqpV+seWSeR_=5zcDEUahkc-Z@mail.gmail.com' \
    --to=bruce.edge@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yunhong.jiang@intel.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.