How to stop logging?

[monty_hall]

My hard drive is filling up with messages from peak pcan - var/log/syslog & kernel are 60-70gb and I have to delete them occassionally. They don't indicate any error, it just looks like status or "what" is happening like sending and recieving. Can I shut this off? Why is this happening? Is there really a problem pcan 7 driver, ubuntu 14.0

Ton of these in syslog:
Apr 26 16:54:49 Perception kernel: [ 122.786708] pcan: pcan_usbfd_decode_canmsg(): rx=[flags=0x00 len=0x08 ts32=0x0742ee39 id=0x0000052f]


Don't have a sample of kernel log, but it's spammed too.


Thanks,

M

[M.Maidhof]

Hi,

please send the output of cat /proc/pcan to see which driver version you use at the moment.

When using an older driver 7.x, please update to version 8.x:

http://www.peak-system.com/fileadmin/me ... 3.1.tar.gz

regards

Michael

[mgdbgj]

Has this issue been resolved?

https://www.peak-system.com/forum/viewt ... slog#p4922 suggest turning off ACPI in BIOS.

I have the same issue and while rotating logs is one solution, it's not a definite solution. I tried upgrading the driver but my 3rd party application does not work with new driver so I'm sticking with 7.15.2 on Ubuntu 16.04.

*------------- PEAK-System CAN interfaces (www.peak-system.com) -------------
*------------- Release_20150729_n (7.15.2) Mar 9 2016 13:02:06 --------------
*------------- [mod] [isa] [pci] [pec] [dng] [par] [usb] [pcc] --------------
*--------------------- 4 interfaces @ major 241 found -----------------------
*n -type- -ndev- --base-- irq --btr- --read-- --write- --irqs-- -errors- status
32 usbpfd -NA- ffffffff 255 0x001c 00000000 00000000 00000000 00000000 0x0000
33 usbpfd -NA- ffffffff 255 0x001c 00000000 00000000 00000000 00000000 0x0000
34 usbpfd -NA- ffffffff 255 0x001c 00000000 00000000 00000000 00000000 0x0000
35 usbpfd -NA- ffffffff 255 0x001c 00000000 00000000 00000000 00000000 0x0000

[M.Maidhof]

Hi,

to prevent those syslog messages with driver 7.15.2, please edit pcan_usbfd.c line 742:

from: #if 1//def DEBUG
to: #ifdef DEBUG

rebuild and reload the driver again, and those messages will no longer occure.

best regards

Michael