Re: ypbind hangs as of current from midday yesterday (kern+user)

[David Laight <david%l8s.co.uk@localhost>]

On Thu, Jun 28, 2007 at 01:49:22PM +1000, Sarton O'Brien wrote:
> On Thu, 28 Jun 2007 12:29:34 pm Christos Zoulas wrote:
> > Did you post a ktrace of it?
> 
> Below is the output. This repeats indefinitely:
> 
>   1447      1 ypbind   RET   read 500/0x1f4
>   1447      1 ypbind   CALL  read(9,0x8068000,0x4000)
>   1447      1 ypbind   GIO   fd 9 read 0 bytes
>        ""
>   1447      1 ypbind   RET   read 0
>   1447      1 ypbind   CALL  close(9)
>   1447      1 ypbind   RET   close 0
>   1447      1 ypbind   CALL  sendto(6,0xbfbfd4b0,0x88,0,0xbfbfde88,0x10)
>   1447      1 ypbind   GIO   fd 6 wrote 136 bytes
>        
> "\0\0\0\0\0\0\0\0\0\0\0\^B\0\^A\M^F\240\0\0\0\^B\0\0\0\^E\0\0\0\^A\0\0\0DF\M^C\^Y\
>         
> \M-\\0\0\0\^Nspike.internal\0\0\0\0\0\0\0\0\0\0\0\0\0\b\0\0\0\0\0\0\0\^B\0\0\0\^C\0\
>         
> \0\0\^D\0\0\0\^E\0\0\0\^T\0\0\0\^_\0\0\^B\0\0\0\0\0\0\0\0\0\0\^A\M^F\M-$\0\0\0\^B\0\
>         \0\0\^B\0\0\0\f\0\0\0\binternal"
>   1447      1 ypbind   RET   sendto 136/0x88

I did wonder if I'd managed to break sendto() - not much actually uses it.
But traceroute(8) does, and seems to work on my system running a very
recent kernel.  But I'm not inside xen....

Unfortunately ktrace doesn't get the 'sockaddr' ...

        David

-- 
David Laight: david%l8s.co.uk@localhost