From nobody@FreeBSD.org  Wed Dec 23 08:26:53 2009
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 2242A1065679
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 23 Dec 2009 08:26:53 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id 110348FC0C
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 23 Dec 2009 08:26:53 +0000 (UTC)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.3/8.14.3) with ESMTP id nBN8QqC4076373
	for <freebsd-gnats-submit@FreeBSD.org>; Wed, 23 Dec 2009 08:26:52 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.3/8.14.3/Submit) id nBN8QqWs076372;
	Wed, 23 Dec 2009 08:26:52 GMT
	(envelope-from nobody)
Message-Id: <200912230826.nBN8QqWs076372@www.freebsd.org>
Date: Wed, 23 Dec 2009 08:26:52 GMT
From: Vaclav Haisman <v.haisman@sh.cvut.cz>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Unspecified lockup/deadlock with 7.2 on AMD64
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         141915
>Category:       kern
>Synopsis:       [hang] Unspecified lockup/deadlock with 7.2 on AMD64
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Dec 23 08:30:02 UTC 2009
>Closed-Date:    
>Last-Modified:  Wed Dec 23 20:29:13 UTC 2009
>Originator:     Vaclav Haisman
>Release:        7.2-STABLE
>Organization:
SU SH
>Environment:
FreeBSD shell.sh.cvut.cz 7.2-STABLE FreeBSD 7.2-STABLE #0: Thu Dec  3 17:36:38 CET 2009     root@shell.sh.cvut.cz:/usr/obj/usr/src/sys/SHELLDELL  amd64
>Description:
I am experiencing some unspecified lockup/deadlock with 7.2 on AMD64,
roughly every two weeks. The <http://shell.sh.cvut.cz/~wilx/textdump.tar.0>
is text dump of the event obtained from DDB. It seems incomplete because
the textdump capture area seems to be too short and there were many cron
jobs running ifconfig every five minutes stuck.

>How-To-Repeat:
Dunno.
>Fix:
Dunno.

>Release-Note:
>Audit-Trail:
>Unformatted:
