Systemd-journal: Error logs

Hello

I get these message on each boot (journalctl -p err -b):

Mär 05 10:13:57 linux-j87s kernel: [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
Mär 05 10:13:57 linux-j87s kernel: [drm:cpt_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun
Mär 05 10:14:00 linux-j87s audispd[829]: No plugins found, exiting
Mär 05 10:14:19 linux-j87s systemd-coredump[1732]: Process 299 (plymouthd) of user 0 dumped core.
Mär 05 10:14:45 linux-j87s pulseaudio[2012]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

Is this something to worry about?
It is a fresh install of 42.2. Everything “out of the box”.

Processor        : 4x Intel(R) Core(TM) i3-3240 CPU @ 3.40GHz
Memory        : 7621MB (1282MB used)
Machine Type        : Physical machine
Operating System        : openSUSE 42.2 (x86_64)
Audio Adapter        : HDA-Intel - HDA Intel PCH
ATA Samsung SSD 850
ATA TOSHIBA MQ01ABF0

Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09)
        Subsystem: ASUSTeK Computer Inc. Device [1043:844d]
        Kernel driver in use: i915
        Kernel modules: i915

The message “systemd-coredump[1656]: Process 246 (plymouthd) of user 0 dumped core.” is known – there’s a Bug Report being worked.

The “pulseaudio” message is indicating that, the “pulseaudio-module-bluetooth” package is expecting a Bluetooth connection which is not present: do you have Bluetooth hardware present on the machine and, if “yes” then, are the systemd Bluetooth services (“bluetooth.service”, “dbus-org.bluez.service”) enabled and running correctly?

The “audispd” message is information only.

The Intel “uncleared pch fifo underrun on pch transcoder A” error seems to be an issue with the current Linux kernels executing on Intel platforms.

  • Please raise an openSUSE Bug Report to address this issue.

The “PCH transcoder A FIFO underrun” error also seems to be an Intel issue and, should also be included in the Bug Report.

Thank you very much for your answer.

No, I dont’ have Bluetooth on this machine, and Bluetooth integration is disabled in KDE System Settings.
I have a Bluetooth-USB Adapter, but I have never connected it since 42.2 installation.
Can I just ignore it or do I have to configure sth.?

Yes, I think it has a wrong priority setting (err).

This Bug seems to be well known for quite a while, but it is still present. https://bugs.freedesktop.org/show_bug.cgi?id=89806

Thank you.

Not sure it is the same problem, but this https://forums.opensuse.org/showthread.php/519086-vblank-wait-timed-out-on-crtc-0?p=2809904#post2809904 might be worth a shot, namely disabling a TV OUT (even if non existing) adding “video=SVIDEO-1:d” to the kernel boot line.

Thank you.
My system is actually running fine afaics.
So there is no need for me to change anything.
Just getting these error messages and I wanted to know if I am going to run into problems at some point.
My bug report:
https://bugzilla.opensuse.org/show_bug.cgi?id=1028107

Disabling Bluetooth integration in KDE is sufficient.

Disabling the Bluetooth services in systemd was causing some errors when 13.2 systems were booted – I haven’t yet had a look to see how Leap 42.2 systems behave when the systemd Bluetooth services are disabled.

Thank you.

UPDATE: The error:
“systemd-coredump[1656]: Process 246 (plymouthd) of user 0 dumped core.”
is gone, since I have changed the network method from “wicked” to “network manager”.
Don’t ask me why.

I have a
“Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller”
and a
“EW-7711UTn nLite Wireless Adapter [Ralink RT2870]”

OK, now my 42.2 seems to run stable.

Three things I have done:

1: Select Breeze instead of Plastik as window decoration. This stops reproducible KWin crashes.
2: Select Network Manager instead of Wicked in Global Options for Yast Network. This stops Plymouth core dump and makes booting a lot faster.
3: Select in Compositor setting XRender instead of OpenGL. This helps against random Desktop freeze.

Now I am happy. :slight_smile:
Just sharing.