[Fedora-xen] "4gb seg fixup, process X" on FC6 dom0

[Jim McBeath]

Thanks for responding, Askar.  I saw that thread, and those fixes
are not working for me.  My system already had the nosegneg file in
/etc/ld.so.conf.d (it was installed there along with the kernel, so that
issue has been fixed in the sources), and ldconfig shows that the system
knows about it:

# ldconfig -N -X -p | 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

The messages are coming from non-mono processes, so that's not it either.

Perhaps a problem with dual cpu being used with Xen and FC6?

Is there anyone else out there running Xen and FC6 on a Core 2 Duo who
can report not having this problem?

--
Jim

On Sun, Jan 21, 2007 at 09:20:02PM +0500, Asrai khn wrote:
> Date: Sun, 21 Jan 2007 21:20:02 +0500
> From: "Asrai khn" <asraikhn at gmail.com>
> To: fedora-xen at redhat.com
> Subject: Re: [Fedora-xen] "4gb seg fixup, process X" on FC6 dom0
> 
> 
>    Yes there is a fix for this you can find the solution in the archives
>    http://www.mail-archive.com/fedora-xen@redhat.com/msg00053.html
>    Thanks. Askar
> 
>    On 1/19/07, Jim McBeath <fedora-xen at j.jimmc.org> wrote:
> 
>      I am running a stock FC6 xen, with all yum updates through today, on a
>      Shuttle box with a Core 2 Duo and 2GB of memory.  I am getting "4gb seg
>      fixup" for plenty of programs, including X, sh, ls, date, grep, less,
>      ssh, su and vim.  This is in dom0, with no domU running.
>      The worst offender is X: in /var/log/messages, every five seconds
>      it consistently logs something like this:
>        Jan 18 19:34:59 gumby kernel: printk: 30302 messages suppressed.
>        Jan 18 19:34:59 gumby kernel: 4gb seg fixup, process X (pid 4383), cs:ip
>      73:47150f2a
>      20,000 is typical for the number of messages suppressed.  It varies in
>      different five-second intervals from about 10,000 to 89,000.
>      I have poked around on the net and searched through the archives
>      for this group, without finding an answer.  I have seen a few posts
>      about 4gb-seg-fixup messages in domU, or from mono programs, or from
>      older OSs that needed a "nosegneg" file in /etc/ld.so.conf.d, but
>      none of those seem to apply here.
>      Any suggestions?
>      --
>      Jim McBeath
>      [root at gumby ~]# uname -a
>      Linux gumby.local 2.6.19-1.2895.fc6xen #1 SMP Wed Jan 10 19:47:12 EST 2007
>      i686 i686 i386 GNU/Linux
>      [root at gumby ~]# ls /etc/ld.so.conf.d
>      kernelcap-2.6.18-1.2869.fc6.conf  mysql-i386.conf
>      kernelcap-2.6.19-1.2895.fc6.conf  qt-i386.conf
>      [root at gumby ~]# cat /etc/ld.so.conf.d/kernelcap-2.6.19-1.2895.fc6.conf
>      # This directive teaches ldconfig to search in nosegneg subdirectories
>      # and cache the DSOs there with extra bit 0 set in their hwcap match
>      # fields.  In Xen guest kernels, the vDSO tells the dynamic linker to
>      # search in nosegneg subdirectories and to match this extra hwcap bit
>      # in the ld.so.cache file.
>      hwcap 0 nosegneg
>      [root at gumby ~]#