Date: Mon, 5 Feb 2007 17:05:51 -0800 From: Marcel Moolenaar <xcllnt@mac.com> To: John Baldwin <jhb@freebsd.org> Cc: FreeBSD Current <freebsd-current@freebsd.org>, Robert Watson <rwatson@freebsd.org>, freebsd-ia64@freebsd.org Subject: Re: [ia64] panic at shutdown (unp_connect) Message-ID: <398D3001-77EE-4032-919D-E1A13BCBC0A7@mac.com> In-Reply-To: <200702051954.21322.jhb@freebsd.org> References: <6671F519-76BF-4866-8A64-92406E7B79AB@mac.com> <200702051954.21322.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 5, 2007, at 4:54 PM, John Baldwin wrote: > On Monday 05 February 2007 18:54, Marcel Moolenaar wrote: >> All, >> >> 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... >> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?398D3001-77EE-4032-919D-E1A13BCBC0A7>