kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: hdf3@comcast.net (don fisher)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Problem with netconsole and eth0 timing
Date: Thu, 27 Sep 2018 16:52:09 -0700	[thread overview]
Message-ID: <b32f04b6-f5b0-2df9-dcd1-4ea63e04ecf8@comcast.net> (raw)
In-Reply-To: <538fdb25-28fb-60b9-9924-c985b02084d7@comcast.net>

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

      reply	other threads:[~2018-09-27 23:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-26  1:26 Problem with netconsole and eth0 timing don fisher
2018-09-26  2:26 ` valdis.kletnieks at vt.edu
2018-09-26 20:25   ` don fisher
2018-09-26 21:33     ` valdis.kletnieks at vt.edu
2018-09-27  4:38       ` don fisher
2018-09-27  7:01         ` valdis.kletnieks at vt.edu
2018-09-27 22:16           ` don fisher
2018-09-27 23:52             ` don fisher [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b32f04b6-f5b0-2df9-dcd1-4ea63e04ecf8@comcast.net \
    --to=hdf3@comcast.net \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).