errors in red - dmesg

Post Reply
zoldaten
Posts: 5
Joined: Thu May 30, 2019 4:44 pm
languages_spoken: english,russian
ODROIDs: odroid-xu4
Has thanked: 0
Been thanked: 0
Contact:

errors in red - dmesg

Unread post by zoldaten » Thu Jun 06, 2019 3:55 pm

Hi!
After install official image - ubuntu 18.04 i have some errors in dmesg:
1.
[ 0.072375] CPU1: thread -1, cpu 1, socket 1, mpidr 80000101
[ 0.096331] CPU2: thread -1, cpu 2, socket 1, mpidr 80000102
[ 0.124322] CPU3: thread -1, cpu 3, socket 1, mpidr 80000103
[ 0.152339] CPU4: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.152347] CPU4: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[ 0.172320] CPU5: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.172326] CPU5: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[ 0.180634] CPU6: thread -1, cpu 2, socket 0, mpidr 80000002
[ 0.180641] CPU6: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[ 0.188625] CPU7: thread -1, cpu 3, socket 0, mpidr 80000003
[ 0.188632] CPU7: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[ 0.188883] smp: Brought up 1 node, 8 CPUs
[ 0.188929] SMP: Total of 8 processors activated (384.00 BogoMIPS).

That means the system is vulnerable with Spectre virus ?
2.
[ 2.075483] console [ttySAC2] enabled
[ 2.079463] 12c30000.serial: ttySAC3 at MMIO 0x12c30000 (irq = 61, base_baud = 0) is a S3C6400/10
[ 2.090133] exynos-mixer 14450000.mixer: Linked as a consumer to 14650000.sys mmu
[ 2.096146] iommu: Adding device 14450000.mixer to group 0
[ 2.103221] exynos-hdmi 14530000.hdmi: Failed to get supply 'vdd': -517
[ 2.109099] exynos-drm-g2d 10850000.g2d: Linked as a consumer to 10a60000.sys mmu
[ 2.115885] exynos-drm-g2d 10850000.g2d: Linked as a consumer to 10a70000.sys mmu
[ 2.123184] iommu: Adding device 10850000.g2d to group 1
[ 2.128791] exynos-drm-g2d 10850000.g2d: The Exynos G2D (ver 4.1) successfull y probed.

something wrong with HDMI ?
3.
[ 2.174286] mali 11800000.mali: GPU identified as 0x0620 r0p1 status 0
[ 2.180519] mali 11800000.mali: Protected mode not available
[ 2.186067] devfreq devfreq0: Couldn't update frequency transition information.
[ 2.193614] mali 11800000.mali: Probed as mali0
[ 2.207089] brd: module loaded
[ 2.209354] libphy: Fixed MDIO Bus: probed

something wrong with GPU ?

4.
[ 4.092535] Registering SWP/SWPB emulation handler
[ 4.097327] registered taskstats version 1
[ 4.101038] Loading compiled-in X.509 certificates
[ 4.111440] Key type encrypted registered
[ 4.132577] OF: graph: no port node found in /soc/hdmi@14530000
[ 4.137888] [drm] Exynos DRM: using 14450000.mixer device for DMA mapping operations
[ 4.144886] exynos-drm exynos-drm: bound 14450000.mixer (ops 0xc0966284)
[ 4.151428] exynos-drm exynos-drm: bound 14530000.hdmi (ops 0xc0966924)
[ 4.158009] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 4.164601] [drm] No driver support for vblank timestamp query.
[ 4.173391] mmc_host mmc1: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0)

something wrong with HDMI ?

User avatar
odroid
Site Admin
Posts: 30976
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 21 times
Been thanked: 138 times
Contact:

Re: errors in red - dmesg

Unread post by odroid » Thu Jun 06, 2019 9:18 pm

Update the kernel first.
The latest one should be 4.14.120-160.

https://wiki.odroid.com/odroid-xu4/os_i ... st-upgrade

User avatar
OverSun
Posts: 1460
Joined: Mon Apr 29, 2013 5:12 pm
languages_spoken: english
Has thanked: 0
Been thanked: 2 times
Contact:

Re: errors in red - dmesg

Unread post by OverSun » Fri Jun 07, 2019 4:30 am

1. yes, this means it's spectre vulnerable. but spectre is not a virus, it's type of vulnerability. also this message doesn't mean it's not mitigated, it means CPU is vulnerable
2. there are things that depend on other things, but there is no mechanism of "this after that" in low level initialization, this is example of that, hdmi doesn't find it's vdd supply, because it's not yet ready, but is going to be ready later and it all goes well after.
3. some devfreq setting was not written by driver to device, which itself means nothing, maybe device doesn't support it, maybe it didn't exists in .dts. if devfreq work fine this easily can be ignored
4. driver didn't find a node describing a port in .dts under hdmi branch, which means nothing as well, maybe there is no such thing for this hardware and driver just present it as error while should as info, or it can be described if custom settings needed, but if it's usual thing then there is nothing to worry about.

There is no real reason to worry about dmesg messages in red if you don't really understand what's happening, most of the time it is not what it seems like, and when there is real problem you can see things not working clearly.

Post Reply

Return to “Issues”

Who is online

Users browsing this forum: No registered users and 0 guests