Hide Forgot
Description of problem: Was running an rsync to backup /home (mirror software raid disk mount) to usb disk. I assume all memory was being used. Try to run 'top', but machine had hung by then. I will try another rsync to see if it can be reproduced. Additional info: reporter: libreport-2.7.2 kernel BUG at mm/workingset.c:426! invalid opcode: 0000 [#1] SMP Modules linked in: uas usb_storage fuse ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_broute bridge ebtable_nat ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables it87 hwmon_vid vfat fat ppdev kvm_amd kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel raid1 snd_hda_codec_realtek joydev snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel sp5100_tco snd_hda_codec i2c_piix4 fam15h_power k10temp snd_hda_core snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer snd parport_pc soundcore parport shpchp acpi_cpufreq video tpm_tis tpm_tis_core tpm binfmt_misc nfsd auth_rpcgss nfs_acl lockd grace sunrpc amdkfd amd_iommu_v2 radeon crc32c_intel serio_raw i2c_algo_bit 8021q drm_kms_helper garp stp llc mrp ttm drm r8169 mii fjes i2c_dev CPU: 3 PID: 57 Comm: kswapd0 Not tainted 4.8.7-200.fc24.x86_64 #1 Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./F2A88XM-HD3P, BIOS F2 12/24/2015 task: ffff9332ebfc5b80 task.stack: ffff9332ecb50000 RIP: 0010:[<ffffffffa11ed48a>] [<ffffffffa11ed48a>] shadow_lru_isolate+0xaa/0x1a0 RSP: 0018:ffff9332ecb53be8 EFLAGS: 00010046 RAX: 0000004000000000 RBX: ffff9330ba8d97e0 RCX: ffffffffa1c4ed5d RDX: 0000000000000001 RSI: ffff9330ba8d96e8 RDI: ffff9330ba8d96e8 RBP: ffff9332ecb53c18 R08: ffff9330ba8d96e8 R09: 0000000000000046 R10: 000000000001d110 R11: 0000000000000000 R12: ffff9332ed0c4d00 R13: ffff9330ba8d96e8 R14: ffff933098bceb10 R15: ffff9330ba8d98f8 FS: 0000000000000000(0000) GS:ffff9332fed80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fee32f67000 CR3: 0000000410547000 CR4: 00000000000406e0 Stack: 00000000000a80fb ffff9332ed0c4d08 ffff9332ed0c4d00 ffff9332ecb53d18 ffff9330cbbbe498 ffff9330ba8d96e8 ffff9332ecb53c68 ffffffffa11ec690 000000000000000c 0000000000000000 ffffffffa11ed3e0 00000000000000b2 Call Trace: [<ffffffffa11ec690>] __list_lru_walk_one.isra.3+0x90/0x120 [<ffffffffa11ed3e0>] ? count_shadow_nodes+0xb0/0xb0 [<ffffffffa11ec743>] list_lru_walk_one+0x23/0x30 [<ffffffffa11ed314>] scan_shadow_nodes+0x34/0x50 [<ffffffffa11cf822>] shrink_slab.part.39+0x1e2/0x3d0 [<ffffffffa11cfa39>] shrink_slab+0x29/0x30 [<ffffffffa11d4478>] shrink_node+0x108/0x320 [<ffffffffa11d5466>] kswapd+0x2f6/0x710 [<ffffffffa11d5170>] ? mem_cgroup_shrink_node+0x170/0x170 [<ffffffffa10c0c08>] kthread+0xd8/0xf0 [<ffffffffa180273f>] ret_from_fork+0x1f/0x40 [<ffffffffa10c0b30>] ? kthread_worker_fn+0x180/0x180 Code: 80 41 89 45 ec 49 8b 46 58 48 85 c0 74 55 48 83 e8 01 49 89 46 58 48 83 c3 08 49 39 df 74 76 48 8b 03 48 85 c0 74 ef a8 02 75 bf <0f> 0b 41 c6 04 24 00 bb 04 00 00 00 fb 66 0f 1f 44 00 00 e8 3e RIP [<ffffffffa11ed48a>] shadow_lru_isolate+0xaa/0x1a0 RSP <ffff9332ecb53be8>
Created attachment 1221961 [details] File: dmesg
*********** 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.
*********** 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.