Patrick Shanahan wrote:
openSUSE Tumbleweed (current)
why does dmesg stop reporting after boot is complete?
Because nothing new was written to the kernel buffer? On one of my database servers: [1522123.888829] rpc-srv/tcp: nfsd: sent only 208512 when sending 262252 bytes - shutting down socket [1523139.680904] rpc-srv/tcp: nfsd: sent only 209960 when sending 262252 bytes - shutting down socket [1548568.544561] perf: interrupt took too long (6213 > 6191), lowering kernel.perf_event_max_sample_rate to 32000 [1723471.677957] device eth0 entered promiscuous mode [1723478.354275] device eth0 left promiscuous mode [1723486.865712] device eth0 entered promiscuous mode [1723551.881018] device eth0 left promiscuous mode [1723561.528521] device eth0 entered promiscuous mode [1723706.519587] device eth0 left promiscuous mode [1723712.606113] device eth0 entered promiscuous mode [1733337.991117] device eth0 left promiscuous mode [3139677.323723] md: data-check of RAID array md0 [3139677.499695] md: delaying data-check of md1 until md0 has finished (they share one or more physical units) [3139738.778876] md: md0: data-check done. [3139738.801598] md: data-check of RAID array md1 [3142835.467023] md: md1: data-check done. That was 49 days ago, nothing has been written since. -- Per Jessen, Zürich (6.8°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org