Your account shows a number of different computers. It would help if you gave a link to the machine having the problem.
"Missing coprocessor" messages can be caused by OS changes/updates where the system is now not properly detecting the hardware. Have you done any updates/driver changes recently - specifically in regards to the iGPU?
The first computer you listed shows valid FGRPB1G tasks up to 18th Aug. There is then a 3 day break until Aug 21, 14:37:59 UTC when the first new task arrived and almost immediately became a compute error. Clicking on the task ID link for that task shows:-
Perhaps you'd like to think back about what you did on that machine during that 3 day interval. That will probably be related to why all subsequent tasks are now not even launching (otherwise there would be more output under a further sub-heading of "Stderr Output") but immediately (and erroneously) being declared as "Aborted by user".
Only you can fix what you must have broken during that time.
the computer had boinc suspended for those 3 days. also another thing its only aborting the gamma-ray pulsar binary search #1 on GPUs 1.22 (FGRPopencl-intel) but not Binary Radio Pulsar Search Arecibo,GBT 1.7 (intel_gpu- newer)
8/21/2023 4:22:47 PM |
)
8/21/2023 4:22:47 PM | Einstein@Home | [error] Missing coprocessor for task LATeah4021L25_1196.0_0_0.0_2379951_1; aborting
Your account shows a number
)
Your account shows a number of different computers. It would help if you gave a link to the machine having the problem.
"Missing coprocessor" messages can be caused by OS changes/updates where the system is now not properly detecting the hardware. Have you done any updates/driver changes recently - specifically in regards to the iGPU?
Cheers,
Gary.
Both Computer 13151490 |
)
Both Computer 13151490 | Einstein@Home (einsteinathome.org) and https://einsteinathome.org/host/12985570 are having the issue.
only the UHD 730 has had a recent driver update.
The first computer you listed
)
The first computer you listed shows valid FGRPB1G tasks up to 18th Aug. There is then a 3 day break until Aug 21, 14:37:59 UTC when the first new task arrived and almost immediately became a compute error. Clicking on the task ID link for that task shows:-
Perhaps you'd like to think back about what you did on that machine during that 3 day interval. That will probably be related to why all subsequent tasks are now not even launching (otherwise there would be more output under a further sub-heading of "Stderr Output") but immediately (and erroneously) being declared as "Aborted by user".
Only you can fix what you must have broken during that time.
Cheers,
Gary.
the computer had boinc
)
the computer had boinc suspended for those 3 days. also another thing its only aborting the gamma-ray pulsar binary search #1 on GPUs 1.22 (FGRPopencl-intel) but not Binary Radio Pulsar Search Arecibo,GBT 1.7 (intel_gpu- newer)
i did update the system to
)
i did update the system to windows 11 but that was before aug 18th
it is now also doing it on
)
it is now also doing it on the gt 730 in the system with the HD 530
Likely the bug in the
)
Likely the bug in the scheduler code that Bernd introduced and then fixed today. See this thread:
https://einsteinathome.org/content/app-version-refers-missing-gpu-type
yea, i get this is a late
)
yea, i get this is a late reply but removing and readding the project fixed it for both my intel GPU's and my GTX 760 2GB