Bug 1054475 - [abrt] BUG: Bad page map in process pool pte:101015001494454 pmd:3db2a1067 [NEEDINFO]
Summary: [abrt] BUG: Bad page map in process pool pte:101015001494454 pmd:3db2a1067
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:312b2573972f44f84913657b6c1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-16 22:01 UTC by Jussi Eloranta
Modified: 2014-08-15 08:52 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-06-23 14:48:55 UTC
Type: ---
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)
File: dmesg (65.58 KB, text/plain)
2014-01-16 22:02 UTC, Jussi Eloranta
no flags Details

Description Jussi Eloranta 2014-01-16 22:01:56 UTC
Additional info:
reporter:       libreport-2.1.11
BUG: Bad page map in process pool  pte:101015001494454 pmd:3db2a1067
addr:00007f8a55e00000 vm_flags:08000070 anon_vma:          (null) mapping:ffff8803983f98e0 index:1db
vma->vm_ops->fault: filemap_fault+0x0/0x400
vma->vm_file->f_op->mmap: ext4_file_mmap+0x0/0x60
CPU: 0 PID: 28200 Comm: pool Not tainted 3.12.6-300.fc20.x86_64 #1
Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./880GXH/USB3, BIOS P1.20 06/24/2010
 ffff8803ebf34508 ffff8803b88f9ad0 ffffffff816630c1 00007f8a55e00000
 ffff8803b88f9b18 ffffffff81167e88 0101015001494454 00000000000001db
 ffff8803db2a1000 0101015001494454 00007f8a55e00000 00007f8a55e29000
Call Trace:
 [<ffffffff816630c1>] dump_stack+0x45/0x56
 [<ffffffff81167e88>] print_bad_pte+0x1a8/0x240
 [<ffffffff81169898>] unmap_single_vma+0x778/0x910
 [<ffffffff8116aa79>] unmap_vmas+0x49/0x90
 [<ffffffff81173d8c>] exit_mmap+0x9c/0x170
 [<ffffffff81066324>] mmput+0x64/0xf0
 [<ffffffff8106b6d8>] do_exit+0x278/0xa00
 [<ffffffff8106bedf>] do_group_exit+0x3f/0xa0
 [<ffffffff8107a97b>] get_signal_to_deliver+0x1cb/0x5c0
 [<ffffffff81012428>] do_signal+0x48/0x5e0
 [<ffffffff811edaf1>] ? fsnotify+0x241/0x320
 [<ffffffff81012a30>] do_notify_resume+0x70/0xa0
 [<ffffffff816723e2>] int_signal+0x12/0x17

Potential duplicate: bug 995744

Comment 1 Jussi Eloranta 2014-01-16 22:02:00 UTC
Created attachment 851291 [details]
File: dmesg

Comment 2 Justin M. Forbes 2014-02-24 13:57:35 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.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.

Comment 3 Alex 2014-02-28 15:22:26 UTC
Description of problem:
Right after login screen.

Version-Release number of selected component:
kernel

Additional info:
reporter:       libreport-2.1.12
cmdline:        BOOT_IMAGE=/vmlinuz-3.13.4-200.fc20.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap vconsole.font=latarcyrheb-sun16 rd.lvm.lv=fedora/root rhgb quiet LANG=en_US.UTF-8
kernel:         3.13.4-200.fc20.x86_64
runlevel:       N 5
type:           Kerneloops

Truncated backtrace:
BUG: Bad page map in process plasma-desktop  pte:008b2a64 pmd:0003f067
addr:00007fe158dbf000 vm_flags:08000070 anon_vma:          (null) mapping:ffff880064881510 index:92
vma->vm_ops->fault: filemap_fault+0x0/0x400
vma->vm_file->f_op->mmap: ext4_file_mmap+0x0/0x60
CPU: 1 PID: 1471 Comm: plasma-desktop Not tainted 3.13.4-200.fc20.x86_64 #1
Hardware name: Dell Inc. Latitude D620                   /0FT292, BIOS A10 05/16/2008
 ffff88005a6f6ac8 ffff88005102dad0 ffffffff81686b68 00007fe158dbf000
 ffff88005102db18 ffffffff811707c3 00000000008b2a64 0000000000000092
 ffff88000003fdf8 00000000008b2a64 00007fe158dbf000 00007fe158e00000
Call Trace:
 [<ffffffff81686b68>] dump_stack+0x45/0x56
 [<ffffffff811707c3>] print_bad_pte+0x1a3/0x250
 [<ffffffff81172205>] unmap_single_vma+0x785/0x920
 [<ffffffff811733a9>] unmap_vmas+0x49/0x90
 [<ffffffff8117c62c>] exit_mmap+0x9c/0x170
 [<ffffffff8114bf1b>] ? wait_on_page_bit_killable+0x7b/0x90
 [<ffffffff8106a673>] mmput+0x63/0xf0
 [<ffffffff8106f868>] do_exit+0x268/0xa10
 [<ffffffff81170b31>] ? __do_fault+0x71/0x500
 [<ffffffff8107008f>] do_group_exit+0x3f/0xa0
 [<ffffffff8107eb0b>] get_signal_to_deliver+0x1cb/0x5d0
 [<ffffffff81013448>] do_signal+0x48/0x5e0
 [<ffffffff811d75e4>] ? mntput+0x24/0x40
 [<ffffffff811ba6e7>] ? __fput+0x167/0x230
 [<ffffffff81013a50>] do_notify_resume+0x70/0xa0
 [<ffffffff8168db7c>] retint_signal+0x48/0x8c

Comment 4 Justin M. Forbes 2014-06-23 14:48:55 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 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.