Bug 1593024

Summary: [abrt] __schedule: WARNING: CPU: 10 PID: 0 at arch/x86/mm/tlb.c:290 switch_mm_irqs_off+0x11a/0x510
Product: [Fedora] Fedora Reporter: dwalker
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: 28CC: airlied, bskeggs, ewk, hdegoede, ichavero, itamar, jarodwilson, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, mchehab, mjg59, steved
Target Milestone: ---Flags: jforbes: needinfo?
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/581bf1e7a03300f6f86a42e6ddba42ecc14c1dc8
Whiteboard: abrt_hash:3c07ba274c916d10076059a13d9c5b95e527baef;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-29 15:11:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: dmesg none

Description dwalker 2018-06-19 21:20:45 UTC 
Description of problem:
System just hung while sleeping

Additional info:
reporter:       libreport-2.9.5
WARNING: CPU: 10 PID: 0 at arch/x86/mm/tlb.c:290 switch_mm_irqs_off+0x11a/0x510
Modules linked in: fuse nfsv3 rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache vfat fat dm_cache_smq dm_cache dm_persistent_data dm_bio_prison libcrc32c edac_mce_amd snd_hda_codec_realtek snd_hda_codec_generic kvm snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep irqbypass crct10dif_pclmul snd_seq crc32_pclmul snd_seq_device wmi_bmof ppdev snd_pcm ghash_clmulni_intel snd_timer snd sp5100_tco joydev garmin_gps k10temp i2c_piix4 soundcore ccp wmi parport_pc gpio_amdpt shpchp gpio_generic parport pinctrl_amd acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd grace sunrpc radeon i2c_algo_bit drm_kms_helper ttm r8169 uas drm crc32c_intel usb_storage mii nvme nvme_core
CPU: 10 PID: 0 Comm: swapper/10 Not tainted 4.16.15-300.fc28.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. AB350M-Gaming 3/AB350M-Gaming 3-CF, BIOS F6 08/18/2017
RIP: 0010:switch_mm_irqs_off+0x11a/0x510
RSP: 0018:ffffb4c6c3283e50 EFLAGS: 00010087
RAX: ffff8f97d8243330 RBX: ffff8f97eb3d4740 RCX: 0000000000000049
RDX: ffff8f97f2526000 RSI: ffff8f97eb3d4740 RDI: ffff8f97f2526b48
RBP: ffff8f97d8242f80 R08: ffff8f97fe8a15a0 R09: 0000000000000000
R10: 0000000000000000 R11: 000102a59311fe40 R12: ffff8f97eb3b0000
R13: ffff8f97eb3b0000 R14: 000000000000000a R15: 00000000000203c0
FS:  0000000000000000(0000) GS:ffff8f97fe880000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f836a191000 CR3: 00000007cf364000 CR4: 00000000003406e0
Call Trace:
 __schedule+0x1f5/0x850
 schedule_idle+0x1e/0x40
 do_idle+0x145/0x1d0
 cpu_startup_entry+0x6f/0x80
 start_secondary+0x1a7/0x200
 secondary_startup_64+0xa5/0xb0
Code: 00 48 8d 3c c2 48 f7 07 9f ff ff ff 0f 84 44 03 00 00 48 8b 85 e0 02 00 00 45 89 f6 4c 0f a3 30 72 0b 48 81 fd e0 a5 28 a8 74 02 <0f> 0b f0 4c 0f b3 30 48 8b 83 e0 02 00 00 f0 4c 0f ab 30 4c 8b
Comment 1 dwalker 2018-06-19 21:21:01 UTC 
Created attachment 1453028 [details]
File: dmesg
Comment 2 Justin M. Forbes 2018-07-23 15:04:15 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 28 kernel bugs.

Fedora 28 has now been rebased to 4.17.7-200.fc28.  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 experience different issues, please open a new bug report for those.
Comment 3 Justin M. Forbes 2018-08-29 15:11:14 UTC 
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 5 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.