Bug 710932

Summary: [abrt] kernel: BUG: Bad page map in process gimp-2.7 pte:7b0f5005 pmd:7f6fe067: TAINTED Bad Page
Product: [Fedora] Fedora Reporter: remadna okba <remadnaokba>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: esandeen, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:9853d62d454ea10a2f3da40e08a28133bca7985c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-22 17:52:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description remadna okba 2011-06-05 21:32:31 UTC 
abrt version: 2.0.1
architecture:   i686
cmdline:        BOOT_IMAGE=/boot/vmlinuz-2.6.38.6-27.fc15.i686 ro root=UUID=630752d9-ec39-4030-92dd-15f5ca729522 rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=fr rhgb quiet
component:      kernel
kernel:         2.6.38.6-27.fc15.i686
kernel_tainted: 32
os_release:     Fedora release 15 (Lovelock)
package:        kernel
reason:         BUG: Bad page map in process gimp-2.7  pte:7b0f5005 pmd:7f6fe067
reported_to:    kerneloops: URL=http://submit.kerneloops.org/submitoops.php
time:           Sun Jun  5 00:24:52 2011

backtrace:
:BUG: Bad page map in process gimp-2.7  pte:7b0f5005 pmd:7f6fe067
:page:f573dea0 count:2 mapcount:-1 mapping:d44f56f8 index:0x15702
:page flags: 0x8000082c(referenced|uptodate|lru|private)
:addr:46949000 vm_flags:08100073 anon_vma:f17d52b8 mapping:f37f3d78 index:26
:vma->vm_ops->fault: filemap_fault+0x0/0x31f
:vma->vm_file->f_op->mmap: ext4_file_mmap+0x0/0x45
:Pid: 4937, comm: gimp-2.7 Not tainted 2.6.38.6-27.fc15.i686 #1
:Call Trace:
: [<c07d0c48>] print_bad_pte+0x167/0x179
: [<c04c2f61>] unmap_vmas+0x376/0x600
: [<c04c7231>] exit_mmap+0x91/0xfe
: [<c0438af9>] mmput+0x68/0xc8
: [<c04e91e6>] flush_old_exec+0x435/0x4f5
: [<c0517771>] load_elf_binary+0x2c3/0x1002
: [<c0462120>] ? arch_local_irq_save+0x12/0x17
: [<c07d8fab>] ? do_page_fault+0x0/0x30c
: [<c05a78ea>] ? ima_must_measure+0x27/0x33
: [<c05a7584>] ? ima_bprm_check+0x26/0x2a
: [<c05174ae>] ? load_elf_binary+0x0/0x1002
: [<c04e8adb>] search_binary_handler+0x97/0x21f
: [<c04e9a1e>] do_execve+0x15f/0x220
: [<c04098ba>] sys_execve+0x36/0x5d
: [<c04032ae>] ptregs_execve+0x12/0x18
: [<c07d66b4>] ? syscall_call+0x7/0xb
: [<c07d0000>] ? audit_free_context+0x2/0xc3

event_log:
:2011-06-05-22:32:22> Submitting oops report to http://submit.kerneloops.org/submitoops.php
:2011-06-05-22:32:24  Kernel oops report was uploaded
Comment 1 Dave Jones 2011-07-22 00:06:46 UTC 
something is very very wrong here, and I think all the 9 bugs you filed are likely coming from the same issue.

The untainted ones are where this problem seems to start happening. (this, and 710942, 710956) all seem to have ext4_file_mmap, but that may not necessarily be the cause, just the victim.

All the other bugs (710925, 710930, 710933, 710935, 710948, 710955) all seem to be fallout that happened after the first bug hits.  It's not clear that they're particularly useful.

Can you attach an lsmod output ? Perhaps you're using something unusual which might explain why you're seeing this, and no-one else is.  Is the hardware known to be good ? (passes memtest86 for eg?)
Comment 2 Dave Jones 2011-08-15 22:24:06 UTC 
*** Bug 710942 has been marked as a duplicate of this bug. ***
Comment 3 Dave Jones 2011-08-15 22:24:12 UTC 
*** Bug 710956 has been marked as a duplicate of this bug. ***
Comment 4 Dave Jones 2011-08-15 22:24:24 UTC 
*** Bug 712250 has been marked as a duplicate of this bug. ***
Comment 5 Dave Jones 2011-08-15 22:24:34 UTC 
*** Bug 712574 has been marked as a duplicate of this bug. ***
Comment 6 Dave Jones 2011-08-15 22:24:41 UTC 
*** Bug 713245 has been marked as a duplicate of this bug. ***
Comment 7 Dave Jones 2011-08-15 22:24:50 UTC 
*** Bug 713246 has been marked as a duplicate of this bug. ***
Comment 8 Dave Jones 2011-08-15 22:36:44 UTC 
Please try the 2.6.40 update, and see if this problem is still repeatable.