Bug 144915
| Summary: | don't know how to make device "cpu/microcode" | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bernard Johnson <bjohnson> |
| Component: | MAKEDEV | Assignee: | Harald Hoyer <harald> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | CC: | yekkim |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-02-21 19:07:54 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: | |||
I just noticed this as well. Bug search brought me to this one: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=63928 Where I commented on a possible solution. It's an older bug report about microcode being split into multiple cpu paths in /dev/cpu/$i/microcode and might explain this particular problem. The only part I'm not sure I get is how in bug 63928, a new microcode_ctl package is mentioned and in fact, is out, but that the same init.d files are in initscripts, which would overwrite them (unless I've missed something that is occuring in rawhide, which is absolultely likely ;) ) Seems as if the microcode files should be in one package or the other. This is not limited to x86 architectures. I see the same on x86_64. *** This bug has been marked as a duplicate of 63928 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 Description of problem: When starting, udev prints out: Starting udev: don't know how to make device "cpu/microcode" Version-Release number of selected component (if applicable): udev-50-1 How reproducible: Always Steps to Reproduce: 1. Boot system 2. 3. Actual Results: Starting udev: don't know how to make device "cpu/microcode" Expected Results: No extraneous messages Additional info: Seems to have no adverse effects