From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.70 (virgin) hangs running SDET
Date: Tue, 10 Jun 2003 10:34:31 -0700 [thread overview]
Message-ID: <12190000.1055266471@flay> (raw)
In-Reply-To: <5930000.1055254447@[10.10.2.4]>
>> The ps instance which is spinning on kernel_flag in proc_root_lookup is
>> what's holding things up.
>>
>> Or is it spinning in proc_lookup() or proc_pid_lookup()? I have a vague
>> feeling that I've seen these traces miss out the innermost stack slot...
>>
>> Suggest:
>>
>> a) Use CONFIG_SPINLINE, get a new sysrq-T trace
>>
>> b) Enable spinlock debugging
>>
>> c) Try disabling the sched_balance_exec() code.
>
>
> Moving that locking around as discussed last night didn't fix it.
> It did last 2.5 cycles of repeated SDET this time instead of 0.5,
> but that might just be coincidence, as the hang looks the same. Got
> a better backtrace out of her this time though ....
>
> Want me to back out the patch I was pointing fingers at? Or I can
> carry on with the path you suggested above if you think it'll help ...
OK, well backing out dcache_lock-vs-tasklist_lock-take-3.patch does
indeed seem to fix the problem. It's done 5.5 whole cycles now, and
still going strong.
M.
next prev parent reply other threads:[~2003-06-10 17:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <60380000.1055188542@flay>
2003-06-09 21:08 ` 2.5.70 (virgin) hangs running SDET Andrew Morton
2003-06-10 5:27 ` Martin J. Bligh
2003-06-10 14:14 ` Martin J. Bligh
2003-06-10 17:34 ` Martin J. Bligh [this message]
2003-06-10 19:46 ` Andrew Morton
2003-06-10 20:01 ` William Lee Irwin III
2003-06-11 5:06 ` Martin J. Bligh
2003-06-11 5:21 ` Andrew Morton
2003-06-11 14:36 ` Martin J. Bligh
2003-06-09 20:21 Martin J. Bligh
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=12190000.1055266471@flay \
--to=mbligh@aracnet.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
/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.