Bug 1254210 - Failed to find cpu0 device node
Summary: Failed to find cpu0 device node
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1389975 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-17 12:40 UTC by Stefan Gies
Modified: 2018-04-02 15:44 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-08-17 14:43:05 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
DMESG file output (71.05 KB, text/plain)
2015-08-17 12:40 UTC, Stefan Gies 		no flags Details
View All

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 !
Note You need to log in before you can comment on or make changes to this bug.