I have a Pi that has recently developed a habit of maxing the SD card with syslog messages (somewhere in the hundreds per second) of the message: "Date/Time user kernel: [ 2257.432445] rc rc0: IR event FIFO is full!"

I found this bug report and it was closed in Feb 2019 as "resolved". I looked at the change log for kernel version "linux/4.9.228-1" and found these 3 lines that seem possibly-related but nothing definitive:

    - USB: serial: ir-usb: add missing endpoint sanity check
    - USB: serial: ir-usb: fix link-speed handling
    - USB: serial: ir-usb: fix IrLAP framing

I also found this bug report and tried adding the following items to /etc/modprobe.d/blacklist-ir_event_fifo_is_full.conf and rebooted:

blacklist ir_lirc_codec
blacklist lirc_dev
blacklist sunxi-cir

I then discovered which mods are active with lsmod | grep "ir", revealing:

Module                  Size  Used by
ir_rc6_decoder         16384  0

So I tried adding that to the blacklist file and rebooted:

blacklist ir_rc6_decoder

And still, this doesn't seem to keep it from loading or stop the logs from filling up. Both /var/log/kern.log and /var/log/syslog fill with these same messages.

I haven't found anything recent where this was happening and have exhausted my searching abilities. I mean, searching for "rc rc0: IR event FIFO is full!" in Google with quotes yields 5 results that all seem to be log files.

I'm looking for any guidance on how to stop these messages from accumulating and filling up the SD card.

Peace, Kevin

  • Any guidance on what? What is the question? – joan May 2 at 9:29
  • @joan, I updated it to be more clear. I need to stop the logging for that particular message so it stops filling up the SD card. It's currently at a rate of many megabits per minute. So after a few hours, the SD card is completely full. – Beez May 3 at 22:39

The way I would approach this problem, if it is just one specific/consistent log message causing trouble, would be to use the filter conditions built into rsyslog. Here is an example of an expression-based filter structure I've used from the relevant rsyslog documentation:

if expr then action-part-of-selector-line

Use the expression arg to capture the message giving your poor SD card grief, and set the selector action to '/dev/null' for example. Pop that filter into a configuration file that defines the log where the message is being stored and that should solve your issue.

New contributor
cnrcbr is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.