Bug 752705 - kernel tainted after rhel6.1 64bit OS installed
Summary: kernel tainted after rhel6.1 64bit OS installed
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: cachefilesd
Version: 6.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: 6.1
Assignee: David Howells
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks: 767187
TreeView+ depends on / blocked
 
Reported: 2011-11-10 07:33 UTC by zou.chris
Modified: 2017-12-06 12:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
RHEL6.1
Last Closed: 2017-12-06 12:24:36 UTC
Target Upstream Version:


Attachments (Terms of Use)
dmesg information (50.00 KB, application/octet-stream)
2011-11-16 00:54 UTC, zou.chris
no flags Details
tainted number (10 bytes, application/octet-stream)
2011-11-16 00:55 UTC, zou.chris
no flags Details
RHEL6.2 Beta Dmesg (58.55 KB, application/octet-stream)
2011-11-16 03:07 UTC, zou.chris
no flags Details

Description zou.chris 2011-11-10 07:33:39 UTC
Description of problem:
kernel tainted after rhel6.1 64bit OS installed

Version-Release number of selected component (if applicable):
RHEL6.1 64bit

How reproducible:


Steps to Reproduce:
1.OS installed by DVDROM
2.After OS installation finished, type "cat /proc/sys/kernel/tainted"
3.The tainted number is not "0", the kernel tainted in rhel6.1 64bit OS.
  
Actual results:


Expected results:


Additional info: 
1.RHEL6 64bit is OK.
2.When we change thurley platfrom or Romley, the tainted number also is not 0
3.After "chkconfig cachefilesd off" reboot OS, the tainted number is 0
4.RHEL6.2 Beta, atfer run the command above in item3, the tainted still is not 0

Comment 3 David Howells 2011-11-15 23:21:01 UTC
Could we get a look at your dmesg log please?  That should contain more information.

This looks like it may be an instance of bug 696396 - which ought to be fixed in RHEL-6.2.

Comment 4 zou.chris 2011-11-16 00:54:18 UTC
Created attachment 533870 [details]
dmesg information

dmesg information

Comment 5 zou.chris 2011-11-16 00:55:04 UTC
Created attachment 533871 [details]
tainted number

tainted number

Comment 6 zou.chris 2011-11-16 01:15:24 UTC
The dmesg information and tainted number see the attachment, the OS is RHEL6.1 64bit. The tainted number is OS installed with full packages.After chkconfig cachefilesd off, the taint is 0, RHEL6.2 beta, I will upload later.

Comment 7 zou.chris 2011-11-16 02:59:20 UTC
In RHEL6.2 Beta, OS installation finished, the tainted number is 536870912, after run "chkconfig cachefilesd off", the tainted number still 536870912, but in RHEL6.1 64bit, the number will change to "0".

Comment 8 zou.chris 2011-11-16 03:07:46 UTC
Created attachment 533883 [details]
RHEL6.2 Beta Dmesg

RHEL6.2 Beta Dmesg

Comment 11 Suzanne Logcher 2012-02-14 23:19:52 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. 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. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 12 Jan Kurik 2017-12-06 12:24:36 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.