RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 815612 - kernel BUG at mm/mmap.c:2352!
Summary: kernel BUG at mm/mmap.c:2352!
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.1
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Li Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-24 04:09 UTC by Tao Ma
Modified: 2016-08-25 14:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-25 14:59:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Tao Ma 2012-04-24 04:09:04 UTC 
Description of problem:
kernel version:
2.6.32-131.21.1.el5.x86_64

<0>[12053827.111539] ------------[ cut here ]------------
<2>[12053827.116475] kernel BUG at mm/mmap.c:2352!
<0>[12053827.120801] invalid opcode: 0000 [#1] SMP
<0>[12053827.125245] last sysfs file: /sys/devices/system/cpu/cpu23/cache/index2/shared_cpu_map
<4>[12053827.133529] CPU 13
<4>[12053827.322373] <0> ffff880c034f51d0 ffff880c034f5140 ffff880a5a9cdcc8 ffffffff8105fb55
<4>[12053827.330476] <0> ffff880ac2ee3d38 ffff880ac2ee3540 ffff880a5a9cdd08 ffffffff81066605
<0>[12053827.338820] Call Trace:
<4>[12053827.341592]  [<ffffffff8105fb55>] mmput+0x65/0x100
<4>[12053827.346704]  [<ffffffff81066605>] exit_mm+0x105/0x140
<4>[12053827.352072]  [<ffffffff810667ed>] do_exit+0x1ad/0x840
<4>[12053827.357442]  [<ffffffff81078680>] ? __sigqueue_free+0x40/0x50
<4>[12053827.363512]  [<ffffffff81066ec1>] do_group_exit+0x41/0xb0
<4>[12053827.369229]  [<ffffffff8107ccf8>] get_signal_to_deliver+0x1e8/0x430
<4>[12053827.375820]  [<ffffffff8100a554>] do_notify_resume+0xf4/0x8a0
<4>[12053827.381889]  [<ffffffff811f82f6>] ? security_task_kill+0x16/0x20
<4>[12053827.388217]  [<ffffffff8107a992>] ? recalc_sigpending+0x32/0x80
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 2 RHEL Program Management 2012-05-03 05:23:34 UTC 
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 5 Linda Wang 2016-08-25 14:59:19 UTC 
This issue has been reported against RHEL6.1.
Since we have not encountered or able to
reproduce this issue with our latest kernels,
and due to lack of information, we plan to close this bz.
If you have encountered these issues again, please 
feel free to reopen the BZ.

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