WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] kernel: 4gb seg fixup messages...

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] kernel: 4gb seg fixup messages...
From: Travis Bell <travisbell@xxxxxx>
Date: Wed, 13 May 2009 15:58:06 +1000
Delivery-date: Tue, 12 May 2009 22:59:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hey everyone,

I've searched through all of the previous posts and tried everything mentioned but I am still getting these messages. Is there anything else I can do? My host machine is running CentOS 5 w/ Xen 3.3.1. My Xen VM is also running CentOS 5.

I've tried doing:

# echo 'hwcap 0 nosegneg' > /etc/ld.so.conf.d/libc6-xen.conf && ldconfig

And rebooted, still happening.

I have updated glibc incase I was running an un-patched glibc.

I have checked /etc/ld.so.conf.d/kernelcap-2.6.18-92.el5xen.conf and the contents currently read:

# hwcap 0 nosegneg

Also, if I do a `ldconfig -v -p 2>&1 | grep libc.so` I get the following:

[root@web1 ~]# ldconfig -v -p 2>&1 | grep libc.so
libc.so.6 (libc6, hwcap: 0x0018000000000000, OS ABI: Linux 2.6.9) => /lib/i686/nosegneg/libc.so.6
libc.so.6 (libc6, OS ABI: Linux 2.6.9) => /lib/libc.so.6

Is there anything else I might be able to do? I am totally lost since that outlines pretty much everything I have read about this problem.

The exact messages I get are:

May 12 23:55:16 web1 kernel: 4gb seg fixup, process ruby (pid 2170), cs:ip 73:00d52006
May 12 23:55:16 web1 kernel: 4gb seg fixup, process ruby (pid 2170), cs:ip 73:00e78c25
May 12 23:55:16 web1 kernel: 4gb seg fixup, process ruby (pid 2170), cs:ip 73:00673c7d
...



Thanks!

--
Travis Bell







_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users