Code 22 fix?
20 Aug 2005 0:37:01 UTC
Topic 189723
(moderation:
How do I get rid of this error?
Is the fact that I'm not running with graphics a problem? I'm only running command line linux. IE No xwindows. the computer is only for crunching.
Thanks for the help.
Cadeus
PS How do I find this post again to see if it is answered Is there an easy way?
Host ID=391055
the error...
4.43
process exited with code 22 (0x16)
dlopen() failed: libGL.so.1: cannot open shared object file: No such file or directory
No graphics.
graphics_lib_handle NULL: running without graphics
Detected CPU type 1
APP DEBUG: Application caught signal 4
Stack trace of LAL functions in worker thread:
TestLALDemod at line 755 of file /home/bema/einsteinathome/CFS/EaH_build_release_4.89b/extra_sources/lalapps-CVS/src/pulsar/FDS_isolated/CFSLALDemod.c
At lowest level status code = 0, description: NO LAL ERROR REGISTERED
Obtained 10 stack frames for this thread.
Use gdb command: 'info line *0xADDRESS' to print corresponding line numbers.
einstein_4.81_i686-pc-linux-gnu[0x80532f5]
/lib/libpthread.so.0[0x40043f54]
/lib/libc.so.6[0x400786b8]
einstein_4.81_i686-pc-linux-gnu[0x804c428]
einstein_4.81_i686-pc-linux-gnu[0x8052e0d]
einstein_4.81_i686-pc-linux-gnu[0x80edcbc]
einstein_4.81_i686-pc-linux-gnu[0x80edbfd]
einstein_4.81_i686-pc-linux-gnu[0x8053172]
/lib/libc.so.6(__libc_start_main+0xbb)[0x4006814f]
einstein_4.81_i686-pc-linux-gnu[0x804b301]
Code 22 fix?
)
No, running without graphics shouldn't be a problem.
However it seems that our SSE detection reports SSE to be present while the CPU gives an "illegal instruction" when executing our code. This is most likely a problem of our App which hasn't shown up during the Beta Testing. Thanks a lot for your report!
What CPU are you running it on?
Probably the easiest is to subscribe to the thread you created. You will get emailed when someone posts to it with, I think, a link you can simply click on.
BM
BM
RE: What CPU are you
)
He is running it on computer ID 391055, reported as a Pentium III (Coppermine).
I had been delving into his computers from his earlier message and had seen the text and was about to suggest to him that he should post the full error message when I noticed that he had already done so. Just goes to show the value of posting full error messages when something "unusual" comes along. Well done Cadeus.
Cheers,
Gary.
RE: No, running without
)
Same here: AMD K6-233
Program received signal SIGSEGV, Segmentation fault. LALDR_DotProd33Matrix (a=0xbfffdbb0, b=0xbfffde80) at DetResponse.c:176 176 DetResponse.c: No such file or directory. in DetResponse.c (gdb) where #0 LALDR_DotProd33Matrix (a=0xbfffdbb0, b=0xbfffde80) at DetResponse.c:176 #1 0x080a0c5c in LALComputeDetAMResponse (status=0x8335630, pResponse=0xbfffe420, pDetAndSrc=0x83357e0, pGPSandAcc=0xbfffe410) at DetResponse.c:874 #2 0x08090637 in LALComputeAM (status=0x83357b8, coe=0x8183f90, ts=0x8335588, params=0x83358c8) at LALComputeAM.c:114 #3 0x0804e7d9 in CreateDemodParams () #4 0x0804c3a0 in boincmain () #5 0x08052e0d in worker () #6 0x080edcbc in boinc_init_options_graphics_lib () #7 0x080edbfd in boinc_init_graphics_lib () #8 0x08053172 in main ()and according to the debugger it crashes here:
(gdb) info registers eax 0x8 8 ecx 0x6 6 edx 0x0 0 ebx 0x2 2 esp 0xbfffdb4c 0xbfffdb4c ebp 0xbfffdb58 0xbfffdb58 esi 0xbfffde80 -1073750400 edi 0xbfffdbb0 -1073751120 eip 0x80a0220 0x80a0220 ---- instruction pointer eflags 0x210246 2163270 cs 0x23 35 ss 0x2b 43 ds 0x2b 43 es 0x2b 43 fs 0x0 0 gs 0x0 0 (gdb) disassemble Dump of assembler code for function LALDR_DotProd33Matrix: 0x080a01fc {LALDR_DotProd33Matrix+0}: push %ebp 0x080a01fd {LALDR_DotProd33Matrix+1}: mov %esp,%ebp 0x080a01ff {LALDR_DotProd33Matrix+3}: push %edi 0x080a0200 {LALDR_DotProd33Matrix+4}: push %esi 0x080a0201 {LALDR_DotProd33Matrix+5}: push %ebx 0x080a0202 {LALDR_DotProd33Matrix+6}: mov 0x8(%ebp),%edi 0x080a0205 {LALDR_DotProd33Matrix+9}: mov 0xc(%ebp),%esi 0x080a0208 {LALDR_DotProd33Matrix+12}: fldz 0x080a020a {LALDR_DotProd33Matrix+14}: xor %ebx,%ebx 0x080a020c {LALDR_DotProd33Matrix+16}: xor %ecx,%ecx 0x080a020e {LALDR_DotProd33Matrix+18}: mov %esi,%esi 0x080a0210 {LALDR_DotProd33Matrix+20}: mov %ecx,%eax 0x080a0212 {LALDR_DotProd33Matrix+22}: mov $0x2,%edx 0x080a0217 {LALDR_DotProd33Matrix+27}: nop 0x080a0218 {LALDR_DotProd33Matrix+28}: fldl (%edi,%eax,8) 0x080a021b {LALDR_DotProd33Matrix+31}: fmull (%esi,%eax,8) 0x080a021e {LALDR_DotProd33Matrix+34}: inc %eax 0x080a021f {LALDR_DotProd33Matrix+35}: dec %edx 0x080a0220 {LALDR_DotProd33Matrix+36}: faddp %st,%st(1) --- crash 0x080a0222 {LALDR_DotProd33Matrix+38}: jns 0x80a0218 {LALDR_DotProd33Matrix+28} 0x080a0224 {LALDR_DotProd33Matrix+40}: inc %ebx 0x080a0225 {LALDR_DotProd33Matrix+41}: add $0x3,%ecx 0x080a0228 {LALDR_DotProd33Matrix+44}: cmp $0x2,%ebx 0x080a022b {LALDR_DotProd33Matrix+47}: jle 0x80a0210 {LALDR_DotProd33Matrix+20} 0x080a022d {LALDR_DotProd33Matrix+49}: pop %ebx 0x080a022e {LALDR_DotProd33Matrix+50}: pop %esi 0x080a022f {LALDR_DotProd33Matrix+51}: pop %edi 0x080a0230 {LALDR_DotProd33Matrix+52}: pop %ebp 0x080a0231 {LALDR_DotProd33Matrix+53}: retWurgl: Not really the same.
)
Wurgl: Not really the same. Your CPU has been (correctly) detected as "CPU type 0" (see stderr output), which means that the App should use the generic version of the code. It already crashed in CreateDemodParams() which is quite a bit earlier than TestLALDemod(). I'm not sure yet if this is a problem of our App or the machine, I'll need to dig a bit deeper there.
BM
BM
Gary: Thanks, I should have
)
Gary:
Thanks, I should have seen this myself (still jetlagged, apparently).
Cadeus:
Figures, I found a machine here which has the same problem - and the same CPU. Most likely the gcc-4 compiler (falsely) generates SSE2 code, but we only look for SSE. So this should be a problem on all machines which have SSE, but not SSE2, like the PIII. Watch out for the next Linux Beta App, I'll post a message here, too.
Wurgl:
Can it be that with "-mfpmath=sse -march=pentium3" the gcc-4.0 actually includes SSE2 instructions, or at least requires a later version of P III than Coppermine?
BM
BM
RE: Cadeus: Figures, I
)
Not likely ... see this coppermine. No problems with the new app ...
Metod ...
RE: Gary: Wurgl: Can it be
)
$ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 5
model : 6
model name : AMD-K6tm w/ multimedia extensions
stepping : 2
cpu MHz : 233.867
cache size : 64 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr mce cx8 mmx
bogomips : 466.94
No idea, during debugging I saw this line:
Loaded symbols for /lib/ld-linux.so.2
0x0805d8c2 in TestLALDemod_for_cpu_type_0 ()
(gdb) cont
Continuing.
It seems to be strange, I could ans still cannot believe that a sinple floating point instruction causes a segmentation fault.
But it is not important, the machine is so slow that it would not help the project very much.
Sorry that it took us so long
)
Sorry that it took us so long - it's holiday time and we are still quite busy...
Anyway: Please check out our Beta Test Page. Ther you'll find an App which allows to manually override the CPU detection and force it to use generic code.
From the whole pool of machines we have I only know of precisely two machines (PIII Coppermine) which have the SSE bit set in the CPUID feature bitmask but file a "signal 4" (illegal instruction) when actually executing SSE instructions. One of these is located at the AEI and has definietly gotten too hot a while ago. Might be some sort of temperature instability. Anyway, if you run into problems, check this out.
BM
BM
RE: Sorry that it took us
)
Can you set the executable flag inside the tar archive?
I think that einstein_0.15_i686-pc-linux-gnu should have mode 755 instead of 644
BTW:
2005-09-01 12:45:16 [Einstein@Home] execv(../../projects/einstein.phys.uwm.edu/einstein_0.15_i686-pc-linux-gnu) failed: -1
Isn't here a ../ too much?
RE: Can you set the
)
Thanks for spotting this! - done.
The softlink is in BOINC/slots/0 , so ../../ referrs back to BOINC/
BM
BM