Bug 1398467

Summary:	Weird error message at system bootup - kernel version 4.8.10
Product:	[Fedora] Fedora	Reporter:	xvr <smith93_28>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	25	CC:	cz172638, gansalmon, ichavero, itamar, jonathan, kernel-maint, labbott, madhu.chinakonda, mchehab, smith93_28
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-17 16:09:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description xvr 2016-11-24 23:50:23 UTC

Description of problem:
I get the following message at system bootup since the installation of kernel 4.8.10:
[FAILED] Failed to start Load Kernel Modules
see 'systemctl status systemd-modules-load' for details

1) Weird, because the system works perfectly, all modules seem to be loaded
2) I can't locate the message in any of the logs
3) The "problem" - if it is one - seems to be related to kernel 4.8.10, since booting a previous version of the kernel produces nothing special

Version-Release number of selected component (if applicable):
kernel-4.8.10-300.fc25.x86_64

How reproducible:
Always, on various hardware

Steps to Reproduce:
1. System bootup

Actual results:


Expected results:


Additional info:

Comment 1 Laura Abbott 2017-01-17 01:23:19 UTC

*********** MASS BUG UPDATE **************
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs.
 
Fedora 25 has now been rebased to 4.9.3-200.fc25.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.
 
If you experience different issues, please open a new bug report for those.

Comment 2 xvr 2017-01-17 16:08:42 UTC

The problem was only under kernel 4.8.10. Later kernels don't have this issue.

Comment 3 Laura Abbott 2017-01-17 16:09:38 UTC

Thank you for letting us know.