This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] ypbind segfaulting in pvops dom0

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] ypbind segfaulting in pvops dom0
From: Michael D Labriola <mlabriol@xxxxxxxx>
Date: Tue, 22 Dec 2009 14:53:52 -0500
Delivery-date: Tue, 22 Dec 2009 11:54:13 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
My pv_ops dom0 pulled from Jeremy's xen/master is up and running.  Noticed 
that over the last few days, ypbind has been segfaulting periodically 
shortly after it starts up.  Have never seen this before.

I get this in /var/log/messages:

Dec 22 18:34:03 localhost ypbind[2896]: broadcast: RPC: Timed out.
Dec 22 18:34:03 localhost kernel: [  103.618631] ypbind[2897]: segfault at 
10 ip 0804c5c4 sp b78492c0 error 4 in ypbind[8048000+8000]

Doing a 'service ypbind restart' starts it right back up, and I haven't 
noticed it crashing more than once per boot (although, that doesn't mean 
it won't happen).


Michael D Labriola
Electric Boat
401-848-8871 (office)
401-316-9844 (cell)

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] ypbind segfaulting in pvops dom0, Michael D Labriola <=