From: hdf3@comcast.net (don fisher)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Problem with netconsole and eth0 timing
Date: Tue, 25 Sep 2018 18:26:06 -0700 [thread overview]
Message-ID: <0f831765-c3f1-17e9-b029-1a7e52d8a38d@comcast.net> (raw)
I am trying to use netconsole to examine some problems I am having
booting Alienware 13 r3 and 14 laptops. I am running opensuse 42.3 with
generic 4.18.7 kernel configured to include netconsole. After building
my kernel and including the proper command (as shown below) in the linux
boot string:
netconsole=64001 at 192.168.7.60/eth0,64001 at 192.168.7.55/34:e6:d7:01:2a:dd
I receive the following error message, as shown by journalctl:
sudo journalctl -b | grep netconsole
Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: local port 64001
Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: local IPv4 address
192.168.7.60
Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: interface 'eth0'
Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: remote port 64001
Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: remote IPv4 address
192.168.7.55
Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: remote ethernet
address 34:e6:d7:01:2a:dd
Sep 24 22:01:25 dfpc60 kernel: netpoll: netconsole: eth0 doesn't exist,
aborting
Sep 24 22:01:25 dfpc60 kernel: netconsole: cleaning up
Sep 24 22:01:25 dfpc60 systemd-modules-load[185]: Module 'netconsole' is
builtin
I examined the timing in more detail and found that the above "eth0:
doesn't exist" message comes at Sep 24 22:01:25.080603.
The wicked message eth0: up comes at Sep 24 22:02:01.173616. The
difference is maybe 36 seconds? There is an eth0: avail message at Sep
24 22:01:34.112744, don't know if that would suffice for netconsole Both
are after netconsole has bailed out. Any obvious solutions I am missing?
The documentation is pretty clear on how to set this up, so there must
be some way to get it to work. I could find nothing on Google.
This is my first post to this list, so if this question is not
appropriate please let me know without flames:-)
Don
next reply other threads:[~2018-09-26 1:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 1:26 don fisher [this message]
2018-09-26 2:26 ` Problem with netconsole and eth0 timing 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
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=0f831765-c3f1-17e9-b029-1a7e52d8a38d@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).