From mboxrd@z Thu Jan 1 00:00:00 1970 From: hdf3@comcast.net (don fisher) Date: Thu, 27 Sep 2018 16:52:09 -0700 Subject: Problem with netconsole and eth0 timing In-Reply-To: <538fdb25-28fb-60b9-9924-c985b02084d7@comcast.net> References: <0f831765-c3f1-17e9-b029-1a7e52d8a38d@comcast.net> <103031.1537928796@turing-police.cc.vt.edu> <04ea042b-8e6d-2699-2dab-986a62d4d3cb@comcast.net> <105446.1537997610@turing-police.cc.vt.edu> <117350.1538031686@turing-police.cc.vt.edu> <538fdb25-28fb-60b9-9924-c985b02084d7@comcast.net> Message-ID: To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org On 9/27/18 3:16 PM, don fisher wrote: > On 9/27/18 12:01 AM, valdis.kletnieks at vt.edu wrote: >> On Wed, 26 Sep 2018 21:38:27 -0700, don fisher said: >> >>> Thanks. I tried building with the driver embedded in the kernel, but the >>> compile failed with a halt. No crash is apparent, just a halt. It turned >>> out that this was repeated until I removed the netconsole command during >>> boot. System appears stable now. I will try tomorrow to embed the >>> driver, then add netconsole option in the command line. >> >> Wait, what?? The *compile* "failed with a halt"?? What the heck does >> that mean? > Don't know what it means. The compile just happened to be what I was > execution. The system just stopped with no output to screen, dmesg or > journal. With trial an error I discovered that if I eliminated the > netconsole command from the grub2 linux command line, the system > appeared stable again. I put that netconsole command in > /etc/default/grub, so it is sort of a pain to insert and remove it. > > Don As threatened, I rebuilt with the alx driver embedded. I tested this kernel just to make sure the alx driver still supported standard Ethernet, which it did. I then add the linux netconsole command and rebooted. Everything worked well for awhile, but the output remote output stopped at 11.909 sec, while dmesg has entries up to 12.627 sec, and later up to 206.453 sec. The last message from dmesg is "work still pending". Before, at 11.977 sec there was a "No iBFT detected" message. This is about the time output terminated. I do not know what iBFT is. The netconsole on the receiver, nc -u -l 64001, is still running at 100% cpu utilization. Journal ctrl on the source gave: 701:Sep 27 16:25:01 dfpc60 kernel: netpoll: netconsole: local port 64001 703:Sep 27 16:25:01 dfpc60 kernel: netpoll: netconsole: local IPv4 address 192.168.7.60 705:Sep 27 16:25:01 dfpc60 kernel: netpoll: netconsole: interface 'eth0' 706:Sep 27 16:25:01 dfpc60 kernel: netpoll: netconsole: remote port 64001 707:Sep 27 16:25:01 dfpc60 kernel: netpoll: netconsole: remote IPv4 address 192.168.7.55 709:Sep 27 16:25:01 dfpc60 kernel: netpoll: netconsole: remote ethernet address 34:e6:d7:01:2a:dd 711:Sep 27 16:25:01 dfpc60 kernel: netpoll: netconsole: device eth0 not up yet, forcing it 719:Sep 27 16:25:01 dfpc60 kernel: netconsole: network logging started 750:Sep 27 16:25:01 dfpc60 systemd-modules-load[186]: Module 'netconsole' is builtin Is the forcing it correct? Don