All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 27052] New: Module KVM : unable to handle kernel NULL pointer dereference at
Date: Wed, 19 Jan 2011 10:04:07 GMT	[thread overview]
Message-ID: <bug-27052-28872@https.bugzilla.kernel.org/> (raw)

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

           Summary: Module KVM : unable to handle kernel NULL pointer
                    dereference at
           Product: Virtualization
           Version: unspecified
    Kernel Version: 2.6.37
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: kvm
        AssignedTo: virtualization_kvm@kernel-bugs.osdl.org
        ReportedBy: prochazka.nicolas@gmail.com
        Regression: No


Hello, 
last git tree for qemu-kvm, kernel 2.6.37 , after some time guests ( Windows
XP) qemu-kvm vms causes this : 
( it seems to be specifiq on some server, here NecEXPRESS 5800 ) It is
difficult to me to reproduce this problem ( not access to this server ) . On
this server, bug is reproductible 100 % 


BUG: unable to handle kernel NULL pointer dereference at           (null)
IP: [<ffffffffa001c38a>] gfn_to_rmap+0x2a/0x70 [kvm]
PGD 1ca9c3067 PUD 1ccba0067 PMD 0
Oops: 0000 [#1] SMP
last sysfs file: /sys/devices/system/cpu/cpu7/cache/index2/shared_cpu_map
CPU 3
Modules linked in: kvm_intel kvm

Pid: 17700, comm: qemu Not tainted 2.6.37 #3 MS-9192-01S/Express5800/120Rh-1
[N8100-xxxxF]
RIP: 0010:[<ffffffffa001c38a>]  [<ffffffffa001c38a>] gfn_to_rmap+0x2a/0x70
[kvm]
RSP: 0018:ffff8801caa179f8  EFLAGS: 00010246
RAX: 0000000000000000 RBX: fffffffffffff001 RCX: ffff8801ca14e948
RDX: 0000000000000000 RSI: fffffffffffff001 RDI: 00000000000fee01
RBP: ffff8801caa17a08 R08: ffff8801ca14e000 R09: 0000000000000022
R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000001
R13: 0000000009204ffc R14: ffff8801ca990000 R15: ffff8801caa17a84
FS:  00007f0c0ab6f710(0000) GS:ffff8800cfcc0000(0000) knlGS:0000000000000000
CS:  0010 DS: 002b ES: 002b CR0: 000000008005003b
CR2: 0000000000000000 CR3: 00000001cb8b7000 CR4: 00000000000026e0
DR0: 00000000000000a0 DR1: 0000000000000000 DR2: 0000000000000003
DR3: 00000000000000b0 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process qemu (pid: 17700, threadinfo ffff8801caa16000, task ffff8802463b4000)
Stack:
 ffff88019f29fff8 ffff8801ca954000 ffff8801caa17a28 ffffffffa001c44c
 0000000000000ff8 ffff880208c2d820 ffff8801caa17ab8 ffffffffa0021075
 0000000400000001 0000000000005f99 0000000000424f99 0000000000000001
Call Trace:
 [<ffffffffa001c44c>] drop_spte+0x7c/0x1f0 [kvm]
 [<ffffffffa0021075>] paging32_sync_page+0xe5/0x1c0 [kvm]
 [<ffffffffa001cd6a>] __kvm_sync_page+0x5a/0xb0 [kvm]
 [<ffffffffa001f6a9>] mmu_sync_children+0x249/0x350 [kvm]
 [<ffffffffa00217ca>] ? kvm_mmu_pte_write+0x29a/0xaa0 [kvm]
 [<ffffffffa00238aa>] ? seg_base+0x1a/0x30 [kvm]
 [<ffffffffa001d4b2>] ? mmu_free_roots+0xc2/0x180 [kvm]
 [<ffffffffa0020305>] ? kvm_mmu_get_page+0x4b5/0x710 [kvm]
 [<ffffffffa001f878>] mmu_sync_roots+0xc8/0x160 [kvm]
 [<ffffffffa00205e0>] kvm_mmu_load+0x80/0x420 [kvm]
 [<ffffffffa00177e5>] kvm_arch_vcpu_ioctl_run+0xc95/0xe20 [kvm]
 [<ffffffff81081800>] ? wake_futex+0x40/0x60
 [<ffffffffa0015fc0>] ? kvm_arch_vcpu_load+0x50/0x140 [kvm]
 [<ffffffffa0005811>] kvm_vcpu_ioctl+0x561/0x860 [kvm]
 [<ffffffff819aeeac>] ? schedule+0x31c/0x990
 [<ffffffff81131087>] do_vfs_ioctl+0xa7/0x560
 [<ffffffff81122b44>] ? fput+0x34/0x280
 [<ffffffff810840fe>] ? sys_futex+0xce/0x170
 [<ffffffff8113158f>] sys_ioctl+0x4f/0x80
 [<ffffffff81003042>] system_call_fastpath+0x16/0x1b
Code: 00 55 48 89 e5 48 83 ec 10 48 89 1c 24 4c 89 64 24 08 0f 1f 44 00 00 41
89 d4 48 89 f3 e8                                    af 3d fe ff 41 83 fc 01 48
89 c2 75 1a <48> 2b 18 48 8d 04 dd 00 00 00 00 48 03 42 18 48 8b 1c            
                       24 4c 8b
RIP  [<ffffffffa001c38a>] gfn_to_rmap+0x2a/0x70 [kvm]
 RSP <ffff8801caa179f8>
CR2: 0000000000000000
---[ end trace 02041dca60973834 ]---

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

             reply	other threads:[~2011-01-19 10:04 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-19 10:04 bugzilla-daemon [this message]
2011-01-19 11:06 ` [Bug 27052] Module KVM : unable to handle kernel NULL pointer dereference at 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
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=bug-27052-28872@https.bugzilla.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.