Description of problem: I disconnected from my network Additional info: reporter: libreport-2.2.2 BUG: Bad rss-counter state mm:ffff880056b5d000 idx:0 val:2 BUG: Bad rss-counter state mm:ffff880056b5d000 idx:1 val:683 BUG: Bad rss-counter state mm:ffff880056b5d000 idx:0 val:2 page:ffffea00072dbb40 count:1 mapcount:1 mapping:ffff88009585bf41 index:0x7f4a18488 page flags: 0x5ffff800080069(locked|uptodate|lru|active|swapbacked) pc:ffff8801d3b36ed0 pc->flags:2 pc->mem_cgroup:ffff8801d5030c00 ------------[ cut here ]------------ kernel BUG at mm/rmap.c:899! invalid opcode: 0000 [#1] SMP Modules linked in: ccm bnep bluetooth 6lowpan_iphc ip6t_rpfilter ip6t_REJECT xt_conntrack 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 snd_hda_codec_idt snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hwdep arc4 iwldvm snd_seq snd_seq_device snd_pcm mac80211 coretemp kvm snd_timer snd crc32c_intel joydev iTCO_wdt iTCO_vendor_support iwlwifi cfg80211 soundcore hp_wmi uvcvideo sparse_keymap rfkill mei_me mei videobuf2_vmalloc videobuf2_memops videobuf2_core hp_accel lis3lv02d lpc_ich mfd_core videodev serio_raw input_polldev media microcode intel_ips i2c_i801 shpchp wmi acpi_cpufreq nfsd auth_rpcgss nfs_acl lockd sunrpc binfmt_misc usb_storage radeon i915 i2c_algo_bit ttm drm_kms_helper drm r8169 mii i2c_core video CPU: 1 PID: 780 Comm: firewalld Not tainted 3.14.3-200.fc20.x86_64 #1 Hardware name: Hewlett-Packard HP Pavilion dv7 Notebook PC/144B, BIOS F.29 11/07/2011 task: ffff8801d0765f00 ti: ffff8801d0894000 task.ti: ffff8801d0894000 RIP: 0010:[<ffffffff811acf8a>] [<ffffffff811acf8a>] page_move_anon_rmap+0x6a/0x80 RSP: 0000:ffff8801d0895ce8 EFLAGS: 00010246 RAX: 000000000000003f RBX: ffffea00072dbb40 RCX: 0000000000000006 RDX: 0000000000000000 RSI: 0000000000000046 RDI: 0000000000000246 RBP: ffff8801d0895d00 R08: 000000000000000a R09: 0000000000000400 R10: 0000000000000000 R11: ffff8801d08959be R12: ffff88009585bf40 R13: 00000007f4a18488 R14: ffffea00025c1330 R15: ffff880095aa4610 FS: 00007f4a185a6740(0000) GS:ffff8801dbc40000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f4a18488f60 CR3: 00000000964c6000 CR4: 00000000000007e0 Stack: ffffea00072dbb40 ffff88003651f000 00007f4a18488f60 ffff8801d0895d88 ffffffff811a0086 ffff8801d0895d70 00000001800f0009 ffff8801d28d42a0 ffff88009704c440 ffff8801d009ac00 ffff8801d0895d80 0000000000000008 Call Trace: [<ffffffff811a0086>] do_wp_page+0x356/0x800 [<ffffffff811a27a8>] handle_mm_fault+0x678/0xef0 [<ffffffff816fa01c>] __do_page_fault+0x18c/0x550 [<ffffffff810d1e41>] ? remove_wait_queue+0x31/0x40 [<ffffffff8108c0bb>] ? do_wait+0x13b/0x260 [<ffffffff8108d20b>] ? SyS_wait4+0x8b/0x110 [<ffffffff816fa402>] do_page_fault+0x22/0x30 [<ffffffff816f6a48>] page_fault+0x28/0x30 Code: 00 49 39 d5 75 1b 49 83 c4 01 4c 89 63 08 5b 41 5c 41 5d 5d c3 31 f6 48 89 df e8 42 e8 fc ff 0f 0b 31 f6 48 89 df e8 36 e8 fc ff <0f> 0b 48 89 d6 e8 8c 06 01 00 48 89 c2 eb c7 0f 0b 0f 1f 44 00 RIP [<ffffffff811acf8a>] page_move_anon_rmap+0x6a/0x80 RSP <ffff8801d0895ce8>
Created attachment 895289 [details] File: dmesg
*********** 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.17.2-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 have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 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.