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 1441680 - Program yum tried to access /dev/mem between f0000->100000
Summary: Program yum tried to access /dev/mem between f0000->100000
Keywords:
Status: CLOSED DUPLICATE of bug 1438869
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: yum
Version: 7.4
Hardware: ppc64le
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Valentina Mukhamedzhanova
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-12 13:00 UTC by Chunyu Hu
Modified: 2017-04-12 13:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-12 13:05:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Chunyu Hu 2017-04-12 13:00:21 UTC 
Description of problem:

yum and several programm try to access /dev/mem address f0000->100000.

[root@ibm-p8-kvm-03-guest-02 ~]# rpm -q yum
yum-3.4.3-154.el7.noarch

[root@ibm-p8-kvm-03-guest-02 ~]# uname -r
3.10.0-648.el7.ppc64le

[root@ibm-p8-kvm-03-guest-02 ~]# hostname
ibm-p8-kvm-03-guest-02.rhts.eng.bos.redhat.com


Version-Release number of selected component (if applicable):

yum-3.4.3-154.el7.noarch

How reproducible:
always

Steps to Reproduce:
[root@ibm-p8-kvm-03-guest-02 ~]# yum search smtctl

Loaded plugins: product-id, search-disabled-repos, subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
Warning: No matches found for: smtctl
No matches found

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


Actual results:

[root@ibm-p8-kvm-03-guest-02 ~]# dmesg
[   77.534166] random: nonblocking pool is initialized
[  162.646585] Program rhsmcertd-worke tried to access /dev/mem between f0000->100000.
[  162.871805] Program rhsmcertd-worke tried to access /dev/mem between f0000->100000.
[  181.218392] Program yum tried to access /dev/mem between f0000->100000.

Expected results:

No error shown when executing yum search.

Additional info:
[root@ibm-p8-kvm-03-guest-02 ~]# grep /dev/mem /var/log/messages  | awk '{print $7,$8,$9, $10, $11,$12,$13 $14}' | sort | uniq
rhsmcertd-worke tried to access /dev/mem between f0000->100000.
rhsmd tried to access /dev/mem between f0000->100000.
yum tried to access /dev/mem between f0000->100000.
Comment 2 Valentina Mukhamedzhanova 2017-04-12 13:05:17 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.