From: spamtrap42@jacob21819.net
On 2026-01-13, c186282 wrote:
> On 1/12/26 23:57, Robert Riches wrote:
>> Each of my /var/log/syslog and /var/log/kern.log is over 1GB
>> today after unplugging two monitors and plugging in two different
>> monitors.
>>
>> The hardware is about 5 years old:
>> - Motherboard: Asus Pro WS X570-ACE
>> - Processor: AMD Ryzen 7 5800X 8-Core Processor
>> - GPU: MSI Radeon RX5500XT
>> - old monitors: 2x Asus VW266H
>> - new monitors: 2x Asus PA279CV
>>
>> Software is Devuan Daedalus.
>>
>> The old monitors were connected to the first two DisplayPort
>> connectors via (probably no-name) DisplayPort-to-HDMI adapters
>> and a Kopul HDMI switchers.
>>
>> The new monitors are connected to the same first two DisplayPort
>> connectors via PearStone DisplayPort-to-HDMI adapters and the
>> same Kopul HDMI switchers.
>>
>> (The switchers let me push a button and see security camera
>> output on one monitor, then push another button to go back to
>> computer stuff.)
>>
>> I had tested the new monitors and adapter cables via the GPU's
>> third DisplayPort connector, with and without going through the
>> switcher. All tested out well.
>>
>> Today, while the machine would have been showing the text console
>> and not X, I physically installed the new monitors on the
>> above-desk mounts and plugging everything in. The switchers
>> showed that there was signal on the input line, but the monitors
>> stayed in standby mode. About the time I plugging things in,
>> syslog and kern.log show the following:
>>
>> 2026-01-12T12:00:37.370890-08:00 one kernel: [180281.980042]
drm:retrieve_link_
>> cap [amdgpu]] *ERROR* retrieve_link_cap: Read receiver caps dpcd data
failed.
>> 2026-01-12T12:00:38.627964-08:00 one kernel: [180283.233347] ------------[
cut h
>> ere ]------------
>> 2026-01-12T12:00:38.627976-08:00 one kernel: [180283.234095] WARNING: CPU:
7 PID
>> : 13497 at drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:3076
dc_update_pla
>> nes_and_stream+0x342/0x880 [amdgpu]
>>
>> then lists of kernel modules, register dumps, stack traces
>> and etc.
>>
>> then a ton of these:
>>
>> 2026-01-12T12:00:38.754724-08:00 one kernel: [180283.364640]
drm:dc_add_plane_to_context [amdgpu]] *ERROR* Head pipe not found for
stream_state 000000000268a75b !
>> 2026-01-12T12:00:38.758717-08:00 one kernel: [180283.365909]
drm:dc_add_plane_to_context [amdgpu]] *ERROR* Head pipe not found for
stream_state 000000000268a75b !
>> 2026-01-12T12:00:38.758720-08:00 one kernel: [180283.367165]
drm:dc_add_plane_to_context [amdgpu]] *ERROR* Head pipe not found for
stream_state 000000000268a75b !
>>
>> at a rate of about 980 per second for a total of about 6,803,402
>> lines and just over 1GB of text in each file. Thankfully, a
>> clean reboot of the machine accomplished via a thin-client
>> machine, the GPU, switchers, and monitors signed a peace treaty
>> and are now happily working together.
>>
>> Has anyone else seen anything similar to that?
>>
>> Thanks.
>
>
> Ummm ... minor errors CAN produce HUGE log files.
>
> You can either do a LOT of research OR just write
> a root crontab script that nukes "older" logs.
With behavior probably inherited from pre-systemd Debian, Devuan
takes care of that pretty well for most practical purposes: keep
the current file and one prior uncompressed, compress everything
older than that, keep only a fixed number of compressed files.
IIRC, I have seen the same or rather similar behavior in all
other distributions I have used.
In this particular case, the flooding has stopped, and there is
enough disk space that the current 1.1GB files won't likely be a
problem between now and when they are rotated off the edge of the
planet. If I had been more prompt in logging in from the
thin-client machine, the files would not have reached the size
they did.
Thanks.
--
Robert Riches
spamtrap42@jacob21819.net
(Yes, that is one of my email addresses.)
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
