Description of problem: I have a config file in /etc/modules-load.d/netconsole.conf that doesn't seem to have affect now (though it did work a few weeks back) during boot. But after booting if I restart systemd-modules-load.service the module gets loaded as expected. Here is some sample output: [root@games1 bruno]# systemctl status systemd-modules-load.service systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static) Active: active (exited) since Thu, 13 Oct 2011 08:33:00 -0500; 3 days ago Main PID: 690 (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/systemd-modules-load.service [root@games1 bruno]# lsmod|grep net [root@games1 bruno]# systemctl restart systemd-modules-load.service [root@games1 bruno]# lsmod|grep net netconsole 5565 0 configfs 19267 2 netconsole Version-Release number of selected component (if applicable): systemd-units-37-1.fc16.i686 How reproducible: It seems to be happening reliably on my machines. Steps to Reproduce: 1. Add a conf file to /etc/modules-load.d (and /etc/modprode.d if options needed) 2. Reboot 3. Actual results: netconsole not loaded on boot Expected results: netconsole loaded late in the boot process Additional info:
There might be some timing issue with netconsole here, as I tried putting 'modprobe netconsole' in /etc/rc.d/rc.local and it didn't load the module either. But did when I ran it after booting.
It works for me. Please boot with 'log_buf_len=1M systemd.log_level=debug systemd.log_target=kmsg' and attach the output of "dmesg". Thanks.
Created attachment 528534 [details] Requested dmesg output
One potential cause of problems is that I believe netconsole needs the specified network interface (default eth0) to exist when the modprobe is done. While it might make sense for netconsole modprobes to be done late in the boot process, I can imagine that other modprobes might need to be done early in the boot process.
Yes, netconsole itself refused to load: [ 29.587105] netconsole: interface 'eth0' [ 29.587110] netconsole: remote port 6666 [ 29.587115] netconsole: remote IP 65.117.131.164 [ 29.587120] netconsole: remote ethernet address ff:ff:ff:ff:ff:ff [ 29.587126] netconsole: eth0 doesn't exist, aborting. [ 29.587131] netconsole: cleaning up I don't think systemd should attempt to handle this. Closing.
We do have a netconsole initscript that should be able to handle this for you. There's some work to convert this properly to systemd that is still to be done, but it should work in the interim.
Thanks. I'll look at using that. I wanted something that would work fairly soon after starting to boot, since I was having trouble using ssh to login and start netconsole before my system was crashing when doing some testing this past weekend. An init script would work just fine if I need to collect some more information for that bug.