All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 27052] Module KVM : unable to handle kernel NULL pointer dereference at
Date: Tue, 8 Feb 2011 10:50:15 GMT	[thread overview]
Message-ID: <201102081050.p18AoF0X003116@demeter1.kernel.org> (raw)
In-Reply-To: <bug-27052-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=27052





--- Comment #20 from prochazka <prochazka.nicolas@gmail.com>  2011-02-08 10:50:13 ---
gfn=fffffffffffff001 idx=511 lvl=1 d=0 spte=0
sp->gfns[511] = fffffffffffff001
sp->gfns[511] = fffffffffffff001
sp->gfns[511] = fffffffffffff001
sp->gfns[510] = fffffffffffff001
sp->gfns[509] = fffffffffffff001
sp->gfns[508] = fffffffffffff001
sp->gfns[507] = fffffffffffff001
------------[ cut here ]------------
kernel BUG at arch/x86/kvm/mmu.c:727!
invalid opcode: 0000 [#1] SMP 
last sysfs file: /sys/devices/system/cpu/cpu7/cache/index2/shared_cpu_map
CPU 2 
Modules linked in: kvm_intel kvm bnx2 [last unloaded: kvm]

Pid: 29624, comm: qemu Not tainted 2.6.37 #4 0P010H/PowerEdge M600
RIP: 0010:[<ffffffffa009d7eb>]  [<ffffffffa009d7eb>] drop_spte+0x2ab/0x2b0
[kvm]
RSP: 0018:ffff8802be535a08  EFLAGS: 00010246
RAX: 0000000000000027 RBX: ffff8802ca8dbff8 RCX: 000000000003ffff
RDX: ffffffff81d550c8 RSI: 0000000000000082 RDI: 0000000000000246
RBP: ffff8802be535a28 R08: 000000000001705a R09: 0000000000000000
R10: 0000000000000000 R11: 000000000000000f R12: fffffffffffff001
R13: ffff8802c47098c0 R14: ffff8802be744000 R15: ffff8802be535a84
FS:  00007f2090ae7710(0000) GS:ffff8800bfc80000(0000) knlGS:0000000000000000
CS:  0010 DS: 002b ES: 002b CR0: 000000008005003b
CR2: 0000000001110000 CR3: 00000002c228a000 CR4: 00000000000426e0
DR0: 0000000000000090 DR1: 00000000000000a4 DR2: 00000000000000ff
DR3: 000000000000000f DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process qemu (pid: 29624, threadinfo ffff8802be534000, task ffff8807fe060000)
Stack:
 0000000000000ff8 ffff8802c47098c0 0000000009a7effc ffff8802fb9a3490
 ffff8802be535ab8 ffffffffa00a22a5 0000000000000001 000000000000fa03
 0000000000455c03 ffff880200000001 ffff880200000000 ffffffff00000001
Call Trace:
 [<ffffffffa00a22a5>] paging32_sync_page+0xe5/0x1c0 [kvm]
 [<ffffffffa009df9a>] __kvm_sync_page+0x5a/0xb0 [kvm]
 [<ffffffffa00a08d9>] mmu_sync_children+0x249/0x350 [kvm]
 [<ffffffff819a529e>] ? _raw_spin_lock+0xe/0x20
 [<ffffffffa00af073>] ? pic_unlock+0x23/0xb0 [kvm]
 [<ffffffffa00aef6a>] ? pic_update_irq+0x7a/0xf0 [kvm]
 [<ffffffffa00af388>] ? picdev_write+0x158/0x3d0 [kvm]
 [<ffffffff8100398e>] ? apic_timer_interrupt+0xe/0x20
 [<ffffffffa00a1535>] ? kvm_mmu_get_page+0x4b5/0x710 [kvm]
 [<ffffffffa00a0aa8>] mmu_sync_roots+0xc8/0x160 [kvm]
 [<ffffffffa00a1810>] kvm_mmu_load+0x80/0x420 [kvm]
 [<ffffffffa00987e5>] kvm_arch_vcpu_ioctl_run+0xc95/0xe20 [kvm]
 [<ffffffffa0086811>] kvm_vcpu_ioctl+0x561/0x860 [kvm]
 [<ffffffff8112176a>] ? do_readv_writev+0x1aa/0x1f0
 [<ffffffff81131087>] do_vfs_ioctl+0xa7/0x560
 [<ffffffff810840fe>] ? sys_futex+0xce/0x170
 [<ffffffff8113158f>] sys_ioctl+0x4f/0x80
 [<ffffffff81003042>] system_call_fastpath+0x16/0x1b
Code: 0f 4c 89 e6 41 c0 e8 05 48 89 da 41 83 e0 01 49 2b 55 30 48 c7 c7 38 a5
0b a0 48 c1 fa 03 e8 21 4f 90 e1 48 89 df e8 f5 fb ff ff <0f> 0b eb fe 90 55 48
89 e5 41 55 41 54 53 48 83 ec 08 0f 1f 44 
RIP  [<ffffffffa009d7eb>] drop_spte+0x2ab/0x2b0 [kvm]
 RSP <ffff8802be535a08>
---[ end trace 37175e4ac115e78c ]---

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2011-02-08 10:50 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-19 10:04 [Bug 27052] New: Module KVM : unable to handle kernel NULL pointer dereference at bugzilla-daemon
2011-01-19 11:06 ` [Bug 27052] " bugzilla-daemon
2011-01-19 11:26 ` bugzilla-daemon
2011-01-19 11:34 ` bugzilla-daemon
2011-01-20 17:29 ` bugzilla-daemon
2011-01-20 17:30 ` bugzilla-daemon
2011-01-20 19:45 ` bugzilla-daemon
2011-01-21  3:27 ` bugzilla-daemon
2011-01-21  3:29 ` bugzilla-daemon
2011-01-25  8:49 ` bugzilla-daemon
2011-01-25 13:09 ` bugzilla-daemon
2011-01-25 13:35 ` bugzilla-daemon
2011-01-25 13:55 ` bugzilla-daemon
2011-01-25 17:08 ` bugzilla-daemon
2011-01-25 17:08 ` bugzilla-daemon
2011-01-25 17:29 ` bugzilla-daemon
2011-01-28  6:58 ` bugzilla-daemon
2011-02-04 21:11 ` bugzilla-daemon
2011-02-04 21:13 ` bugzilla-daemon
2011-02-08  9:46 ` bugzilla-daemon
2011-02-08 10:50 ` bugzilla-daemon [this message]
2011-02-10  8:25 ` bugzilla-daemon
2011-02-10 13:36 ` bugzilla-daemon
2011-02-10 13:50 ` bugzilla-daemon
2011-02-10 14:14 ` bugzilla-daemon
2011-02-10 14:16 ` bugzilla-daemon
2011-02-10 16:57 ` bugzilla-daemon
2011-02-10 16:58 ` bugzilla-daemon
2011-02-11 15:43 ` bugzilla-daemon
2011-02-11 21:33 ` bugzilla-daemon
2011-02-12 17:06 ` bugzilla-daemon
2011-02-13 16:11 ` bugzilla-daemon
2011-02-13 16:38 ` bugzilla-daemon
2011-02-13 19:39 ` bugzilla-daemon
2011-02-13 20:13 ` bugzilla-daemon
2011-02-14 14:52 ` bugzilla-daemon
2011-02-14 15:50 ` bugzilla-daemon
2011-02-14 15:51 ` bugzilla-daemon
2011-02-14 16:02 ` bugzilla-daemon
2011-04-21 11:45 ` bugzilla-daemon
2011-04-21 12:13 ` bugzilla-daemon
2011-04-21 12:39 ` bugzilla-daemon

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=201102081050.p18AoF0X003116@demeter1.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.org \
    /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.