Re: [ia64] panic at shutdown (unp_connect)

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_at_mac.com
>
>
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"