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 1435430 - yum warning: /dev/mem (mmap): Operation not permitted
Summary: yum warning: /dev/mem (mmap): Operation not permitted
Keywords:
Status: CLOSED DUPLICATE of bug 1438869
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: subscription-manager
Version: 7.4
Hardware: ppc64le
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-23 18:58 UTC by Robert Peterson
Modified: 2017-05-02 15:12 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-10 15:52:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Robert Peterson 2017-03-23 18:58:34 UTC 
Description of problem:
Almost every yum command gives this WARNING message when
it's done, on ppc64le arch:

Complete!

** COLLECTED WARNINGS **
/dev/mem (mmap): Operation not permitted
No SMBIOS nor DMI entry point found, sorry.
** END OF WARNINGS **

dmesg says:
[ 3657.769255] Program yum tried to access /dev/mem between f0000->100000.

Version-Release number of selected component (if applicable):
RHEL7.4
I used a variety of kernels, but this time:
Linux gfs-p8-02-lp01 3.10.0-618.el7.bz1429822.ppc64le #1 SMP Thu Mar 23 12:18:25 EDT 2017 ppc64le ppc64le ppc64le GNU/Linux

How reproducible:
Always

Steps to Reproduce:
1.yum -y update -or- yum -y install <anything>

Actual results:
See above

Expected results:
No warnings should be issued

Additional info:
This is an LPAR
Comment 2 Thomas Huth 2017-03-29 06:58:16 UTC 
FWIW, I get the same error messages on a (big endian) bare-metal POWER8 system here:

$ uname -r
3.10.0-628.el7.ppc64
$ yum --version
3.4.3
  Installed: rpm-4.11.3-25.el7.ppc64 at 2017-03-29 01:30
  Built    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at 2017-03-17 09:53
  Committed: Panu Matilainen <pmatilai> at 2017-03-17

  Installed: subscription-manager-1.19.4-1.el7.ppc64 at 2017-03-29 01:31
  Built    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at 2017-03-20 19:48
  Committed: Kevin Howell <khowell> at 2017-03-20

  Installed: yum-3.4.3-154.el7.noarch at 2017-03-29 01:30
  Built    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at 2017-03-27 16:30
  Committed: Valentina Mukhamedzhanova <vmukhame> at 2017-03-27

** COLLECTED WARNINGS **
Failed to open memory buffer (/dev/mem): Permission denied
No SMBIOS nor DMI entry point found, sorry.
** END OF WARNINGS **


... and in dmesg I've got:

 Program rhsmcertd-worke tried to access /dev/mem between f0000->100000.
 Program yum tried to access /dev/mem between f0000->100000.
Comment 3 Erico Nunes 2017-04-04 13:24:52 UTC 
I get the same on s390x, so it's not just ppc64.

# uname -r
3.10.0-637.el7.s390x
# yum --version
3.4.3
  Installed: rpm-4.11.3-25.el7.s390x at 2017-04-04 12:45
  Built    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at 2017-03-17 09:57
  Committed: Panu Matilainen <pmatilai> at 2017-03-17

  Installed: subscription-manager-1.19.5-1.el7.s390x at 2017-04-04 12:45
  Built    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at 2017-03-30 17:53
  Committed: Kevin Howell <khowell> at 2017-03-30

  Installed: yum-3.4.3-154.el7.noarch at 2017-04-04 12:45
  Built    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at 2017-03-27 16:30
  Committed: Valentina Mukhamedzhanova <vmukhame> at 2017-03-27

** COLLECTED WARNINGS **
/dev/mem (mmap): Operation not permitted
No SMBIOS nor DMI entry point found, sorry.
** END OF WARNINGS **

# dmesg
[  130.610557] Program rhsmcertd-worke tried to access /dev/mem between f0000->100000.
[  130.771300] Program rhsmcertd-worke tried to access /dev/mem between f0000->100000.
[ 1393.946460] Program rhsmd tried to access /dev/mem between f0000->100000.
[ 1578.622139] Program yum tried to access /dev/mem between f0000->100000.
[ 1583.880329] Program yum tried to access /dev/mem between f0000->100000.
[ 1678.823551] Program yum tried to access /dev/mem between f0000->100000.
[ 1773.450485] Program yum tried to access /dev/mem between f0000->100000.
[ 1808.989671] Program yum tried to access /dev/mem between f0000->100000.
Comment 4 Milos Malik 2017-04-05 12:15:54 UTC 
# uname -a
Linux intentionally.removed.redhat.com 3.10.0-632.el7.ppc64 #1 SMP Mon Mar 27 22:55:04 EDT 2017 ppc64 ppc64 ppc64 GNU/Linux
#

yumdownloader triggers such messages too:

# dmesg
[ 1570.781208] Program yum tried to access /dev/mem between f0000->100000.
[ 1661.490834] Program yum tried to access /dev/mem between f0000->100000.
[ 1782.470679] Program yumdownloader tried to access /dev/mem between f0000->100000.
[ 1911.827690] Program yumdownloader tried to access /dev/mem between f0000->100000.
#
Comment 11 Mike Gahagan 2017-04-07 15:27:58 UTC 
As far as I know this is expected behavior. The kernel doesn't allow access to /dev/mem for any architecture other than x86 for security reasons.
Comment 12 Michal Domonkos 2017-04-07 15:38:17 UTC 
(In reply to Mike Gahagan from comment #11)
> As far as I know this is expected behavior. The kernel doesn't allow access
> to /dev/mem for any architecture other than x86 for security reasons.

Thanks, that's one more reason to think this should be solved in sub-man, so reassigning.
Comment 13 Kevin Howell 2017-04-10 15:52:56 UTC 

*** This bug has been marked as a duplicate of bug 1438869 ***
Note You need to log in before you can comment on or make changes to this bug.