Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: ifconfig, socket locking, diagnostic panic, whee



On Sun, Apr 27, 2008 at 10:24:41PM +0000, Jonathan A. Kollasch wrote:

> So, I got this lovely panic:
> 
> # ifconfig -a                                                                 
>  
> xennet0: flags=8822<BROADCAST,NOTRAILERS,SIMPLEX,MULTICAST> mtu 1500
>         capabilities=2800<TCP4CSUM_Tx,UDP4CSUM_Tx>
>         enabled=0
>         address: 00:16:3e:06:6f:a0
> panic: kernel diagnostic assertion "solocked(so)" failed: file 
> "/local/netbsd-5/src/sys/kern/uipc_socket.c", line 519
> Stopped in pid 273.1 (ifconfig) at      netbsd:breakpoint+0x4:  popl    %ebp
> db> bt
> breakpoint(c0441fd3,caf1ac28,c0457fc0,c03a8ba7,0) at netbsd:breakpoint+0x4
> panic(c044bd44,c0410578,c0410e79,c043b150,207) at netbsd:panic+0x1c2
> __kernassert(c0410578,c043b150,207,c0410e79,0) at netbsd:__kernassert+0x39
> socreate(7,caf1aca0,2,0,cacbd260) at netbsd:socreate+0x1dc
> fsocreate(7,0,2,0,cacbd260) at netbsd:fsocreate+0x7b
> sys___socket30(cacbd260,caf1ad00,caf1ad28,caf1ad40,c039cdce) at 
> netbsd:sys___socket30+0x35
> syscall(caf1ad48,1f,1f,1f,1f) at netbsd:syscall+0xaa
> db> 
> 
> This is reproducible for me.
> 
> This is a XEN3PAE kernel, 4.99.61,
> sources might be a day or three out of date.

I think this should be fixed now. Can you give it a go?

Cheers,
Andrew



Home | Main Index | Thread Index | Old Index