From: ChenLiang <chenliang88@huawei.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: <kvm@vger.kernel.org>, <david.Woodhouse@intel.com>
Subject: Re: bug: host crash when vf is passthrough to vm.
Date: Sat, 11 Oct 2014 16:21:21 +0800 [thread overview]
Message-ID: <5438E881.1070402@huawei.com> (raw)
In-Reply-To: <1413013059.4202.8.camel@ul30vt.home>
Thanks for your reply.
I will try new kernel. And do you have any suggestion?
I have google it, sadly, nothing mention this bug.
Best regards
ChenLiang
On 2014/10/11 15:37, Alex Williamson wrote:
> On Sat, 2014-10-11 at 11:02 +0800, ChenLiang wrote:
>> Hi all:
>>
>> kernel: 3.0.93-0.8-default
>> qemu: 1.5
>
> This is a very old kernel and rather old QEMU as well. This bug is
> hopefully fixed in a newer kernel. Thanks,
>
> Alex
>
>> crash log:
>>
>> [134397.708857] BUG: unable to handle kernel NULL pointer dereference at 0000000000000012
>> [134397.717334] IP: [] iommu_disable_dev_iotlb+0x15/0x30
>> [134397.724268] PGD 0
>> [134397.726686] Oops: 0000 [#1] SMP
>> [134397.730335] kbox: Begin to handle event info
>> [134397.734992] kbox: kbox: Enter into handle die dump while current state:Dump State Init
>> [134397.751054]
>> [134398.043275] kbox: End handling event info
>> [134398.047757] CPU 1
>> [134398.049678] Modules linked in: mlx4_en(FX) mlx4_core(FX) compat(FX) openvswitch crc32c libcrc32c gre nm_dev(FN) ip6table_filter ip6_tables iptable_filter ip_tables ebtable_nat ebtables x_tables uvpdump i
>> [134398.125560] Supported: No, Unsupported modules are loaded
>> [134398.131338]
>> [134398.133220] Pid: 183980, comm: qemu-kvm Tainted: GF NX 3.0.93-0.8-default #1 HUAWEI TECHNOLOGIES CO.,LTD. CH80TXSUA/CH80TXSUA
>> [134398.146013] RIP: 0010:[] [] iommu_disable_dev_iotlb+0x15/0x30
>> [134398.155649] RSP: 0018:ffff8817f0e13be0 EFLAGS: 00010202
>> [134398.161342] RAX: 0000000000000002 RBX: ffff880bf34e6600 RCX: 0000000000000007
>> [134398.169158] RDX: ffff880bf34e6650 RSI: 0000000000000292 RDI: ffff880bf2011000
>> [134398.176970] RBP: 0000000000000000 R08: dead000000200200 R09: dead000000100100
>> [134398.184793] R10: ffff8817f5d4c380 R11: ffffffff8128e350 R12: ffff880bf34e6640
>> [134398.192549] R13: ffff880bf5d3de80 R14: ffff880653e4a000 R15: ffff880bf34d7858
>> [134398.200360] FS: 00007f6d17fff980(0000) GS:ffff880c3ee20000(0000) knlGS:0000000000000000
>> [134398.209109] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
>> [134398.215223] CR2: 0000000000000012 CR3: 000000096ed95000 CR4: 00000000001427e0
>> [134398.223000] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
>> [134398.230812] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
>> [134398.238630] Process qemu-kvm (pid: 183980, threadinfo ffff8817f0e12000, task ffff8817804ac300)
>> [134398.247906] Stack:
>> [134398.250260] ffffffff8128f756 00000000ffffffed ffff880bf34d7840 0000000000000292
>> [134398.258383] ffff880bf34d7640 ffff880653e4a090 00000000ffffffed ffff880653e4a000
>> [134398.266509] ffff880653e4a000 ffff880bee6c4878 ffffffff812938c6 ffff880bebe17d60
>> [134398.274659] Call Trace:
>> [134398.277503] [] domain_remove_one_dev_info+0x156/0x280
>> [134398.284582] [] intel_iommu_attach_device+0x156/0x170
>> [134398.291583] [] kvm_assign_device+0x73/0x150 [kvm]
>> [134398.298360] [] kvm_vm_ioctl_assign_device+0x247/0x3c0 [kvm]
>> [134398.306303] [] kvm_vm_ioctl_assigned_device+0x2fc/0x6a0 [kvm]
>> [134398.314401] [] kvm_vm_ioctl+0x101/0x300 [kvm]
>> [134398.320789] [] do_vfs_ioctl+0x8b/0x3b0
>> [134398.326566] [] sys_ioctl+0xa1/0xb0
>> [134398.331996] [] system_call_fastpath+0x16/0x1b
>> [134398.338376] [<00007f6d15b77e57>] 0x7f6d15b77e56
>> [134398.343373] Code: c6 05 97 dc de 00 01 eb a7 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 48 8b 7f 28 48 85 ff 74 12 48 8b 87 30 09 00 00 48 85 c0 74 06 40 10 01 75 05 f3 c3 0f 1f 00 e9 ab 61 00 00 66 66
>> [134398.364424] RIP [] iommu_disable_dev_iotlb+0x15/0x30
>> [134398.371441] RSP
>> [134398.375314] CR2: 0000000000000012
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe kvm" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
>
> .
>
prev parent reply other threads:[~2014-10-11 8:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-11 3:02 bug: host crash when vf is passthrough to vm ChenLiang
2014-10-11 7:37 ` Alex Williamson
2014-10-11 8:21 ` ChenLiang [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=5438E881.1070402@huawei.com \
--to=chenliang88@huawei.com \
--cc=alex.williamson@redhat.com \
--cc=david.Woodhouse@intel.com \
--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.