Bug 503758 - hang check timeout defaults too low for -RT
Summary: hang check timeout defaults too low for -RT
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: realtime-kernel
Version: 1.2
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: Jon Masters
QA Contact: David Sommerseth
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-02 15:00 UTC by Jon Masters
Modified: 2016-05-22 23:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-12-03 12:42:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
increase hung_task_timeout_secs on rt (1012 bytes, patch)
2009-06-02 21:48 UTC, Luis Claudio R. Goncalves
no flags Details | Diff

Description Jon Masters 2009-06-02 15:00:33 UTC
Description of problem:

The default value of the task hangcheck timer is hardcoded to 120 seconds. We need to replace this with a macro and conditional in the case of -RT.

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

.29 RT kernels with hangcheck turned on.

Comment 1 Luis Claudio R. Goncalves 2009-06-02 20:18:51 UTC
I will build -20 today changing this default to 10 minutes (600s) as suggested by Rostedt and Jon. That will be the only change in the kernel so that we can compare the results and infere the impact of this change.

Comment 2 Luis Claudio R. Goncalves 2009-06-02 21:48:14 UTC
Created attachment 346323 [details]
increase hung_task_timeout_secs on rt

Comment 3 Thomas Gleixner 2009-06-02 21:50:44 UTC
> Description of problem:
> 
> The default value of the task hangcheck timer is hardcoded to 120 seconds. We

This is not a problem description. It's a description of a fact.

> need to replace this with a macro and conditional in the case of -RT.

Why ?

Thanks,

         tglx

Comment 4 Jon Masters 2009-12-01 06:35:00 UTC
Luis, Clark, what do you think we should do with this bug?

Comment 5 Luis Claudio R. Goncalves 2009-12-03 12:42:06 UTC
Jon, it has already been addressed in V2.
Thanks!


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