Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1361598 - importing dmidecode causes an error mesage in dmesg on non-x86 architectures
Summary: importing dmidecode causes an error mesage in dmesg on non-x86 architectures
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: python-dmidecode
Version: 6.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Petr Oros
QA Contact: Mike Gahagan
URL:
Whiteboard:
Depends On:
Blocks: 1324586
TreeView+ depends on / blocked
 
Reported: 2016-07-29 13:22 UTC by Jakub Filak
Modified: 2017-12-06 12:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 12:39:14 UTC


Attachments (Terms of Use)

Description Jakub Filak 2016-07-29 13:22:36 UTC
Description of problem:
"python -C 'import dmidecode'" results in the following error in the kernel ring buffer:

   Program <progam> tried to access /dev/mem between f0000->100000.

Version-Release number of selected component (if applicable):
python-dmidecode-3.10.13-3.el6

How reproducible:
always

Steps to Reproduce:
1. python -C 'import dmidecode'
2.
3.

Actual results:
The error message in dmesg.


Expected results:
No error message.

Comment 7 Jan Kurik 2017-12-06 12:39:14 UTC
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/


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