public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: Eric Paris <eparis@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michal Hocko <mhocko@suse.cz>, Ben Zhang <benzh@chromium.org>
Subject: Re: [PATCH] watchdog: print all locks on a softlock
Date: Thu, 1 May 2014 15:17:20 -0400	[thread overview]
Message-ID: <20140501191720.GA198341@redhat.com> (raw)
In-Reply-To: <1398970535-6880-1-git-send-email-eparis@redhat.com>

On Thu, May 01, 2014 at 02:55:35PM -0400, Eric Paris wrote:
> If the CPU hits a softlockup this patch will also have it print the
> information about all locks being held on the system.  This might help
> determine if a lock is being held too long leading to this problem.

I am not sure this helps you.  A softlockup is the result of pre-emption
disabled, ie the scheduler not being called after 60 seconds.  Holding a
lock does not disable pre-emption usually.  So I don't think this is going
to add anything.

Are you trying to debug a hung task?  The the hung_task thread checks to
see if a task hasn't scheduled in 2 minutes or so.  That could be the
result of long lock (but that output already dumps the lockdep stuff).

Cheers,
Don

> 
> Signed-off-by: Eric Paris <eparis@redhat.com>
> Cc: Frederic Weisbecker <fweisbec@gmail.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Don Zickus <dzickus@redhat.com>
> Cc: Michal Hocko <mhocko@suse.cz>
> Cc: Ben Zhang <benzh@chromium.org>
> ---
>  kernel/watchdog.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/kernel/watchdog.c b/kernel/watchdog.c
> index 516203e..a027240 100644
> --- a/kernel/watchdog.c
> +++ b/kernel/watchdog.c
> @@ -322,6 +322,7 @@ static enum hrtimer_restart watchdog_timer_fn(struct hrtimer *hrtimer)
>  			current->comm, task_pid_nr(current));
>  		print_modules();
>  		print_irqtrace_events(current);
> +		debug_show_all_locks();
>  		if (regs)
>  			show_regs(regs);
>  		else
> -- 
> 1.9.0
> 

  reply	other threads:[~2014-05-01 19:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-01 18:55 [PATCH] watchdog: print all locks on a softlock Eric Paris
2014-05-01 19:17 ` Don Zickus [this message]
2014-05-01 20:09   ` Frederic Weisbecker
2014-05-01 20:43     ` Frederic Weisbecker
2014-05-01 21:11     ` Don Zickus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140501191720.GA198341@redhat.com \
    --to=dzickus@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=benzh@chromium.org \
    --cc=eparis@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox