From: Avi Kivity <avi@redhat.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Andrea Arcangeli <aarcange@redhat.com>
Subject: Re: 2.6.38.1 general protection fault
Date: Sat, 26 Mar 2011 11:15:00 +0200 [thread overview]
Message-ID: <4D8DAE94.7070604@redhat.com> (raw)
In-Reply-To: <4D8C6110.6090204@wpkg.org>
On 03/25/2011 11:32 AM, Tomasz Chmielewski wrote:
> I got this on a 2.6.38.1 system which (I think) had some problem accessing guest image on a btrfs filesystem.
>
>
> general protection fault: 0000 [#1] SMP
> last sysfs file: /sys/kernel/uevent_seqnum
> CPU 0
> Modules linked in: ipt_MASQUERADE vhost_net kvm_intel kvm iptable_filter xt_tcpudp iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables bridge stp btrfs zlib_deflate crc32c libcrc32c coretemp f71882fg snd_pcm snd_timer snd soundcore i2c_i801 snd_page_alloc tpm_tis tpm tpm_bios pcspkr i7core_edac edac_core r8169 mii raid10 raid456 async_pq async_xor xor async_memcpy async_raid6_recov raid6_pq async_tx raid1 raid0 ahci libahci sata_nv sata_sil sata_via 3w_9xxx 3w_xxxx [last unloaded: scsi_wait_scan]
>
> Pid: 10199, comm: kvm Not tainted 2.6.38.1 #1 MSI MS-7522/MSI X58 Pro-E (MS-7522)
> RIP: 0010:[<ffffffffa02cae20>] [<ffffffffa02cae20>] kvm_unmap_rmapp+0x20/0x70 [kvm]
> RSP: 0018:ffff880508ee9bf0 EFLAGS: 00010202
> RAX: 00008805d6b087f8 RBX: ffff8805b7b10000 RCX: 0000000000000050
> RDX: 0000000000000000 RSI: 00008805d6b087f8 RDI: ffff8805b7b10000
> RBP: ffff880508ee9c10 R08: ffff8801061d4000 R09: ffffc9001f19aff0
> R10: 0000000000000030 R11: 0000000000000000 R12: 0000000000000000
> R13: ffffc9001f19aff8 R14: 0000000000000060 R15: ffff8801061d4000
> FS: 00007f7ca25d6730(0000) GS:ffff8800bf400000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: 0000000000462b10 CR3: 00000003ac47f000 CR4: 00000000000026e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process kvm (pid: 10199, threadinfo ffff880508ee8000, task ffff88001b5a5b00)
> Stack:
> ffffffffffffffcf 00000000000220ff 0000000000000001 ffff8801061d4050
> ffff880508ee9c80 ffffffffa02c8a54 0000000000000030 ffffffffa02cae00
> 0000000000000000 00007f7c80a2b000 ffff8805b7b10000 0000000000000001
> Call Trace:
> [<ffffffffa02c8a54>] kvm_handle_hva+0xb4/0x170 [kvm]
> [<ffffffffa02cae00>] ? kvm_unmap_rmapp+0x0/0x70 [kvm]
> [<ffffffffa02c8b27>] kvm_unmap_hva+0x17/0x20 [kvm]
> [<ffffffffa02b1e72>] kvm_mmu_notifier_invalidate_range_start+0x62/0xb0 [kvm]
> [<ffffffff8113ea11>] __mmu_notifier_invalidate_range_start+0x51/0x70
> [<ffffffff8111e2c1>] copy_page_range+0x3b1/0x460
> [<ffffffff812c5628>] ? rb_insert_color+0x98/0x140
> [<ffffffff81060cdc>] dup_mm+0x2fc/0x500
> [<ffffffff810617fe>] copy_process+0x8be/0x11b0
> [<ffffffff81062165>] do_fork+0x75/0x350
> [<ffffffff81177bcd>] ? mntput+0x1d/0x40
> [<ffffffff8115b095>] ? fput+0x1e5/0x270
> [<ffffffff815aa7f5>] ? _raw_spin_lock_irq+0x15/0x20
> [<ffffffff81075141>] ? sigprocmask+0x91/0x110
> [<ffffffff81014ab8>] sys_clone+0x28/0x30
> [<ffffffff8100c3e3>] stub_clone+0x13/0x20
> [<ffffffff8100c0c2>] ? system_call_fastpath+0x16/0x1b
> Code: 49 89 01 eb 91 66 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 48 83 ec 08 0f 1f 44 00 00 45 31 e4 48 89 fb 49 89 f5 eb 1d 0f 1f 00<f6> 06 01 74 38 48 8b 15 a4 66 02 00 48 89 df 41 bc 01 00 00 00
> RIP [<ffffffffa02cae20>] kvm_unmap_rmapp+0x20/0x70 [kvm]
> RSP<ffff880508ee9bf0>
> ---[ end trace 85201a339b7635fc ]---
>
>
>
0: 55 push %rbp
1: 48 89 e5 mov %rsp,%rbp
4: 41 55 push %r13
6: 41 54 push %r12
8: 53 push %rbx
9: 48 83 ec 08 sub $0x8,%rsp
d: 0f 1f 44 00 00 nopl 0x0(%rax,%rax,1)
12: 45 31 e4 xor %r12d,%r12d
15: 48 89 fb mov %rdi,%rbx
18: 49 89 f5 mov %rsi,%r13
1b: eb 1d jmp 0x3a
1d: 0f 1f 00 nopl (%rax)
20: f6 06 01 testb $0x1,(%rsi)
Looks like the top 16 bits of %rsi are flipped.
Also wierd to see a fork(). What's your qemu command line?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2011-03-26 9:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 9:32 2.6.38.1 general protection fault Tomasz Chmielewski
2011-03-26 9:15 ` Avi Kivity [this message]
2011-03-26 10:42 ` Tomasz Chmielewski
2011-03-27 9:42 ` Avi Kivity
2011-03-28 6:24 ` Tomasz Chmielewski
2011-03-28 9:19 ` Avi Kivity
2011-03-28 17:54 ` Andrea Arcangeli
2011-03-28 18:02 ` Avi Kivity
2011-03-28 20:04 ` Andrea Arcangeli
2011-03-28 20:14 ` Tomasz Chmielewski
2011-04-20 9:28 ` Thomas Treutner
2011-04-20 10:54 ` Tomasz Chmielewski
2011-03-29 13:34 ` Marcelo Tosatti
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=4D8DAE94.7070604@redhat.com \
--to=avi@redhat.com \
--cc=aarcange@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mangoo@wpkg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).