On Sat, 26 May 2018 13:38:29 +0100 John Pilkington <johnpilk222(a)gmail.com&gt; wrote: No specific idea, but anything writing that often should be visible in top. Once you know what program it is, you can use rpm -qf to find which package it is. You could also try disabling dmesg logging, and see what complains. Does anything show up in journalctl -r?

you might try a find /sys -name "rc1*" and see if some piece of hw has that name. It may be some driver trying to manage the ir remote hardware. When I do it on my machine I get this: find /sys -name "rc1*" -ls 33248 0 drwxr-xr-x 5 root root 0 May 8 15:50 /sys/devices/pci0000:00/0000:00:14.4/0000:04:06.2/rc/rc1 33252 0 lrwxrwxrwx 1 root root 0 May 8 15:50 /sys/class/rc/rc1 -> ../../devices/pci0000:00/0000:00:14.4/0000:04:06.2/rc/rc1 lspci | grep -i 04:06 04:06.0 Multimedia video controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder (rev 05) 04:06.1 Multimedia controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] (rev 05) 04:06.2 Multimedia controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05) 04:06.4 Multimedia controller: Conexant Systems, Inc. CX23880/1/2/3 PCI Video and Audio Decoder [IR Port] (rev 05) modinfo cx88 shows it has a parameter disable_ir Yours may be a cx88 I think they are pretty common or some similar card. To find it I did lsmod | grep dvb and then lsmod | grep cx88 and modinfo the various pieces and mine does have a disable for ir. On Sat, May 26, 2018 at 4:48 PM, John Pilkington <johnpilk222(a)gmail.com&gt; wrote: > On 26/05/18 21:04, stan wrote: >> >> On Sat, 26 May 2018 13:38:29 +0100 >> John Pilkington <johnpilk222(a)gmail.com&gt; wrote: >> >>> I just upgraded my kde/f26 system to f27 using dnf. It seems to be >>> working well but dmesg has >>> >>> <timestamp> rc rc1: error -5 >>> >>> repeated around 10 times per second. ISTR that when I first saw it >>> it was rc0: >>> >>> Searching hasn't been much help. I use MythTV but not the lirc >>> infra-red remote-control features, and thought it might be >>> lirc-related, so installed lirc-disable-kernel-rc. But the messages >>> continue. They make it impossible to query dmesg for anything else. >>> >>> /etc/rc.d includes various Kxxx files, and rc-local.service is >>> 'static' >>> >>> Suggestions please... >> >> >> No specific idea, but anything writing that often should be visible in >> top. Once you know what program it is, you can use rpm -qf to find >> which package it is. >> >> You could also try disabling dmesg logging, and see what complains. >> Does anything show up in journalctl -r? > > > Thanks to both Samuel and stan for your responses. > > Yes, there are 2 tuners cards, one PCI and one usb. The spam continued when > I unplugged the usb device; I don't want to disable them unless all else > has failed. > > I had looked at atop, and can compare what I see with another very similar > 'production' box running the same MythTV version under SL7.5. The spam > continues in f27 with MythTV inactive. > > systemd-journal and rsyslogd are active; rcu_sched shows up intermittently. > There's also more akonadi activity which I don't knowingly use. > > journalctl -r looks as if it ought to be useful but I haven't used it before > on either box. Before the 26>27 upgrade it looks as if it was almost > exclusively pulseaudio stuff, switching between intel and nvidia for reasons > that were never clear; now it looks much denser and almost all kde related. > > I'll try a reboot and leaving MythTV inactive. > _______________________________________________ > users mailing list -- users(a)lists.fedoraproject.org > To unsubscribe send an email to users-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.o...

install modulename /bin/true blacklist won't prevent a dependency from loading a module, I have sometimes just did a mv on the ko file and depmod to rebuilt the module index, but that has to be redone each new kernel.