Bug 1254210

Summary: Failed to find cpu0 device node
Product: [Fedora] Fedora Reporter: Stefan Gies <stefan998>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: gansalmon, itamar, jamsheer.posibolt, jemate683, jonathan, kernel-maint, madhu.chinakonda, mchehab, redhat, stefan998
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: 2015-08-17 14:43:05 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:
Attachments:
Description Flags
DMESG file output none

Description Stefan Gies 2015-08-17 12:40:23 UTC
Created attachment 1063808 [details]
DMESG file output

Description of problem: On boot the error mesaage was "Failed to find cpu0 device node"


Version-Release number of selected component (if applicable): 23


How reproducible:


Steps to Reproduce:
1. Install Fedora 23 Alpha to a PC with AMD Sempron 3000+ with Asrock K7S41GX Motherboard
2.
3.

Actual results: Failed to find cpu0 device node


Expected results: No error


Additional info:

Comment 1 Stefan Gies 2015-08-17 12:41:36 UTC
Fedora 23 Alpha was a 32bit Version.

Comment 2 Josh Boyer 2015-08-17 14:43:05 UTC
This is a warning message from the OF layer in the kernel.  Since i686 has CONFIG_OF enabled (for OLPC reasons) and your machine doesn't utilize OF or device trees, it errors out.  There's nothing actually wrong here.

Comment 3 injeso969 2016-10-30 23:08:24 UTC
*** Bug 1389975 has been marked as a duplicate of this bug. ***

Comment 4 jamseer 2018-03-12 07:58:41 UTC
The getting a message "failed to find cpu0 device node error" , At that time you can trace current all logs they you will get some mount error at that system you should apply fsck command after that you can restart the system ,

Comment 5 Stefan Gies 2018-04-02 15:44:18 UTC
The error is not valid anymore !