From mboxrd@z Thu Jan  1 00:00:00 1970
From: hdf3@comcast.net (don fisher)
Date: Wed, 26 Sep 2018 13:25:35 -0700
Subject: Problem with netconsole and eth0 timing
In-Reply-To: <103031.1537928796@turing-police.cc.vt.edu>
References: <0f831765-c3f1-17e9-b029-1a7e52d8a38d@comcast.net>
 <103031.1537928796@turing-police.cc.vt.edu>
Message-ID: <04ea042b-8e6d-2699-2dab-986a62d4d3cb@comcast.net>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On 9/25/18 7:26 PM, valdis.kletnieks at vt.edu wrote:
> On Tue, 25 Sep 2018 18:26:06 -0700, don fisher said:
> 
>> 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.
> 
> Here's the big clue:
> 
> Sep 24 22:01:25 dfpc60 systemd-modules-load[185]: Module 'netconsole' is builtin
> 
> which means that it's going to get initialized during *very* early boot, before
> the initramfs gets called. netconsole is able to do the equivalent of
> 'ifconfig' (or at least enough of it to set the IPs/ports/ARP entries before
> the rest of networking comes up), but it can't also get the physical device up and
> running if the hardware driver isn't present.
> 
> Since it's builtin, this is probably a custom-built kernel.  So make sure that
> the driver for eth0 is also builtin.
> 
Would you tell me how to tell the driver that it is to be eth0, ip 
address etc. Maybe on linux command line, but I do not know the format.

Thanks
Don