Bug 1004456

Summary:	CPU-specific kernel drivers fail to autoload with 3.11 kernel
Product:	[Fedora] Fedora	Reporter:	David Woodhouse <dwmw2>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	johannbg, lnykryn, msekleta, plautrba, systemd-maint, vpavlin, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	systemd-204-11.fc19	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-10 00:00:51 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:
Embargoed:

Description David Woodhouse 2013-09-04 16:27:37 UTC

http://cgit.freedesktop.org/systemd/systemd/commit?id=bf7f800f

> After a recent change present in 3.11-rc1 there is a driver, called processor, 
> that can be bound to the CPU devices whose sysfs directories are located under 
> /sys/devices/system/cpu/. A side effect of this is that, after the driver has 
> been bound to those devices, the kernel adds DRIVER=processor to ENV for CPU
> uevents and they don't match the default rule for autoloading modules matching 
> MODALIAS: 
> 
> DRIVER!="?*", ENV{MODALIAS}=="?*", IMPORT{builtin}="kmod load $env{MODALIAS}" > 
> any more. However, there are some modules whose module aliases match specific 
> CPU features through the modalias string and those modules should be loaded 
> automatically if a compatible CPU is present. Yet, with the processor driver 
> bound to the CPU devices the above rule is not sufficient for that, so we need 
> a new default udev rule allowing those modules to be autoloaded even if the 
> CPU devices have drivers.

Comment 1 David Woodhouse 2013-09-04 16:58:25 UTC

http://koji.fedoraproject.org/koji/taskinfo?taskID=5894848

Comment 2 Fedora Update System 2013-09-05 12:23:13 UTC

systemd-204-11.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/systemd-204-11.fc19

Comment 3 Fedora Update System 2013-09-06 05:15:44 UTC

Package systemd-204-11.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing systemd-204-11.fc19'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-15934/systemd-204-11.fc19
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2013-09-10 00:00:51 UTC

systemd-204-11.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.