linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

xypista · 2015-07-18 11:43:07

Since the Linux kernel 4.1.2 upgrade, this message appears on boot:

[    0.791819] Failed to find cpu0 device node
[    0.792059] Unable to detect cache hierarcy from DT for CPU 0

Pastebins: dmesg, journalctl -k

CPU: Intel Core2 Duo E6420 (intel-ucode is keeping microcode updated)

Something similar reported here: https://bbs.archlinuxcn.org/viewtopic.php?id=3429

Everything seems to be working just fine. Is it safe to ignore?

Last edited by xypista (2015-09-04 14:18:42)

drot · 2015-07-18 11:58:34

Hmm yes, same message here (dmesg).

Teryn · 2015-07-19 20:41:25

Same thing here. Those two lines while using the new 4.1.2-2 kernel package, specifically.

Jul 19 11:52:09 lappy kernel: Failed to find cpu0 device node
Jul 19 11:52:09 lappy kernel: Unable to detect cache hierarcy from DT for CPU 0

Not sure what to make of it, since I could find only a handful of references to this error in relation to people who are using the new kernel (like here on the manjaro forums).

Maybe this is something unique to Arch or Arch-based distros, then? Perhaps using the LTS kernel package (3.14.48-1) is good general advice until this problem is further explored, because those errors did not happen when I booted with the LTS kernel.

Kilzool · 2015-07-19 22:35:22

Same thing here on Linux 4.1.2-2 w/ [AMD] K8 [Athlon64/Opteron]

ralessi · 2015-07-20 09:02:17

Not only do I have the same, but my laptop (Thinkpad X60s) also freezes after an hour or so. I submitted a bug report to bugzilla.kernel.org last week: https://bugzilla.kernel.org/show_bug.cgi?id=101621

xypista · 2015-07-20 19:00:34

ralessi wrote:

Not only do I have the same, but my laptop (Thinkpad X60s) also freezes after an hour or so. I submitted a bug report to bugzilla.kernel.org last week: https://bugzilla.kernel.org/show_bug.cgi?id=101621

I'm running my PC for hours every day and I did not experienced any kind of freezing. Also about that bugzilla report, I don't think these messages has anything to do with Intel graphics (I don't have one). Maybe you have an another issue that is unrelated to this.

ralessi · 2015-07-24 08:44:03

xypista wrote:

I'm running my PC for hours every day and I did not experienced any kind of freezing. Also about that bugzilla report, I don't think these messages has anything to do with Intel graphics (I don't have one). Maybe you have an another issue that is unrelated to this.

You may be right. As I said in my bug report, I'm not entirely sure this bug is graphics related. At least it is specific to the thinkpad X60. I just added to my report a snapshot of the messages I get when the kernel crashes at shutdown, which happens every time. This is a regression since it did not happen with kernels older than 4.1.1.

slackfenderson · 2015-07-26 01:24:42

This is definitely an upstream problem specific to the 4.1.x kernel. I would recommend reverting to 4.0.x. If you use git the 4.2.0 rc{1,2,3} does not have this problem.

I would not ignore the message as I regard anything red in my journal as a Bad Thing.
However I also am unable to detect any degradation in performance, cpu0 is alive and kicking.

It may be like the cgroup mismatch error at shutdown, probably of no concern, but i still use the shutdown hook to make it go away.

Reverting to your previous kernel is your best bet, LTS is a fine choice, git is a fun and unstable choice, ignoring it is probably not prudent.

Last edited by slackfenderson (2015-07-26 02:30:51)

xypista · 2015-08-08 12:48:03

I still have the problem with 4.1.4 and even with 4.2-rc5 (i686). Altough I just installed x86_64 Arch which is not showing this message for me. Maybe it is only afflicting i686? Anyone having this with x86_64?

Last edited by xypista (2015-08-08 12:48:13)

djgera · 2015-08-09 00:23:34

Such message is related to DT (Open Firmware Device Tree), and is enabled only on x86, there is no such thing on x86_64. Of course such option does not make sense if your hardware is not an embedded device.

ferthelet · 2015-08-19 02:44:08

djgera wrote:

Such message is related to DT (Open Firmware Device Tree), and is enabled only on x86, there is no such thing on x86_64. Of course such option does not make sense if your hardware is not an embedded device.

I have a Samsung NC10 Netbook with an Atom processor (x86)

[ 0.831643] Failed to find cpu0 device node
[ 0.832001] Unable to detect cache hierarcy from DT for CPU 0

Running currently Linux 4.1.5-1-ARCH #1 SMP PREEMPT Tue Aug 11 15:56:51 CEST 2015 i686 GNU/Linux

I don't know why this was marked as solved !?

Thank you!

xypista · 2015-08-20 01:18:28

I marked it because I thought that if it is related to the OF DT and is true that it has nothing to do with non-embedded devices, than you can just ignore the message. I guess it is not the preferred way to handle these errors (and I agree, idk why I marked it), so I removed the solved mark.

https://git.kernel.org/cgit/linux/kerne … acheinfo.c
This source file is the one that responsible for printing these errors. There are commits around 4.1RC that makes changes to this file (around these warning messages) and others. Someone should look into it / report it upstream.

Last edited by xypista (2015-09-17 10:05:53)

Jean3799 · 2015-09-03 04:40:40

xypista wrote:

I marked it because I thought that if it is related to the OF DT and is true that it has nothing to do with non-embedded devices, than you can just ignore the message. I guess it is not the preferred way to handle these errors (and I agree, idk why I marked it), so I removed the solved mark.
https://github.com/torvalds/linux/blob/ … acheinfo.c
This source file is the one that responsible for printing these errors. There are commits around 4.1RC that makes changes to this file (around these warning messages) and others. Someone should look into it / report it upstream.

.... I just started getting this error too.Is a fix on its way? Also how do I report this bug? I don't know which logs to send.

Last edited by Jean3799 (2015-09-03 20:00:46)

kozaki · 2015-09-06 22:01:31

Same line here (Atom N450 GMA 950) that freezes with any 4x linux kernel I threw in.
journalctl (passw "sesameOpen") for the latest failed boot attempt.
Related thread with some logs while having the boot issue: » [kernels 4x] System won't finish bootin and hang after pacman -Syu.
This tiny machine boots and runs fine with kernel linux-3.19.8-ck. Also have linux-4.1.5-1 and linux-4.0.1 in cache (not tested). linux-4.1.6 is the highest version that's available on [Testing].

Teryn · 2015-09-26 03:18:54

Still no solution to the error on my machine. There has also been graphical errors occuring, too, the screen display becomes a mess of garbled, mismatched pixels (no guarantee it's related, but they started happening at the same time).

This is an old ASUS EeePC 1000HE and I'm worried that this graphical instability isn't good for it (I'm on assistance and probably cannot afford a newer laptop). I'd like to try an older kernel, since none of these problems, the error message or the graphical problems, happened on the more recent kernel 3x versions.

EDIT (Oct 1st, 2015): Ok, it seems like the graphics issue was an Intel driver issue with me. I fixed it by changing the acceleration method to "uxa" as listed here:

https://wiki.archlinux.org/index.php/In … SNA_issues

Nothing unusual seems to be happening because of the cpu0 error, but I could be wrong. Both an Intel driver/ucode and 4.+ kernel upgrade could have happened around the same time, so I correlated the graphics issue to the journalctl error incorrectly.

Last edited by Teryn (2015-10-01 21:59:13)

firekage · 2015-10-03 23:59:01

I have Acer AOD 270 with Intel Atom N2600 and PoverVR graphic aka GMA3600. I have to this message at boot but my system works. Well, it works in text mode, in terminal but as soon as i enable kdm.service/sddm.service and login to GUI mode - black screen. Funny thing is that .xsession-errors and Xorg.0.logs are clean, nothing here. In Xorg.0.log there is only one message: server terminated. Nothing more. I know that it should have xf86-video-fbdev not xf86-video-intel, but i can't start gui with either of them.

Last edited by firekage (2015-10-04 00:02:17)

andrej.podzimek · 2015-10-07 23:15:50

This is actually a critical problem on 64-bit systems, because only one CPU is actually used. That makes a standard 8-CPU system (4 cores by 2 threads) sort of unusable (or crippled at least). However, this doesn't affect the 4.1 kernel series on x86_64. Only 4.2 kernels are affected.

aatoma · 2015-10-08 11:31:24

Same issue here.
My Acer AAO 110L vith Atom N260 started showing the dreaded 'Failed to find cpu0 device node' message after upgrading to kernel 4.x (I can't remember if the first 4.x kernel I tried was 4.0.x or 4.1.x).
Even if I can't tell for sure that the error message has something to do with the issue, now my tiny laptop screen goes black after say 5 to 15 minutes from login.
No disk activity, no reaction to keystrokes and no remote access, I can only power it off and reboot.
A couple of times the screen became a garbled mess of coloured pixels instead of going black.
As this is not my primary machine, I didn't investigate further, but now it appears I'm not alone so I'll try to dig a bit more information.

Last edited by aatoma (2015-10-08 11:31:41)

rwd · 2015-10-10 07:56:08

Has anyone actually reported this bug? I can't find any mention of 'Failed to find cpu0 device node' on bugs.archlinux.org or bugzilla.kernel.org besides the already mentioned, and seemingly unrelated https://bugzilla.kernel.org/show_bug.cgi?id=101621.

aatoma · 2015-10-15 11:05:48

The problem is I'm not really sure what to report.
After testing a few old kernels (4.0.x and 4.1.x) the only thing I'm sure of is that my netbook only works flawlessly when running 3.19.x
But on the other hand I've been able to work for a few hours with 4.1.3 (which shows the 'Failed to find ...' message on startup) only noticing a few graphics artifact.
So, the relationship between the error message on boot and the sudden death of the machine or garbled screen, might not be deterministic (or even misleading).
Would a generic bug like 'Atom processors having problems with 4.0+ kernels' help? Is this a graphics driver issue?

This issue is even more worrying now that linux-lts kernel moved to the 4.1.x line

rwd · 2015-10-15 21:52:05

I think we better make a thread about the freezes so we might grab attention of someone who is able to help define what/how to report, something like 'x86 - random freezes since upgrading to 4x kernel'.

aatoma · 2015-10-28 08:11:13

I experienced a few more system locks, and noticed that they all happened when the battery was low.
So, the issue I'm facing could be power management related and any connection to the 'Failed to find...' message fully incidental.
In the meanwhile, testing has become cumbersome (swapping kernels, waiting for the battery to reach low level ...)

danger89 · 2015-11-21 16:08:17

Same issue with my Acer Aspire One. Intel Atom processor.

archlinuxforever · 2016-01-08 03:04:09

Same issue since kernel 4.1.4-1 with netbook Point of View mobii with Intel(R) Atom(TM) CPU N270 @ 1.60GHz.

Since I boot I see this message:

[oscar@oscar_mobii ~]$ dmesg | grep cpu0
[    1.220776] Failed to find cpu0 device node
[oscar@oscar_mobii ~]$

But my netbook never freezes.

I updated system these dates:

[oscar@oscar_mobii ~]$ cat /var/log/pacman.log | grep 'upgraded linux'
[2015-06-19 19:53] [ALPM] upgraded linux-api-headers (3.18.5-1 -> 4.0-1)
[2015-06-19 19:57] [ALPM] upgraded linux-firmware (20150410.ec89525-1 -> 20150527.3161bfa-1)
[2015-06-19 19:57] [ALPM] upgraded linux (4.0.1-1 -> 4.0.5-1)
[2015-08-08 22:57] [ALPM] upgraded linux-firmware (20150527.3161bfa-1 -> 20150722.e10097a-1)
[2015-08-08 22:57] [ALPM] upgraded linux (4.0.5-1 -> 4.1.4-1)
[2015-11-13 21:37] [ALPM] upgraded linux-api-headers (4.0-1 -> 4.1.4-1)
[2015-11-13 21:44] [ALPM] upgraded linux-firmware (20150722.e10097a-1 -> 20150904.6ebf5d5-1)
[2015-11-13 21:44] [ALPM] upgraded linux (4.1.4-1 -> 4.2.5-1)
[2016-01-03 18:59] [ALPM] upgraded linux (4.2.5-1 -> 4.3.3-2)
[2016-01-05 22:44] [ALPM] upgraded linux-firmware (20150904.6ebf5d5-1 -> 20151207.bbe4917-1)
[2016-01-06 16:24] [ALPM] upgraded linux-firmware (20150722.e10097a-1 -> 20151207.bbe4917-1)
[2016-01-06 16:24] [ALPM] upgraded linux (4.1.4-1 -> 4.3.3-2)
[oscar@oscar_mobii ~]$

Now I have 4.3.3 kernel:

[oscar@oscar_mobii ~]$ uname -a
Linux oscar_mobii 4.3.3-2-ARCH #1 SMP PREEMPT Wed Dec 23 20:25:12 CET 2015 i686 GNU/Linux
[oscar@oscar_mobii ~]$

[oscar@oscar_mobii ~]$ cat /proc/cpuinfo 
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 28
model name	: Intel(R) Atom(TM) CPU N270   @ 1.60GHz
stepping	: 2
microcode	: 0x212
cpu MHz		: 800.000
cache size	: 512 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 1
apicid		: 0
initial apicid	: 0
fdiv_bug	: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 xtpr pdcm movbe lahf_lm dtherm
bugs		:
bogomips	: 3193.01
clflush size	: 64
cache_alignment	: 64
address sizes	: 32 bits physical, 32 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 28
model name	: Intel(R) Atom(TM) CPU N270   @ 1.60GHz
stepping	: 2
microcode	: 0x212
cpu MHz		: 1600.000
cache size	: 512 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 1
apicid		: 1
initial apicid	: 1
fdiv_bug	: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 xtpr pdcm movbe lahf_lm dtherm
bugs		:
bogomips	: 3193.01
clflush size	: 64
cache_alignment	: 64
address sizes	: 32 bits physical, 32 bits virtual
power management:

[oscar@oscar_mobii ~]$

I have also the message "Unable to detect cache hierarchy from DT for CPU 0" on dmesg:

[oscar@oscar_mobii ~]$ dmesg | grep 'CPU 0'
[    0.000000] CPU 0 irqstacks, hard=f5834000 soft=f5836000
[    1.221135] Unable to detect cache hierarchy from DT for CPU 0
[oscar@oscar_mobii ~]$

The message in journalctl is in red, so it means that is a several error.

Last edited by archlinuxforever (2016-01-08 03:22:11)

bernd_b · 2016-02-07 23:08:00

I found two pages where the boot message "Failed to find cpu0 device node" is considered harmless:

https://www.reddit.com/r/archlinux/comm … find_cpu0/ says:

This is from an optional generic 'cpufreq_cpu0' module. I think it probably should not exist in most kernels. But I also think it is a harmless error message. 
Basically, it is saying that the device node that it supports does not exist, so it just exits.

https://bugzilla.redhat.com/show_bug.cgi?id=1254210 says:

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.

But honestly, I still don't understand anything told there.

Arch Linux

#1 2015-07-18 11:43:07

linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#2 2015-07-18 11:58:34

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#3 2015-07-19 20:41:25

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#4 2015-07-19 22:35:22

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#5 2015-07-20 09:02:17

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#6 2015-07-20 19:00:34

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#7 2015-07-24 08:44:03

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#8 2015-07-26 01:24:42

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#9 2015-08-08 12:48:03

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#10 2015-08-09 00:23:34

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#11 2015-08-19 02:44:08

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#12 2015-08-20 01:18:28

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#13 2015-09-03 04:40:40

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#14 2015-09-06 22:01:31

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#15 2015-09-26 03:18:54

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#16 2015-10-03 23:59:01

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#17 2015-10-07 23:15:50

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#18 2015-10-08 11:31:24

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#19 2015-10-10 07:56:08

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#20 2015-10-15 11:05:48

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#21 2015-10-15 21:52:05

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#22 2015-10-28 08:11:13

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#23 2015-11-21 16:08:17

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#24 2016-01-08 03:04:09

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

#25 2016-02-07 23:08:00

Re: linux-4.1.2-2 i686 "Failed to find cpu0 device node" boot msg

Board footer