Message boards :
Graphics cards (GPUs) :
Segmentation Violation Errors
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 21 Dec 07 Posts: 47 Credit: 5,252,135 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]()
|
I have a host that has been hit with a lot of these errors lately...just had 2 back to back...nothing has changed on my end and I noticed that on some of these others have errored out the same task for the same reasons....whats up? Here is the stderr out : process exited with code 193 (0xc1, -63) </message> <stderr_txt> # Using CUDA device 0 # Device 0: "GeForce GTX 260" # Clock rate: 1350000 kilohertz # Number of multiprocessors: 27 # Number of cores: 216 MDIO ERROR: cannot open file "restart.coor" SIGSEGV: segmentation violation Stack trace (16 frames): acemd_6.51_x86_64-pc-linux-gnu__cuda[0x4b5a89] /lib/libc.so.6[0x7f37d75de100] [0x7fffe07fe78c] /lib/libc.so.6(__gettimeofday+0x1a)[0x7f37d763a11a] /usr/lib/libcuda.so[0x7f37d658aef2] /usr/lib/libcuda.so[0x7f37d630e0db] /usr/lib/libcuda.so[0x7f37d630e1a1] /usr/lib/libcuda.so(cuCtxSynchronize+0x25)[0x7f37d62f29e5] ../../projects/www.ps3grid.net/libcudart.so.2(cudaThreadSynchronize+0x36)[0x7f37d80bd766] acemd_6.51_x86_64-pc-linux-gnu__cuda[0x49649d] acemd_6.51_x86_64-pc-linux-gnu__cuda[0x48d5f9] acemd_6.51_x86_64-pc-linux-gnu__cuda(sin+0x1553)[0x4086a3] acemd_6.51_x86_64-pc-linux-gnu__cuda(sin+0x1786)[0x4088d6] acemd_6.51_x86_64-pc-linux-gnu__cuda(sin+0x31b)[0x40746b] /lib/libc.so.6(__libc_start_main+0xf4)[0x7f37d75ca1c4] acemd_6.51_x86_64-pc-linux-gnu__cuda(sinh+0x49)[0x407249] |
|
Send message Joined: 10 Apr 08 Posts: 254 Credit: 16,836,000 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
could you post the link to the WU? thanks |
Stefan LedwinaSend message Joined: 16 Jul 07 Posts: 464 Credit: 298,573,998 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]()
|
Hi Ignasi, the failed WUs aren't hard to find, just have a look at Jeff's computers... ;) Here are some of his WUs with the segmentation violation errors - 120112, 119678, 119395... pixelicious.at - my little photoblog |
|
Send message Joined: 21 Dec 07 Posts: 47 Credit: 5,252,135 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]()
|
Sorry I didn't provide links initially...here are 2 older tasks with others having compute errors as well as mine...80674 and 82729 Ignasi or GDF ...do you have any explanation for this? Something I can do on my end? The Q9550 is OCk but I don't think that has a bearing on it as it always has been and ran without a glitch on the 6.48 app...all these errors have been on the 6.51 app. |
|
Send message Joined: 17 Aug 08 Posts: 2705 Credit: 1,311,122,549 RAC: 0 Level ![]() Scientific publications ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Sorry for not posting anything useful, but this thread just reminded me of something.. funny :p MrS Scanning for our furry friends since Jan 2002 |
©2025 Universitat Pompeu Fabra