Date: Wed, 11 Jun 2003 07:36:00 -0700
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
Message-ID: <26960000.1055342159@[10.10.2.4]>
In-Reply-To: <20030610222116.2fb9c001.akpm@digeo.com>
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]> <20030610222116.2fb9c001.akpm@digeo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 947
Lines: 28

>> 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?

Damn it, we really need this shit to use frame pointers, and give accurate
info ;-(
 
> You haven't tried disabling sched_migrate_task() yet?

Nope, will do that next, but I presume you mean balance on exec, from
previous conversations ... 

Thanks,

M.


-
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/