Created attachment 1210 [details] photo of the cli I've updated to core176. After the reboot the firewall log entries are output wre output on the cli. Even I'm logged in.
I just checked my IPFire systems and I don't find that effect. On my production system, I looked at the cli via ssh. Nothing is showing up on that. On my vm testbed I looked at both the ssh terminal and the console terminal. In both cases nothing was show on the cli while there were some entries in the /var/log/messages file.
(In reply to Adolf Belka from comment #1) > I just checked my IPFire systems and I don't find that effect. I cannot reproduce this in a VM either. > On my production system, I looked at the cli via ssh. Nothing is showing up > on that. SSH and a serial console would be different the kernel would probably not print anything onto those.
(In reply to Michael Tremer from comment #2) > (In reply to Adolf Belka from comment #1) > > > On my production system, I looked at the cli via ssh. Nothing is showing up > > on that. > > SSH and a serial console would be different the kernel would probably not > print anything onto those. Okay, good point. I just looked at my production mini appliance with the serial console and I saw nothing. In the messages log there were lots of new entries occurring. So I also don't see that on my physical system. This sounds a very weird effect. What could cause the syslog messages to be shown in the console.
I too have seen this behavior -- when playing with testing and unstable. I didn't think it much of a problem, figured it would be gone in the released version. I do not see it now on my c176 operational system. FWIW, It was happening with a VGA connected monitor (not serial, not ssh).
(In reply to Charles Brown from comment #4) > I too have seen this behavior -- when playing with testing and unstable. I > didn't think it much of a problem, figured it would be gone in the released > version. I do not see it now on my c176 operational system. > FWIW, It was happening with a VGA connected monitor (not serial, not ssh). Okay, I have been able to reproduce this. I just updated a mini pc to c176. After reboot I started getting logs to cli. This particular pc uses an HDMI-to-VGA dongle to connect the monitor.
(In reply to Charles Brown from comment #5) > (In reply to Charles Brown from comment #4) > > I too have seen this behavior -- when playing with testing and unstable. I > > didn't think it much of a problem, figured it would be gone in the released > > version. I do not see it now on my c176 operational system. > > FWIW, It was happening with a VGA connected monitor (not serial, not ssh). > > Okay, I have been able to reproduce this. I just updated a mini pc to c176. > After reboot I started getting logs to cli. > This particular pc uses an HDMI-to-VGA dongle to connect the monitor. I started seeing logs on the console when plugging in ethernet to green (showing green0 NIC down then up. Then started see logs from ipblocklist.
I do not think this is a c176 thing -- I am sure I have seen this on earlier releases. Perhaps it has to do with the HDMI-to-VGA dongle for connecting to my VGA monitor.
Just swapped hardware with this: https://fireinfo.ipfire.org/profile/28e51db7a0a974df7f6ec45098e415da016916ea and started getting the logs echoed to the console again. This was not happening on the previous box. Not something new, it seems to occur whenever I swap to this box
I've two IPFire C182 in use with this behavior. Both of them has Intel Core 8/9th gen CPUs (Intel i5 8500t / Intel i7 9700) It looks like the search for power management functions of the cpu crashes during the boot process and then all messages are displayed on the cli.
(In reply to Daniel Weismüller from comment #9) > It looks like the search for power management functions of the cpu crashes > during the boot process and then all messages are displayed on the cli. What is crashing here? Do you have logs?
(In reply to Daniel Weismüller from comment #9) > I've two IPFire C182 in use with this behavior. > Both of them has Intel Core 8/9th gen CPUs (Intel i5 8500t / Intel i7 9700) > > It looks like the search for power management functions of the cpu crashes > during the boot process and then all messages are displayed on the cli. Hi Daniel, I always have the annoying "logging showing on console" using the ipfire system in Comment #8 above. To mitigate the issue, through some web searching, I found this works for me to quit the noise ... I have added a line "dmesg -n 1" to my /etc/sysconfig/rc.local
Created attachment 1448 [details] Boot Log Snipette I do have errors in my bootloog also. Perhaps this is somehow related to the issue -- having all runtime logs spewed to the console
Created attachment 1455 [details] part of the logfile where you can see the crash after which the kernel messages appear on the cli Today I made a reboot and snipped the part of the logfile where you can see the crash after which the kernel messages appear on the cli
This behavior seems to appear because cpufrequtils tries to load modules for an AMD cpu. Cpufrequtils are no longer being developed and, in my opinion, are also superfluous as the functionality is now implemented in the Linux kernel. In addition, the addon cpufrequtils will be dropped, so in my opinion the bug can be closed.