Red Hat Bugzilla – Bug 842121
[abrt]: BUG: Bad page map in process geeqie pte:20000000000000 pmd:15ba2e067
Last modified: 2012-11-14 11:33:06 EST
libreport version: 2.0.10
cmdline: BOOT_IMAGE=/vmlinuz-3.4.4-4.fc16.x86_64 root=UUID=abb3a498-7e1c-4dc3-ba8c-c1772e7a9edd ro rd.md=0 rd.lvm=0 rd.dm=0 KEYTABLE=us LANG=zh_CN.UTF-8 rd.luks=0 loglevel=7
:BUG: Bad page map in process geeqie pte:20000000000000 pmd:15ba2e067
:addr:00007f2db8bb3000 vm_flags:08000071 anon_vma: (null) mapping:ffff8801e9fc9d70 index:202
:Pid: 20937, comm: geeqie Not tainted 3.4.4-4.fc16.x86_64 #1
: [<ffffffff81145989>] print_bad_pte+0x1d9/0x270
: [<ffffffff8114730c>] unmap_single_vma+0x5cc/0x850
: [<ffffffff8112f446>] ? release_pages+0x1d6/0x220
: [<ffffffff81147d70>] unmap_vmas+0x60/0xb0
: [<ffffffff8114fc16>] exit_mmap+0x96/0x140
: [<ffffffff810553e7>] mmput+0x77/0x110
: [<ffffffff8105c4b5>] exit_mm+0x105/0x130
: [<ffffffff8105c649>] do_exit+0x169/0x8d0
: [<ffffffff8108bad0>] ? wake_up_state+0x10/0x20
: [<ffffffff81069f7d>] ? signal_wake_up+0x2d/0x40
: [<ffffffff8106b123>] ? zap_other_threads+0x83/0xa0
: [<ffffffff8105d102>] do_group_exit+0x42/0xa0
: [<ffffffff8105d177>] sys_exit_group+0x17/0x20
: [<ffffffff816043e9>] system_call_fastpath+0x16/0x1b
# Mass update to all open bugs.
Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.
Please retest with this kernel, and let us know if your problem has been fixed.
In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with. Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.
If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.