Red Hat Bugzilla – Bug 210001
mono uses TLS method that is inefficient on xen
Last modified: 2008-11-02 12:54:17 EST
Description of problem: The following messages appear ad nauseum in the kernel message logs: 4gb seg fixup, process beagled (pid 3608), cs:ip 73:0811cbff Version-Release number of selected component (if applicable): beagle-0.2.10-3.fc6 kernel-xen-2.6.18-1.2747.fc6 How reproducible: Every time Steps to Reproduce: 1. Boot, log in as user with beagle enabled. 2. Read kernel message logs. Actual results: Message as described above Expected results: Relative silence Additional info:
Maybe this is some sort of mono/xen conflict.
This is apparently mono doing TLS in a way that is inefficient on xen.
miguel says we can fix this by building mono with: ./configure --with-xen_opt=yes I'll take a look at exactly what that does.
It adds -mno-tls-direct-seg-refs to the build, and makes the jit runtime detect xen and use another TLS approach if running in xen. Seems safe to turn on.
built as mono-core-1.1.17.1-3.fc6
This does not appear to have had any effect on supressing the TLS / 4gb messages. I'm running latest FC6 updates: mono-core-1.1.17.1-3.fc6 beagle-0.2.10-5.fc6 $ beagled # tail /var/log/messages Oct 26 15:15:37 localhost kernel: 4gb seg fixup, process mono (pid 17412), cs:ip 73:0811cd78 Oct 26 15:15:37 localhost kernel: 4gb seg fixup, process mono (pid 17412), cs:ip 73:42882e6f Oct 26 15:15:37 localhost kernel: 4gb seg fixup, process mono (pid 17412), cs:ip 73:0811ccc1 Oct 26 15:15:44 localhost kernel: printk: 104092 messages suppressed. Oct 26 15:15:44 localhost kernel: 4gb seg fixup, process beagled (pid 17412), cs:ip 73:0811cbff Oct 26 15:15:49 localhost kernel: printk: 13 messages suppressed. Oct 26 15:15:49 localhost kernel: 4gb seg fixup, process beagled (pid 17412), cs:ip 73:0811cbff Oct 26 15:15:54 localhost kernel: printk: 5 messages suppressed. Oct 26 15:15:54 localhost kernel: 4gb seg fixup, process beagled (pid 17412), cs:ip 73:0811cbff Oct 26 15:15:59 localhost kernel: printk: 7 messages suppressed. Oct 26 15:15:59 localhost kernel: 4gb seg fixup, process beagled (pid 17412), cs:ip 73:0811cbff Oct 26 15:16:04 localhost kernel: printk: 5 messages suppressed.
And beagled was restarted after the upgrade? Very strange, i wonder whats causing that now. I'm not sure how to debug it though...
For information I too have installed Xen on Fedora Core 6 and am getting similar messages. I have installed: beagle.i386 0.2.10-6.fc6 installed mono-core.i386 1.1.17.1-3.fc6 installed The messages I have got are: Nov 6 15:46:41 lin kernel: 4gb seg fixup, process expr (pid 11181), cs:ip 73:41e825b9 ... Nov 6 17:31:11 lin kernel: 4gb seg fixup, process beagled-helper (pid 4602), cs:ip 73:0811cb2a ... Nov 6 19:48:01 lin kernel: 4gb seg fixup, process beagled (pid 4485), cs:ip 73:0811cbff If I can help and you need more information then please ask.
*** Bug 214148 has been marked as a duplicate of this bug. ***
Reopening, as the fix doesn't seem to have helped.
*** Bug 213353 has been marked as a duplicate of this bug. ***
I am experiencing the same problems as well, additionaly it seems that this freezes my virtual machine. I have one X-enabled and one without Xorg. The one with xorg crashes after some time and I have to destroy it in virt-manager. The one without X seems to work fine, maybe because beagle is not running there.
Am having the same problem. mono-core-1.1.17.1-3.fc6 beagle-0.2.13-1.fc6 Output from dmesg: [...] printk: 426 messages suppressed. 4gb seg fixup, process beagled-helper (pid 4178), cs:ip 73:0811cb2a printk: 104241 messages suppressed. 4gb seg fixup, process beagled-helper (pid 4178), cs:ip 73:0811cb2a
*** Bug 220572 has been marked as a duplicate of this bug. ***
*** Bug 220753 has been marked as a duplicate of this bug. ***
*** Bug 231409 has been marked as a duplicate of this bug. ***
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Can you please check if this is still happening with the version shipped with F9?
ping ?
Hello, According to my experiences, this was resolved long ago - at least, there are no more messages displayed continuously on console. Since I'm not a programmer, I cannot give you more in-depth information. Regards, Răzvan
I have not seen this since Fedora 9.
Based on the last two comments, I'm going to close this out as CURRENTRELEASE. Chris Lalancette