From owner-freebsd-current@FreeBSD.ORG Fri Apr 2 23:10:58 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CACE1106564A; Fri, 2 Apr 2010 23:10:58 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtpout027.mac.com (asmtpout027.mac.com [17.148.16.102]) by mx1.freebsd.org (Postfix) with ESMTP id 0737B8FC0C; Fri, 2 Apr 2010 23:10:57 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii Received: from [172.24.241.149] (natint3.juniper.net [66.129.224.36]) by asmtp027.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0L09002O6V26J890@asmtp027.mac.com>; Fri, 02 Apr 2010 16:10:57 -0700 (PDT) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0908210000 definitions=main-1004020238 From: Marcel Moolenaar In-reply-to: <20100402225502.GA1835@mech-cluster241.men.bris.ac.uk> Date: Fri, 02 Apr 2010 16:10:53 -0700 Message-id: <3B66ECFA-2A16-44E2-A94A-0C9AA57B4153@mac.com> References: <20100402225502.GA1835@mech-cluster241.men.bris.ac.uk> To: Anton Shterenlikht X-Mailer: Apple Mail (2.1078) Cc: freebsd-current@freebsd.org, freebsd-ia64@freebsd.org Subject: Re: ia64 -> panic: deadlkres: possible deadlock detected for 0xe00000001187d880, blocked for 1801437 ticks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Apr 2010 23:10:59 -0000 On Apr 2, 2010, at 3:55 PM, Anton Shterenlikht wrote: > Hi Marcel > > I got this panic while trying to build some port > on -current (csup'ed on 1-APR-2010) > > panic: deadlkres: possible deadlock detected for 0xe00000001187d880, blocked for 1801437 ticks > > cpuid = 1 > KDB: enter: panic > [ thread pid 0 tid 100046 ] > Stopped at kdb_enter+0x92: [I2] addl r14=0xffffffffffe1fbf0,gp ;; > db> > db> bt > Tracing pid 0 tid 100046 td 0xe000000010d4f500 > kdb_enter(0xe000000004853640, 0xe000000004853640, 0xe00000000439d170, 0x793) at kdb_enter+0x92 > panic(0xe00000000484b490, 0xe00000000484b6d0, 0xe00000001187d880, 0x1b7cdd) at panic+0x2f0 > deadlkres(0xa00000007ebca2d8, 0xe00000001187d880, 0xe00000000484b410, 0x1b7cdd) at deadlkres+0x470 > fork_exit(0xe000000004893250, 0x0, 0xa0000000bd3db550) at fork_exit+0x110 > enter_userland() at enter_userland > db> > > The panic followed a long freeze, of a sort that > I've seen a lot on ia64 in the last couple of weeks. > Do I get the panic (as opposed to a seemingly endless freeze) > because of a recently added > > options DEADLKRES > > in my kernel config? Yes, exactly. At the db> prompt, can you type: db> show thread 0xe00000001187d880 This should give you something like: Thread 100001 at 0xe00000001187d880: proc (pid 1): 0xe00000301220c000 name: kernel stack: 0xa00000021afd2000-0xa00000021afd9fff flags: 0x10005 pflags: 0 state: RUNNING (CPU 0) priority: 52 container lock: sched lock 0 (0xe000003400ad5080) With the thread ID, 100001 in the example above, type: db> thread 100001 This should give you something like: [ thread pid 1 tid 100001 ] kdb_enter+0x92: [I2] addl r14=0xffffffffffe279b8,gp ;; Then type the following for a backtrace: db> bt FYI, -- Marcel Moolenaar xcllnt@mac.com