From owner-freebsd-amd64@FreeBSD.ORG  Wed Jan 30 09:40:41 2008
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 494AE16A41B;
	Wed, 30 Jan 2008 09:40:41 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 33B8213C47E;
	Wed, 30 Jan 2008 09:40:40 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <47A04617.6030608@FreeBSD.org>
Date: Wed, 30 Jan 2008 10:40:39 +0100
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031)
MIME-Version: 1.0
To: Dennis Glatting <freebsd@penx.com>
References: <1201388299.84900.12.camel@Sylvester.dco.penx.com>	<20080129202643.6BF568DE@fep1.cogeco.net>	<200801291900.42989.jhb@freebsd.org>
	<1201660069.95413.9.camel@Sylvester.dco.penx.com>
In-Reply-To: <1201660069.95413.9.camel@Sylvester.dco.penx.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: kensmith@freebsd.org, freebsd-amd64@freebsd.org
Subject: Re: Multi processor locking problem under 7.0
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jan 2008 09:40:41 -0000

Dennis Glatting wrote:

>>> There are no errors on the screen but it no longer proceeds with the 
>>> port build. When I suspend the process and restart the make in the 
>>> same session it has no problem getting past this impasse and with a 
>>> few suspends the make finishes without error. It does not happen 
>>> every time which is very odd.
>>>
>>> Based on your description above it seems like it may be the same problem.
>>>
>>> What do you think?
>> If you have threads blocked on "vmo_de" then upgrade to the latest RELENG_7 or 
>> RELENG_7_0 (specifically the sys/kern/subr_sleepqueue.c file) and try again.
>>
> 
> I got the right file and updated my systems. I ran dump on the IBM
> system five times. Dump hung four times, three times when 99.99%
> complete. Below is a ps output.
> 
> How do I tell what the threads are blocked on?
> 
> 
> Daffy> ps -axwHl | grep dump
>     0   801     1   0  96  0 20952  4060 select Is    ??
> 0:00.00 /usr/sbin/sshd -f /etc/ssh/dumper/sshd_config
>     0 14682   870   0   8  0 34388 26628 wait   I+    p0    0:00.20 dump
> 0uaLCf 24 /dev/null /usr (dump)
>     0 14774 14682   0   4  0 34388 30680 sbwait I+    p0    0:01.01
> dump: /dev/aacd0s1e: pass 4: 14.97% done, finished in 0:03 at T
>     0 14775 14774   0  20  0 34388 26644 pause  I+    p0    0:00.69 dump
> 0uaLCf 24 /dev/null /usr (dump)
>     0 14776 14774   0  20  0 34388 26644 pause  I+    p0    0:00.69 dump
> 0uaLCf 24 /dev/null /usr (dump)
>     0 14777 14774   0  20  0 34388 26644 pause  I+    p0    0:00.69 dump
> 0uaLCf 24 /dev/null /usr (dump)
>   600 14896 12552   0  96  0  5900  1184 -      R+    p2    0:00.00 grep
> dump

The wait channel is the "select/wait/..." column, but your problem is 
known and is believed to be unrelated to what John said.  He was 
addressing the other respondent ("Paul") who described an apparently 
unrelated problem where dump is not in play at all (and which has 
different symptoms).

Kris