From owner-freebsd-current@FreeBSD.ORG Wed Feb 14 15:53:05 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3B86A16A408; Wed, 14 Feb 2007 15:53:05 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 0870013C4A5; Wed, 14 Feb 2007 15:53:02 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id D2AA547884; Wed, 14 Feb 2007 10:53:01 -0500 (EST) Date: Wed, 14 Feb 2007 15:53:01 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Marcel Moolenaar In-Reply-To: <398D3001-77EE-4032-919D-E1A13BCBC0A7@mac.com> Message-ID: <20070214154704.Q83707@fledge.watson.org> References: <6671F519-76BF-4866-8A64-92406E7B79AB@mac.com> <200702051954.21322.jhb@freebsd.org> <398D3001-77EE-4032-919D-E1A13BCBC0A7@mac.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD Current , freebsd-ia64@freebsd.org Subject: Re: [ia64] panic at shutdown (unp_connect) 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: Wed, 14 Feb 2007 15:53:05 -0000 On Mon, 5 Feb 2007, Marcel Moolenaar wrote: > On Feb 5, 2007, at 4:54 PM, John Baldwin wrote: > >> On Monday 05 February 2007 18:54, Marcel Moolenaar wrote: >> >>> I've been seeing the following panic on and off for a while. Is this a >>> known issue? Has anyone seen this before? >> >> I've saw this today on a recent 6.x on amd64, but I think it is supposed to >> be fixed in HEAD. > > This actually happened with -CURRENT; sources updated Feb 1st 2007. If the > fix happened within the last, say, week then I just need to update and > rebuild. Otherwise, it seems that the problem may not be fixed or it remains > a problem on ia64. I'll update and rebuild... After looking at John's report, I've committed uipc_usrreq.c:1.192 and uipc_usrreq.c:1.193. The former probably isn't relevant, but the latter may resolve this issue. If this is a reproduceable problem it would be very helpful to hear whether it still occurs with the latest revision of uipc_usrreq.c in HEAD. Thanks, Robert N M Watson Computer Laboratory University of Cambridge > >>> fatal kernel trap (cpu 1): >>> >>> trap vector = 0x14 (Page Not Present) >>> cr.iip = 0xe00000000440f5c0 >>> cr.ipsr = 0x1010080a6018 >>> (ac,mfl,ic,i,dt,dfh,rt,cpl=0,it,ri=0,bn) >>> cr.isr = 0x400000000 (code=0,vector=0,r,ei=0) >>> cr.ifa = 0x48 >>> curthread = 0xe000000028861600 >>> pid = 435, comm = ypbind >>> >>> [thread pid 435 tid 100060 ] >>> Stopped at unp_connect+0x580: [M0] ld8 r14=[r14] > *snip* > >>> unp_connect+0x580 is line 1005 of src/sys/kern/uipc_usrreq.c and the >>> panic indicates that unp2 is NULL. > > -- > Marcel Moolenaar > xcllnt@mac.com > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"