Date: Tue, 10 Jun 2003 22:21:16 -0700
From: Andrew Morton <akpm@digeo.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.70 (virgin) hangs running SDET
Message-Id: <20030610222116.2fb9c001.akpm@digeo.com>
In-Reply-To: <25140000.1055307962@[10.10.2.4]>
References: <60380000.1055188542@flay>
	<20030609140834.11ad0d63.akpm@digeo.com>
	<5930000.1055254447@[10.10.2.4]>
	<12190000.1055266471@flay>
	<20030610124613.40e65da7.akpm@digeo.com>
	<25140000.1055307962@[10.10.2.4]>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 780
Lines: 20

"Martin J. Bligh" <mbligh@aracnet.com> wrote:
>
> OK, did that. your patches + debug up the wazoo. Bugger all output,
>  and a hang that looks similar, but the culprit is hiding even more,
>  as far as I can't see ;-(

yes, nobody's spinning on the /proc lock any more.

I don't understand why all the tasks in set_cpus_allowed() are showing up
as being in " R " state.  Possibly the wait_for_completion() in there is
stack gunk and they're really spinning on the runqueue lock?

You haven't tried disabling sched_migrate_task() yet?


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/