Forum > Linux

SETI MB CUDA for Linux

<< < (43/162) > >>

Raistmer:

--- Quote from: sunu on 12 Jul 2009, 03:03:43 pm ---Raistmer do you mean something like this? From cuda 2.2 release notes:

o Individual GPU program launches are limited to a run time
  of less than 5 seconds on a GPU with a display attached.
  Exceeding this time limit causes a launch failure reported
  through the CUDA driver or the CUDA runtime. GPUs without
  a display attached are not subject to the 5 second run time
  restriction. For this reason it is recommended that CUDA is
  run on a GPU that is NOT attached to an X display.

So yes, it also exists in linux.

--- End quote ---
Exactly. Timer value varies between OSes but it's the same thing.

--- Quote ---Curiously I've crunched tens of thousands of workunits with my GPU that also runs X with ever seeing that kind of error.

--- End quote ---
Well, maybe you have more fast GPU than user who have issues?...

Tye:

--- Quote from: sunu on 12 Jul 2009, 09:26:46 am ---
--- Quote from: Raistmer on 12 Jul 2009, 07:01:59 am ---GPU that used by Windows for video output will subject of 3 or 2 seconds timeout, but secong GPU will not.
Don't know if this relevant to Linux though.

--- End quote ---

Well, if it is because of the first gpu also drawing the screen then it will probably also exist in linux. We don't have a big sample of seti cuda users with multi gpus in linux. Actually the sample is non-existent  :D

What Tye describes might be some faulty config, strange driver behavior, or some weird motherboard-gpu-gpu hardware incompatibility.

--- End quote ---

Looking at it a bit closer, it turns out that one 680i motherboard (an ASUS 680i MB) can work with the problem card in the primary slot and the other brand/model (a XFX 680i) cannot, so I think you're right and it's a wierd motherboard-gpu issue (even is crashy with one of those gpus in the primary slot - but put a different one in the primary and move it to the secondary and it's fine).  I may look at see if there's a newer BIOS later, but since all three GPUs are stable and in different machines CUDA'ing away with the 185 drivers, I'll probably take a break from messing with them for awhile.  ;)  Plus I don't have any unused CUDA GPUs on hand to test with.

b0b3r:
To make some clearance;
- this host have 3 gpu's.
- one nvidia 630 in chipset and two on 295 card.
- display is on 630 in chipset.
- 295 card is dedicated to cuda.
- also this machine is not a workstation, there is no xorg, only text console, mostly work through ssh.


--- Quote from: sunu on 12 Jul 2009, 02:22:28 pm ---Your system sees three devices.

In your host 5018683, boinc doesn't even see your graphics cards. Are you sure that you have intalled them correctly?

Also in both of your hosts upgrade boinc. 6.4.5 is too old.

--- End quote ---

I actually do some test so that's why cuda devices disappear.
6.4.5 is currently marked as stable on linux that's why I'm using it and like you see there is no problem with second host.

Strange thing is that both hosts are totally same machine. The only difference is that host with number 2 is newer (in meaning it was built with same components but about week later) and got some new workunits that the older one yet not try.

sunu:

--- Quote from: b0b3r on 12 Jul 2009, 04:05:32 pm ---6.4.5 is currently marked as stable on linux that's why I'm using it

--- End quote ---

Disregard that and get a newer version.


--- Quote from: b0b3r on 12 Jul 2009, 04:05:32 pm ---and like you see there is no problem with second host.

--- End quote ---

It has problems, those "unspecified launch failure" errors.

sunu:

--- Quote from: Raistmer on 12 Jul 2009, 03:38:19 pm ---Well, maybe you have more fast GPU than user who have issues?...

--- End quote ---
I have a GTX280 and he a GTX295, each GTX295 core more or less the same with GTX280 under cuda. Him saying that he is not running X makes the error message much more strange.


--- Quote from: Tye on 12 Jul 2009, 03:50:52 pm ---I may look at see if there's a newer BIOS later

--- End quote ---

I would do the same.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version