Starting from Saturday all my astropulse units terminate with the error 193.
Examples are
http://setiathome.berkeley.edu/workunit.php?wuid=424327268
and wuid=424408731, 424408695, 424408670, 424408643, etc.

Since other computers are also reporting errors I suppose the cause is not lying on my side? Unfortunately I used up my daily "quota" of wu's so my pc is now running idle.

---

193 is a Linux issue. My first ap_v5 with r112 (64-bit SSE3) had that problem. I have not seen it since.

Crunch3r apparently had that issue in the past with another project and it was resolved by a kernel upgrade/update. I have not upgraded/updated my kernel as of yet, since that error was a one-time deal thus far.

Only thing I can suggest is try a kernel upgrade (those are risky, typically), try a newer release of the OS you are running (if that is not inconvenient), and I don't think it has any significance, but maybe upgrading BOINC to 5.10.45? There's nothing wrong with 5.8.x per se, but sometimes you never know..

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

The cause was a faulty optimized astropulse 32bit SSE2 version that I downloaded. I got another one and my client is crunching numbers again.

---