Bug 214597
Summary: | 4gb seg fixup on many binaries -- something didn't upgrade? | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Russell McOrmond <russell> |
Component: | glibc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | mcr |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 2.5-3 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-11-09 13:04:55 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Russell McOrmond
2006-11-08 15:55:14 UTC
I don't know if the following makes any sense... If I look at: Nov 8 13:26:09 calcutta kernel: 4gb seg fixup, process sshd (pid 1110), cs:ip 73:009c143e I'm assuming that the "009c143e" is an address in that process that has a problem. If I go to /proc/1110/mem I see: 00960000-00a80000 r-xp 00000000 03:01 214171 /lib/libc-2.4.so Am I wrong in guessing that the problem might still be in libc? # rpm -qif /lib/libc-2.4.so Name : glibc Relocations: (not relocatable) Version : 2.4 Vendor: Red Hat, Inc. Release : 11 Build Date: Tue 12 Sep 2006 10:57:34 AM EDT Install Date: Sun 17 Sep 2006 08:49:02 PM EDT Build Host: hs20-bc1-5.build.redhat.com Group : System Environment/Libraries Source RPM: glibc-2.4-11.src.rpm Size : 10127877 License: LGPL Signature : DSA/SHA1, Fri 15 Sep 2006 12:06:16 PM EDT, Key ID b44269d04f2a6fd2 Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> Summary : The GNU libc libraries. Sorry for replying to my own bugs. It seems that I had the i386 version of glibc installed, and not the i686 version. Installing the right glibc cleaned up many of the remaining problems. This may be something to just add to documentation. Remaining warnings are much fewer. Nov 8 13:45:12 calcutta kernel: 4gb seg fixup, process modprobe (pid 153), cs:ip 73:080f693b Nov 8 13:45:13 calcutta kernel: 4gb seg fixup, process nash (pid 490), cs:ip 73:080f3a06 Yeah, in FC5 only glibc.i686 had /lib/*/nosegneg/ libraries, in FC6 also glibc.i386 as whole is -mno-tls-direct-seg-refs. The remaining warnings are from statically linked binaries, only FC6 libc.a and libpthread.a is built with -mno-tls-direct-seg-refs. But even if FC5 libc.a was changed, you'd still need to relink all statically linked programs. In FC5 just use glibc.i686 and live with a few warnings from statically linked programs or upgrade to FC6. |