From: Luiz Capitulino <lcapitulino@redhat.com>
To: Rob Landley <rob@landley.net>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] x86-64 apic panic on shutdown on 1.4.93.
Date: Thu, 27 Jun 2013 09:44:20 -0400 [thread overview]
Message-ID: <20130627094420.0a294881@redhat.com> (raw)
In-Reply-To: <1372225951.2776.148@driftwood>
On Wed, 26 Jun 2013 00:52:31 -0500
Rob Landley <rob@landley.net> wrote:
> I intermittently get this from current kernels running under currentish
> qemu-git. Look familiar to anybody?
Which kernel do you run in the host? Is the guest doing anything
special?
>
> reboot: machine restart
> general protection fault: fff2 [#1]
> CPU: 0 PID: 44 Comm: oneit Not tainted 3.10.0-rc7+ #3
> Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
> task: ffff8800068fd500 ti: ffff880006a26000 task.ti: ffff880006a26000
> RIP: 0010:[<ffffffff81014441>] [<ffffffff81014441>]
> lapic_shutdown+0x32/0x34
> RSP: 0018:ffff880006a27e28 EFLAGS: 00000202
> RAX: 2193fbf9078bfbf9 RBX: 0000000000000202 RCX: 0000000000000000
> RDX: ffffffff81015f71 RSI: 00000000000000ff RDI: 00000000000000f0
> RBP: fffffffffee1dead R08: 0000000000000400 R09: 0000000000000000
> R10: 0000000000000000 R11: ffff88000699f500 R12: 0000000000000000
> R13: 0000000001234567 R14: 0000000000000004 R15: 0000000000423872
> FS: 0000000000000000(0000) GS:ffffffff81308000(0000)
> knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: 0000000000657ad0 CR3: 000000000697c000 CR4: 00000000000006b0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 0000000000000000 DR7: 0000000000000000
> Stack:
> 0000000028121969 ffffffff81013bda 00000000000003f9 ffffffff81013dc5
> 0000000000000000 ffffffff8102ad4b 0000000000000000 0000000000000000
> 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> Call Trace:
> [<ffffffff81013bda>] ? native_machine_shutdown+0x6/0x1a
> [<ffffffff81013dc5>] ? native_machine_restart+0x1d/0x31
> [<ffffffff8102ad4b>] ? SyS_reboot+0x126/0x15b
> [<ffffffff810374bc>] ? schedule_tail+0x1e/0x44
> [<ffffffff8122f57f>] ? ret_from_fork+0xf/0xb0
> [<ffffffff8122f690>] ? system_call_fastpath+0x16/0x1b
> Code: 53 f6 c4 02 75 1b 31 c0 83 3d af 42 50 00 00 74 0c 31 c0 83 3d b4
> 42 50 00 00 0f 94 c0 85 c0 74 0a 9c 5b fa e8 88 ff ff ff 53 9d <5b> c3
> 50 e8 11 ec 00 00 e8 d6 2f ff ff 48 8b 05 43 4b 32 00 bf
> RIP [<ffffffff81014441>] lapic_shutdown+0x32/0x34
> RSP <ffff880006a27e28>
> ---[ end trace dd3c376274d1a087 ]---
prev parent reply other threads:[~2013-06-27 13:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 5:52 [Qemu-devel] x86-64 apic panic on shutdown on 1.4.93 Rob Landley
2013-06-27 13:44 ` Luiz Capitulino [this message]
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=20130627094420.0a294881@redhat.com \
--to=lcapitulino@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=rob@landley.net \
/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.