Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 858204 [details] kernel log Description of problem: [70113.347271] BUG: unable to handle kernel paging request at ffffffffffffff89 [70113.347311] IP: [<ffffffff811ced17>] do_mount+0x887/0xa90 [70113.347339] PGD 1c0f067 PUD 1c11067 PMD 0 [70113.347360] Oops: 0002 [#1] SMP [70113.347377] Modules linked in: tcp_lp rfcomm nls_utf8 isofs fuse ip6t_rpfilter ip6t_REJECT xt_conntrack cfg80211 ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw bnep joydev hid_logitech_dj btusb bluetooth rfkill usb_storage vfat fat x86_pkg_temp_thermal coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul iTCO_wdt crc32c_intel iTCO_vendor_support snd_hda_codec_realtek ghash_clmulni_intel snd_hda_codec_hdmi snd_hda_intel snd_hda_codec microcode snd_hwdep snd_seq serio_raw snd_seq_device i2c_i801 snd_pcm r8169 lpc_ich mfd_core snd_page_alloc [70113.347739] mii mei_me snd_timer mei shpchp snd soundcore binfmt_misc i915 i2c_algo_bit drm_kms_helper drm i2c_core video [70113.347793] CPU: 6 PID: 2418 Comm: chrome Not tainted 3.12.9-301.fc20.x86_64 #1 [70113.347822] Hardware name: Gigabyte Technology Co., Ltd. Z87M-D3H/Z87M-D3H, BIOS F9a 09/30/2013 [70113.347856] task: ffff8807b6205280 ti: ffff88078d43e000 task.ti: ffff88078d43e000 [70113.347886] RIP: 0010:[<ffffffff811ced17>] [<ffffffff811ced17>] do_mount+0x887/0xa90 [70113.347920] RSP: 0018:ffff88078d43fe40 EFLAGS: 00010282 [70113.347941] RAX: 0000000000000000 RBX: 0000000000000009 RCX: 0000000000000000 [70113.347969] RDX: ffff88079497dd98 RSI: 0000000000000286 RDI: 0000000000000286 [70113.347997] RBP: ffff88078d43ff08 R08: ffff88079497dd99 R09: 0000000000000000 [70113.348024] R10: ffff8804959f1d98 R11: 00000000000001c4 R12: 0000000000000001 [70113.348052] R13: 00007fff614fbd48 R14: 0000000000000000 R15: 00007fff614fbd74 [70113.348081] FS: 00007f95716bca00(0000) GS:ffff88081f380000(0000) knlGS:0000000000000000 [70113.348112] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [70113.348135] CR2: ffffffffffffff89 CR3: 000000078d41f000 CR4: 00000000001407e0 [70113.348159] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [70113.348174] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [70113.348189] Stack: [70113.348194] ffff88078d43fe88 ffff8807949b9100 ffff88078d43ff50 ffff88078d43fef8 [70113.348212] ffffffff8157e2f5 0000000000000001 0000000000000000 ffff88078d43fef8 [70113.348230] 00000001811ae34a 0000000000000000 0000000000000000 ffff8807949b9110 [70113.348248] Call Trace: [70113.348258] [<ffffffff8157e2f5>] ? sk_run_filter+0x295/0x700 [70113.348271] [<ffffffff810cf8d1>] SyS_futex+0x71/0x150 [70113.348284] [<ffffffff81676cb7>] tracesys+0xdd/0xe2 [70113.348295] Code: ff ff 89 d8 48 98 e9 56 f8 ff ff b8 ea ff ff ff 48 98 e9 4a f8 ff ff 48 c7 c7 4b 01 a3 81 be d0 00 00 00 4c 89 4d a0 e8 58 ea f8 <ff> 49 89 85 40 03 00 00 48 8b 43 08 41 bd f4 ff ff ff 4c 8b 4d [70113.348374] RIP [<ffffffff811ced17>] do_mount+0x887/0xa90 [70113.348387] RSP <ffff88078d43fe40> [70113.348394] CR2: ffffffffffffff89 [70113.354039] ---[ end trace f56c0cc1612bc139 ]---
Created attachment 858206 [details] Memory 100% fine after 145 hours test!!!
*********** MASS BUG UPDATE ************** 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 20 kernel bugs. Fedora 20 has now been rebased to 3.13.4-200.fc20. Please test this kernel update 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.
Mikhail, this _really_ looks like hardware problem, but not detectable by memtest. Note that you are reporting strange crashes not only in kernel but also on other components like gnome, so whole system is very unstable. Thought is also possible that random memory corruptions are caused by some kernel driver or subsystem, but that is less probable. There is some problem with Gigabyte *87* motherboards like yours Z87M-D3H, I have another memory corruption bug reported by someone else on Z87-HD3 (https://bugzilla.kernel.org/show_bug.cgi?id=68171) As Alan already pointed on https://bugzilla.kernel.org/show_bug.cgi?id=64521, it could be electro magnetic interference (EMI) . Perhaps those boards have pure EMI protection. It is possible that nearby is located some strong electro magnetic source i.e. radio emitter and that disturb board functioning. You could also ask Gigabyte for support (perhaps board sill has guarantee, hence you can ask for new one, not from *87* series ?). I'm going to close your bug reports from Z87M-D3H as duplicate of that one. Even if you hit true kernel bug, we can not be sure it was not caused by corruption. Obviously I will not close your bug reports happened on other hardware.
*** Bug 1065780 has been marked as a duplicate of this bug. ***
*** Bug 1063006 has been marked as a duplicate of this bug. ***
*** Bug 1058065 has been marked as a duplicate of this bug. ***
*** Bug 998320 has been marked as a duplicate of this bug. ***
*** Bug 1015748 has been marked as a duplicate of this bug. ***
*** Bug 1019233 has been marked as a duplicate of this bug. ***
*** Bug 1021257 has been marked as a duplicate of this bug. ***
*** Bug 1023750 has been marked as a duplicate of this bug. ***
*** Bug 1027419 has been marked as a duplicate of this bug. ***
*** Bug 1033948 has been marked as a duplicate of this bug. ***
*** Bug 1036259 has been marked as a duplicate of this bug. ***
*** Bug 1043656 has been marked as a duplicate of this bug. ***
*** Bug 1034410 has been marked as a duplicate of this bug. ***
*** Bug 1043729 has been marked as a duplicate of this bug. ***
*** Bug 1047052 has been marked as a duplicate of this bug. ***
*** Bug 1057306 has been marked as a duplicate of this bug. ***
*** Bug 1059889 has been marked as a duplicate of this bug. ***
*** Bug 1069368 has been marked as a duplicate of this bug. ***
*** Bug 1070445 has been marked as a duplicate of this bug. ***
Did you try to use only 2 DIMM slots as suggested on this thread http://www.tonymacx86.com/general-help/121042-solved-4-dimm-crashing-freezing-ga-z87.html ?
I remember this bug: https://groups.google.com/forum/#!topic/linux.kernel/Z5MJEk_OWGE It was CPU floating point state problem that cause memory corruption. Are your CPU AES-NI capable or have some other cryptography/checksum offload engine ? If so you could try to disable that by removing proper modules .
Also on bug that I worked before https://bugzilla.kernel.org/show_bug.cgi?id=68171, corruption was easier to reproduce when external USB dongle was used, perhaps issue is related with USB hardware or software.
(In reply to Stanislaw Gruszka from comment #23) > Did you try to use only 2 DIMM slots as suggested on this thread > http://www.tonymacx86.com/general-help/121042-solved-4-dimm-crashing- > freezing-ga-z87.html ? Yes, but it's not helps solve problem described at https://bugzilla.redhat.com/show_bug.cgi?id=989070 When I insert the ESI Juli @ sound card in the PCI slot and the system becomes unbootable. Please look photos: https://bugzilla.redhat.com/attachment.cgi?id=869294 and https://bugzilla.redhat.com/attachment.cgi?id=869295 (In reply to Stanislaw Gruszka from comment #24) > I remember this bug: > https://groups.google.com/forum/#!topic/linux.kernel/Z5MJEk_OWGE > > It was CPU floating point state problem that cause memory corruption. Are > your CPU AES-NI capable or have some other cryptography/checksum offload > engine ? If so you could try to disable that by removing proper modules . How do it?
(In reply to Mikhail from comment #26) > Yes, but it's not helps solve problem described at > https://bugzilla.redhat.com/show_bug.cgi?id=989070 > When I insert the ESI Juli @ sound card in the PCI slot and the system > becomes unbootable. > > Please look photos: https://bugzilla.redhat.com/attachment.cgi?id=869294 and > https://bugzilla.redhat.com/attachment.cgi?id=869295 This is certainly a H/W problem, ask Gigabyte for support. > How do it? Look at modules with *aes* , *crc* or other encryption/checksum names and blacklist them.
*********** MASS BUG UPDATE ************** 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 20 kernel bugs. Fedora 20 has now been rebased to 3.14.4-200.fc20. 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.