Bug 786839

Summary:	failed to set kernel thread priorities at boot
Product:	Red Hat Enterprise MRG	Reporter:	evcz
Component:	realtime-kernel	Assignee:	Luis Claudio R. Goncalves <lgoncalv>
Status:	CLOSED NOTABUG	QA Contact:	David Sommerseth <davids>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	2.1	CC:	bhu, lgoncalv, ovasik, williams
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-02-02 15:42:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description evcz 2012-02-02 14:40:09 UTC

Description of problem:
On 3.0.9-rt26.46.el6rt.x86_64 in the boot.log multiple errors are reported related to kernel thread prioriorities

Version-Release number of selected component (if applicable):
3.0.9-rt26.46.el6rt.x86_64

How reproducible:
boot the system using 3.0.9-rt26.46.el6rt.x86_64

Steps to Reproduce:
1. install 3.0.9-rt26.46.el6rt.x86_64
2. boot 3.0.9-rt26.46.el6rt.x86_64
3. cat /var/boot.log
  
Actual results:
Setting kernel thread priorities: chrt: failed to set pid 7's policy: Invalid argument
chrt: failed to set pid 15's policy: Invalid argument
chrt: failed to set pid 22's policy: Invalid argument
chrt: failed to set pid 28's policy: Invalid argument
chrt: failed to set pid 34's policy: Invalid argument
chrt: failed to set pid 40's policy: Invalid argument
chrt: failed to set pid 46's policy: Invalid argument
chrt: failed to set pid 52's policy: Invalid argument
^[[60G[^[[0;32m  OK  ^[[0;39m]

Expected results:
Setting kernel thread priorities: ^[[60G[^[[0;32m  OK  ^[[0;39m]

Additional info:
in /etc/security/limits.conf I do have some limits in place for rtprio but only for *, not for root.

Additionally on the same machines no errors are reported while booting 2.6.33.9-rt31.79.el6rt.x86_64

Comment 1 Luis Claudio R. Goncalves 2012-02-02 15:05:56 UTC

What is the version of rtctl you are using?

The current version of rtctl should have and empty rtgroups for mrg-2.1, meaning that it would use the default priorities. That would make it quite hard for these errors to happen.

Comment 2 evcz 2012-02-02 15:42:51 UTC

Hi, yes
You are correct.

The machines that were reporting me those errors were still running
rtctl-1.9-2.el6.noarch

instead the updated ones (rtctl-1.9-5.el6.noarch) are booting up without errors.

Sorry for the bug report :/

Comment 3 Luis Claudio R. Goncalves 2012-02-02 16:17:29 UTC

Thanks for verifying that! And thanks for reporting the anomalous behaviour you are observing in your system, that helps us to offer a better product.