Re: [PATCH] disable softlockup detection at boottime
- From: Ingo Molnar <mingo@xxxxxxx>
- Date: Tue, 29 Apr 2008 14:35:22 +0200
* Dimitri Sivanich <sivanich@xxxxxxx> wrote:
On Mon, Apr 28, 2008 at 06:55:44PM +0200, Ingo Molnar wrote:
good idea - but why dont you set softlockup_thresh to 0, which is the
"off" switch already? (and that way it can be turned back on later as
well, by the sysadmin.)
I'm getting unaligned access errors trying to set it to anything, so
it's not working for me currently (2.6.25):
It's tripping up on the address of 'one', which is an int that is not
properly aligned for the unsigned long comparison in
proc_doulongvec_minmax on my 64 bit machine. Also, the value '0' is
invalid for softlockup_thresh, correct?
I temporarily got around these issues with the following hack.
ah, sorry. But ... perhaps using threshold -1 would be the most
intuitive setting? (for 'infinite timeout' ==> softlockup detector
turned off) That way it all becomes configurable as part of the
threshold? No strong opinion though.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
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] disable softlockup detection at boottime
- From: Dimitri Sivanich
- Re: [PATCH] disable softlockup detection at boottime
- References:
- [PATCH] disable softlockup detection at boottime
- From: Dimitri Sivanich
- Re: [PATCH] disable softlockup detection at boottime
- From: Ingo Molnar
- Re: [PATCH] disable softlockup detection at boottime
- From: Dimitri Sivanich
- [PATCH] disable softlockup detection at boottime
- Prev by Date: Re: [patch/rfc 2.6.25-git] gpio: sysfs interface
- Next by Date: Re: sound: azx_get_response timeout
- Previous by thread: Re: [PATCH] disable softlockup detection at boottime
- Next by thread: Re: [PATCH] disable softlockup detection at boottime
- Index(es):
Relevant Pages
|