Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1408016
| From | Mailing Lists <mailinglists35@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | How was "120" chosen for CONFIG_DEFAULT_HUNG_TASK_TIMEOUT? |
| Date | 2016-05-27 13:30 +0200 |
| Message-ID | <rDo7L-2N5-5@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
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 linux.kernel | Previous | Next | Find similar | Unroll thread
How was "120" chosen for CONFIG_DEFAULT_HUNG_TASK_TIMEOUT? Mailing Lists <mailinglists35@gmail.com> - 2016-05-27 13:30 +0200
csiph-web