![](https://seccdn.libravatar.org/avatar/7ec4c6d48964b25c3232ec6b29240b2a.jpg?s=120&d=mm&r=g)
On 9/30/18 2:20 PM, Carlos E. R. wrote:
On 30/09/2018 16.59, don fisher wrote:
On 9/30/18 1:31 AM, Andrei Borzenkov wrote:
28.09.2018 23:46, don fisher пишет:
I do not know what documentation you mean nor what "system messages" means.
The documentation is in: /usr/src/linux-4.18.7/Documentation/networking/netconsole.txt
My system is currently running at loglevel=8. By system messages I did mean the standard network traffic from the system. From the netconsole.txt, "the network device (eth1 in the above case) can run any kind of other network traffic, netconsole is not intrusive".
I do now know enough about networking to diagnose the problem. I am not even sure if the problem is with the transmitter or receiver. I am sure that it stops at he same place every boot. The only exception is when I went into Yast2 and disabled wicked. Then it went a little further, but still not to completion. Is there a way to look at the receiver and see if it has messages in the queue, or some overflow, or something else? Any other lists to report to? This is almost working, so I hate to give up now.
Sometime ago I had netconsole working. Then a month later it did not work for me, same configuration on my side. I did not investigate further, I could solve the problem I had somehow (other "how"). Is there any limit on the number, or total length, of messages that can be received by nc? I am concerned about the repeatable cutoff in the messages. Don
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org