Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1617941 - RT system hang due to wrong of rq's nr_running [rhel-7.5.z]
RT system hang due to wrong of rq's nr_running [rhel-7.5.z]
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kernel-rt (Show other bugs)
7.4
x86_64 Linux
high Severity urgent
: rc
: ---
Assigned To: Luis Claudio R. Goncalves
Jiri Kastner
Marie Dolezelova
: ZStream
Depends On: 1608672 1618466
Blocks:
  Show dependency treegraph
 
Reported: 2018-08-16 04:25 EDT by Oneata Mircea Teodor
Modified: 2018-09-25 15:11 EDT (History)
9 users (show)

See Also:
Fixed In Version: kernel-rt-3.10.0-862.13.1.rt56.816.el7
Doc Type: Bug Fix
Doc Text:
Previously, preemption was enabled too early after a context switch. If a task was migrated to another CPU after a context switch, a mismatch between CPU and runqueue during load balancing sometimes occurred. Consequently, a runnable task on an idle CPU failed to run, and the operating system became unresponsive. This update disables preemption in the schedule_tail() function. As a result, CPU migration during post-schedule processing no longer occurs, which prevents the above mismatch. The operating system no longer hangs due to this bug.
Story Points: ---
Clone Of: 1608672
Environment:
Last Closed: 2018-09-25 15:10:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:2763 None None None 2018-09-25 15:11 EDT

  None (edit)
Description Oneata Mircea Teodor 2018-08-16 04:25:39 EDT
This bug has been copied from bug #1608672 and has been proposed to be backported to 7.5 z-stream (EUS).
Comment 8 errata-xmlrpc 2018-09-25 15:10:41 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2018:2763

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