Re: dmesg spam after f26 -> f27 upgrade
On 26/05/18 21:04, stan wrote:
On Sat, 26 May 2018 13:38:29 +0100
John Pilkington <johnpilk222(a)gmail.com> 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.