On 9/25/2018 4:21 PM, don fisher wrote:
I am trying to use netconsole to examine some problems I am having booting certain 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@192.168.7.60/eth0,64001@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
From Google(netpoll is intended for monitoring multiple file descriptors to see if I/O is possible on any of them. It supports edge-triggered and level-triggered interfaces.)
I looked at dmesg and netconsole is trying eth0: at 2.348515 sec after boot. The first other mention I see of eth0: is at 9.739663 sec. The message is:
[ 9.739663] alx 0000:3c:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet [a4:4c:c8:5e:e0:12] which I assume is just recognition if loading the driver.
From sudo journalctl -b | grep eth0: Sep 24 22:02:01 dfpc60 wicked[942]: eth0 up
Wicked seems to appear about half a second after netconsole looks for eth0:
Is there something I can do in systemd, the eth0: configuration, or elsewhere to get wicked to load eth0 earlier? I was a little surprised that netconsole did not go back and try again a little later.
Doesn't sysd have a way to specify the order in which things come up? If this was sysv, you'd make one depend on the other in the headers which would alter it's run order. I find it odd that netconsole would load so soon, since I notice my builtin ethernet driver loads at about 4s, while my module-based ethernet drivers load at around 10-11s. Kernel finishes booting around 5.6-5.7s. The network interfaces are renamed about 11 seconds later and configured about 4-5 seconds after that. It is *MUCH* more likely you will be able to get a console on a serial device. If it is a laptop, doesn't it allow plugin cards? Then would build that devices driver into the kernel. Also of note -- there is an option under kernel hacking to enable "Remote debugging over FireWire early on boot" It sounds like it is before the kernel comes up. Dunno if that would be a usable device for logging.
Thanks Don
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org