Bug 1274821 - failed to find cpu0 device node error with kernel 4.2
Summary: failed to find cpu0 device node error with kernel 4.2
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 22
Hardware: i386
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-23 15:09 UTC by ashish
Modified: 2016-07-19 18:19 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 18:19:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description ashish 2015-10-23 15:09:24 UTC
Description of problem:
after installing fedora 22 updated, getting error"failed to find cpu0 device node error" and boot stucks.

issuing is coming with linux kernel update 4.2. as i am able to boot in older kernel i.e. 4.0 from grub menu.

I am using dell mini laptop with intel atom processor N455.

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

How reproducible:
after reinstalling kernel 4.2, problem reproduced

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
system dell mini with atom 455
system info
http://paste.fedoraproject.org/282956/44561087/

Comment 1 marc-schmitzer 2015-11-05 18:21:26 UTC
I'm seeing the same message, system seems to work fine, though.

uname -r: 4.2.3-200.fc22.i686+PAE
CPU: Intel(R) Pentium(R) Dual  CPU  T2410  @ 2.00GHz

Comment 2 Fedora End Of Life 2016-07-19 18:19:05 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.