![](https://seccdn.libravatar.org/avatar/7ec4c6d48964b25c3232ec6b29240b2a.jpg?s=120&d=mm&r=g)
On 9/27/18 9:08 PM, Andrei Borzenkov wrote:
27.09.2018 07:27, don fisher пишет:
I did try netconsole as a module, and tried loading in with a command in /etc/modprobe.d. I did not appear to work.
You forgot to show what you did so I take it it as rant instead of question.
What I did is:
In /etc/modprobe.d/20-netconsole.conf, there is the line:
options netconsole netconsole=64001@192.168.7.60/eth0,64001@192.168.7.55/34:e6:d7:01:2a:dd
as described in the link you referenced.
This is not "command" and it does not load anything. It just provides options for module when (if) module is loaded. Did you load netconsole module at all?
That is the same line I used with the native module netconsole. I also tried in user mode the route where you: CONFIGFS_FS NETCONSOLE NETCONSOLE_DYNAMIC
and load parameters into /sys/kernel/config/netconsole/hostname/*. This works fine, but is not available early enough in the boot sequence to report the crash.
It is not clear again. You mean, crash happens before ethernet driver is loaded and you can configure netconsole to use it?
The crash occurs rather early in the boot process. I did include a file /etc/modules-load.d/netconsole.conf that contains the line netconsole. I thought that would load the module. Then the file /etc/modprobe.d/20-netconsole.conf should add the parameters. Did not appear to work according to journalctl dump. I have now built both the netconsole interface and the alx driver native to the kernel. This works fine outputting a dmesg dump for about 12 seconds, then the output stops. That is about the same time it took for my Ethernet devices to come up. So there could be a conflict between the networks setup by netconsole and maybe being clobbered by wicked. The documentation claims that system messages may go over the net with the kernel messages. Don -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org