* Ravikiran G Thirumalai <[email protected]> wrote: > > also, i think the valid threshold should be between 1 and 60 seconds > > i think. > > 60 seconds! Is that not a pretty high threshold? The reason for > lowering the tolerance threshold from 10s is to catch bugs early in > lab environments, but why do we need to raise the tolerance thresh > beyond 10s? just in case someone sees false positives and wants to turn it off. Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [patch] Change softlockup trigger limit using a kernel parameter
- From: Jeremy Fitzhardinge <[email protected]>
- Re: [patch] Change softlockup trigger limit using a kernel parameter
- References:
- [patch] Change softlockup trigger limit using a kernel parameter
- From: Ravikiran G Thirumalai <[email protected]>
- Re: [patch] Change softlockup trigger limit using a kernel parameter
- From: Andrew Morton <[email protected]>
- Re: [patch] Change softlockup trigger limit using a kernel parameter
- From: Ravikiran G Thirumalai <[email protected]>
- Re: [patch] Change softlockup trigger limit using a kernel parameter
- From: Andrew Morton <[email protected]>
- Re: [patch] Change softlockup trigger limit using a kernel parameter
- From: Ingo Molnar <[email protected]>
- Re: [patch] Change softlockup trigger limit using a kernel parameter
- From: Ravikiran G Thirumalai <[email protected]>
- [patch] Change softlockup trigger limit using a kernel parameter
- Prev by Date: Re: [1/2] 2.6.22-git: known regressions
- Next by Date: [GIT PATCH] hwmon patches against 2.6.22
- Previous by thread: Re: [patch] Change softlockup trigger limit using a kernel parameter
- Next by thread: Re: [patch] Change softlockup trigger limit using a kernel parameter
- Index(es):
 |