Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1408016 > unrolled thread
| Started by | Mailing Lists <mailinglists35@gmail.com> |
|---|---|
| First post | 2016-05-27 13:30 +0200 |
| Last post | 2016-05-27 13:30 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
How was "120" chosen for CONFIG_DEFAULT_HUNG_TASK_TIMEOUT? Mailing Lists <mailinglists35@gmail.com> - 2016-05-27 13:30 +0200
| From | Mailing Lists <mailinglists35@gmail.com> |
|---|---|
| Date | 2016-05-27 13:30 +0200 |
| Subject | How was "120" chosen for CONFIG_DEFAULT_HUNG_TASK_TIMEOUT? |
| Message-ID | <rDo7L-2N5-5@gated-at.bofh.it> |
Hello, I'm trying to understand how this value has been chosen. Was it arbitrary, or did it come up after some rationale? If alter it to a lower value like 30 (or 60), and a piece of third party code hung in D state triggers the kernel hung task complain message, can I still report this as an issue to that code's issue tracker even if the message is not shown at default value of 120? Thanks. Please cc me for replies, as I'm not subscribed.
Back to top | Article view | linux.kernel
csiph-web