 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I've been noticing message of this sort in my /var/log/messages:
kernel: 4gb seg fixup, process povray (pid 1501), cs:ip 73:00962939
I've no idea what that is and if I should be worried at all. Does anybody have
an idea?
I was a bit concerned since there was the "kernel" involved! Perhaps it is not
even a povray issue but I'm just falling back to "guilt by association"!
--
Rahul
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Rahul nous illumina en ce 2009-01-28 18:19 -->
> I've been noticing message of this sort in my /var/log/messages:
>
> kernel: 4gb seg fixup, process povray (pid 1501), cs:ip 73:00962939
>
> I've no idea what that is and if I should be worried at all. Does anybody have
> an idea?
>
> I was a bit concerned since there was the "kernel" involved! Perhaps it is not
> even a povray issue but I'm just falling back to "guilt by association"!
>
> --
> Rahul
>
>
Just a wild guess here.
I think that it may be related to some memory paging that may be happening while
POV-Ray is running. Memory paging causes a great many "page faults" when a bit
of instructions or data that need to be accessed have been pushed to the swap
file, and thus, need to get fetched back into RAM.
--
Alain
-------------------------------------------------
Sometimes my love of the arcane combines with my askew humor to make me
unintelligible!!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Alain <ele### [at] netscape net> wrote:
> > kernel: 4gb seg fixup, process povray (pid 1501), cs:ip 73:00962939
> >
> Just a wild guess here.
> I think that it may be related to some memory paging that may be happening while
> POV-Ray is running. Memory paging causes a great many "page faults" when a bit
> of instructions or data that need to be accessed have been pushed to the swap
> file, and thus, need to get fetched back into RAM.
Another equally wild guess: 32 bit code on a 64 bit machine?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"clipka" <nomail@nomail> wrote:
> Another equally wild guess: 32 bit code on a 64 bit machine?
Very reasonable guess. Thank you. We've been switching our servers slowly from
32bit to 64bit.
How can I test though! Because I am getting this header. Any other way to test
if this is a 32 or 64 bit executable?
/usr/local/bin//povray -v
Persistence of Vision(tm) Ray Tracer Version 3.6.1 (g++ 3.4.1 @
i686-pc-linux-gnu)
This is an official version prepared by the POV-Ray Team. See the
documentation on how to contact the authors or visit us on the
internet at http://www.povray.org/.
POV-Ray is based on DKBTrace 2.12 by David K. Buck & Aaron A. Collins
Copyright 1991-2003 Persistence of Vision Team
Copyright 2003-2004 Persistence of Vision Raytracer Pty. Ltd.
Primary POV-Ray 3.5/3.6 Developers: (Alphabetically)
Chris Cason Thorsten Froehlich Nathan Kopp Ron Parker
Contributing Authors: (Alphabetically)
Steve Anger Eric Barish Dieter Bayer Steve A. Bennett
David K. Buck Nicolas Calimet Aaron A. Collins Chris Dailey
Steve Demlow Andreas Dilger Alexander Enzmann Dan Farmer
Mark Gordon Christoph Hormann Mike Hough Chris Huff
Kari Kivisalo Lutz Kretzschmar Jochen Lippert Pascal Massimino
Jim McElhiney Douglas Muir Juha Nieminen Bill Pulver
Eduard Schwan Wlodzimierz Skiba Robert Skinner Yvo Smellenbergh
Zsolt Szalavari Scott Taylor Massimo Valentini Timothy Wegner
Drew Wells Chris Young
Other contributors are listed in the documentation.
Support libraries used by POV-Ray:
ZLib 1.2.1, Copyright 1995-1998 Jean-loup Gailly and Mark Adler
LibPNG 1.2.5, Copyright 1998-2002 Glenn Randers-Pehrson
LibJPEG 6b, Copyright 1998 Thomas G. Lane
LibTIFF 3.6.1, Copyright 1988-1997 Sam Leffler, 1991-1997 SGI
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> How can I test though! Because I am getting this header. Any other way to test
> if this is a 32 or 64 bit executable?
>
> /usr/local/bin//povray -v
> Persistence of Vision(tm) Ray Tracer Version 3.6.1 (g++ 3.4.1 @
> i686-pc-linux-gnu)
That's very likely a 32-bit exe. You might try "file /usr/local/bin/povray"
to know it for sure.
- NC
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Rahul" <nomail@nomail> wrote:
> How can I test though! Because I am getting this header. Any other way to test
> if this is a 32 or 64 bit executable?
>
> /usr/local/bin//povray -v
> Persistence of Vision(tm) Ray Tracer Version 3.6.1 (g++ 3.4.1 @
> i686-pc-linux-gnu)
The "i686" in the "i686-pc-linux-gnu" platform string is the key: It tells you
that the binary is compatible with "i686" processors - which is an unofficial
but common alias for the Intel Pentium II (following Intel's pre-Pentium era
designations for x86-compatible CPUs) - obviously a 32-bit processor.
In case of a 64-bit executable, the platform string would instead read something
like "ia64-pc-linux-gnu", or "amd64-pc-linux-gnu".
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"clipka" <nomail@nomail> wrote:
> "Rahul" <nomail@nomail> wrote:
> In case of a 64-bit executable, the platform string would instead read something
> like "ia64-pc-linux-gnu", or "amd64-pc-linux-gnu".
Hmm...so I do have a 32 bit executable on a 32 bit machine. I'm not sure why I
am getting those errors then. 32-vs-64 bit must have been a red herring for me.
ANy other ideas?
/usr/local/bin/povray: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
for GNU/Linux 2.2.0, statically linked, for GNU/Linux 2.2.0, stripped
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Xeon(TM) CPU 2.80GHz
stepping : 9
cpu MHz : 2790.776
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush
dts acpi mmx fxsr sse sse2 ss ht tm pbe cid xtpr
bogomips : 6982.48
processor : 1
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Xeon(TM) CPU 2.80GHz
stepping : 9
cpu MHz : 2790.776
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush
dts acpi mmx fxsr sse sse2 ss ht tm pbe up cid xtpr
bogomips : 6982.48
--
Rahul
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Rahul" <nomail@nomail> wrote:
> I've been noticing message of this sort in my /var/log/messages:
>
> kernel: 4gb seg fixup, process povray (pid 1501), cs:ip 73:00962939
>
> I've no idea what that is and if I should be worried at all. Does anybody
> have an idea?
Do you happen to be running Xen?
I just did a quick google for "4gb seg fixup" and found zillions of entries, all
related to Xen as it seems - the quintessence of the articles being that the
severity of the messages probably ranges from cosmetic to a performance issue
(depending on how frequent they appear), that it affects various different
programs running under Xen, and that you need to replace a certain library with
a "Xen-friendly" version to get rid of this (details are mentioned in most all
the googled articles).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"clipka" <nomail@nomail> wrote:
> "Rahul" <nomail@nomail> wrote:
>
> Do you happen to be running Xen?
No. No Xen. Its a raw server. No virtualization at all.
> I just did a quick google for "4gb seg fixup" and found zillions of entries, all
> related to Xen as it seems -
Ah! I guess I always searched for povray+"4gb seg fixup" and so never came
across those entries. I'll see if I can somehow relate them to my problems.
the quintessence of the articles being that the
> severity of the messages probably ranges from cosmetic to a performance issue
> (depending on how frequent they appear), that it affects various different
> programs running under Xen, and that you need to replace a certain library with
> a "Xen-friendly" version to get rid of this (details are mentioned in most all
> the googled articles).
My errors seem pretty often too. Almost for every povray invocation.
--
Rahul
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Rahul" <nomail@nomail> wrote:
> My errors seem pretty often too. Almost for every povray invocation.
Well, those poor Xen victims talk about up to, like, 40 messages a second, so
consider yourself lucky ;)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
