From: Andrew Morton <akpm@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: a.p.zijlstra@chello.nl, linux-kernel@vger.kernel.org
Subject: Re: softlockup: automatically detect hung TASK_UNINTERRUPTIBLE tasks
Date: Wed, 6 Feb 2008 16:31:11 -0800 [thread overview]
Message-ID: <20080206163111.54088622.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080207000425.GA21918@elte.hu>
On Thu, 7 Feb 2008 01:04:25 +0100
Ingo Molnar <mingo@elte.hu> wrote:
>
> * Andrew Morton <akpm@linux-foundation.org> wrote:
>
> > > Does that kernel have:
> > >
> > > commit ed50d6cbc394cd0966469d3e249353c9dd1d38b9
> > > Author: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > > Date: Sat Feb 2 00:23:08 2008 +0100
> > >
> > > debug: softlockup looping fix
> >
> > yup. It was fetched less than 24 hours ago.
>
> does the patch below improve the situation?
>
Nope.
But I tested it on mainline, and mainline exhibits the never-powers-off
symptom, whereas ed50d6cbc394cd0966469d3e249353c9dd1d38b9 demonstrates the
powers-off-after-20-seconds symptom.
So we _may_ be dealing with two bugs here, and your patch might have fixed
the first, but that success is obscured by the second. I guess I need to
prepare a tree which has ed50d6cbc394cd0966469d3e249353c9dd1d38b9 at its
tip. (Wonders how to do that).
btw, mainline (plus this patch, not that it changed anything) prints
<stopping disk stuff>
Disabling non-boot CPUs
CPU 1 is now offline
and that's it. This machine has eight cpus. Might be a hint?
next prev parent reply other threads:[~2008-02-07 0:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200801252259.m0PMxHmD012059@hera.kernel.org>
2008-02-06 0:46 ` softlockup: automatically detect hung TASK_UNINTERRUPTIBLE tasks Andrew Morton
2008-02-06 14:50 ` Peter Zijlstra
2008-02-06 18:05 ` Andrew Morton
2008-02-07 0:04 ` Ingo Molnar
2008-02-07 0:31 ` Andrew Morton [this message]
2008-02-07 0:47 ` Andrew Morton
2008-02-07 0:51 ` Ingo Molnar
2008-02-07 1:12 ` Andrew Morton
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=20080206163111.54088622.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.