Bug 1105839 - [abrt] kernel BUG at include/linux/mm.h:449! [NEEDINFO]
Summary: [abrt] kernel BUG at include/linux/mm.h:449!
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:b4b4e6606c647a618959e61ec1f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-08 04:42 UTC by macbruins
Modified: 2014-12-10 15:01 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-12-10 15:01:27 UTC
Type: ---
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)
File: dmesg (42.81 KB, text/plain)
2014-06-08 04:42 UTC, macbruins
no flags Details

Description macbruins 2014-06-08 04:42:22 UTC
Additional info:
reporter:       libreport-2.2.1
kernel BUG at include/linux/mm.h:449!
invalid opcode: 0000 [#1] SMP 
Modules linked in: arc4 md4 nls_utf8 cifs dns_resolver fscache cfg80211 rfkill ip6t_REJECT nf_conntrack_ipv6 nf_conntrack_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter xt_conntrack nf_conntrack ip6_tables xen_netfront coretemp microcode nfsd auth_rpcgss nfs_acl lockd sunrpc xen_blkfront
CPU: 1 PID: 22384 Comm: firefox Not tainted 3.13.9-200.fc20.x86_64 #1
task: ffff88013ebc1140 ti: ffff8800b831a000 task.ti: ffff8800b831a000
RIP: e030:[<ffffffff816857b4>]  [<ffffffff816857b4>] get_page.part.43+0x4/0x6
RSP: e02b:ffff8800b831bc78  EFLAGS: 00010246
RAX: 0000000000000000 RBX: 000000019e340945 RCX: 0000000000000000
RDX: ffffea0000000000 RSI: 00007f0104719000 RDI: 000000019e340945
RBP: ffff8800b831bc78 R08: ffff8800fd6e0508 R09: 00007f0104714000
R10: 00000007f0104714 R11: ffff88003992ff40 R12: ffff88003981a8c8
R13: ffff8800399768c8 R14: 00007f0104719000 R15: 0000000000000008
FS:  00007f010e5c2780(0000) GS:ffff880149100000(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00007f57dccaf008 CR3: 0000000122c9a000 CR4: 0000000000002660
Stack:
 ffff8800b831bd28 ffffffff8117329e 0000000000000000 ffff8800bc5e4880
 ffff88013e467480 ffff88013ebc1140 ffff8801403a9118 ffff8800bc5e4800
 ffffea0000e60680 ffffea0000e65d80 ffff88004cc03118 ffff8800b831bfd8
Call Trace:
 [<ffffffff8117329e>] copy_pte_range+0x34e/0x510
 [<ffffffff8117433d>] copy_page_range+0x30d/0x490
 [<ffffffff8106acb8>] dup_mm+0x328/0x640
 [<ffffffff8106b9f5>] copy_process.part.26+0x9f5/0x1530
 [<ffffffff8106c6e4>] do_fork+0xb4/0x350
 [<ffffffff8106ca06>] SyS_clone+0x16/0x20
 [<ffffffff816970c9>] stub_clone+0x69/0x90
 [<ffffffff81696d69>] ? system_call_fastpath+0x16/0x1b
Code: 74 0c 4c 89 e0 48 c1 e0 06 48 29 d8 eb 02 31 c0 5b 41 5c 5d c3 55 48 89 e5 0f 0b 55 48 89 e5 0f 0b 55 48 89 e5 0f 0b 55 48 89 e5 <0f> 0b 55 48 89 e5 0f 0b 55 48 89 e5 0f 0b 55 48 89 e5 0f 0b 55 
RIP  [<ffffffff816857b4>] get_page.part.43+0x4/0x6
 RSP <ffff8800b831bc78>

Comment 1 macbruins 2014-06-08 04:42:25 UTC
Created attachment 903207 [details]
File: dmesg

Comment 2 Josh Boyer 2014-06-09 12:23:35 UTC
Does this happen with any of the 3.14.y updates in F20?

Comment 3 macbruins 2014-06-10 05:58:10 UTC
The bug happened only once and it was the only kernel crash I had since I started using F20.

Comment 4 Justin M. Forbes 2014-11-13 16:02:05 UTC
*********** 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.

Comment 5 Justin M. Forbes 2014-12-10 15:01:27 UTC
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.


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