https://bugs.kde.org/show_bug.cgi?id=353983
--- Comment #83 from Nick <nick.craig....@gmail.com> --- I can't post the actual error bugs.kde.org keeps telling me its spam ! Anyway ... Just had the panel rendering freeze again, was using with kmail at the time, so did a bit of detective work. As I had enabled seconds on the panel clock it gives me a time to look for in the logs. So the panel froze at 00:13:35. Looking at /var/log/syslog, the following entry exists at 00:13:33 that's relevant to the GPU. There was nothing else around that time that was unusual. This URL explains the error I'm getting http://docs.nvidia.com/deploy/xid-errors/index.html#topic_5_2 This error is inserted into /var/log/syslog by the Nvidia driver and indicates an error. If I've understood this correctly, this is XID error 31. So I looked up the NVidia documentation which states: XID 31: Fifo: MMU Error This event is logged when a fault is reported by the MMU, such as when an illegal address access is made by an applicable unit on the chip Typically these are application-level bugs, but can also be driver bugs or hardware bugs. When this event is logged, NVIDIA recommends the following: Run the application in cuda-gdb or cuda-memcheck , or Run the application with CUDA_DEVICE_WAITS_ON_EXCEPTION=1 and then attach later with cuda-gdb, or File a bug if the previous two come back inconclusive to eliminate potential NVIDIA driver or hardware bug. Note: The cuda-memcheck tool instruments the running application and reports which line of code performed the illegal read. The cuda-memcheck tool sounds like it might be very useful for tracking down this bug. Has anybody tried running cuda-memcheck with plasma ? Is it even possible ? -- You are receiving this mail because: You are watching all bug changes.
