Bug 1391257

Summary: [abrt] general protection fault in __kmalloc
Product: [Fedora] Fedora Reporter: Donavan Lance <tusklahoma>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: gansalmon, ichavero, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone: ---Flags: jforbes: needinfo?
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/3064e349a36423ef818529ec4065ea897386806d
Whiteboard: abrt_hash:14d0075f85b4b16424a32b2cf8964fb47ffea790;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-28 17:17:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: dmesg none

Description Donavan Lance 2016-11-02 21:41:10 UTC 
Description of problem:
Problem occurs when starting / shutting down Windows guests running in KVM. Guests include
Windows Server 2012 r2, Windows Server 2016, and Windows 10 Pro.

Steps to reproduce:

Install Fedora 24 and all available updates.
Install virt-manager and set up KVM environment (add vfio modules to initramfs and PCIe ids for vfio_pci to claim).
Install Windows using KVM.
Eventually the system crashes when starting up / shutting down guest.

Additional info:
reporter:       libreport-2.7.2
general protection fault: 0000 [#1] SMP
Modules linked in: rfcomm fuse ccm arc4 xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_broute bridge stp llc ebtable_nat ip6table_raw ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_security ip6table_mangle iptable_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_security iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables cmac bnep vfat fat snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_realtek snd_hda_codec_generic ath10k_pci kvm ath10k_core iTCO_wdt iTCO_vendor_support eeepc_wmi mac80211 asus_wmi sparse_keymap crct10dif_pclmul
 crc32_pclmul snd_hda_intel ghash_clmulni_intel intel_cstate intel_uncore snd_hda_codec intel_rapl_perf snd_hda_core snd_hwdep snd_seq snd_seq_device snd_pcm ath cfg80211 btusb hci_uart btrtl snd_timer btqca btbcm snd i2c_i801 btintel i2c_smbus pinctrl_sunrisepoint bluetooth soundcore mei_me pinctrl_intel intel_lpss_acpi mei intel_lpss rfkill shpchp acpi_als tpm_tis kfifo_buf tpm_tis_core industrialio tpm acpi_pad nfsd auth_rpcgss nfs_acl lockd grace sunrpc xfs libcrc32c nouveau i915 mxm_wmi ttm e1000e i2c_algo_bit crc32c_intel drm_kms_helper serio_raw drm ptp pps_core nvme nvme_core wmi video i2c_hid fjes vfio_pci irqbypass vfio_iommu_type1 vfio_virqfd vfio
CPU: 5 PID: 2758 Comm: CPU 0/KVM Not tainted 4.8.4-200.fc24.x86_64 #1
Hardware name: System manufacturer System Product Name/MAXIMUS VIII HERO ALPHA, BIOS 1701 03/25/2016
task: ffff90fa8795dd00 task.stack: ffff90fa10644000
RIP: 0010:[<ffffffff8f227753>]  [<ffffffff8f227753>] __kmalloc+0xc3/0x1f0
RSP: 0018:ffff90fa10647af8  EFLAGS: 00010246
RAX: 2effff90fbf545cd RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000005920 RSI: 0000000000000000 RDI: 000000000001c920
RBP: ffff90fa10647b28 R08: ffff90fc43d5c920 R09: 00000000000fee00
R10: 2effff90fbf545cd R11: 0000000000000000 R12: 00000000024080c0
R13: 0000000000000008 R14: ffff90fc03003cc0 R15: ffff90fc03003cc0
FS:  00007f218dedd700(0000) GS:ffff90fc43d40000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055dbfe403698 CR3: 000000103c1ac000 CR4: 00000000003426e0
Stack:
 ffffffffc0b55c2c 0000000000000001 0000000000000000 0000000000000000
 ffff90fa10647c28 0000000000000000 ffff90fa10647b38 ffffffffc0b55c2c
 ffff90fa10647b88 ffffffffc0b6e83f ffffb945c7e03000 ffff90f9882e8000
Call Trace:
 [<ffffffffc0b55c2c>] ? kvm_kvzalloc+0x1c/0x30 [kvm]
 [<ffffffffc0b55c2c>] kvm_kvzalloc+0x1c/0x30 [kvm]
 [<ffffffffc0b6e83f>] kvm_arch_create_memslot+0x4f/0x1c0 [kvm]
 [<ffffffffc0b563d5>] __kvm_set_memory_region.part.55+0x795/0xa90 [kvm]
 [<ffffffffc0b566ed>] __kvm_set_memory_region+0x1d/0x20 [kvm]
 [<ffffffffc0b62104>] __x86_set_memory_region+0x104/0x1e0 [kvm]
 [<ffffffffc0c2eef7>] vmx_create_vcpu+0xd57/0x1050 [kvm_intel]
 [<ffffffff8f0b08e9>] ? get_signal+0x289/0x630
 [<ffffffffc0b6d81e>] kvm_arch_vcpu_create+0x3e/0x60 [kvm]
 [<ffffffffc0b56a27>] kvm_vm_ioctl+0x2d7/0x780 [kvm]
 [<ffffffff8f29e5bc>] ? eventfd_read+0x5c/0x90
 [<ffffffff8f24f657>] ? __vfs_read+0x37/0x150
 [<ffffffff8f264cf3>] do_vfs_ioctl+0xa3/0x5f0
 [<ffffffff8f2652b9>] SyS_ioctl+0x79/0x90
 [<ffffffff8f802572>] entry_SYSCALL_64_fastpath+0x1a/0xa4
Code: 49 83 78 10 00 4d 8b 10 0f 84 ce 00 00 00 4d 85 d2 0f 84 c5 00 00 00 49 63 47 20 49 8b 3f 4c 01 d0 40 f6 c7 0f 0f 85 1a 01 00 00 <48> 8b 18 48 8d 4a 01 4c 89 d0 65 48 0f c7 0f 0f 94 c0 84 c0 74 
RIP  [<ffffffff8f227753>] __kmalloc+0xc3/0x1f0
Comment 1 Donavan Lance 2016-11-02 21:41:20 UTC 
Created attachment 1216787 [details]
File: dmesg
Comment 2 Justin M. Forbes 2017-04-11 14:44:09 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-100.fc24.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.
Comment 3 Justin M. Forbes 2017-04-28 17:17:21 UTC 
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the 
relevant data from the latest kernel you are running and any data that might have been requested previously.