Bug 746481

Summary: modules-load.d stuff isn't being loaded during boot
Product: [Fedora] Fedora Reporter: Bruno Wolff III <bruno>
Component: systemdAssignee: Lennart Poettering <lpoetter>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: bruno, harald, johannbg, kay, lpoetter, metherid, mschmidt, notting, plautrba
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-17 14:01:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Requested dmesg output none

Description Bruno Wolff III 2011-10-16 13:54:44 UTC 
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:
Comment 1 Bruno Wolff III 2011-10-16 14:03:09 UTC 
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.
Comment 2 Michal Schmidt 2011-10-17 12:44:23 UTC 
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.
Comment 3 Bruno Wolff III 2011-10-17 13:12:40 UTC 
Created attachment 528534 [details]
Requested dmesg output
Comment 4 Bruno Wolff III 2011-10-17 13:34:26 UTC 
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.
Comment 5 Michal Schmidt 2011-10-17 14:01:17 UTC 
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.
Comment 6 Bill Nottingham 2011-10-17 15:55:51 UTC 
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.
Comment 7 Bruno Wolff III 2011-10-17 16:22:17 UTC 
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.