On 1/19/07, Jim McBeath <fedora-xen@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@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@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@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@gumby ~]#

--
Fedora-xen mailing list
Fedora-xen@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen