Oddbjornik 的帖子

141) 留言板 : Number crunching : GPU errors from cold (消息 1363346)
发表于：1 May 2013 作者： Oddbjornik Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Post:
I see you run optimised apps x41g. I would try upgrading to x41zc from http://jgopt.org
142) 留言板 : Number crunching : Panic Mode On (82) Server Problems? (消息 1346089)
发表于：13 Mar 2013 作者： Oddbjornik Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Post:
Cricket graph seems to be free falling.

Finally time to panic again.
143) 留言板 : Number crunching : Panic Mode On (82) Server Problems? (消息 1345919)
发表于：12 Mar 2013 作者： Oddbjornik Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Post:
The tcp fix did it purrrfectly.

Thanks you for eliminating an insanity plea


Yes, that tiny fix turned out to be a very powerful medicine!
144) 留言板 : Number crunching : Panic Mode On (82) Server Problems? (消息 1345594)
发表于：11 Mar 2013 作者： Oddbjornik Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Post:
I am sure I missed this tcp fix. Is it a tcp optimizer?
Can you point this out

Michael


It is a long and winding discussion in this thread, but all you have to do is set or add the following DWORD to the registry:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters]
"Tcp1323Opts"=dword:00000003
145) 留言板 : Number crunching : Windows TCP Settings - Follow up - Help with server communication (消息 1345303)
发表于：11 Mar 2013 作者： Oddbjornik Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Post:


Can someone with Win7x64 who applied this try downloading this video driver from the dell site see what kinda of speed you get. I think it is just an isolated to the Dell.com website?

http://www.dell.com/support/drivers/us/en/555/DriverDetails/Product/latitude-e6530?driverId=FW2RY&osCode=W732&fileId=3111115485&languageCode=en


I got ~600 KBps on Win7x64 with the fix applied. Speed varied wildly between 300 KBps and 1.1 MBps.
146) 留言板 : Number crunching : NVIDIA GeForce GTX Titan (消息 1345177)
发表于：11 Mar 2013 作者： Oddbjornik Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Post: 

[mbcuda]
processpriority = abovenormal
pfblockspersm = 15                # maybe even 16 for this one
pfperiodsperlaunch = 200



I understand the process priority, but could you give a hint as to what the other two parameters mean? And perhaps suggest values for a 4GB GTX 680?
147) 留言板 : Number crunching : Windows TCP Settings - Follow up - Help with server communication (消息 1343872)
发表于：7 Mar 2013 作者： Oddbjornik Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Post:


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters]
"Tcp1323Opts"=dword:00000003




All I did was add that single value to the windows registry, and all of a sudden all my downloads complete without errors, and at about 6 KBps.

Incredible!!
148) 留言板 : Number crunching : Abandoned tasks - Ongoing issue (消息 1341727)
发表于：28 Feb 2013 作者： Oddbjornik Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Post:

Are all these systems contacting Seti directly or through Proxies?

Last week it failed without using a proxy, today failed while using a proxy.


I've seen the same, in opposite sequence; last November it failed twice while using a proxy, on February 14th and again on the 15th it failed without a proxy.
149) 留言板 : Number crunching : Abandoned tasks - Ongoing issue (消息 1341647)
发表于：28 Feb 2013 作者： Oddbjornik Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Post:
One of my hosts abandoned all its tasks on February 15 at approximately 12:06:35 local time (11:06:35 UTC). Here is the somewhat contradictory log fragment surrounding the abandonement:

15-Feb-2013 11:56:38 [SETI@home] Sending scheduler request: To fetch work.
15-Feb-2013 11:56:38 [SETI@home] Requesting new tasks for CPU and NVIDIA
15-Feb-2013 11:56:43 [SETI@home] Scheduler request completed: got 0 new tasks
15-Feb-2013 11:56:43 [SETI@home] No tasks sent
15-Feb-2013 11:56:43 [SETI@home] This computer has reached a limit on tasks in progress
15-Feb-2013 11:56:43 [SETI@home] Project has no tasks available
15-Feb-2013 12:06:52 [SETI@home] Sending scheduler request: To fetch work.
15-Feb-2013 12:06:52 [SETI@home] Requesting new tasks for CPU
15-Feb-2013 12:06:58 [SETI@home] Scheduler request completed: got 0 new tasks
15-Feb-2013 12:06:58 [SETI@home] Not sending work - last request too recent: 23 sec


Does that make any sense? I can't find any event log messages indicating computer clock adjustment around that time, and even if the time had been adjusted it certainly would only have been by a few seconds, not ten minutes.

And also; a too recent request should only be ignored, not punished like this :-)

It kind of points to the borderline paranoid assumption that someone else has called the scheduler, reporting that all tasks for this host have been abandoned, 23 seconds prior to my completely legitimate call at 12:06:52.
150) 留言板 : Number crunching : Lunatics_x41zc_win32_cuda42.exe BSOD on 560ti card (消息 1335436)
发表于：7 Feb 2013 作者： Oddbjornik Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Post:
I drilled two 80mm holes in the bottom of the cabinet, more or less corresponding to the fans on the GPU card. I also lifted the cabinet about 20mm from the table to provide easy airflow.

After these minor changes, the GPU temperature fell to a stable 71-73C, and it runs at full speed constantly (no more underclocking). I'm actually a little surprised that the effect was so big.
151) 留言板 : Number crunching : Lunatics_x41zc_win32_cuda42.exe BSOD on 560ti card (消息 1335274)
发表于：6 Feb 2013 作者： Oddbjornik Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Post:
I'm happy to let you know that my new GTX 680 card now runs three parallel Cuda 5.0 tasks on the old Dell, without complaint.

The ASUS card, i.e. the GTX 680, runs much quieter than my old EVGA 560ti card, frankly because it has inadequate cooling. It quickly reaches its Tmax of 98C, and then downclocks itself so it stays at 98C. That is not quite what I expected, but it looks like the net effect is approximately the same amount of crunching for less electricity and less noise. Not totally happy with the 98C, though.

So the 560ti card apparently had issues that the new card doesn't have. And that, I suppose, is as far as we get on this thread.

Thank you for all your help and suggestions.
152) 留言板 : Number crunching : Lunatics_x41zc_win32_cuda42.exe BSOD on 560ti card (消息 1335003)
发表于：5 Feb 2013 作者： Oddbjornik Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Post:
I don't have any other hosts with room for this card, and I don't have any other cards capable of cuda 4.2, so there is nothing that can be swapped anywhere, unfortunately.
153) 留言板 : Number crunching : Lunatics_x41zc_win32_cuda42.exe BSOD on 560ti card (消息 1334994)
发表于：5 Feb 2013 作者： Oddbjornik Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Post:
Hmm... I did all that, and the cuda 4.2 build still crashes.

Cuda 3.2 actually also caused a crash in the middle of the night, but the computer restarted and then kept running as if nothing had happened. The crash signature is the same, as far as I can see;

Cuda 3.2 crash:

*** STOP: 0x00000116 (0xfffffa800a413010, 0xfffffa60034e8630, 0xffffffffc000009a, 
0x0000000000000004)

*** dxgkrnl.sys - Address 0xfffffa600375ead4 base at 0xfffffa6003703000 DateStamp 
0x4d384226


Cuda 4.2 crash:

*** STOP: 0x00000116 (0xfffffa80093ea4e0, 0xfffffa6003130adc, 0xffffffffc000009a, 
0x0000000000000004)

*** dxgkrnl.sys - Address 0xfffffa6003305ad4 base at 0xfffffa60032aa000 DateStamp 
0x4d384226


I would guess this means that the software does something that my hardware can't quite handle, and that the 4.2 software does it to a much higher degree than the 3.2 version. That seems to be in line with your general explanation of the development from 3.2 to 4.2.

And now I've gone and done a fun thing. I've bought an ASUS GeForce GTX 680 DirectCU II 4 GB that I'll replace the 560ti card with.

Unless you wish to do further research on the 560ti card for development reasons, I suggest I wait for the 680 card which should be here in a couple of days, and then take it from there. Cuda 5.0 and all...
154) 留言板 : Number crunching : Lunatics_x41zc_win32_cuda42.exe BSOD on 560ti card (消息 1334724)
发表于：4 Feb 2013 作者： Oddbjornik Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Post:
There's no overclocking.
The cooler fan runs slow and quiet, so I guess i could lower the temp by cranking up the fan speed.
But I like it quiet, and 80C seems to work ok.
155) 留言板 : Number crunching : Lunatics_x41zc_win32_cuda42.exe BSOD on 560ti card (消息 1334703)
发表于：4 Feb 2013 作者： Oddbjornik Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Post:
I have run 2 passes of Memtest86+ without any errors. It ran for about two and a half hours.
I have downgraded Nvidia driver to 306.97. Didn't help.
The PSU is a Corsair HX 650 watt. Should be adequate. The system draws a maximum of 330 watt.
CPU temp hovers around 80 under full load. It used to be 15 degrees hotter before I got an Akasa Nero 2 cooler.
The video card temperature never gets off the ground; the BSOD occurs about five seconds into the task, before any heating up has had time to happen.

So I guess I'm down to start shuffling the memory modules around then...?

Or getting myself a proper rig, instead of this juiced up old Dell :-)

BlueScreenView gives this info about the crash: 
Technical Information:

*** STOP: 0x00000116 (0xfffffa8007653110, 0xfffffa60032e1630, 0xffffffffc000009a, 
0x0000000000000004)

*** dxgkrnl.sys - Address 0xfffffa6003557ad4 base at 0xfffffa60034fc000 DateStamp 
0x4d384226
156) 留言板 : Number crunching : Lunatics_x41zc_win32_cuda42.exe BSOD on 560ti card (消息 1334409)
发表于：3 Feb 2013 作者： Oddbjornik Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Post:
There are no memory timing settings in this BIOS, as far as I can see. It's just an old Dell computer...
157) 留言板 : Number crunching : Lunatics_x41zc_win32_cuda42.exe BSOD on 560ti card (消息 1334400)
发表于：3 Feb 2013 作者： Oddbjornik Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Post:
Screendumps from CPU-Z:


158) 留言板 : Number crunching : Lunatics_x41zc_win32_cuda42.exe BSOD on 560ti card (消息 1334383)
发表于：3 Feb 2013 作者： Oddbjornik Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Post:
...and the cuda 4.2 build bluescreened within seconds.
159) 留言板 : Number crunching : Lunatics_x41zc_win32_cuda42.exe BSOD on 560ti card (消息 1334380)
发表于：3 Feb 2013 作者： Oddbjornik Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Post:
The cuda 3.2 build of x41zc runs without problems.

I'm not much into memory timings and voltages, and I don't know how to adjust any of those settings on this system.

I'll give the cuda 4.2 build another chance. If it still fails, I'd be happy to run any logging/checking/whatever might be needed to find out what the problem is.
160) 留言板 : Number crunching : Lunatics_x41zc_win32_cuda42.exe BSOD on 560ti card (消息 1334266)
发表于：3 Feb 2013 作者： Oddbjornik Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Post:
No, I haven't, but I'm starting to suspect that the problem might be that I restart the already started cuda tasks with new versions of the program and dlls.

I will let the existing tasks finish, then try the Cuda32 version of x41zc on freshly downloaded tasks, and if that works, the Cuda42 version also on freshly downloaded tasks.


前 20 · 后面 20


 
©2020 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.