This seems to happen in many different drivers but it happened more often in newer versions such as 530 vs 525. Then nvidia-modeset goes to 100% There are many reports of this appearing since driver 4.70 and I can confirm I've seen this in various machines. https://forums.de........

A quick fix is to run this command: sudo brctl setageing br0 0 This causes the aging of the MAC address to time out immediately or in 0 seconds, which delete the entry frmo the FDB (Forwarding Database) and causes the error to go away. The default time is 300 seconds or 5 minutes. You can also add it under your br0 definition like this in /etc/network/interfaces to make it permanent and automatic: auto br........

#if you have nvidia make sure you install the nvidia-cuda-toolkit so hardware acceleration can be used wget http://ffmpeg.org/releases/ffmpeg-3.3.2.tar.bz2 tar -jxvf ffmpeg-3.3.2.tar.bz2 cd ffmpeg-3.3.2/ ./configure --disable-yasm install prefix /usr/local source path ........

mysql errors even though these files do exist: 110405 13:21:37 InnoDB: Operating system error number 13 in a file operation. InnoDB: The error means mysqld does not have the access rights to InnoDB: the directory. InnoDB: File name ./ibdata1 InnoDB: File operation call: 'open'. InnoDB: Cannot continue operation. 110405 13:26:15 InnoDB: Operating system error number 13 in a file operation. InnoDB: The error means my........

don't delete /var/lib/mysql/ib_logfile0 or ibdata1 or mysql won't restart I didn't realize they were internal and not part of replication like the relay files! /usr/libexec/mysqld: ready for connections. Version: '4.1.22-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 110127 16:31:00 [Note] /usr/libexec/mysqld: Normal shutdown 110127 16:31:00 InnoDB: Starting shutdown...........