[ kvm-Bugs-1848393 ] crash in vmx; most likely linked to suspend/resume

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Bugs item #1848393, was opened at 2007-12-11 06:51
Message generated for change (Comment added) made by jessorensen
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1848393&group_id=180599

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: kernel
Group: None
>Status: Closed
>Resolution: Out of Date
Priority: 8
Private: No
Submitted By: Amit Shah (amitshah)
Assigned to: Nobody/Anonymous (nobody)
Summary: crash in vmx; most likely linked to suspend/resume

Initial Comment:
This is repeatable only after suspend-to-disk and resume.

The following stack trace is obtained on running a guest.

[ 1159.163996] invalid opcode: 0000 [2] SMP
[ 1159.164001] CPU 1
[ 1159.164071] Pid: 14327, comm: qemu-system-x86 Tainted: G    B  2.6.22-14-generic #1
[ 1159.164074] RIP: 0010:[<ffffffff884974dd>]  [<ffffffff884974dd>] :kvm_intel:vmx_vcpu_load+0x5d/0x110
[ 1159.164083] RSP: 0018:ffff81000254fc98  EFLAGS: 00010287
[ 1159.164086] RAX: ffff81000254fcb0 RBX: ffff81003cf80000 RCX: ffff810080a48000
[ 1159.164089] RDX: ffffffff805d1900 RSI: 0000000000000286 RDI: ffff81000100f740
[ 1159.164091] RBP: 0000000000000001 R08: 0000000000000001 R09: 0000000000000003
[ 1159.164093] R10: 0000000000000000 R11: ffffffff88497480 R12: 0000000000000000
[ 1159.164096] R13: 000000000000ae80 R14: 000000000000ae80 R15: 0000000000000001
[ 1159.164099] FS:  00002b26a842d5d0(0000) GS:ffff810001026280(0000) knlGS:0000000000000000
[ 1159.164102] CS:  0010 DS: 002b ES: 002b CR0: 000000008005003b
[ 1159.164104] CR2: 00002b69b4efc000 CR3: 0000000037eb6000 CR4: 00000000000006a0
[ 1159.164107] Process qemu-system-x86 (pid: 14327, threadinfo ffff81000254e000, task ffff8100288e74a0)
[ 1159.164109] Stack:  ffff81003cf80000 0000000000000001 000000000000ae80 000000003ccf8000
[ 1159.164114]  0000000000000000 ffff81003cf80000 ffff81003cd23000 ffffffff884794b3
[ 1159.164119]  0000000010002800 0000000000000001 0000000000000000 ffff81003cf80000
[ 1159.164123] Call Trace:
[ 1159.164140]  [<ffffffff884794b3>] :kvm:kvm_arch_vcpu_ioctl_run+0x13/0x460
[ 1159.164153]  [<ffffffff88475c4f>] :kvm:kvm_vcpu_ioctl+0x35f/0x3a0
[ 1159.164161]  [<ffffffff803ab002>] sock_aio_write+0x172/0x190
[ 1159.164175]  [<ffffffff802a84f5>] core_sys_select+0x275/0x300
[ 1159.164192]  [<ffffffff80240719>] __dequeue_signal+0x19/0x1d0
[ 1159.164199]  [<ffffffff8023ffce>] recalc_sigpending+0xe/0x30
[ 1159.164203]  [<ffffffff8024212c>] dequeue_signal+0x5c/0x190
[ 1159.164211]  [<ffffffff8042ffa7>] thread_return+0x0/0x6c9
[ 1159.164216]  [<ffffffff802a6e05>] do_ioctl+0x35/0xe0
[ 1159.164222]  [<ffffffff802a6f24>] vfs_ioctl+0x74/0x2d0
[ 1159.164229]  [<ffffffff802a7215>] sys_ioctl+0x95/0xb0
[ 1159.164237]  [<ffffffff80209e8e>] system_call+0x7e/0x83
[ 1159.164248]
[ 1159.164249]
[ 1159.164250] Code: 0f c7 30 0f 96 c0 84 c0 0f 85 85 00 00 00 3b 6b 48 74 77 89
[ 1159.164259] RIP  [<ffffffff884974dd>] :kvm_intel:vmx_vcpu_load+0x5d/0x110
[ 1159.164265]  RSP <ffff81000254fc98>


relevant vmx_vcpu_load objdump output:

 2288:       48 89 df                mov    %rbx,%rdi
    228b:       e8 60 ff ff ff          callq  21f0 <vcpu_clear>
    2290:       48 89 df                mov    %rbx,%rdi
    2293:       e8 00 00 00 00          callq  2298 <vmx_vcpu_load+0x58>
                        2294: R_X86_64_PC32     kvm_migrate_apic_timer-0x4
    2298:       48 8b 8b 90 14 00 00    mov    0x1490(%rbx),%rcx
    229f:       48 63 c5                movslq %ebp,%rax
    22a2:       48 c7 c2 00 00 00 00    mov    $0x0,%rdx
                        22a5: R_X86_64_32S      .data.percpu+0x8
    22a9:       48 8b 04 c5 00 00 00    mov    0x0(,%rax,8),%rax
    22b0:       00
                        22ad: R_X86_64_32S      _cpu_pda

The crash happens at 0x229d.

rmmod kvm-intel results in a segfault with a different panic:

[ 1220.845622] Pid: 14351, comm: rmmod Tainted: G    B  2.6.22-14-generic #1
[ 1220.845627] RIP: 0010:[<ffffffff88495350>]  [<ffffffff88495350>] :kvm_intel:hardware_disable+0x0/0x10
[ 1220.845641] RSP: 0018:ffff81000125fec0  EFLAGS: 00010096
[ 1220.845645] RAX: ffffffff8849bde0 RBX: 0000000000000000 RCX: 0000000000000001
[ 1220.845650] RDX: 0000000000000000 RSI: 00000000000000fc RDI: 0000000000000000
[ 1220.845655] RBP: ffffffff8849c080 R08: 0000000000000000 R09: 0000000000000000
[ 1220.845659] R10: 0000000000000001 R11: ffffffff88495350 R12: 0000000000000000
[ 1220.845665] R13: ffffffff88474bc0 R14: 00007fff5c1dfe80 R15: 0000000000000880
[ 1220.845671] FS:  00002af54ee3d6e0(0000) GS:ffff810001026280(0000) knlGS:0000000000000000
[ 1220.845676] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 1220.845681] CR2: 00007ffff33e3350 CR3: 0000000030127000 CR4: 00000000000006a0
[ 1220.845687] Process rmmod (pid: 14351, threadinfo ffff81000125e000, task ffff81003eb5b4a0)
[ 1220.845691] Stack:  ffffffff8023ad66 0000000000000000 0000000000000880 0000000000000000
[ 1220.845701]  ffffffff88474b81 0000000000000000 ffffffff80258887 65746e695f6d766b
[ 1220.845710]  ffffffff804e006c 0000000000000014 0000000b0000000e 0000000000000296
[ 1220.845717] Call Trace:
[ 1220.845724]  [<ffffffff8023ad66>] on_each_cpu+0x26/0x40
[ 1220.845746]  [<ffffffff88474b81>] :kvm:kvm_exit+0x61/0xa0
[ 1220.845755]  [<ffffffff80258887>] sys_delete_module+0x167/0x1f0
[ 1220.845783]  [<ffffffff80209e8e>] system_call+0x7e/0x83
[ 1220.845805]
[ 1220.845807]
[ 1220.845809] Code: 0f 01 c4 c3 66 66 66 2e 0f 1f 84 00 00 00 00 00 8b 87 04 24
[ 1220.845827] RIP  [<ffffffff88495350>] :kvm_intel:hardware_disable+0x0/0x10
[ 1220.845837]  RSP <ffff81000125fec0>


----------------------------------------------------------------------

>Comment By: Jes Sorensen (jessorensen)
Date: 2010-06-18 14:02

Message:
Spoke to Amit about this one and he said it is no longer an issue, so
closing


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1848393&group_id=180599
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux