[vc_row][vc_column width=”1/1″][vc_column_text]Original: http://digitalhacksblog.blogspot.com/2013/12/quick-note-pcduino-changing-debug.html
I had recently run into an issue where the rsyslogd process was chewing up about 75% of the CPU when I was using the mali driver for GLES2 support. I found out that the mali_debug_level and the ump_debug_level were set to 10. As a result there was a significant amount of messages being generated by these drivers. I changed the mali_debug_level to 2 and ump_debug_level to 2 and the high utilization and the messages went away.
Create a conf file for mali in /etc/modprobe.d with one line in it.
cat > /etc/modprobe.d/mali.conf
options mali mali_debug_level=2
Create a conf file for ump in /etc/modprobe.d with one line in it.
cat > /etc/modprobe.d/ump.conf
options ump ump_debug_level=2
I believe this will still get you critical and error messages.
- To list settable options for a module use: modinfo <module>
- If module isn’t loaded you can do modprobe <module> [<parameter>=<value>]
- To determine active value look in /sys/module/<module>/parameters