Bug 962224

Summary:	Module not found
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Marc collin <marc.collin>
Component:	Basesystem	Assignee:	Fabian Vogt <fvogt>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	marc.collin, tiwai, trenn
Version:	Current
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	dmesg dmesg

Description Marc collin 2016-01-16 14:28:27 UTC

I builded acpi_call module.
I created this file: /etc/modules-load.d/acpi_call.conf
This file contain: acpi_call

acpi_call.ko is located in
/lib/modules/4.4.0-1-default/extra/

with journalctl -b --pri=3 i found

systemd[1]: Failed to start Load Kernel Modules.
systemd-modules-load[131]: Failed to find module 'acpi_call'

Comment 1 Takashi Iwai 2016-01-18 17:17:00 UTC

Is acpi_call module itself loaded after boot despite the error message, or isn't it present at all?

Also, you can load acpi_call module manually without any problem, right?

Modules listed in /etc/modules-load.d/*.conf are loaded at first in initrd by systemd there, and this is often incomplete and spews the error messages.  It's a known problem.  But usually the module is loaded after initrd again.

Comment 2 Marc collin 2016-01-20 21:23:26 UTC

ya no problem to load it manually.

Comment 3 Takashi Iwai 2016-01-20 22:01:58 UTC

You didn't answer to the first question...

Comment 4 Marc collin 2016-01-22 00:20:37 UTC

ya the module is loaded

Comment 5 Takashi Iwai 2016-01-22 06:39:55 UTC

Then it must be a normal bug in dracut.  It can't resolve the deep dependency properly yet.  Reassigned to dracut guys.

(Besides, dracut fetches all modules in extra/* directory unconditionally by
 0150-Find-kernel-modules-in-extra-and-weak-updates-path-a.patch.
 This is known to have a bad side effect for KMPs.  But it's another story.)

Comment 6 Fabian Vogt 2016-01-22 07:48:11 UTC

Can you try to replace

> [[ $_mods ]] && instmods $_mods

in /usr/lib/dracut/modules.d/00systemd/module-setup.sh (line 172) with

> [[ $_mods ]] && hostonly='' instmods $_mods

and report whether it's included in the initrd with:

> mkinitrd
> lsinitrd /boot/initrd-4.4.0-1-default | grep acpi_call

Comment 7 Marc collin 2016-01-23 01:47:55 UTC

@Fabian Vogt

i done you change without restarting

your last command return

10 Jan 12 20:12 etc/modules-load.d/acpi_call.conf
Jan 22 20:45 lib/modules/4.4.0-1-default/extra/acpi_call.ko

Comment 8 Takashi Iwai 2016-01-23 09:13:33 UTC

Could you give the full kernel message after boot, not only that error line?
Also, what shows "modinfo acpi_call"?

There is a known problem in dracut (I believe it's not fixed yet) when a module has a deeper dependency.

Comment 9 Fabian Vogt 2016-01-23 11:11:17 UTC

(In reply to Marc collin from comment #7)
> @Fabian Vogt
> 
> i done you change without restarting
> 
> your last command return
> 
> 10 Jan 12 20:12 etc/modules-load.d/acpi_call.conf
> Jan 22 20:45 lib/modules/4.4.0-1-default/extra/acpi_call.ko

Ok, so that solved it. If you can confirm that it is loaded after a restart,
I'll submit the fix to Base:System and Factory.

Comment 10 Marc collin 2016-01-23 13:13:53 UTC

Created attachment 662967 [details]
dmesg

seem ok, module loaded

Comment 11 Marc collin 2016-01-23 13:13:57 UTC

Created attachment 662968 [details]
dmesg

seem ok, module loaded

Comment 12 Fabian Vogt 2016-01-28 14:58:02 UTC

Fix is on its way to Factory and TW.