From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0.aculab.com (mx0.aculab.com [213.249.233.131]) by ozlabs.org (Postfix) with SMTP id 0BC49B6F6F for ; Thu, 7 Jul 2011 17:48:39 +1000 (EST) Received: from mx0.aculab.com ([127.0.0.1]) by localhost (mx0.aculab.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 02544-09 for ; Thu, 7 Jul 2011 08:48:33 +0100 (BST) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: [PATCH 4/4] powerpc: Enable lockup and hung task detectors in pseriesand ppc64 defeconfigs Date: Thu, 7 Jul 2011 08:46:30 +0100 Message-ID: In-Reply-To: <20110706231337.327165192@samba.org> From: "David Laight" To: "Anton Blanchard" , Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , =20 > As a result of changes to Kconfig files, we no longer enable > the lockup and hung task detectors. Both are very light weight > and provide useful information in the event of a hang, so > reenable them. ... > +CONFIG_LOCKUP_DETECTOR=3Dy > +CONFIG_DETECT_HUNG_TASK=3Dy Is one of thise responsible for generating a kernel stack traceback when a process has been sleeping uninterruptably for a 'long' time? We have a kernel subsystem that has several 'worker' threads, these always sleep uninterruptable (they are shut down by explicit request) and, at times, can be idle for long periods. Perhaps it should be possible to disable the check either on a per-process of per sleep basis? David