Bug 722706 - [abrt] kernel: BUG: Bad page map in process dracut pte:101015001494454 pmd:1dae09067: TAINTED -----B
Summary: [abrt] kernel: BUG: Bad page map in process dracut pte:101015001494454 pmd:1...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:fcd897ff5885d8c0437df7bb5dc...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-16 20:39 UTC by Bob Nolty
Modified: 2011-11-22 18:07 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-22 18:07:34 UTC
Type: ---


Attachments (Terms of Use)

Description Bob Nolty 2011-07-16 20:39:34 UTC
abrt version: 2.0.3
architecture:   x86_64
cmdline:        ro root=UUID=4ed49223-5a9b-48b4-a177-9aa7ee877163 rd_LVM_LV=vg_dom0/dom0_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
component:      kernel
kernel:         2.6.38.8-32.fc15.x86_64
kernel_tainted: 32
kernel_tainted_long: System has hit bad_page.
os_release:     Fedora release 15 (Lovelock)
package:        kernel
reason:         BUG: Bad page map in process dracut  pte:101015001494454 pmd:1dae09067
time:           Sat Jul 16 13:33:35 2011

backtrace:
:BUG: Bad page map in process dracut  pte:101015001494454 pmd:1dae09067
:addr:0000000000400000 vm_flags:08001875 anon_vma:          (null) mapping:ffff8802198fe9d8 index:0
:vma->vm_ops->fault: filemap_fault+0x0/0x36c
:vma->vm_file->f_op->mmap: ext4_file_mmap+0x0/0x52
:Pid: 3194, comm: dracut Tainted: G    B       2.6.38.8-32.fc15.x86_64 #1
:Call Trace:
: [<ffffffff8146ee73>] print_bad_pte+0x1a3/0x1bc
: [<ffffffff810f3fda>] handle_pte_fault+0x2fe/0x7a5
: [<ffffffff8106c917>] ? search_exception_tables+0x27/0x38
: [<ffffffff8103085e>] ? fixup_exception+0x1a/0x60
: [<ffffffff810f13cf>] ? pmd_offset+0x19/0x3f
: [<ffffffff810f47f8>] handle_mm_fault+0x1bb/0x1ce
: [<ffffffff81478f30>] do_page_fault+0x358/0x37a
: [<ffffffff81128b28>] ? pipe_write+0x448/0x45a
: [<ffffffff814761d5>] page_fault+0x25/0x30
: [<ffffffff8123168c>] ? __get_user_4+0x1c/0x30
: [<ffffffff8115e1e9>] ? vma_dump_size+0xf2/0x128
: [<ffffffff8115ec63>] elf_core_dump+0x9e3/0xe7b
: [<ffffffff81111cca>] ? kfree+0xcc/0xd8
: [<ffffffff81127cb7>] do_coredump+0x732/0x963
: [<ffffffff81063652>] ? dequeue_signal+0xa9/0x11b
: [<ffffffff81064fde>] get_signal_to_deliver+0x37a/0x3a9
: [<ffffffff81008f43>] do_signal+0x69/0x67f
: [<ffffffff8104127e>] ? should_resched+0xe/0x2d
: [<ffffffff81129e21>] ? path_put+0x1f/0x23
: [<ffffffff8109fc99>] ? audit_syscall_exit+0x12d/0x148
: [<ffffffff8100959a>] do_notify_resume+0x28/0x83
: [<ffffffff81009e90>] int_signal+0x12/0x17

comment:
:I don't know that I did anything to cause it.  In the desktop I was running Brasero, Chromium and Transmission.
:
:I have 8 GB of physical ram, and top reports that no swap is being used.
:
:I got 3 of this error at the same moment, with different addresses in the error message.

Comment 1 Dave Jones 2011-08-15 22:36:39 UTC
Please try the 2.6.40 update, and see if this problem is still repeatable.


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