1588395 – kernel 4.16.1-4.16.13-200 are crashing under XEN

Bug 1588395 - kernel 4.16.1-4.16.13-200 are crashing under XEN

Summary: kernel 4.16.1-4.16.13-200 are crashing under XEN

Keywords:
Status:	CLOSED INSUFFICIENT_DATA
Alias:	None
Product:	Fedora
Classification:	Fedora
Component:	kernel
Sub Component:
Version:	28
Hardware:	x86_64
OS:	Linux
Priority:	unspecified
Severity:	urgent
Target Milestone:	---
Assignee:	Kernel Maintainer List
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:
URL:
Whiteboard:
Depends On:	1578846
Blocks:
TreeView+	depends on / blocked

Reported:	2018-06-07 08:28 UTC by customercare
Modified:	2019-02-21 21:11 UTC (History)
CC List:	17 users (show)
Fixed In Version:
Clone Of:
Environment:
Last Closed:	2019-02-21 21:11:01 UTC
Type:	Bug
Embargoed:
Dependent Products:

Attachments	(Terms of Use)
Bootlog of faulty kernelline (27.02 KB, text/plain) 2018-06-07 08:28 UTC, customercare	no flags	Details
View All

Description customercare 2018-06-07 08:28:00 UTC

Created attachment 1448643 [details]
Bootlog of faulty kernelline

Description of problem:

This is the only useful log we can supply, because the 4.16.x kernels are crashing undeterministically before the server can save data to the disks, and it's highly unstable, as you can see here. No idea what will happen on a system with more activity as this server :(

No kernel-oops, no console message on the monitor scree, no helpful output :(

reboot   system boot  4.16.13-200.fc27 Thu Jun  7 08:18   still running
reboot   system boot  4.16.13-200.fc27 Thu Jun  7 02:08   still running
reboot   system boot  4.16.13-200.fc27 Wed Jun  6 17:43   still running
root     pts/0        a.b.c.d          Wed Jun  6 14:17 - 14:46  (00:29)
root     pts/0        a.b.c.d          Mon Jun  4 23:27 - 00:06  (00:38)
root     pts/0        a.b.c.d          Sun Jun  3 17:32 - 22:18  (04:46)
root     pts/0        a.b.c.d          Sun Jun  3 13:54 - 17:30  (03:36)
reboot   system boot  4.16.12-200.fc27 Sun Jun  3 11:48   still running
reboot   system boot  4.16.12-200.fc27 Sat Jun  2 23:46   still running
root     pts/0        a.b.c.d          Sat Jun  2 21:32 - 23:09  (01:36)
reboot   system boot  4.16.12-200.fc27 Sat Jun  2 21:31   still running
root     pts/0        a.b.c.d          Sat Jun  2 21:27 - 21:29  (00:01)
root     pts/0        a.b.c.d          Thu May 31 16:37 - 17:02  (00:25)
root     pts/3        a.b.c.d          Fri May 25 12:50 - 14:06  (01:15)
root     pts/0        a.b.c.d          Fri May 25 12:49 - 14:05  (01:16)
root     pts/0        a.b.c.d          Mon May  7 08:02 - 08:03  (00:00)
reboot   system boot  4.15.17-200.fc26 Mon May  7 00:24 - 21:29 (26+21:05)

If you check the boot log of the faulty kernel line, you will notice three things:

a) 

Jun 07 08:18:13 a.b.c.d kernel: mce: Unable to init MCE device (rc: -5)

b)

Jun 07 08:18:13 a.b.c.d kernel: x86/mm: Found insecure W+X mapping at address 00000000d38f8ebb/0xffff880000000000
Jun 07 08:18:13 a.b.c.d kernel: WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:266 note_page+0x622/0x810
Jun 07 08:18:13 a.b.c.d kernel: Modules linked in:
Jun 07 08:18:13 a.b.c.d kernel: CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.16.13-200.fc27.x86_64 #1
Jun 07 08:18:13 a.b.c.d kernel: RIP: e030:note_page+0x622/0x810
Jun 07 08:18:13 a.b.c.d kernel: RSP: e02b:ffffc90000e2be40 EFLAGS: 00010286
Jun 07 08:18:13 a.b.c.d kernel: RAX: 0000000000000000 RBX: ffffc90000e2bec8 RCX: ffffffff82253c48
Jun 07 08:18:13 a.b.c.d kernel: RDX: 0000000000000001 RSI: 00000000000000e3 RDI: 0000000000000200
Jun 07 08:18:13 a.b.c.d kernel: RBP: 8010000000000065 R08: 00000000000000e3 R09: 0000000000000004
Jun 07 08:18:13 a.b.c.d kernel: R10: ffff8800ff80c7a0 R11: 0000000000000001 R12: 0000000000000005
Jun 07 08:18:13 a.b.c.d kernel: R13: 0000000000000000 R14: 00003ffffffff000 R15: 0000000000000000
Jun 07 08:18:13 a.b.c.d kernel: FS:  00007f65b8d9a0c0(0000) GS:ffff8800fac00000(0000) knlGS:0000000000000000
Jun 07 08:18:13 a.b.c.d kernel: CS:  e033 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 07 08:18:13 a.b.c.d kernel: CR2: 00007f65b8954000 CR3: 000000000220a000 CR4: 0000000000002660
Jun 07 08:18:13 a.b.c.d kernel: Call Trace:
Jun 07 08:18:13 a.b.c.d kernel:  ptdump_walk_pgd_level_core+0x3c0/0x4a0
Jun 07 08:18:13 a.b.c.d kernel:  ? rest_init+0xb0/0xb0
Jun 07 08:18:13 a.b.c.d kernel:  ptdump_walk_pgd_level_checkwx+0x15/0x50
Jun 07 08:18:13 a.b.c.d kernel:  kernel_init+0x30/0x110
Jun 07 08:18:13 a.b.c.d kernel:  ret_from_fork+0x35/0x40
Jun 07 08:18:13 a.b.c.d kernel: Code: e6 23 00 41 f7 c7 00 01 00 00 0f 85 50 fe ff ff e9 c0 fc ff ff 48 89 f2 48 c7 c7 80 35 09 82 c6 05 4e 41 2c 01 01 e8 fe 7f 03 00 <0f> 0b 48 8b 73 10 e9 67 fa ff ff 4d 89 c8 b9 10 00 00 00 be 10 
Jun 07 08:18:13 a.b.c.d kernel: ---[ end trace e7132623d520c922 ]---
Jun 07 08:18:13 a.b.c.d kernel: x86/mm: Checked W+X mappings: FAILED, 7122 W+X pages found.


c)

Jun 07 08:18:14 a.b.c.d systemd[1]: Started dracut initqueue hook.
Jun 07 08:18:14 a.b.c.d systemd[1]: Starting File System Check on /dev/disk/by-uuid/dca7eea1-687e-476a-a9a0-c41ef0329113...
Jun 07 08:18:14 a.b.c.d systemd[1]: Reached target Remote File Systems (Pre).
Jun 07 08:18:14 a.b.c.d systemd[1]: Reached target Remote File Systems.
Jun 07 08:18:14 a.b.c.d systemd-fsck[269]: /dev/xvda1: recovering journal
Jun 07 08:18:16 a.b.c.d kernel: blkfront: xvda: empty barrier op failed
Jun 07 08:18:16 a.b.c.d kernel: blkfront: xvda: barrier or flush: disabled; persistent grants: disabled; indirect descriptors: disabled;
Jun 07 08:18:18 a.b.c.d systemd-fsck[269]: /dev/xvda1: Clearing orphaned inode 1454683 (uid=27, gid=27, mode=0100600, size=0)
Jun 07 08:18:18 a.b.c.d systemd-fsck[269]: /dev/xvda1: Clearing orphaned inode 1573310 (uid=0, gid=0, mode=0100600, size=0)
Jun 07 08:18:18 a.b.c.d systemd-fsck[269]: /dev/xvda1: Clearing orphaned inode 1454682 (uid=27, gid=27, mode=0100600, size=0)
Jun 07 08:18:18 a.b.c.d systemd-fsck[269]: /dev/xvda1: Clearing orphaned inode 1452649 (uid=27, gid=27, mode=0100600, size=0)
Jun 07 08:18:18 a.b.c.d systemd-fsck[269]: /dev/xvda1: Clearing orphaned inode 1452648 (uid=27, gid=27, mode=0100600, size=0)
Jun 07 08:18:18 a.b.c.d systemd-fsck[269]: /dev/xvda1: clean, 487702/5177344 files, 15396929/20709120 blocks
Jun 07 08:18:18 a.b.c.d systemd[1]: Started File System Check on /dev/disk/by-uuid/dca7eea1-687e-476a-a9a0-c41ef0329113.
Jun 07 08:18:18 a.b.c.d systemd[1]: Mounting /sysroot...


the reason, why we don't know anything useful:  the system resets and takes everything with it.


Version-Release number of selected component (if applicable):

4.16.1 - 4.16.13-200 FC27


CPU INFO:

processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 44
model name	: Intel(R) Xeon(R) CPU           E5645  @ 2.40GHz
stepping	: 2
microcode	: 0x14
cpu MHz		: 2400.127
cache size	: 12288 KB
physical id	: 0
siblings	: 1
core id		: 1
cpu cores	: 1
apicid		: 3
initial apicid	: 3
fpu		: yes
fpu_exception	: yes
cpuid level	: 11
wp		: yes
flags		: fpu de tsc msr pae cx8 apic sep cmov pat clflush mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nopl cpuid pni ssse3 cx16 sse4_1 sse4_2 popcnt hypervisor lahf_lm epb dtherm ida arat
bugs		: null_seg cpu_meltdown spectre_v1 spectre_v2
bogomips	: 4800.28
clflush size	: 64
cache_alignment	: 64
address sizes	: 40 bits physical, 48 bits virtual
power management:

running under XEN.

Comment 1 Justin M. Forbes 2018-07-23 15:01:57 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 27 kernel bugs.

Fedora 27 has now been rebased to 4.17.7-100.fc27.  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 28, and are still experiencing this issue, please change the version to Fedora 28.

If you experience different issues, please open a new bug report for those.

Comment 2 customercare 2018-07-23 16:37:37 UTC

Kernel 4.17.7-100.fc27 crashed about 1h after it got started. 

It resets the VM, so it's a serious issue that happens.

Comment 3 Laura Abbott 2018-10-01 21:25:06 UTC

We apologize for the inconvenience.  There is 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 27 kernel bugs.
 
Fedora 27 has now been rebased to 4.18.10-100.fc27.  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 28 or Fedora 29, and are still experiencing this issue, please change the version to Fedora 28 or 29.
 
If you experience different issues, please open a new bug report for those.

Comment 4 customercare 2018-10-02 07:55:32 UTC

....TEST Kernel X86_64 4.18.10-100 in progress...

Comment 5 customercare 2018-10-02 16:35:52 UTC

see 1578846

8 1/2 hours until crashed as all kernel 4.16++

Comment 6 Ben Cotton 2018-11-27 14:11:04 UTC

This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Ben Cotton 2018-11-30 23:04:20 UTC

Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 8 customercare 2018-12-02 00:03:23 UTC

Still happens under 4.18.19 and a different XEN :

root     pts/0        91.61.38.71      Sun Dec  2 01:01   still logged in
reboot   system boot  4.18.19-100.fc27 Sat Dec  1 18:39   still running
root     pts/0        91.61.38.71      Sat Dec  1 12:15 - 12:51  (00:36)
root     pts/0        77.190.150.169   Sat Dec  1 12:03 - 12:04  (00:00)
root     pts/0        91.61.38.71      Sat Dec  1 10:51 - 11:04  (00:12)
root     pts/0        79.239.195.133   Fri Nov 30 20:16 - 20:19  (00:02)
root     pts/0        77.190.90.246    Fri Nov 30 19:48 - 19:56  (00:07)
reboot   system boot  4.18.19-100.fc27 Fri Nov 30 18:39   still running

Comment 9 customercare 2018-12-02 00:05:44 UTC

Different CPU aswell : 

]# cat /proc/cpuinfo 
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 60
model name	: Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz
stepping	: 3
microcode	: 0x17
cpu MHz		: 3300.060
cache size	: 8192 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 1
apicid		: 3
initial apicid	: 3
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu de tsc msr pae cx8 apic sep cmov pat clflush mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nopl cpuid pni pclmulqdq ssse3 sdbg cx16 sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes f16c rdrand hypervisor lahf_lm abm cpuid_fault epb fsgsbase erms dtherm ida arat pln pts
bugs		: null_seg cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf
bogomips	: 6600.12
clflush size	: 64
cache_alignment	: 64
address sizes	: 39 bits physical, 48 bits virtual
power management:

Comment 10 customercare 2019-01-15 17:26:24 UTC

4.19.9-201 ... same result as always, but i#m pretty sure i did not have had any problem when that kernel was the actual stable one.
In which module does bug happen? is it nvidia ? 


marius    5620 38.0  0.0      0     0 ?        Ds   17:55  10:14 [wineserver]
marius    5631  0.0  0.0 2650212 7964 ?        Sl   17:55   0:00 C:\windows\system32\winedevice.exe
marius    5644  0.0  0.0 2658076 9288 ?        Sl   17:55   0:00 C:\windows\system32\winedevice.exe
marius    5660  0.1  0.0 2657740 9972 ?        Sl   17:55   0:02 C:\windows\system32\winedevice.exe
root     10055  0.0  0.0 118508  1020 pts/0    S+   18:22   0:00              \_ grep --color=auto wine


an 15 18:10:58 eve kernel: general protection fault: 0000 [#1] SMP NOPTI
Jan 15 18:10:58 eve kernel: CPU: 4 PID: 5834 Comm: Client.exe Tainted: P           OE     4.19.9-201.fc28.x86_64 #1
Jan 15 18:10:58 eve kernel: Hardware name: To be filled by O.E.M. To be filled by O.E.M./M5A97 R2.0, BIOS 2201 12/10/2013
Jan 15 18:10:58 eve kernel: RIP: 0010:__mutex_lock.isra.5+0x74/0x490
Jan 15 18:10:58 eve kernel: Code: 49 01 00 00 48 39 c6 0f 84 c7 03 00 00 65 48 8b 04 25 00 5c 01 00 48 8b 00 a8 08 75 18 49 8b 07 48 83 e0 f8 0f 84 a5 01 00 00 <8b> 40 38 85 c0 0f 85 9a 01 00 00 65 48 8b 04 25 00 5c 01 00 48 8b
Jan 15 18:10:58 eve kernel: RSP: 0018:ffffae1905cf7d20 EFLAGS: 00010286
Jan 15 18:10:58 eve kernel: RAX: 8000000000000000 RBX: ffff997fbc8383c0 RCX: 0000000000000063
Jan 15 18:10:58 eve kernel: RDX: 8000000000000000 RSI: ffff998023341f00 RDI: ffff997fbc8383c0
Jan 15 18:10:58 eve kernel: RBP: ffffae1905cf7da0 R08: ffff997f7e703eb0 R09: 0000000000000000
Jan 15 18:10:58 eve kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002
Jan 15 18:10:58 eve kernel: R13: ffff997f7874b700 R14: ffff997fbc8383c0 R15: ffff997fbc8383c0
Jan 15 18:10:58 eve kernel: FS:  0000000081fd4000(0063) GS:ffff9980aeb00000(006b) knlGS:000000001bae3b40
Jan 15 18:10:58 eve kernel: CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
Jan 15 18:10:58 eve kernel: CR2: 00001484dd93a000 CR3: 00000002c045a000 CR4: 00000000000406e0
Jan 15 18:10:58 eve kernel: Call Trace:
Jan 15 18:10:58 eve kernel: ? __schedule+0x25b/0x860
Jan 15 18:10:58 eve kernel: pipe_wait+0xa7/0xb0
Jan 15 18:10:58 eve kernel: ? finish_wait+0x80/0x80
Jan 15 18:10:58 eve kernel: pipe_read+0x20a/0x2d0
Jan 15 18:10:58 eve kernel: __vfs_read+0x133/0x190
Jan 15 18:10:58 eve kernel: vfs_read+0x8a/0x140
Jan 15 18:10:58 eve kernel: ksys_read+0x4f/0xb0
Jan 15 18:10:58 eve kernel: do_fast_syscall_32+0xa7/0x254
Jan 15 18:10:58 eve kernel: entry_SYSCALL_compat_after_hwframe+0x45/0x4d
Jan 15 18:10:58 eve kernel: Modules linked in: twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common fuse xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c tun bridge stp llc xt_multiport devlink ebtable_filter ebtables ip6table_filter ip6_tables it87 hwmon_vid nvidia_drm(POE) nvidia_modeset(POE) nvidia_uvm(OE) uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common snd_usb_audio videodev snd_usbmidi_lib media snd_rawmidi snd_hda_codec_hdmi edac_mce_amd kvm_amd nvidia(POE) kvm irqbypass snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec eeepc_wmi snd_hda_core asus_wmi sparse_keymap snd_hwdep drm_kms_helper rfkill video wmi_bmof snd_seq snd_seq_device drm
Jan 15 18:10:58 eve kernel: snd_pcm fam15h_power k10temp sp5100_tco i2c_piix4 snd_timer snd ipmi_devintf soundcore ipmi_msghandler pcc_cpufreq acpi_cpufreq vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc dm_crypt mxm_wmi crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel serio_raw r8169 wmi
Jan 15 18:10:58 eve kernel: ---[ end trace 34388ea4d17727fd ]---
Jan 15 18:10:58 eve kernel: RIP: 0010:__mutex_lock.isra.5+0x74/0x490
Jan 15 18:10:58 eve kernel: Code: 49 01 00 00 48 39 c6 0f 84 c7 03 00 00 65 48 8b 04 25 00 5c 01 00 48 8b 00 a8 08 75 18 49 8b 07 48 83 e0 f8 0f 84 a5 01 00 00 <8b> 40 38 85 c0 0f 85 9a 01 00 00 65 48 8b 04 25 00 5c 01 00 48 8b
Jan 15 18:10:58 eve kernel: RSP: 0018:ffffae1905cf7d20 EFLAGS: 00010286
Jan 15 18:10:58 eve kernel: RAX: 8000000000000000 RBX: ffff997fbc8383c0 RCX: 0000000000000063
Jan 15 18:10:58 eve kernel: RDX: 8000000000000000 RSI: ffff998023341f00 RDI: ffff997fbc8383c0
Jan 15 18:10:58 eve kernel: RBP: ffffae1905cf7da0 R08: ffff997f7e703eb0 R09: 0000000000000000
Jan 15 18:10:58 eve kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002
Jan 15 18:10:58 eve kernel: R13: ffff997f7874b700 R14: ffff997fbc8383c0 R15: ffff997fbc8383c0
Jan 15 18:10:58 eve kernel: FS:  0000000081fd4000(0063) GS:ffff9980aeb00000(006b) knlGS:000000001bae3b40
Jan 15 18:10:58 eve kernel: CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
Jan 15 18:10:58 eve kernel: CR2: 00001484dd93a000 CR3: 00000002c045a000 CR4: 00000000000406e0
Jan 15 18:11:00 eve abrt-dump-journal-oops[1337]: Reported 1 kernel oopses to Abrt
Jan 15 18:17:13 eve kernel: general protection fault: 0000 [#2] SMP NOPTI
Jan 15 18:17:13 eve kernel: CPU: 7 PID: 6043 Comm: Client.exe Tainted: P      D    OE     4.19.9-201.fc28.x86_64 #1
Jan 15 18:17:13 eve kernel: Hardware name: To be filled by O.E.M. To be filled by O.E.M./M5A97 R2.0, BIOS 2201 12/10/2013
Jan 15 18:17:13 eve kernel: RIP: 0010:__mutex_lock.isra.5+0x74/0x490
Jan 15 18:17:13 eve kernel: Code: 49 01 00 00 48 39 c6 0f 84 c7 03 00 00 65 48 8b 04 25 00 5c 01 00 48 8b 00 a8 08 75 18 49 8b 07 48 83 e0 f8 0f 84 a5 01 00 00 <8b> 40 38 85 c0 0f 85 9a 01 00 00 65 48 8b 04 25 00 5c 01 00 48 8b
Jan 15 18:17:13 eve kernel: RSP: 0018:ffffae1907c5fd70 EFLAGS: 00010286
Jan 15 18:17:13 eve kernel: RAX: a020000000000000 RBX: ffff9980519ffb00 RCX: 0000000000000001
Jan 15 18:17:13 eve kernel: RDX: a020000000000000 RSI: ffff99803e7f3e00 RDI: ffff997fb963c900
Jan 15 18:17:13 eve kernel: RBP: ffffae1907c5fdf0 R08: 0000000000000040 R09: 0000000000000000
Jan 15 18:17:13 eve kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002
Jan 15 18:17:13 eve kernel: R13: 0000000000000040 R14: ffff997fb963c900 R15: ffff997fb963c900
Jan 15 18:17:13 eve kernel: FS:  0000000081fdc000(0063) GS:ffff9980aebc0000(006b) knlGS:000000001b8b3b40
Jan 15 18:17:13 eve kernel: CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
Jan 15 18:17:13 eve kernel: CR2: 0000000020330000 CR3: 000000025a1cc000 CR4: 00000000000406e0
Jan 15 18:17:13 eve kernel: Call Trace:
Jan 15 18:17:13 eve kernel: ? current_time+0x4f/0x90
Jan 15 18:17:13 eve kernel: ? __switch_to_asm+0x40/0x70
Jan 15 18:17:13 eve kernel: ? __switch_to_asm+0x34/0x70
Jan 15 18:17:13 eve kernel: ? __switch_to_asm+0x40/0x70
Jan 15 18:17:13 eve kernel: ? __switch_to_asm+0x34/0x70
Jan 15 18:17:13 eve kernel: ? __switch_to_asm+0x40/0x70
Jan 15 18:17:13 eve kernel: ? __switch_to_asm+0x40/0x70
Jan 15 18:17:13 eve kernel: pipe_write+0x36/0x3f0
Jan 15 18:17:13 eve kernel: ? __switch_to_asm+0x34/0x70
Jan 15 18:17:13 eve kernel: ? __switch_to_asm+0x40/0x70
Jan 15 18:17:13 eve kernel: __vfs_write+0x136/0x1a0
Jan 15 18:17:13 eve kernel: vfs_write+0xa5/0x1a0
Jan 15 18:17:13 eve kernel: ksys_write+0x4f/0xb0
Jan 15 18:17:13 eve kernel: do_fast_syscall_32+0xa7/0x254
Jan 15 18:17:13 eve kernel: entry_SYSCALL_compat_after_hwframe+0x45/0x4d
Jan 15 18:17:13 eve kernel: Modules linked in: twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common fuse xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c tun bridge stp llc xt_multiport devlink ebtable_filter ebtables ip6table_filter ip6_tables it87 hwmon_vid nvidia_drm(POE) nvidia_modeset(POE) nvidia_uvm(OE) uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common snd_usb_audio videodev snd_usbmidi_lib media snd_rawmidi snd_hda_codec_hdmi edac_mce_amd kvm_amd nvidia(POE) kvm irqbypass snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec eeepc_wmi snd_hda_core asus_wmi sparse_keymap snd_hwdep drm_kms_helper rfkill video wmi_bmof snd_seq snd_seq_device drm
Jan 15 18:17:13 eve kernel: snd_pcm fam15h_power k10temp sp5100_tco i2c_piix4 snd_timer snd ipmi_devintf soundcore ipmi_msghandler pcc_cpufreq acpi_cpufreq vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc dm_crypt mxm_wmi crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel serio_raw r8169 wmi
Jan 15 18:17:13 eve kernel: ---[ end trace 34388ea4d17727fe ]---
Jan 15 18:17:13 eve kernel: RIP: 0010:__mutex_lock.isra.5+0x74/0x490
Jan 15 18:17:13 eve kernel: Code: 49 01 00 00 48 39 c6 0f 84 c7 03 00 00 65 48 8b 04 25 00 5c 01 00 48 8b 00 a8 08 75 18 49 8b 07 48 83 e0 f8 0f 84 a5 01 00 00 <8b> 40 38 85 c0 0f 85 9a 01 00 00 65 48 8b 04 25 00 5c 01 00 48 8b
Jan 15 18:17:13 eve kernel: RSP: 0018:ffffae1905cf7d20 EFLAGS: 00010286
Jan 15 18:17:13 eve kernel: RAX: 8000000000000000 RBX: ffff997fbc8383c0 RCX: 0000000000000063
Jan 15 18:17:13 eve kernel: RDX: 8000000000000000 RSI: ffff998023341f00 RDI: ffff997fbc8383c0
Jan 15 18:17:13 eve kernel: RBP: ffffae1905cf7da0 R08: ffff997f7e703eb0 R09: 0000000000000000
Jan 15 18:17:13 eve kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002
Jan 15 18:17:13 eve kernel: R13: ffff997f7874b700 R14: ffff997fbc8383c0 R15: ffff997fbc8383c0
Jan 15 18:17:13 eve kernel: FS:  0000000081fdc000(0063) GS:ffff9980aebc0000(006b) knlGS:000000001b8b3b40
Jan 15 18:17:13 eve kernel: CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
Jan 15 18:17:13 eve kernel: CR2: 0000000020330000 CR3: 000000025a1cc000 CR4: 00000000000406e0
Jan 15 18:17:15 eve abrt-dump-journal-oops[1337]: Reported 1 kernel oopses to Abrt
Jan 15 18:20:51 eve kernel: general protection fault: 0000 [#3] SMP NOPTI
Jan 15 18:20:51 eve kernel: CPU: 2 PID: 5620 Comm: wineserver Tainted: P      D    OE     4.19.9-201.fc28.x86_64 #1
Jan 15 18:20:51 eve kernel: Hardware name: To be filled by O.E.M. To be filled by O.E.M./M5A97 R2.0, BIOS 2201 12/10/2013
Jan 15 18:20:51 eve kernel: RIP: 0010:__mutex_lock.isra.5+0x74/0x490
Jan 15 18:20:51 eve kernel: Code: 49 01 00 00 48 39 c6 0f 84 c7 03 00 00 65 48 8b 04 25 00 5c 01 00 48 8b 00 a8 08 75 18 49 8b 07 48 83 e0 f8 0f 84 a5 01 00 00 <8b> 40 38 85 c0 0f 85 9a 01 00 00 65 48 8b 04 25 00 5c 01 00 48 8b
Jan 15 18:20:51 eve kernel: RSP: 0018:ffffae1901eb7d70 EFLAGS: 00010286
Jan 15 18:20:51 eve kernel: RAX: 8000000000000000 RBX: ffff9980282f7100 RCX: 0000000000000001
Jan 15 18:20:51 eve kernel: RDX: 8000000000000000 RSI: ffff997fbc871f00 RDI: ffff997fbddf93c0
Jan 15 18:20:51 eve kernel: RBP: ffffae1901eb7df0 R08: 0000000000000040 R09: 0000000000000000
Jan 15 18:20:51 eve kernel: R10: ffffae1901eb7ed8 R11: 0000000000000000 R12: 0000000000000002
Jan 15 18:20:51 eve kernel: R13: ffff9980282f7100 R14: ffff997fbddf93c0 R15: ffff997fbddf93c0
Jan 15 18:20:51 eve kernel: FS:  00007fbd04093740(0000) GS:ffff9980aea80000(0000) knlGS:0000000000000000
Jan 15 18:20:51 eve kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 15 18:20:51 eve kernel: CR2: 000011d5f5eff000 CR3: 0000000378398000 CR4: 00000000000406e0
Jan 15 18:20:51 eve kernel: Call Trace:
Jan 15 18:20:51 eve kernel: ? current_time+0x4f/0x90
Jan 15 18:20:51 eve kernel: ? generic_update_time+0xb6/0xd0
Jan 15 18:20:51 eve kernel: pipe_read+0x3f/0x2d0
Jan 15 18:20:51 eve kernel: ? pipe_write+0x25c/0x3f0
Jan 15 18:20:51 eve kernel: __vfs_read+0x133/0x190
Jan 15 18:20:51 eve kernel: vfs_read+0x8a/0x140
Jan 15 18:20:51 eve kernel: ksys_read+0x4f/0xb0
Jan 15 18:20:51 eve kernel: do_syscall_64+0x5b/0x160
Jan 15 18:20:51 eve kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jan 15 18:20:51 eve kernel: RIP: 0033:0x7fbd037c2e61
Jan 15 18:20:51 eve kernel: Code: fe ff ff 50 48 8d 3d 16 b7 09 00 e8 99 05 02 00 66 0f 1f 84 00 00 00 00 00 48 8d 05 81 3b 2d 00 8b 00 85 c0 75 13 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 57 c3 66 0f 1f 44 00 00 41 54 49 89 d4 55 48
Jan 15 18:20:51 eve kernel: RSP: 002b:00007ffd0b4065e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
Jan 15 18:20:51 eve kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fbd037c2e61
Jan 15 18:20:51 eve kernel: RDX: 0000000000000040 RSI: 0000000002a78350 RDI: 0000000000000155
Jan 15 18:20:51 eve kernel: RBP: 0000000002a78200 R08: 0000000002a57130 R09: 0000000000000007
Jan 15 18:20:51 eve kernel: R10: 00376cae8f8d5f4c R11: 0000000000000246 R12: 00007ffd0b40664c
Jan 15 18:20:51 eve kernel: R13: 00007ffd0b4066b8 R14: 0000000000000000 R15: 0000000000000000
Jan 15 18:20:51 eve kernel: Modules linked in: twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common fuse xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c tun bridge stp llc xt_multiport devlink ebtable_filter ebtables ip6table_filter ip6_tables it87 hwmon_vid nvidia_drm(POE) nvidia_modeset(POE) nvidia_uvm(OE) uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common snd_usb_audio videodev snd_usbmidi_lib media snd_rawmidi snd_hda_codec_hdmi edac_mce_amd kvm_amd nvidia(POE) kvm irqbypass snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec eeepc_wmi snd_hda_core asus_wmi sparse_keymap snd_hwdep drm_kms_helper rfkill video wmi_bmof snd_seq snd_seq_device drm
Jan 15 18:20:51 eve kernel: snd_pcm fam15h_power k10temp sp5100_tco i2c_piix4 snd_timer snd ipmi_devintf soundcore ipmi_msghandler pcc_cpufreq acpi_cpufreq vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc dm_crypt mxm_wmi crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel serio_raw r8169 wmi
Jan 15 18:20:51 eve kernel: ---[ end trace 34388ea4d17727ff ]---
Jan 15 18:20:51 eve kernel: RIP: 0010:__mutex_lock.isra.5+0x74/0x490
Jan 15 18:20:51 eve kernel: Code: 49 01 00 00 48 39 c6 0f 84 c7 03 00 00 65 48 8b 04 25 00 5c 01 00 48 8b 00 a8 08 75 18 49 8b 07 48 83 e0 f8 0f 84 a5 01 00 00 <8b> 40 38 85 c0 0f 85 9a 01 00 00 65 48 8b 04 25 00 5c 01 00 48 8b
Jan 15 18:20:51 eve kernel: RSP: 0018:ffffae1905cf7d20 EFLAGS: 00010286
Jan 15 18:20:51 eve kernel: RAX: 8000000000000000 RBX: ffff997fbc8383c0 RCX: 0000000000000063
Jan 15 18:20:51 eve kernel: RDX: 8000000000000000 RSI: ffff998023341f00 RDI: ffff997fbc8383c0
Jan 15 18:20:51 eve kernel: RBP: ffffae1905cf7da0 R08: ffff997f7e703eb0 R09: 0000000000000000
Jan 15 18:20:51 eve kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002
Jan 15 18:20:51 eve kernel: R13: ffff997f7874b700 R14: ffff997fbc8383c0 R15: ffff997fbc8383c0
Jan 15 18:20:51 eve kernel: FS:  00007fbd04093740(0000) GS:ffff9980aea80000(0000) knlGS:0000000000000000
Jan 15 18:20:51 eve kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 15 18:20:51 eve kernel: CR2: 000011d5f5eff000 CR3: 0000000378398000 CR4: 00000000000406e0
Jan 15 18:20:51 eve kernel: general protection fault: 0000 [#4] SMP NOPTI
Jan 15 18:20:51 eve kernel: CPU: 2 PID: 5620 Comm: wineserver Tainted: P      D    OE     4.19.9-201.fc28.x86_64 #1
Jan 15 18:20:51 eve kernel: Hardware name: To be filled by O.E.M. To be filled by O.E.M./M5A97 R2.0, BIOS 2201 12/10/2013
Jan 15 18:20:51 eve kernel: RIP: 0010:__mutex_lock.isra.5+0x74/0x490
Jan 15 18:20:51 eve kernel: Code: 49 01 00 00 48 39 c6 0f 84 c7 03 00 00 65 48 8b 04 25 00 5c 01 00 48 8b 00 a8 08 75 18 49 8b 07 48 83 e0 f8 0f 84 a5 01 00 00 <8b> 40 38 85 c0 0f 85 9a 01 00 00 65 48 8b 04 25 00 5c 01 00 48 8b
Jan 15 18:20:51 eve kernel: RSP: 0018:ffffae1901eb7db0 EFLAGS: 00010286
Jan 15 18:20:51 eve kernel: RAX: 8000000000000000 RBX: ffff997fbddf93c0 RCX: 0000000000000000
Jan 15 18:20:51 eve kernel: RDX: 8000000000000000 RSI: ffff997fbc871f00 RDI: ffff997fbddf93c0
Jan 15 18:20:51 eve kernel: RBP: ffffae1901eb7e30 R08: 0000000000000000 R09: 0000000000000000
Jan 15 18:20:51 eve kernel: R10: 0000000000000000 R11: 0000000000000001 R12: 0000000000000002
Jan 15 18:20:51 eve kernel: R13: ffff9980aca2e920 R14: ffff997f2e1c2f00 R15: ffff997fbddf93c0
Jan 15 18:20:51 eve kernel: FS:  00007fbd04093740(0000) GS:ffff9980aea80000(0000) knlGS:0000000000000000
Jan 15 18:20:51 eve kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 15 18:20:51 eve kernel: CR2: 000011d5f5eff000 CR3: 000000012520a000 CR4: 00000000000406e0
Jan 15 18:20:51 eve kernel: Call Trace:
Jan 15 18:20:51 eve kernel: ? kmem_cache_free+0x1b1/0x1e0
Jan 15 18:20:51 eve kernel: pipe_release+0x1e/0xa0
Jan 15 18:20:51 eve kernel: __fput+0xb4/0x220
Jan 15 18:20:51 eve kernel: task_work_run+0x84/0xa0
Jan 15 18:20:51 eve kernel: do_exit+0x2d2/0xb30
Jan 15 18:20:51 eve kernel: ? ksys_read+0x4f/0xb0
Jan 15 18:20:51 eve kernel: rewind_stack_do_exit+0x17/0x20
Jan 15 18:20:51 eve kernel: Modules linked in: twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common fuse xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c tun bridge stp llc xt_multiport devlink ebtable_filter ebtables ip6table_filter ip6_tables it87 hwmon_vid nvidia_drm(POE) nvidia_modeset(POE) nvidia_uvm(OE) uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common snd_usb_audio videodev snd_usbmidi_lib media snd_rawmidi snd_hda_codec_hdmi edac_mce_amd kvm_amd nvidia(POE) kvm irqbypass snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec eeepc_wmi snd_hda_core asus_wmi sparse_keymap snd_hwdep drm_kms_helper rfkill video wmi_bmof snd_seq snd_seq_device drm
Jan 15 18:20:51 eve kernel: snd_pcm fam15h_power k10temp sp5100_tco i2c_piix4 snd_timer snd ipmi_devintf soundcore ipmi_msghandler pcc_cpufreq acpi_cpufreq vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc dm_crypt mxm_wmi crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel serio_raw r8169 wmi
Jan 15 18:20:51 eve kernel: ---[ end trace 34388ea4d1772800 ]---
Jan 15 18:20:51 eve kernel: RIP: 0010:__mutex_lock.isra.5+0x74/0x490
Jan 15 18:20:51 eve kernel: Code: 49 01 00 00 48 39 c6 0f 84 c7 03 00 00 65 48 8b 04 25 00 5c 01 00 48 8b 00 a8 08 75 18 49 8b 07 48 83 e0 f8 0f 84 a5 01 00 00 <8b> 40 38 85 c0 0f 85 9a 01 00 00 65 48 8b 04 25 00 5c 01 00 48 8b
Jan 15 18:20:51 eve kernel: RSP: 0018:ffffae1905cf7d20 EFLAGS: 00010286
Jan 15 18:20:51 eve kernel: RAX: 8000000000000000 RBX: ffff997fbc8383c0 RCX: 0000000000000063
Jan 15 18:20:51 eve kernel: RDX: 8000000000000000 RSI: ffff998023341f00 RDI: ffff997fbc8383c0
Jan 15 18:20:51 eve kernel: RBP: ffffae1905cf7da0 R08: ffff997f7e703eb0 R09: 0000000000000000
Jan 15 18:20:51 eve kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002
Jan 15 18:20:51 eve kernel: R13: ffff997f7874b700 R14: ffff997fbc8383c0 R15: ffff997fbc8383c0
Jan 15 18:20:51 eve kernel: FS:  00007fbd04093740(0000) GS:ffff9980aea80000(0000) knlGS:0000000000000000
Jan 15 18:20:51 eve kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 15 18:20:51 eve kernel: CR2: 000011d5f5eff000 CR3: 000000012520a000 CR4: 00000000000406e0
Jan 15 18:20:51 eve kernel: Fixing recursive fault but reboot is needed!
Jan 15 18:20:51 eve kernel: general protection fault: 0000 [#5] SMP NOPTI
Jan 15 18:20:51 eve kernel: CPU: 6 PID: 6051 Comm: Client.exe Tainted: P      D    OE     4.19.9-201.fc28.x86_64 #1
Jan 15 18:20:51 eve kernel: Hardware name: To be filled by O.E.M. To be filled by O.E.M./M5A97 R2.0, BIOS 2201 12/10/2013
Jan 15 18:20:51 eve kernel: RIP: 0010:__mutex_lock.isra.5+0x74/0x490
Jan 15 18:20:51 eve kernel: Code: 49 01 00 00 48 39 c6 0f 84 c7 03 00 00 65 48 8b 04 25 00 5c 01 00 48 8b 00 a8 08 75 18 49 8b 07 48 83 e0 f8 0f 84 a5 01 00 00 <8b> 40 38 85 c0 0f 85 9a 01 00 00 65 48 8b 04 25 00 5c 01 00 48 8b
Jan 15 18:20:51 eve kernel: RSP: 0018:ffffae1907cb7e00 EFLAGS: 00010286
Jan 15 18:20:51 eve kernel: RAX: 8000000000000000 RBX: ffff997fbddf93c0 RCX: ffff9980aca2e900
Jan 15 18:20:51 eve kernel: RDX: 8000000000000000 RSI: ffff997f7e705d00 RDI: ffff997fbddf93c0
Jan 15 18:20:51 eve kernel: RBP: ffffae1907cb7e78 R08: 0000000000000000 R09: 0000000000000000
Jan 15 18:20:51 eve kernel: R10: ffffae1907cb7ea8 R11: 0000000000000000 R12: 0000000000000002
Jan 15 18:20:51 eve kernel: R13: ffff9980aca2e920 R14: ffff997f2e1c2f00 R15: ffff997fbddf93c0
Jan 15 18:20:51 eve kernel: FS:  0000000081fbc000(0063) GS:ffff9980aeb80000(006b) knlGS:000000001c193b40
Jan 15 18:20:51 eve kernel: CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
Jan 15 18:20:51 eve kernel: CR2: 000000001c192ae0 CR3: 000000025a1cc000 CR4: 00000000000406e0
Jan 15 18:20:51 eve kernel: Call Trace:
Jan 15 18:20:51 eve kernel: ? kmem_cache_free+0x1b1/0x1e0
Jan 15 18:20:51 eve kernel: pipe_release+0x1e/0xa0
Jan 15 18:20:51 eve kernel: __fput+0xb4/0x220
Jan 15 18:20:51 eve kernel: task_work_run+0x84/0xa0
Jan 15 18:20:51 eve kernel: exit_to_usermode_loop+0xd3/0xe0
Jan 15 18:20:51 eve kernel: do_fast_syscall_32+0x234/0x254
Jan 15 18:20:51 eve kernel: entry_SYSCALL_compat_after_hwframe+0x45/0x4d
Jan 15 18:20:51 eve kernel: Modules linked in: twofish_generic twofish_avx_x86_64 twofish_x86_64_3way twofish_x86_64 twofish_common fuse xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c tun bridge stp llc xt_multiport devlink ebtable_filter ebtables ip6table_filter ip6_tables it87 hwmon_vid nvidia_drm(POE) nvidia_modeset(POE) nvidia_uvm(OE) uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common snd_usb_audio videodev snd_usbmidi_lib media snd_rawmidi snd_hda_codec_hdmi edac_mce_amd kvm_amd nvidia(POE) kvm irqbypass snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec eeepc_wmi snd_hda_core asus_wmi sparse_keymap snd_hwdep drm_kms_helper rfkill video wmi_bmof snd_seq snd_seq_device drm
Jan 15 18:20:51 eve kernel: snd_pcm fam15h_power k10temp sp5100_tco i2c_piix4 snd_timer snd ipmi_devintf soundcore ipmi_msghandler pcc_cpufreq acpi_cpufreq vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc dm_crypt mxm_wmi crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel serio_raw r8169 wmi
Jan 15 18:20:51 eve kernel: ---[ end trace 34388ea4d1772801 ]---
Jan 15 18:20:51 eve kernel: RIP: 0010:__mutex_lock.isra.5+0x74/0x490
Jan 15 18:20:51 eve kernel: Code: 49 01 00 00 48 39 c6 0f 84 c7 03 00 00 65 48 8b 04 25 00 5c 01 00 48 8b 00 a8 08 75 18 49 8b 07 48 83 e0 f8 0f 84 a5 01 00 00 <8b> 40 38 85 c0 0f 85 9a 01 00 00 65 48 8b 04 25 00 5c 01 00 48 8b
Jan 15 18:20:51 eve kernel: RSP: 0018:ffffae1905cf7d20 EFLAGS: 00010286
Jan 15 18:20:51 eve kernel: RAX: 8000000000000000 RBX: ffff997fbc8383c0 RCX: 0000000000000063
Jan 15 18:20:51 eve kernel: RDX: 8000000000000000 RSI: ffff998023341f00 RDI: ffff997fbc8383c0
Jan 15 18:20:51 eve kernel: RBP: ffffae1905cf7da0 R08: ffff997f7e703eb0 R09: 0000000000000000
Jan 15 18:20:51 eve kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002
Jan 15 18:20:51 eve kernel: R13: ffff997f7874b700 R14: ffff997fbc8383c0 R15: ffff997fbc8383c0
Jan 15 18:20:51 eve kernel: FS:  0000000081fbc000(0063) GS:ffff9980aeb80000(006b) knlGS:000000001c193b40
Jan 15 18:20:51 eve kernel: CS:  0010 DS: 002b ES: 002b CR0: 0000000080050033
Jan 15 18:20:51 eve kernel: CR2: 000000001c192ae0 CR3: 000000025a1cc000 CR4: 00000000000406e0
Jan 15 18:20:56 eve abrt-dump-journal-oops[1337]: Reported 3 kernel oopses to Abrt

Comment 11 customercare 2019-01-15 17:35:26 UTC

Remove Comment #10 .. different bugreport :(

Comment 12 Justin M. Forbes 2019-01-29 16:24:25 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.20.5-100.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 have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29.

If you experience different issues, please open a new bug report for those.

Comment 13 Justin M. Forbes 2019-02-21 21:11:01 UTC

*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 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.

Note You need to log in before you can comment on or make changes to this bug.