Squelching syslog messages

I’m getting an enormous amount of these messages scrolling by in dmesg and it’s filling about 1GB of /var/log/kern.log and /var/log/syslog both PER HOUR. On the TX1 that means my root partition fills up really quickly. How can I squelch these messages?

We’re using 4 Point Grey blackfly USB3.0 cameras and it only seems to happen when they’re active.

[  379.853264] platform ca.regulator: Driver reg-fixed-sync-voltage requests probe deferral
[  379.853389] platform cb.regulator: Driver reg-fixed-sync-voltage requests probe deferral
[  379.853510] platform cc.regulator: Driver reg-fixed-sync-voltage requests probe deferral
[  379.853636] platform cd.regulator: Driver reg-fixed-sync-voltage requests probe deferral
[  379.853745] reg-fixed-sync-voltage ce.regulator: Consumer c0 does not have device name
[  379.853769] platform ce.regulator: Driver reg-fixed-sync-voltage requests probe deferral
[  379.853892] platform d1.regulator: Driver reg-fixed-sync-voltage requests probe deferral
[  379.908296] platform d3.regulator: Driver reg-fixed-sync-voltage requests probe deferral
[  379.908515] reg-fixed-sync-voltage 5.regulator: Consumer c1 does not have device name
[  379.908595] platform 5.regulator: Driver reg-fixed-sync-voltage requests probe deferral
[  379.908814] platform 7.regulator: Driver reg-fixed-sync-voltage requests probe deferral
[  379.909024] platform d.regulator: Driver reg-fixed-sync-voltage requests probe deferral
[  379.909167] platform c9.regulator: Driver reg-fixed-sync-voltage requests probe deferral
[  379.909292] platform ca.regulator: Driver reg-fixed-sync-voltage requests probe deferral
[  379.909475] platform cb.regulator: Driver reg-fixed-sync-voltage requests probe deferral
[  379.909683] platform cc.regulator: Driver reg-fixed-sync-voltage requests probe deferral
[  379.909840] platform cd.regulator: Driver reg-fixed-sync-voltage requests probe deferral
[  379.909966] reg-fixed-sync-voltage ce.regulator: Consumer c0 does not have device name
[  379.910003] platform ce.regulator: Driver reg-fixed-sync-voltage requests probe deferral
[  379.910164] platform d1.regulator: Driver reg-fixed-sync-voltage requests probe deferral
[  379.910646] platform d3.regulator: Driver reg-fixed-sync-voltage requests probe deferral

Squelching syslog will only hide your root problem. With this occurring every 120 microseconds or so you are also taking a significant performance hit, so better to root cause this. One thing to try is a powered USB 3.0 hub (or a hub from a different vendor).

Syslog itself does not have a mechanism to limit file size, but logrotate can be used to do so. This will at least let you work for a few hours at a time until you can fix the root cause. See the man page or http://www.thegeekstuff.com/2010/07/logrotate-examples

A couple related posts: https://devtalk.nvidia.com/default/topic/974704/jetson-tx1/crash-logs-from-2-different-tx1s/post/5011322/#5011322 and https://devtalk.nvidia.com/default/topic/766303/jetson-tk1/-customkernel-the-grinch-19-3-8-for-jetson-tk1-developed/post/4378669/#4378669