can anyone tell me what this error report is?
can anyone tell me what this error report is? |
|
| log in |
Questions and Answers : Unix/Linux : can anyone tell me what this error report is?
| Author | Message |
|---|---|
|
in the past few days i have gotten this error report in dmesg. my desktop gets corrupted and the longer i wait the worse it gets until the system locks. or at least X does. | |
ID: 918491 ·  | |
|
Checking with the error in Google, it seems no one knows and a lot of people have this problem. Might be your drivers, though. Try different ones. There's a 34 page thread here about that problem. | |
| ID: 918498 · | |
|
thanks ill check on it. only problem is i can't go too old .. i have to see what lower ver are available higher than 180.60 which did not work with my vid card at all. | |
| ID: 918500 · | |
|
I wonder if it has to do with all the VLAR results you've been killing lately | |
| ID: 918502 · | |
I wonder if it has to do with all the VLAR results you've been killing lately LOL i got the vlar killer deliberately because they lock up my pre-release tesla. since i installed that app it has not locked up once. it seems the windows version of the app causes boinc to reschedule the wu to the cpus but this one doesn't. it just kills them off. i seriously doubt this is what is causing it since the behavior started just a day or 2 ago, and i had been running the tesla several days before that as the only cuda processor leaving the gtx to my desktop only temporarily while i find out how to make boinc see and use both cards properly. then this happens.. too many changes i think. ____________ | |
| ID: 918504 · | |
...while i find out how to make boinc see and use both cards properly. then this happens.. Did you find it yet, or not? If not, then make a cc_config.xml file in your BOINC Data directory (if you haven't got the file yet) and add into it: <cc_config> <options> <use_all_gpus>1</use_all_gpus> </options> </cc_config> Save the file, make sure it has an .xml extension, not something else, and then just restart BOINC. That should do it. ____________ Jord - BOINC FAQ Service - BOINC User Wiki Real is just a matter of perception. | |
| ID: 918508 · | |
|
according to xfx there are many reported problems with the 185 series drivers resulting in this kind of output however it is also triggered by an 'oops' in the card itself. xfx suspects a possible ram chip error so since i was within my 30 days, i contacted newegg for a swapout rma explaining it is thought to have bad ram. will see what the new one does when it arrives. | |
| ID: 921966 · | |
in the past few days i have gotten this error report in dmesg. my desktop gets corrupted and the longer i wait the worse it gets until the system locks. or at least X does. Could be the kernel which is not new anymore. I use 2.6.30 for several months and don't have any problem. With the first kernel version in Ubuntu Jaunty I got many computation errors. It could also be the graphic driver. I use 190.25 and just downloaded 190.32 to be installed. Kernels are found here: http://kernel.ubuntu.com/~kernel-ppa/mainline/ nVidia drivers can be found here: http://ppa.launchpad.net/nvidia-vdpau/ppa/ubuntu/pool/main/n/nvidia-graphics-drivers-190/ Good luck. ____________ ______ DeMus  | |
| ID: 934305 · | |
in the past few days i have gotten this error report in dmesg. my desktop gets corrupted and the longer i wait the worse it gets until the system locks. or at least X does. im running gentoo... i installed 2.6.29 which seemed to help some... since i swapped my 285 out i no longer get the report on device 0, only on device 1 which is a prerelease tesla and i know it is buggy. i am going to replace that shortly. ____________ | |
| ID: 935553 · | |
Questions and Answers : Unix/Linux : can anyone tell me what this error report is?
| Copyright © 2013 University of California |
