Kernel 5.0 development thread

MastaG
Posts: 310
Joined: Mon Aug 26, 2013 6:05 pm
languages_spoken: english
Has thanked: 18 times
Been thanked: 4 times
Contact:

Re: Kernel 5.0 development thread

Unread post by MastaG » Tue Feb 05, 2019 4:41 pm

@memeka thanks for getting the r21p0 driver working!
That's great man!
Also I hope Alyssa will be able to work out support for our T628 in the near future. (I also hope she has a Odroid XU4 to hack on.)

I still need to test your kernel on my XU3 (analog audio jack), will hope to do this sometime near the end of the week.

User avatar
odroid
Site Admin
Posts: 33615
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 491 times
Been thanked: 500 times
Contact:

Re: Kernel 5.0 development thread

Unread post by odroid » Wed Feb 06, 2019 10:48 am

memeka wrote:
Mon Feb 04, 2019 9:23 pm
Just for the fun, I tried panfrost:
-----------------------------------------
Just eglinfo is working :)
Nice :o
We have to send some XU4 samples to Panfrost team if they don't have.

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 57 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Wed Feb 06, 2019 11:01 am

Panfrost job submission for T6xx is not working atm.
People working on panfrost have xu3/xu4 but focus for now on T8xx/bifrost development (probably on rk3399).
So we need to wait for them to fix T6xx issues.

Those interested can follow https://gitlab.freedesktop.org/panfrost/mesa/issues/12

PS - I pushed a panfrost 5.0 kernel branch on my repo which has latest mali kernel driver integrated, necessary for panfrost.

User avatar
odroid
Site Admin
Posts: 33615
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 491 times
Been thanked: 500 times
Contact:

Re: Kernel 5.0 development thread

Unread post by odroid » Wed Feb 06, 2019 11:04 am

I see. Well noted.

strause
Posts: 10
Joined: Fri Feb 24, 2017 10:18 pm
languages_spoken: english
Location: Czech Republic
Has thanked: 0
Been thanked: 0
Contact:

Re: Kernel 5.0 development thread

Unread post by strause » Thu Feb 07, 2019 5:22 am

Hi, i tried your kernel from odroidxu4-5.0.y branch. I must say good job :)

I found one issue. Sound is speeded up in raspotify and kodi - youtube addon, I think it's two times faster than should be, maybe more.

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 57 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Thu Feb 07, 2019 9:40 am

strause wrote:
Thu Feb 07, 2019 5:22 am
I found one issue. Sound is speeded up in raspotify and kodi - youtube addon, I think it's two times faster than should be, maybe more.
Maybe can @odroid also test this? Is it an issue just with the youtube addon in kodi? do other addons/playing movies/music work ok?
It might the issue just for specific frequencies? We might have to change some alsa/pulse daemon software settings...

User avatar
odroid
Site Admin
Posts: 33615
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 491 times
Been thanked: 500 times
Contact:

Re: Kernel 5.0 development thread

Unread post by odroid » Thu Feb 07, 2019 9:43 am

I tested an H264 BBB sample video for 5 minute on Kodi but there was no such sound speed up issue.
Right. we need to know the audio format and sample frequency.

MastaG
Posts: 310
Joined: Mon Aug 26, 2013 6:05 pm
languages_spoken: english
Has thanked: 18 times
Been thanked: 4 times
Contact:

Re: Kernel 5.0 development thread

Unread post by MastaG » Thu Feb 07, 2019 11:01 pm

Hi @memeka
I've had some time to try out your kernel (odroidxu4-5.0.y) using your config on my XU3.
It seems to boot but I don't get any output on my monitor.
I'm using the mini-hdmi cable and a regular DVI monitor (so it doesn't provide any hdmi-audio support).
Here's the dmesg: https://pastebin.com/qRxdMr8N

I did get some warning during compilation:

Code: Select all

  CC      drivers/gpu/drm/exynos/exynos_hdmi.o
drivers/gpu/drm/exynos/exynos_hdmi.c:731:22: let op: unsigned conversion from ‘int’ to ‘unsigned char’ changes value from ‘5656’ to ‘24’ [-Woverflow]
    0x01, 0xD1, 0x29, 0x1618, 0x418, 0x190, 0xF5, 0xCF,
                      ^~~~~~
drivers/gpu/drm/exynos/exynos_hdmi.c:731:30: let op: unsigned conversion from ‘int’ to ‘unsigned char’ changes value from ‘1048’ to ‘24’ [-Woverflow]
    0x01, 0xD1, 0x29, 0x1618, 0x418, 0x190, 0xF5, 0xCF,
                              ^~~~~
drivers/gpu/drm/exynos/exynos_hdmi.c:731:37: let op: unsigned conversion from ‘int’ to ‘unsigned char’ changes value from ‘400’ to ‘144’ [-Woverflow]
    0x01, 0xD1, 0x29, 0x1618, 0x418, 0x190, 0xF5, 0xCF,
                                     ^~~~~
drivers/gpu/drm/exynos/exynos_hdmi.c:732:10: let op: unsigned conversion from ‘int’ to ‘unsigned char’ changes value from ‘360’ to ‘104’ [-Woverflow]
    0x8D, 0x168, 0xF5, 0xD8, 0x45, 0xA0, 0xAC, 0x80,
          ^~~~~
I'm not sure whether this would be the cause.

Furthermore your kernel doesn't build a: exynos5422-odroidxu4-kvm.dtb, the other dtbs are all there though :)

So apart from the display not turning on, it works fine and stable.

MastaG
Posts: 310
Joined: Mon Aug 26, 2013 6:05 pm
languages_spoken: english
Has thanked: 18 times
Been thanked: 4 times
Contact:

Re: Kernel 5.0 development thread

Unread post by MastaG » Thu Feb 07, 2019 11:37 pm

Woops, I've forgot to properly set my hdmi switch to the correct port.. :P
Everything works great using your kernel on my XU3.
Including analog audio !

Great work memeka!
Attachments
Schermafdruk van 2019-02-07 15-36-03.png
Schermafdruk van 2019-02-07 15-36-03.png (801.06 KiB) Viewed 7160 times

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 57 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Fri Feb 08, 2019 3:40 am

@MastaG good to hear

There’s no kvm dtb on mainline, you just need to build it yourself I think :)

User avatar
odroid
Site Admin
Posts: 33615
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 491 times
Been thanked: 500 times
Contact:

Re: Kernel 5.0 development thread

Unread post by odroid » Fri Feb 08, 2019 9:57 am

Yes! Kernel 5.0 RC5 is working nicely and stably so far. :D

I hope we can run Kodi 18 on X11 soon.

MastaG
Posts: 310
Joined: Mon Aug 26, 2013 6:05 pm
languages_spoken: english
Has thanked: 18 times
Been thanked: 4 times
Contact:

Re: Kernel 5.0 development thread

Unread post by MastaG » Fri Feb 08, 2019 5:50 pm

Kodi 18 runs very well on Wayland on gnome 3.30 :)
So does RetroArch.

Only thing left would be to get igalia's ozone version of Chromium playing nice with our mali drivers on wayland.
Firefox wayland runs pretty good, but the lack of video acceleration makes full screen youtube slow.

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 57 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Fri Feb 08, 2019 6:06 pm

@MastaG what's wrong with igalia's chromium?
last time i compiled it, worked pretty good, webgl was on, video was great: https://www.youtube.com/watch?v=F5atp58gGQM

MastaG
Posts: 310
Joined: Mon Aug 26, 2013 6:05 pm
languages_spoken: english
Has thanked: 18 times
Been thanked: 4 times
Contact:

Re: Kernel 5.0 development thread

Unread post by MastaG » Fri Feb 08, 2019 6:29 pm

Hmm.. I didn't got it to work.
Did you cross-compile it yourself? if yes, would still happen to have your gn flags and perhaps some patches?

dante6913
Posts: 96
Joined: Sat Oct 01, 2016 7:16 am
languages_spoken: english, Portuguese
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Kernel 5.0 development thread

Unread post by dante6913 » Mon Feb 11, 2019 4:45 am

odroid wrote:
Wed Jan 30, 2019 8:31 am
dante6913 wrote:
Wed Jan 30, 2019 1:01 am
I'm getting an error with
"sudo make modules_install
sudo cp -f arch/arm/boot/zImage /media/boot"

modules_install tells me that can't find .ko files
and sudo cp -f arch/arm/boot/zImage /media/boot tells me that this file doesn't exist. So I was not able to build the kernel and boot with it.
Is there any date for releasing a image of ubuntu 18.04 with kernel 5.0, so the less skilled could test it?
Thanks
Was there any error while building kernel with "make -j8" ?
Do you have enough space on eMMC/SD?
Thank you Odroid, the problem was lack of space. Change of sd card and I was able to build the kernel with no issue.

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 57 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Tue Feb 19, 2019 11:39 am

UPDATES

* rebased on v5.0-rc7
* fixes for CPU HYP mode
* fixes for KVM (ARM timers proper support) - UNTESTED
* add CPU supend/resume support - UNTESTED
* secondary CPU DAI support - UNTESTED

So many new things to test! :)

User avatar
odroid
Site Admin
Posts: 33615
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 491 times
Been thanked: 500 times
Contact:

Re: Kernel 5.0 development thread

Unread post by odroid » Tue Feb 19, 2019 12:22 pm

Nice update!

MastaG
Posts: 310
Joined: Mon Aug 26, 2013 6:05 pm
languages_spoken: english
Has thanked: 18 times
Been thanked: 4 times
Contact:

Re: Kernel 5.0 development thread

Unread post by MastaG » Tue Feb 19, 2019 8:04 pm

@memeka Thanks for the update!
Does this require changes to the kernel config as well? e.g. enabling some more options?

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 57 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Tue Feb 19, 2019 8:27 pm

For kvm yes, I will put my config here in a few hours

User avatar
emk2203
Posts: 47
Joined: Fri Oct 16, 2015 12:29 am
languages_spoken: english, german
ODROIDs: C1+, C2, XU4, HC1, HC2, N2
Has thanked: 7 times
Been thanked: 0
Contact:

Re: Kernel 5.0 development thread

Unread post by emk2203 » Tue Feb 19, 2019 8:58 pm

Cloudshell 1 display doesn't work. The modules spidev.ko, spi-s3c64xx.ko and fbtft_device.ko are generated and loaded as fbtft, spidev and spi_s3c64xx. I hardlinked spi-s3c64xx.ko to spi_s3c64xx.ko just in case that something relies on the old name from the kernel 3 series.

But the display stays dark and without input.

Code: Select all

echo 0 | sudo tee /sys/class/backlight/*/bl_power
(worked on the 4 series kernels from HK) gives an error message. The /sys/class/backlight directory is empty.

EDIT: This was based on the rc6 config. I compiled only a few minutes before your update came. I just installed the rc7, no changes, still no display.

User avatar
emk2203
Posts: 47
Joined: Fri Oct 16, 2015 12:29 am
languages_spoken: english, german
ODROIDs: C1+, C2, XU4, HC1, HC2, N2
Has thanked: 7 times
Been thanked: 0
Contact:

Re: Kernel 5.0 development thread

Unread post by emk2203 » Tue Feb 19, 2019 10:06 pm

memeka wrote:
Tue Feb 19, 2019 11:39 am
UPDATES

* rebased on v5.0-rc7
* fixes for CPU HYP mode
* fixes for KVM (ARM timers proper support) - UNTESTED
* add CPU supend/resume support - UNTESTED
* secondary CPU DAI support - UNTESTED

So many new things to test! :)
The System.map file isn't generated for rc7. It was for rc6.

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 57 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Tue Feb 19, 2019 10:35 pm

spidev patches are not added, neither are the drivers for HK's fbtft.

User avatar
emk2203
Posts: 47
Joined: Fri Oct 16, 2015 12:29 am
languages_spoken: english, german
ODROIDs: C1+, C2, XU4, HC1, HC2, N2
Has thanked: 7 times
Been thanked: 0
Contact:

Re: Kernel 5.0 development thread

Unread post by emk2203 » Tue Feb 19, 2019 11:16 pm

I thought that the cloudshell displays were somewhat standard stuff and would work without any non-standard patches or drivers. Well, obviously not...

Since the hktft9340 should be just a ili9340, is it possible to force use of the ili9340 driver? That would get rid of the need to have the extra driver. Are the spidev patches needed with 5.0.0?

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 57 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Wed Feb 20, 2019 2:49 am

On 4.14 there were spidev and fbtft patches which I did not port...

MastaG
Posts: 310
Joined: Mon Aug 26, 2013 6:05 pm
languages_spoken: english
Has thanked: 18 times
Been thanked: 4 times
Contact:

Re: Kernel 5.0 development thread

Unread post by MastaG » Thu Feb 21, 2019 8:45 pm

I've tried your kernel 5.0 rc7.
It works but it segfaults when I login to the shell.

Code: Select all

[    0.000000] Booting Linux on physical CPU 0x100
[    0.000000] Linux version 5.0.0-rc7-fedoraXU+ (root@odroidxu4) (gcc version 8.2.1 20181215 (Red Hat 8.2.1-6) (GCC)) #2 SMP PREEMPT Thu Feb 21 12:22:35 CET 2019
[    0.000000] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), cr=10c5387d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Hardkernel Odroid XU3
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] cma: Reserved 128 MiB at 0xb6800000
[    0.000000] Samsung CPU ID: 0xe5422001
[    0.000000] On node 0 totalpages: 518656
[    0.000000]   Normal zone: 1728 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 196608 pages, LIFO batch:63
[    0.000000]   HighMem zone: 322048 pages, LIFO batch:63
[    0.000000] Running under secure firmware.
[    0.000000] random: get_random_bytes called from start_kernel+0x8c/0x4e8 with crng_init=0
[    0.000000] percpu: Embedded 17 pages/cpu @(ptrval) s38476 r8192 d22964 u69632
[    0.000000] pcpu-alloc: s38476 r8192 d22964 u69632 alloc=17*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [0] 4 [0] 5 [0] 6 [0] 7 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 516928
[    0.000000] Kernel command line: console=tty1 console=ttySAC2,115200n8 root=UUID=9d706ec0-8dc5-4882-ae7f-3b9fbfe449e7 rootwait ro rhgb quiet LANG=nl_NL.UTF-8 ro fsck.repair=yes net.ifnames=0  HPD=true vout=hdmi usbhid.quirks=0x0eef:0x0005:0x0004 smsc95xx.macaddr=00:1e:06:61:7a:39 false s5p_mfc.mem=16M
[    0.000000] hdmi: using HDMI mode
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 1896732K/2074624K available (9216K kernel code, 752K rwdata, 2496K rodata, 1024K init, 334K bss, 46820K reserved, 131072K cma-reserved, 1157120K highmem)
[    0.000000] Virtual kernel memory layout:
                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                   vmalloc : 0xf0800000 - 0xff800000   ( 240 MB)
                   lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
                   pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
                   modules : 0xbf000000 - 0xbfe00000   (  14 MB)
                     .text : 0x(ptrval) - 0x(ptrval)   (10208 kB)
                     .init : 0x(ptrval) - 0x(ptrval)   (1024 kB)
                     .data : 0x(ptrval) - 0x(ptrval)   ( 753 kB)
                      .bss : 0x(ptrval) - 0x(ptrval)   ( 335 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[    0.000000] hperf_hmp: fast CPUs mask: 000000F0
[    0.000000] hperf_hmp: slow CPUs mask: 0000000F
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] 	Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] GIC: Using split EOI/Deactivate mode
[    0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[    0.000000] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[    0.000000] Switching to timer-based delay loop, resolution 41ns
[    0.000009] Ignoring duplicate/late registration of read_current_timer delay
[    0.000022] clocksource: mct-frc: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[    0.000037] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
[    0.000058] genirq: irq_chip COMBINER did not update eff. affinity mask of irq 53
[    0.001017] Console: colour dummy device 80x30
[    0.001035] printk: console [tty1] enabled
[    0.001074] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
[    0.001086] pid_max: default: 32768 minimum: 301
[    0.001228] LSM: Security Framework initializing
[    0.001238] Yama: becoming mindful.
[    0.001267] SELinux:  Initializing.
[    0.001463] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001482] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.002455] CPU: Testing write buffer coherency: ok
[    0.002990] CPU0: thread -1, cpu 0, socket 1, mpidr 80000100
[    0.024111] Setting up static identity map for 0x40100000 - 0x40100060
[    0.024439] ARM CCI driver probed
[    0.024668] Exynos MCPM support installed
[    0.032047] rcu: Hierarchical SRCU implementation.
[    0.048047] smp: Bringing up secondary CPUs ...
[    0.080438] CPU1: thread -1, cpu 1, socket 1, mpidr 80000101
[    0.104412] CPU2: thread -1, cpu 2, socket 1, mpidr 80000102
[    0.136397] CPU3: thread -1, cpu 3, socket 1, mpidr 80000103
[    0.168421] CPU4: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.168431] CPU4: Spectre v2: using ICIALLU workaround
[    0.192402] CPU5: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.192410] CPU5: Spectre v2: using ICIALLU workaround
[    0.204607] CPU6: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.204615] CPU6: Spectre v2: using ICIALLU workaround
[    0.216613] CPU7: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.216620] CPU7: Spectre v2: using ICIALLU workaround
[    0.216783] smp: Brought up 1 node, 8 CPUs
[    0.216795] SMP: Total of 8 processors activated (384.00 BogoMIPS).
[    0.216801] CPU: All CPU(s) started in HYP mode.
[    0.216805] CPU: Virtualization extensions available.
[    0.218710] devtmpfs: initialized
[    0.235205] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
[    0.235340] hperf_hmp: registered cpufreq transition notifier
[    0.235616] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.235633] futex hash table entries: 2048 (order: 5, 131072 bytes)
[    0.237998] pinctrl core: initialized pinctrl subsystem
[    0.240042] NET: Registered protocol family 16
[    0.243376] DMA: preallocated 2048 KiB pool for atomic coherent allocations
[    0.244771] audit: initializing netlink subsys (disabled)
[    0.244958] audit: type=2000 audit(0.244:1): state=initialized audit_enabled=0 res=1
[    0.245448] cpuidle: using governor menu
[    0.246025] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.246034] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.292205] EXYNOS5420 PMU initialized
[    0.388014] usbcore: registered new interface driver usbfs
[    0.388067] usbcore: registered new interface driver hub
[    0.388225] usbcore: registered new device driver usb
[    0.388888] s3c-i2c 12c60000.i2c: slave address 0x00
[    0.388902] s3c-i2c 12c60000.i2c: bus frequency set to 65 KHz
[    0.389708] s3c-i2c 12c60000.i2c: i2c-0: S3C I2C adapter
[    0.389871] s3c-i2c 12c80000.i2c: slave address 0x00
[    0.389884] s3c-i2c 12c80000.i2c: bus frequency set to 65 KHz
[    0.390109] s3c-i2c 12c80000.i2c: i2c-2: S3C I2C adapter
[    0.390535] media: Linux media interface: v0.10
[    0.390573] videodev: Linux video capture interface: v2.00
[    0.390687] pps_core: LinuxPPS API ver. 1 registered
[    0.390695] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.390950] s3c2410-wdt 101d0000.watchdog: watchdog inactive, reset disabled, irq disabled
[    0.391753] Advanced Linux Sound Architecture Driver Initialized.
[    0.392273] NetLabel: Initializing
[    0.392281] NetLabel:  domain hash size = 128
[    0.392288] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[    0.392351] NetLabel:  unlabeled traffic allowed by default
[    0.392401] random: fast init done
[    0.393206] clocksource: Switched to clocksource mct-frc
[    0.937928] VFS: Disk quotas dquot_6.6.0
[    0.937996] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.952455] NET: Registered protocol family 2
[    0.953092] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)
[    0.953123] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.953257] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.953416] TCP: Hash tables configured (established 8192 bind 8192)
[    0.953539] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.953578] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.953904] NET: Registered protocol family 1
[    0.954497] RPC: Registered named UNIX socket transport module.
[    0.954505] RPC: Registered udp transport module.
[    0.954513] RPC: Registered tcp transport module.
[    0.954520] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.954762] Trying to unpack rootfs image as initramfs...
[    7.574517] Freeing initrd memory: 12560K
[    7.575826] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 5 counters available
[    7.576673] hw perfevents: enabled with armv7_cortex_a15 PMU driver, 7 counters available
[    7.581718] Initialise system trusted keyrings
[    7.581974] workingset: timestamp_bits=14 max_order=19 bucket_order=5
[    7.591144] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    7.591955] NFS: Registering the id_resolver key type
[    7.591977] Key type id_resolver registered
[    7.591985] Key type id_legacy registered
[    7.592002] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    7.592041] romfs: ROMFS MTD (C) 2007 Red Hat, Inc.
[    7.738527] Key type asymmetric registered
[    7.738536] Asymmetric key parser 'x509' registered
[    7.738597] bounce: pool size: 64 pages
[    7.738641] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[    7.738864] io scheduler mq-deadline registered
[    7.738874] io scheduler kyber registered
[    7.739136] io scheduler bfq registered
[    7.741624] samsung-usb2-phy 12130000.phy: 12130000.phy supply vbus not found, using dummy regulator
[    7.741723] samsung-usb2-phy 12130000.phy: Linked as a consumer to regulator.0
[    7.742491] exynos5_usb3drd_phy 12100000.phy: 12100000.phy supply vbus not found, using dummy regulator
[    7.742580] exynos5_usb3drd_phy 12100000.phy: Linked as a consumer to regulator.0
[    7.742596] exynos5_usb3drd_phy 12100000.phy: 12100000.phy supply vbus-boost not found, using dummy regulator
[    7.742953] exynos5_usb3drd_phy 12500000.phy: 12500000.phy supply vbus not found, using dummy regulator
[    7.743052] exynos5_usb3drd_phy 12500000.phy: Linked as a consumer to regulator.0
[    7.743068] exynos5_usb3drd_phy 12500000.phy: 12500000.phy supply vbus-boost not found, using dummy regulator
[    7.751703] dma-pl330 121a0000.pdma: Loaded driver for PL330 DMAC-241330
[    7.751716] dma-pl330 121a0000.pdma: 	DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    7.754343] dma-pl330 121b0000.pdma: Loaded driver for PL330 DMAC-241330
[    7.754355] dma-pl330 121b0000.pdma: 	DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    7.755186] dma-pl330 10800000.mdma: Loaded driver for PL330 DMAC-241330
[    7.755198] dma-pl330 10800000.mdma: 	DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32
[    7.818854] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    7.821073] 12c00000.serial: ttySAC0 at MMIO 0x12c00000 (irq = 62, base_baud = 0) is a S3C6400/10
[    7.821530] 12c10000.serial: ttySAC1 at MMIO 0x12c10000 (irq = 63, base_baud = 0) is a S3C6400/10
[    7.821909] 12c20000.serial: ttySAC2 at MMIO 0x12c20000 (irq = 64, base_baud = 0) is a S3C6400/10
[    7.822007] printk: console [ttySAC2] enabled
[    7.822378] 12c30000.serial: ttySAC3 at MMIO 0x12c30000 (irq = 65, base_baud = 0) is a S3C6400/10
[    7.823983] exynos-trng 10830600.rng: Exynos True Random Number Generator.
[    7.824878] iommu: Adding device 14450000.mixer to group 0
[    7.825392] exynos-mixer 14450000.mixer: Linked as a consumer to 14650000.sysmmu
[    7.826941] exynos-hdmi 14530000.hdmi: Failed to get supply 'vdd': -517
[    7.832797] iommu: Adding device 10850000.g2d to group 1
[    7.832820] exynos-drm-g2d 10850000.g2d: Linked as a consumer to 10a60000.sysmmu
[    7.832839] exynos-drm-g2d 10850000.g2d: Linked as a consumer to 10a70000.sysmmu
[    7.838790] mali 11800000.mali: Continuing without Mali regulator control
[    7.840266] mali 11800000.mali: GPU identified as 0x0620 r0p1 status 0
[    7.840788] mali 11800000.mali: Protected mode not available
[    7.841243] devfreq devfreq0: Couldn't update frequency transition information.
[    7.847945] mali 11800000.mali: Probed as mali0
[    7.858582] brd: module loaded
[    7.859144] libphy: Fixed MDIO Bus: probed
[    7.859467] usbcore: registered new interface driver r8152
[    7.859518] usbcore: registered new interface driver cdc_ether
[    7.859554] usbcore: registered new interface driver cdc_subset
[    7.861682] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    7.861709] ehci-exynos: EHCI EXYNOS driver
[    7.862044] exynos-ehci 12110000.usb: EHCI Host Controller
[    7.862076] exynos-ehci 12110000.usb: new USB bus registered, assigned bus number 1
[    7.862398] exynos-ehci 12110000.usb: irq 91, io mem 0x12110000
[    7.877256] exynos-ehci 12110000.usb: USB 2.0 started, EHCI 1.00
[    7.877566] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.00
[    7.877578] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    7.877587] usb usb1: Product: EHCI Host Controller
[    7.877596] usb usb1: Manufacturer: Linux 5.0.0-rc7-fedoraXU+ ehci_hcd
[    7.877605] usb usb1: SerialNumber: 12110000.usb
[    7.878197] hub 1-0:1.0: USB hub found
[    7.878242] hub 1-0:1.0: 3 ports detected
[    7.879147] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    7.879173] ohci-exynos: OHCI EXYNOS driver
[    7.879366] exynos-ohci 12120000.usb: USB Host Controller
[    7.879391] exynos-ohci 12120000.usb: new USB bus registered, assigned bus number 2
[    7.879529] exynos-ohci 12120000.usb: irq 91, io mem 0x12120000
[    7.941498] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.00
[    7.941510] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    7.941519] usb usb2: Product: USB Host Controller
[    7.941528] usb usb2: Manufacturer: Linux 5.0.0-rc7-fedoraXU+ ohci_hcd
[    7.941537] usb usb2: SerialNumber: 12120000.usb
[    7.942096] hub 2-0:1.0: USB hub found
[    7.942141] hub 2-0:1.0: 3 ports detected
[    7.944281] mousedev: PS/2 mouse device common for all mice
[    7.945621] i2c /dev entries driver
[    7.962367] vdd_ldo9: Bringing 3300000uV into 3000000-3000000uV
[    7.971518] vddq_mmc2: Bringing 3300000uV into 2800000-2800000uV
[    7.983287] vdd_sd: Bringing 3300000uV into 2800000-2800000uV
[    8.213262] usb 1-1: new high-speed USB device number 2 using exynos-ehci
[    8.369603] usb 1-1: New USB device found, idVendor=0424, idProduct=9514, bcdDevice= 2.00
[    8.369614] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    8.370231] hub 1-1:1.0: USB hub found
[    8.370339] hub 1-1:1.0: 5 ports detected
[    8.657250] usb 1-1.1: new high-speed USB device number 3 using exynos-ehci
[    8.765720] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00, bcdDevice= 2.00
[    8.765731] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    9.048522] s5m-rtc s2mps14-rtc: registered as rtc0
[    9.049068] s2mps11-clk s2mps11-clk: DMA mask not set
[    9.052678] iommu: Adding device 11f50000.jpeg to group 2
[    9.052701] s5p-jpeg 11f50000.jpeg: Linked as a consumer to 11f10000.sysmmu
[    9.053072] s5p-jpeg 11f50000.jpeg: encoder device registered as /dev/video30
[    9.053305] s5p-jpeg 11f50000.jpeg: decoder device registered as /dev/video31
[    9.053313] s5p-jpeg 11f50000.jpeg: Samsung S5P JPEG codec
[    9.053554] iommu: Adding device 11f60000.jpeg to group 3
[    9.053575] s5p-jpeg 11f60000.jpeg: Linked as a consumer to 11f20000.sysmmu
[    9.053930] s5p-jpeg 11f60000.jpeg: encoder device registered as /dev/video32
[    9.054109] s5p-jpeg 11f60000.jpeg: decoder device registered as /dev/video33
[    9.054117] s5p-jpeg 11f60000.jpeg: Samsung S5P JPEG codec
[    9.054856] iommu: Adding device 11000000.codec to group 4
[    9.055320] s5p-mfc 11000000.codec: Linked as a consumer to 11200000.sysmmu
[    9.055342] s5p-mfc 11000000.codec: Linked as a consumer to 11210000.sysmmu
[    9.073172] s5p-mfc 11000000.codec: preallocated 16 MiB buffer for the firmware and context buffers
[    9.074648] s5p-mfc 11000000.codec: decoder registered as /dev/video10
[    9.074822] s5p-mfc 11000000.codec: encoder registered as /dev/video11
[    9.076230] Registered IR keymap rc-cec
[    9.076356] rc rc0: s5p-cec as /devices/platform/soc/101b0000.cec/rc/rc0
[    9.076699] input: s5p-cec as /devices/platform/soc/101b0000.cec/rc/rc0/input0
[    9.077707] iommu: Adding device 13e00000.video-scaler to group 5
[    9.078142] exynos-gsc 13e00000.video-scaler: Linked as a consumer to 13e80000.sysmmu
[    9.078878] iommu: Adding device 13e10000.video-scaler to group 6
[    9.079383] exynos-gsc 13e10000.video-scaler: Linked as a consumer to 13e90000.sysmmu
[    9.084282] exynos-tmu 10060000.tmu: Linked as a consumer to regulator.7
[    9.085292] exynos-tmu 10064000.tmu: Linked as a consumer to regulator.7
[    9.086245] exynos-tmu 10068000.tmu: Linked as a consumer to regulator.7
[    9.087207] exynos-tmu 1006c000.tmu: Linked as a consumer to regulator.7
[    9.088166] exynos-tmu 100a0000.tmu: Linked as a consumer to regulator.7
[    9.089043] device-mapper: uevent: version 1.0.3
[    9.089439] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-devel@redhat.com
[    9.090425] cpu cpu0: Linked as a consumer to regulator.44
[    9.090508] cpu cpu0: Dropping the link to regulator.44
[    9.091219] cpu cpu0: Linked as a consumer to regulator.44
[    9.098329] cpu cpu4: Linked as a consumer to regulator.40
[    9.106935] sdhci: Secure Digital Host Controller Interface driver
[    9.106940] sdhci: Copyright(c) Pierre Ossman
[    9.107121] Synopsys Designware Multimedia Card Interface Driver
[    9.107677] dwmmc_exynos 12200000.mmc: IDMAC supports 32-bit address mode.
[    9.107760] dwmmc_exynos 12200000.mmc: Using internal DMA controller.
[    9.107770] dwmmc_exynos 12200000.mmc: Version ID is 250a
[    9.107806] dwmmc_exynos 12200000.mmc: DW MMC controller at irq 93,64 bit host data width,64 deep fifo
[    9.107880] dwmmc_exynos 12200000.mmc: Linked as a consumer to regulator.18
[    9.107931] dwmmc_exynos 12200000.mmc: Linked as a consumer to regulator.3
[    9.108014] dwmmc_exynos 12200000.mmc: allocated mmc-pwrseq
[    9.125125] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    9.138244] dwmmc_exynos 12220000.mmc: IDMAC supports 32-bit address mode.
[    9.138278] dwmmc_exynos 12220000.mmc: Using internal DMA controller.
[    9.138287] dwmmc_exynos 12220000.mmc: Version ID is 250a
[    9.138317] dwmmc_exynos 12220000.mmc: DW MMC controller at irq 94,64 bit host data width,64 deep fifo
[    9.138393] dwmmc_exynos 12220000.mmc: Linked as a consumer to regulator.19
[    9.138450] dwmmc_exynos 12220000.mmc: Linked as a consumer to regulator.13
[    9.153336] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    9.185124] s5p-secss 10830000.sss: s5p-sss driver registered
[    9.185458] hidraw: raw HID events driver (C) Jiri Kosina
[    9.186735] mmc_host mmc0: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0)
[    9.186836] exynos-bus soc:bus_wcore: Linked as a consumer to regulator.41
[    9.187380] exynos-bus soc:bus_wcore: Dropping the link to regulator.41
[    9.193989] mmc0: new HS200 MMC card at address 0001
[    9.194779] mmcblk0: mmc0:0001 016G92 14.7 GiB 
[    9.195265] mmcblk0boot0: mmc0:0001 016G92 partition 1 4.00 MiB
[    9.195759] mmcblk0boot1: mmc0:0001 016G92 partition 2 4.00 MiB
[    9.195879] mmcblk0rpmb: mmc0:0001 016G92 partition 3 512 KiB, chardev (244:0)
[    9.197307] exynos-nocp: new NoC Probe device registered: 10ca1000.nocp
[    9.197448] exynos-nocp: new NoC Probe device registered: 10ca1400.nocp
[    9.197570] exynos-nocp: new NoC Probe device registered: 10ca1800.nocp
[    9.197696] exynos-nocp: new NoC Probe device registered: 10ca1c00.nocp
[    9.198542] exynos-adc 12d10000.adc: Linked as a consumer to regulator.4
[    9.201005]  mmcblk0: p1 p2 p3
[    9.205863] NET: Registered protocol family 17
[    9.205884] NET: Registered protocol family 15
[    9.206069] Key type dns_resolver registered
[    9.206558] Registering SWP/SWPB emulation handler
[    9.206954] registered taskstats version 1
[    9.206958] Loading compiled-in X.509 certificates
[    9.221958] mmc_host mmc1: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0)
[    9.222949] mmc1: new ultra high speed SDR104 SDHC card at address 0007
[    9.225343] Key type big_key registered
[    9.227825] mmcblk1: mmc1:0007 SD32G 29.0 GiB 
[    9.228824]  mmcblk1: p1
[    9.235280] Key type encrypted registered
[    9.235301] ima: No TPM chip found, activating TPM-bypass!
[    9.235317] ima: Allocated hash algorithm: sha256
[    9.235335] No architecture policies found
[    9.266836] exynos-hdmi 14530000.hdmi: Linked as a consumer to regulator.6
[    9.267353] exynos-hdmi 14530000.hdmi: Linked as a consumer to regulator.7
[    9.267911] OF: graph: no port node found in /soc/hdmi@14530000
[    9.273239] [drm] Exynos DRM: using 14450000.mixer device for DMA mapping operations
[    9.273297] exynos-drm exynos-drm: bound 14450000.mixer (ops 0xc0a66a1c)
[    9.273312] exynos-drm exynos-drm: bound 14530000.hdmi (ops 0xc0a670c0)
[    9.273401] exynos-drm-g2d 10850000.g2d: The Exynos G2D (ver 4.1) successfully registered.
[    9.273408] exynos-drm exynos-drm: bound 10850000.g2d (ops 0xc0a67fd4)
[    9.273413] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    9.273417] [drm] No driver support for vblank timestamp query.
[    9.273441] [drm] Cannot find any crtc or sizes
[    9.273981] [drm] Initialized exynos 1.1.0 20180330 for exynos-drm on minor 0
[    9.274245] [drm] Cannot find any crtc or sizes
[    9.274681] exynos-dwc3 soc:usb3-0: Linked as a consumer to regulator.9
[    9.275201] exynos-dwc3 soc:usb3-0: Linked as a consumer to regulator.11
[    9.275475] dwc3 12000000.dwc3: Failed to get clk 'ref': -2
[    9.279983] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[    9.279997] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 3
[    9.280213] xhci-hcd xhci-hcd.1.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x0000000002010010
[    9.280244] xhci-hcd xhci-hcd.1.auto: irq 163, io mem 0x12000000
[    9.280562] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.00
[    9.280568] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    9.280573] usb usb3: Product: xHCI Host Controller
[    9.280578] usb usb3: Manufacturer: Linux 5.0.0-rc7-fedoraXU+ xhci-hcd
[    9.280582] usb usb3: SerialNumber: xhci-hcd.1.auto
[    9.280894] hub 3-0:1.0: USB hub found
[    9.280918] hub 3-0:1.0: 1 port detected
[    9.281129] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[    9.281139] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 4
[    9.281148] xhci-hcd xhci-hcd.1.auto: Host supports USB 3.0  SuperSpeed
[    9.281237] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    9.281334] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.00
[    9.281339] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    9.281344] usb usb4: Product: xHCI Host Controller
[    9.281349] usb usb4: Manufacturer: Linux 5.0.0-rc7-fedoraXU+ xhci-hcd
[    9.281353] usb usb4: SerialNumber: xhci-hcd.1.auto
[    9.281660] hub 4-0:1.0: USB hub found
[    9.281683] hub 4-0:1.0: 1 port detected
[    9.282632] exynos-dwc3 soc:usb3-1: Linked as a consumer to regulator.9
[    9.283149] exynos-dwc3 soc:usb3-1: Linked as a consumer to regulator.11
[    9.283402] dwc3 12400000.dwc3: Failed to get clk 'ref': -2
[    9.287704] dwc3 12400000.dwc3: changing max_speed on rev 5533200a
[    9.291438] rtc rtc1: invalid alarm value: 1900-01-23T00:00:00
[    9.291573] s3c-rtc 101e0000.rtc: registered as rtc1
[    9.292856] exynos-bus soc:bus_wcore: Linked as a consumer to regulator.41
[    9.293029] exynos-bus: new bus device registered: soc:bus_wcore ( 84000 KHz ~ 400000 KHz)
[    9.293564] exynos-bus: new bus device registered: soc:bus_noc ( 67000 KHz ~ 100000 KHz)
[    9.293944] exynos-bus: new bus device registered: soc:bus_fsys_apb (100000 KHz ~ 200000 KHz)
[    9.294181] exynos-bus: new bus device registered: soc:bus_fsys (100000 KHz ~ 200000 KHz)
[    9.294612] exynos-bus: new bus device registered: soc:bus_fsys2 ( 75000 KHz ~ 150000 KHz)
[    9.295158] exynos-bus: new bus device registered: soc:bus_mfc ( 96000 KHz ~ 333000 KHz)
[    9.295643] exynos-bus: new bus device registered: soc:bus_gen ( 89000 KHz ~ 267000 KHz)
[    9.295952] exynos-bus: new bus device registered: soc:bus_peri ( 67000 KHz ~  67000 KHz)
[    9.296505] exynos-bus: new bus device registered: soc:bus_g2d ( 84000 KHz ~ 333000 KHz)
[    9.296986] exynos-bus: new bus device registered: soc:bus_g2d_acp ( 67000 KHz ~ 267000 KHz)
[    9.297508] exynos-bus: new bus device registered: soc:bus_jpeg ( 75000 KHz ~ 300000 KHz)
[    9.298000] exynos-bus: new bus device registered: soc:bus_jpeg_apb ( 84000 KHz ~ 167000 KHz)
[    9.298369] exynos-bus: new bus device registered: soc:bus_disp1_fimd (120000 KHz ~ 200000 KHz)
[    9.298799] exynos-bus: new bus device registered: soc:bus_disp1 (120000 KHz ~ 300000 KHz)
[    9.299224] exynos-bus: new bus device registered: soc:bus_gscl_scaler (150000 KHz ~ 300000 KHz)
[    9.299774] exynos-bus: new bus device registered: soc:bus_mscl ( 84000 KHz ~ 400000 KHz)
[    9.303354] s5m-rtc s2mps14-rtc: setting system clock to 2019-02-21T11:38:26 UTC (1550749106)
[    9.341027] ALSA device list:
[    9.341031]   No soundcards found.
[    9.342009] Freeing unused kernel memory: 1024K
[    9.361428] Run /init as init process
[    9.385662] NET: Registered protocol family 10
[    9.403991] Segment Routing with IPv6
[    9.410455] systemd[1]: systemd 239 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
[    9.410818] systemd[1]: Detected architecture arm.
[    9.410828] systemd[1]: Running in initial RAM disk.
[    9.416285] systemd[1]: Set hostname to <odroidxu4>.
[    9.599224] random: systemd: uninitialized urandom read (16 bytes read)
[    9.599535] systemd[1]: Listening on Journal Socket (/dev/log).
[    9.599670] random: systemd: uninitialized urandom read (16 bytes read)
[    9.599696] systemd[1]: Reached target Local File Systems.
[    9.599745] random: systemd: uninitialized urandom read (16 bytes read)
[    9.599906] systemd[1]: Listening on udev Kernel Socket.
[    9.599973] systemd[1]: Reached target Timers.
[    9.600284] systemd[1]: Listening on Journal Socket.
[    9.604283] systemd[1]: Starting Setup Virtual Console...
[    9.655025] audit: type=1130 audit(1550749106.848:2): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    9.742463] audit: type=1130 audit(1550749106.936:3): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-vconsole-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    9.742500] audit: type=1131 audit(1550749106.936:4): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-vconsole-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    9.743090] audit: type=1130 audit(1550749106.936:5): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    9.779001] audit: type=1130 audit(1550749106.972:6): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    9.995773] audit: type=1130 audit(1550749107.188:7): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-cmdline comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   10.089066] audit: type=1130 audit(1550749107.280:8): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=dracut-pre-udev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   10.123291] audit: type=1130 audit(1550749107.316:9): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   10.466907] dma-pl330 3880000.adma: Loaded driver for PL330 DMAC-241330
[   10.466916] dma-pl330 3880000.adma: 	DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6
[   10.467619] samsung-i2s samsung-i2s-sec: DMA channels sourced from device 3830000.i2s
[   10.489284] dma-pl330 3880000.adma: PM domain MAU will not be powered off
[   10.497759] max98090 5-0010: MAX98090 REVID=0x43
[   10.499495] max98090 5-0010: use default 2.8v micbias
[   10.501677] odroid-audio sound: snd-soc-dummy-dai <-> samsung-i2s mapping ok
[   10.502955] odroid-audio sound: multicodec <-> snd-soc-dummy-dai mapping ok
[   10.883842] synth uevent: /devices/platform/soc/101b0000.cec/rc/rc0/input0: failed to send uevent
[   10.883856] input input0: uevent: failed to send synthetic uevent
[   10.892058] input: gpio_keys as /devices/platform/gpio_keys/input/input1
[   10.936859] smsc95xx: unknown parameter 'macaddr' ignored
[   10.937073] smsc95xx v1.0.6
[   10.986561] audit: type=1130 audit(1550749108.180:10): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-udev-trigger comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   11.007893] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-12110000.usb-1.1, smsc95xx USB 2.0 Ethernet, 72:2c:af:3d:f5:60
[   11.008895] usbcore: registered new interface driver smsc95xx
[   13.275090] audit: type=1130 audit(1550749110.468:11): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=plymouth-start comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   13.391727] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
[   14.644083] systemd-journald[213]: Received SIGTERM from PID 1 (systemd).
[   14.717500] printk: systemd: 12 output lines suppressed due to ratelimiting
[   14.917228] kauditd_printk_skb: 30 callbacks suppressed
[   14.917233] audit: type=1404 audit(1550749112.108:42): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 enabled=1 old-enabled=1 lsm=selinux res=1
[   15.352975] SELinux:  Class xdp_socket not defined in policy.
[   15.352981] SELinux: the above unknown classes and permissions will be allowed
[   15.352996] SELinux:  policy capability network_peer_controls=1
[   15.353001] SELinux:  policy capability open_perms=1
[   15.353004] SELinux:  policy capability extended_socket_class=1
[   15.353008] SELinux:  policy capability always_check_network=0
[   15.353012] SELinux:  policy capability cgroup_seclabel=1
[   15.353016] SELinux:  policy capability nnp_nosuid_transition=1
[   15.470908] audit: type=1403 audit(1550749112.664:43): auid=4294967295 ses=4294967295 lsm=selinux res=1
[   15.477539] systemd[1]: Successfully loaded SELinux policy in 560.840ms.
[   15.534801] audit: type=1400 audit(1550749112.728:44): avc:  denied  { create } for  pid=1 comm="systemd" name="pstore" scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:pstore_t:s0 tclass=dir permissive=0
[   15.787218] systemd[1]: Relabelled /dev, /run and /sys/fs/cgroup in 252.031ms.
[   15.793439] systemd[1]: systemd 239 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
[   15.793817] systemd[1]: Detected architecture arm.
[   15.796592] systemd[1]: Set hostname to <odroidxu4>.
[   15.980332] random: crng init done
[   15.980343] random: 7 urandom warning(s) missed due to ratelimiting
[   16.698264] audit: type=1130 audit(1550749113.892:45): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   16.698329] audit: type=1131 audit(1550749113.892:46): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   16.701087] systemd[1]: Stopped Switch Root.
[   16.701666] audit: type=1130 audit(1550749113.896:47): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=initrd-switch-root comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   16.701701] audit: type=1131 audit(1550749113.896:48): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=initrd-switch-root comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   16.702239] systemd[1]: systemd-journald.service: Service has no hold-off time (RestartSec=0), scheduling restart.
[   16.702554] systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1.
[   16.702621] systemd[1]: Stopped Journal Service.
[   16.702674] audit: type=1130 audit(1550749113.896:49): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   16.702713] audit: type=1131 audit(1550749113.896:50): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   16.706444] systemd[1]: Starting Journal Service...
[   16.707967] systemd[1]: Listening on multipathd control socket.
[   16.708032] systemd[1]: Stopped target Switch Root.
[   16.745170] audit: type=1305 audit(1550749113.936:51): audit_enabled=1 old=1 auid=4294967295 ses=4294967295 subj=system_u:system_r:syslogd_t:s0 res=1
[   16.782599] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   16.830182] EXT4-fs (mmcblk0p3): re-mounted. Opts: (null)
[   16.949176] systemd-journald[482]: Received request to flush runtime journal from PID 1
[   17.358774] synth uevent: /devices/platform/soc/101b0000.cec/rc/rc0/input0: failed to send uevent
[   17.358779] input input0: uevent: failed to send synthetic uevent
[   17.782745] gpiomem-exynos 13400000.gpiomem: Initialised: GPIO register area is 2
[   17.785473] gpiomem-exynos 13400000.gpiomem: Initialised: Registers at 0x13400000
[   17.785481] gpiomem-exynos 13400000.gpiomem: Initialised: Registers at 0x14010000
[   18.908641] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[   38.325433] EXT4-fs (mmcblk1p1): recovery complete
[   38.911255] EXT4-fs (mmcblk1p1): mounted filesystem with ordered data mode. Opts: (null)
[   38.952476] kauditd_printk_skb: 14 callbacks suppressed
[   38.952483] audit: type=1130 audit(1550749136.144:66): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=dracut-shutdown comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   38.981432] audit: type=1130 audit(1550749136.176:67): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=plymouth-read-write comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   38.981453] audit: type=1131 audit(1550749136.176:68): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=plymouth-read-write comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   38.987378] audit: type=1130 audit(1550749136.180:69): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=nfs-config comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   38.987428] audit: type=1131 audit(1550749136.180:70): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=nfs-config comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   39.239757] audit: type=1130 audit(1550749136.432:71): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=import-state comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   39.622373] audit: type=1130 audit(1550749136.816:72): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   39.685918] audit: type=1305 audit(1550749136.880:73): audit_enabled=1 old=1 auid=4294967295 ses=4294967295 subj=system_u:system_r:auditd_t:s0 res=1
[   39.685939] audit: type=1305 audit(1550749136.880:74): audit_pid=601 old=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:auditd_t:s0 res=1
[   43.965002] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[   45.555855] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1
[   57.740019] NFSD: starting 90-second grace period (net f0000189)
[  235.431541] Unable to handle kernel NULL pointer dereference at virtual address 000000a4
[  235.438201] pgd = f2a706da
[  235.440869] [000000a4] *pgd=00000000
[  235.444435] Internal error: Oops: 5 [#1] PREEMPT SMP ARM
[  235.449673] Modules linked in: nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 ipt_REJECT nf_reject_ipv4 xt_conntrack ebtable_nat ip6table_nat nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat_ipv4 nf_nat iptable_mangle iptable_raw iptable_security nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables evdev exynos_gpiomem sch_fq_codel nfsd smsc95xx gpio_keys ipv6
[  235.496140] CPU: 4 PID: 1205 Comm: pulseaudio Not tainted 5.0.0-rc7-fedoraXU+ #2
[  235.503484] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[  235.509559] PC is at is_connected_input_ep+0x0/0x94
[  235.514404] LR is at snd_soc_dapm_dai_get_connected_widgets+0x180/0x264
[  235.520987] pc : [<c081569c>]    lr : [<c08183e8>]    psr: 20000013
[  235.527226] sp : e4ffdcc8  ip : ffffffff  fp : ed027440
[  235.532428] r10: c081b248  r9 : e4ffdd40  r8 : ed203680
[  235.537624] r7 : 00000001  r6 : ed0274dc  r5 : c0e08d48  r4 : e4ffdccc
[  235.544125] r3 : ed0275a4  r2 : c081b248  r1 : e4ffdccc  r0 : 00000000
[  235.550624] Flags: nzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none
[  235.557730] Control: 10c5387d  Table: 6441406a  DAC: 00000051
[  235.563449] Process pulseaudio (pid: 1205, stack limit = 0x8aedc5cd)
[  235.569776] Stack: (0xe4ffdcc8 to 0xe4ffe000)
[  235.574110] dcc0:                   a1e5e980 e4ffdccc e4ffdccc 9a210258 006000c0 c205f000
[  235.582257] dce0: c205f000 00000001 ed2b1a00 c0e08d48 00000001 00000001 c205cc7c c081e7ec
[  235.590400] dd00: 0000000e c0807ac8 c205f000 00000001 00000004 c081eda8 00000000 ffffffff
[  235.598548] dd20: c205f000 00000001 0000000b 00000004 00000010 c0e08d48 000f4240 00000011
[  235.606695] dd40: 0000000b 9a210258 e4ffdd70 c0e08d48 00000000 e4ffdd9c c205c800 c0e08d48
[  235.614837] dd60: 00000001 00000001 c205cc7c c0806b30 ed2b1a00 9a210258 e4fdc240 e4fdc240
[  235.622984] dd80: c205c800 c205cc68 ffffe000 c0806cd0 eea2af80 c097a6e0 e4fdc248 edca83b8
[  235.631127] dda0: 00000000 e4fa9440 c0151ae4 c205cc80 c205cc80 9a210258 ee829800 00000000
[  235.639274] ddc0: c205c800 e4fdc240 c2535fb0 e4fdc240 00000000 00000006 e4fdc240 c0806e54
[  235.647419] dde0: c0aa9d08 c0e08d48 eea2af80 c02ba410 00000018 9a210258 e4fdc240 e4fdc240
[  235.655564] de00: c2535fb0 00000802 00000000 e4fdc248 c02ba364 c02b1d8c e4ffdec0 00000000
[  235.663711] de20: 00000802 e4ffdf70 00000000 00000000 00000006 c02c49e0 c0ef9cc4 00000904
[  235.671856] de40: e4ffdf44 00000000 00000002 c0e08d48 00000041 ffffe000 00000406 0007ffff
[  235.680001] de60: e4ffdec8 fffdffef 00000001 00000000 c0b79664 c0e08d48 00000002 c2535fb0
[  235.688146] de80: eea8ac10 edcadc38 c0e8a3f0 c07f9be8 e4fe5bc0 9a210258 e4fdc0c0 c0e08d48
[  235.696294] dea0: c0e08d48 e4ffdf70 00000001 fffff000 e4ffc000 00000142 0057e148 c02c7004
[  235.704437] dec0: eea8ac10 edcadc38 d8f22008 00000008 c2409019 00001000 00000000 ec98eb28
[  235.712582] dee0: c2535fb0 00000101 00000002 000012ba 00000000 00000000 00000000 e4ffdf00
[  235.720728] df00: 0057e148 c02c9ae8 bea7893c ffffe000 005876c4 00000142 00000ff0 9a210258
[  235.728874] df20: 00000011 e4fa4200 e4fa4218 00000000 c2409000 00000000 00080802 00000002
[  235.737019] df40: ffffff9c 00080802 c0e08d48 9a210258 c2409000 00000011 c0e08d48 ffffff9c
[  235.745166] df60: c2409000 c02b343c e4fdc180 00000000 00000802 bea70000 00000006 00000100
[  235.753310] df80: 00000001 9a210258 00080802 b6fd18f8 00000004 00000142 c0101204 e4ffc000
[  235.761459] dfa0: 00000142 c0101000 00080802 b6fd18f8 ffffff9c bea7893c 00080802 00000000
[  235.769600] dfc0: 00080802 b6fd18f8 00000004 00000142 b1bf640c bea7893c 81204101 0057e148
[  235.777747] dfe0: b687d000 bea787d0 b1b6e64c b67f9f44 60000010 ffffff9c 00000000 00000000
[  235.785899] [<c081569c>] (is_connected_input_ep) from [<9a210258>] (0x9a210258)
[  235.793172] Code: e58500a4 e1a00008 e28dd014 e8bd8ff0 (e59030a4) 
[  235.799402] ---[ end trace 15c0dc80b9edaa8a ]---
I think it's caused by pulseaudio trying to do something with the audio driver..

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 57 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Thu Feb 21, 2019 9:13 pm

@MastaG thanks for testing
i will try to clean up the patches. There are some suspend patches I did not add, and suspend also has issues on xu4 with USB :(
can you test if sound actually works? can you test both HDMI and max audio codec?
I might leave the max audio codec drivers for now, add them later (5.2-ish) when they are more polished .... they are mostly for xu3 anyway (or xu4 over i2s) but i think we can wait a bit for them to get fixed :)

MastaG
Posts: 310
Joined: Mon Aug 26, 2013 6:05 pm
languages_spoken: english
Has thanked: 18 times
Been thanked: 4 times
Contact:

Re: Kernel 5.0 development thread

Unread post by MastaG » Fri Feb 22, 2019 6:29 pm

You're welcome memeka.
I couldn't test hdmi-audio, because I have to bring the odroid into the living room for that and we're currently redacorating the house.
But I've set vout to hdmi instead of dvi in boot.ini.
But no audio hardware is showing up in gnome.
Running kodi takes like 30 seconds before it starts and then shows no audio devices.
Running alsamixer does nothing and simply stalls.
So audio is kinda regressed I guess.

MastaG
Posts: 310
Joined: Mon Aug 26, 2013 6:05 pm
languages_spoken: english
Has thanked: 18 times
Been thanked: 4 times
Contact:

Re: Kernel 5.0 development thread

Unread post by MastaG » Mon Feb 25, 2019 12:33 am

However, everything was working fine in RC5, including the headphone jack.
So if you can manage to fix the regression and we could keep it working, that'll be great :)

Lets jack!
https://youtu.be/m0EiujcV3Tg

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 57 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Mon Feb 25, 2019 2:20 am

@MastaG how is FF working under wayland in fedora?
Any egl acceleration? Is webgl working? How is it playing YouTube 1080p?

MastaG
Posts: 310
Joined: Mon Aug 26, 2013 6:05 pm
languages_spoken: english
Has thanked: 18 times
Been thanked: 4 times
Contact:

Re: Kernel 5.0 development thread

Unread post by MastaG » Mon Feb 25, 2019 5:34 pm

@memeka,

I'll have a more in depth look at firefox once I've sorted out the issue where my eMMC's boot partition seems to go corrupt everytime I shut down.
I have to restore everything from byte 0 to the end of the fat32 boot partition in order to get it to boot again.. probably some hidden part gets corrupted or something.
But I'm receiving my uart cable this week, then I'll know more. (perhaps my eMMC has had it's best days or something)

But I've just installed Fedora's default firefox-wayland package.
It's pretty heavy on top of gnome (even for a XU4) but once it has started scrolling on pages is pretty smooth.
I've yet to try WebGL, but I don't know whether firefox supports OpenGL ES for acceleration.
And even if it does, then it's probably not enabled.. because the fedora package maintainers don't pass any GLES configure options in their spec files.
For this reason I had to re-build mutter using the modified spec file to enable these bits.
Regarding html5 video accelerated video decoding, I don't think firefox supports it at all.. https://bugzilla.mozilla.org/show_bug.c ... &id=563206
So the bigger you make the player window.. the worse it gets.. so viewing videos in windowed mode plays back OK.. but fullscreen will get choppy.

That's why soon I'll take another shot at cross-compiling ozone-wayland's branch of Chromium against my fedora 29 sysroot.
However unlike Ubuntu.. this is very unsupported and requires many hacks/buildfixes.
Perhaps you can take a look at my build flags and compare them to yours if you still happen to have them:

Code: Select all

#!/bin/bash
export BUILD_CC=clang
export BUILD_CXX=clang++
export BUILD_AR=llvm-ar
export BUILD_NM=llvm-nm

export CC=clang
export CXX=clang++
export CFLAGS="-mcpu=cortex-a15"
export CXXFLAGS="-mcpu=cortex-a15"
export AR=llvm-ar
export NM=llvm-nm
export GYP_CROSS_COMPILE=1
export LDFLAGS="-mcpu=cortex-a15"

GOOGLE_API_KEY="xxx"
GOOGLE_DEFAULT_CLIENT_ID="xxx"
GOOGLE_DEFAULT_CLIENT_SECRET="xxx"

arg="custom_toolchain=\"//build/toolchain/linux/unbundle:default\" \
host_toolchain=\"//build/toolchain/linux/unbundle:host\" \
v8_snapshot_toolchain=\"//build/toolchain/linux/unbundle:host\" \
target_sysroot=\"/media/data2/f29root\"
use_sysroot=true
is_official_build=true \
fieldtrial_testing_like_official_build=true \
google_api_key=\"${GOOGLE_API_KEY}\" \
google_default_client_id=\"${GOOGLE_DEFAULT_CLIENT_ID}\" \
google_default_client_secret=\"${GOOGLE_DEFAULT_CLIENT_SECRET}\" \
proprietary_codecs=true \
ffmpeg_branding=\"Chrome\" \
host_cpu=\"x64\" \
current_os=\"linux\" \
target_os=\"linux\" \
target_cpu=\"arm\" \
current_cpu=\"arm\" \
arm_arch=\"armv7ve\" \
arm_float_abi=\"hard\" \
arm_fpu=\"neon-vfpv4\" \
arm_tune=\"cortex-a15\" \
arm_version=7 \
arm_use_neon=true \
arm_use_thumb=false \
is_debug=false \
symbol_level=0 \
remove_webcore_debug_symbols=true \
is_clang=true \
clang_use_chrome_plugins=false \
linux_use_bundled_binutils=false \
treat_warnings_as_errors=false \
fatal_linker_warnings=false \
use_lld=true \
use_gold=false \
use_custom_libcxx=false \
use_allocator=\"tcmalloc\" \
enable_nacl=false \
use_jumbo_build=true \
enable_hangout_services_extension=true \
use_cups=true \
use_gnome_keyring=true \
use_kerberos=true \
use_pulseaudio=true \
use_system_freetype=true \
use_system_libjpeg=true \
is_component_build=false \
use_ozone=true \
ozone_auto_platforms=false \
ozone_platform_headless=true \
ozone_platform_wayland=true \
ozone_platform_x11=true \
ozone_platform_gbm=false \
use_xkbcommon=true \
use_system_libwayland=true \
use_system_minigbm=true \
use_wayland_gbm=true \
use_v4l2_codec=true \
use_v4lplugin=true \
use_linux_v4l2_only=true \
is_cfi=false \
enable_linux_installer=false"

gn_system_libraries="flac \
freetype \
libjpeg \
libwebp \
libxml \
libxslt \
yasm"

./build/linux/unbundle/replace_gn_files.py --system-libraries ${gn_system_libraries}

gn gen --args="${arg}" out/Release

Bernini
Posts: 9
Joined: Sun Nov 26, 2017 3:56 am
languages_spoken: english, french, italian
ODROIDs: Odroid XU4
Has thanked: 2 times
Been thanked: 0
Contact:

Re: Kernel 5.0 development thread

Unread post by Bernini » Wed Feb 27, 2019 2:56 am

@memeka I didn't see you were prepping 5.0 until today, thanks for the hard work.

Question: the explanations linked suggest building on the Odroid itself, and talk about using GCC 5 - are there any cross-compilation toolchains I can download and use to compile on my regular x86_64 system?

Thanks.

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 57 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Wed Feb 27, 2019 5:04 am

No ideas what would work for crosscompile
I’m using default gcc on Ubuntu 18.04 - gcc7 I think

elatllat
Posts: 1687
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 31 times
Been thanked: 96 times
Contact:

Re: Kernel 5.0 development thread

Unread post by elatllat » Wed Feb 27, 2019 7:15 am

Code: Select all

gcc --version | grep gcc
gcc (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 57 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Wed Feb 27, 2019 9:50 am

UPDATE

* updated to v5.0-rc8
* removed secondary CPU DAI patches (better wait for 5.2 kernel when all will be added with correct dependencies)
* to test: USB issues with suspend?
Last edited by memeka on Wed Feb 27, 2019 9:59 am, edited 1 time in total.

User avatar
odroid
Site Admin
Posts: 33615
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 491 times
Been thanked: 500 times
Contact:

Re: Kernel 5.0 development thread

Unread post by odroid » Wed Feb 27, 2019 9:56 am

Great!
So official Linux 5.0 must be out next Sunday, 3 March, if everything goes well. :o
I bet the next LTS Kernel will be 5.4 in October or November. ;)

MastaG
Posts: 310
Joined: Mon Aug 26, 2013 6:05 pm
languages_spoken: english
Has thanked: 18 times
Been thanked: 4 times
Contact:

Re: Kernel 5.0 development thread

Unread post by MastaG » Thu Feb 28, 2019 4:06 pm

memeka wrote:
Wed Feb 27, 2019 9:50 am
UPDATE

* updated to v5.0-rc8
* removed secondary CPU DAI patches (better wait for 5.2 kernel when all will be added with correct dependencies)
* to test: USB issues with suspend?
Thanks for the update memeka!

The headphone jack audio works again on my XU3, no more kernel panics

Furthermore I took a quick glance at Firefox and it seems hardware accelerated compositing is disabled by default for the arm 32bit platform.
I tried to force-enable it by setting: layers.acceleration.force-enabled to true in about:config.
Then when I restart firefox it tells me that it loads libEGL.so (from the arm mali r12p004 package) and then it presents me with a blank window, all grey...
It's definitely the mali driver, because when I use the mesa drivers, it'll render correctly but will obviously fall back to the vmware softpipe driver.

Even without hardware accelerated compositing it can still use mali's GLES driver for WebGL, but only WebGL1.
The mali driver misses one or two extensions for firefox to support WebGL2.
I've tried some WebGL demo's and they work fine though.

That's one of the reasons why I hope panfrost will properly support our T628 sooner than later.


I'd like to know how to test suspend/resume.
In gnome there's a big "pause"-like button on the lock screen which normally put's your computer into sleep-mode.
I tried that, but it looks like the odroid shuts itself down as only the red led remains on.
But I cannot wake it up, by using my usb mouse/keyboard nor the power-button.
Perhaps the pause-button in gnome is not the correct way for testing this though:P

Overall it performs really great and seems to be a little better in terms of graphics performance compared to 4.14 when running Gnome on Wayland and Kodi on both DRM and Wayland.
So I'm very happy!

I'll take another shot at building Chromium ozone-wayland soon and once the official 5.0 kernel is out, I'll do a public Fedora 29 image with gnome on wayland, kodi, retroarch, selinux-support and hopefully chromium :)

User avatar
emk2203
Posts: 47
Joined: Fri Oct 16, 2015 12:29 am
languages_spoken: english, german
ODROIDs: C1+, C2, XU4, HC1, HC2, N2
Has thanked: 7 times
Been thanked: 0
Contact:

Re: Kernel 5.0 development thread

Unread post by emk2203 » Thu Feb 28, 2019 8:22 pm

5.0-rc8 looks fine here.

Question: Is there a place for the patches for the cloudshell drivers, or do I have to sift through the source tree? I really would like to get the cloudshell to work, but cannot find what was patched for a particular purpose right away.

I am thinking about something like Ubuntu has with their mainline kernels, where the applied patches are in the mainline kernel directories.

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 57 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Thu Feb 28, 2019 8:26 pm

@emk2203
you would need to sift through the 4.14 HK kernel, see which are appropriate, and update them for 5.0 -> some of them need to be updated, some of them may not be needed, some of them would need more work :)
this is basically what i've done with the other patches in my tree :) just look on HK tree, pick and fix :)

dante6913
Posts: 96
Joined: Sat Oct 01, 2016 7:16 am
languages_spoken: english, Portuguese
ODROIDs: C2
Has thanked: 0
Been thanked: 0
Contact:

Re: Kernel 5.0 development thread

Unread post by dante6913 » Sun Mar 03, 2019 3:46 am

Hi, I'm not being able tu use an emmc card with kernel 5.0 rc8. Building it from a stock 18.04 in ubuntu in the emmc card or copying from the image of a full working sd card with kernel 5.0 allway hang on boot with this error:

mmc0: tunning execution failed: -5.

Kernel 5.0 isn't functional with emmc card?
With emmc card works fine,

elatllat
Posts: 1687
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 31 times
Been thanked: 96 times
Contact:

Re: Kernel 5.0 development thread

Unread post by elatllat » Tue Mar 05, 2019 12:24 pm

I wonder if the "Adiantum encryption system" can now benefit the XU4

Code: Select all

uname -r
needs to be v5.0+

Code: Select all

cryptsetup --version
needs to be v2.0.6+

[EDIT]

Code: Select all

cd /opt/
wget https://www.kernel.org/pub/linux/utils/cryptsetup/v2.1/cryptsetup-2.1.0.tar.xz
tar -xf cryptsetup-2.1.0.tar.xz       
cd cryptsetup-2.1.0
apt install uuid-dev libdevmapper-dev libpopt-dev libjson-c-dev libblkid-dev
./configure        
make
then

Code: Select all

./cryptsetup benchmark --cipher xchacha12,aes-adiantum-plain64 --key-size 256
./cryptsetup benchmark --cipher aes-xts --key-size 256
On the N2 adiantum is an order of magnitude slower than xts (84 vs 427 MiB/s).
the XU4 is 92.4 so likely not helpful there (untested) but I guess for rpi0w like things that are about 10 MiB/s it might help.
Last edited by elatllat on Sun Mar 24, 2019 9:29 pm, edited 5 times in total.

User avatar
odroid
Site Admin
Posts: 33615
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 491 times
Been thanked: 500 times
Contact:

Re: Kernel 5.0 development thread

Unread post by odroid » Wed Mar 06, 2019 10:10 am

@memeka,
Do you have a plan to release 5.0 official instead of the RC?

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 57 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Wed Mar 06, 2019 11:17 am

@odroid
Yes, I am still trying to get sleep function to work before that...
I think I might give up on sleep for now, and maybe try again at next LTS. Seems like 5.0 is not LTS release. I will try few more things...

jeanmarc
Posts: 11
Joined: Tue Mar 05, 2019 9:02 pm
languages_spoken: english
ODROIDs: 2 Odroid HC1 boards with 250 GB SSD disk with standard kernel.org kernel Odroid N2 board
Location: near Paris
Has thanked: 0
Been thanked: 0
Contact:

Re: Kernel 5.0 development thread

Unread post by jeanmarc » Fri Mar 08, 2019 12:49 am

I created a kernel.org 5.0 kernel for the Odroid HC1 card with 250 GB SSD. Please look on the following link to see the startup ... and some remaining problems

https://forum.odroid.com/viewtopic.php ... 5#p248515

Thanks
- Jean Marc :) -

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 57 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Fri Mar 08, 2019 2:35 am

Please use the kernel tree specified in OP, it has additional fixes on top of mainline.

dpetrini
Posts: 1
Joined: Fri Mar 08, 2019 4:39 am
languages_spoken: english
ODROIDs: XU4
Has thanked: 0
Been thanked: 0
Contact:

Re: Kernel 5.0 development thread

Unread post by dpetrini » Fri Mar 08, 2019 5:02 am

Hi,

Are these last patches for mainline 5.0 already supporting Energy Aware Scheduling in Odroid-XU4-Exynos?

BR

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 57 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Fri Mar 08, 2019 8:46 am

dpetrini wrote:
Fri Mar 08, 2019 5:02 am
Are these last patches for mainline 5.0 already supporting Energy Aware Scheduling in Odroid-XU4-Exynos?
I did not test energy aware scheduling, I don't know if there is an energy model for Exynos 5422 in mainline.
But these patches do modify the scheduler to add HMP scheduling (allow all 8 cores to run at the same time) - without HMP, only 4 cores can run.
If you want to test EAS, you need to modify the kernel config, disabled HPERF_HMP and enable ENERGY_MODEL.

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 57 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Fri Mar 08, 2019 8:56 am

Linux odroid 5.0.0 #11 SMP PREEMPT Fri Mar 8 09:34:16 ACDT 2019 armv7l armv7l armv7l GNU/Linux

I have pushed 5.0.0 kernel in my repository.
Here's a sample config: http://paste.ubuntu.com/p/4pw5sGJGPj/

This config enables KVM by default (there is no need for separate dtb now).

Code: Select all

[    0.000000] Booting Linux on physical CPU 0x100
[    0.000000] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), cr=30c5387d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Samsung CPU ID: 0xe5422001
[    0.000000] percpu: Embedded 17 pages/cpu @(ptrval) s39244 r8192 d22196 u69632
[    0.003051] CPU: Testing write buffer coherency: ok
[    0.003557] CPU0: thread -1, cpu 0, socket 1, mpidr 80000100
[    0.024698] Exynos MCPM support installed
[    0.048049] smp: Bringing up secondary CPUs ...
[    0.080411] CPU1: thread -1, cpu 1, socket 1, mpidr 80000101
[    0.104382] CPU2: thread -1, cpu 2, socket 1, mpidr 80000102
[    0.136374] CPU3: thread -1, cpu 3, socket 1, mpidr 80000103
[    0.168395] CPU4: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.168404] CPU4: Spectre v2: using ICIALLU workaround
[    0.192376] CPU5: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.192384] CPU5: Spectre v2: using ICIALLU workaround
[    0.204575] CPU6: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.204582] CPU6: Spectre v2: using ICIALLU workaround
[    0.216588] CPU7: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.216595] CPU7: Spectre v2: using ICIALLU workaround
[    0.216850] smp: Brought up 1 node, 8 CPUs
[    0.216921] CPU: All CPU(s) started in HYP mode.
[    0.216940] CPU: Virtualization extensions available.
[    1.520316] kvm [1]: 8-bit VMID
[    1.521306] kvm [1]: vgic interrupt IRQ16
[    1.521685] kvm [1]: Hyp mode initialized successfully
But I did not test if kvm actually works in userspace.

elatllat
Posts: 1687
Joined: Tue Sep 01, 2015 8:54 am
languages_spoken: english
ODROIDs: XU4, N1, N2
Has thanked: 31 times
Been thanked: 96 times
Contact:

Re: Kernel 5.0 development thread

Unread post by elatllat » Fri Mar 08, 2019 9:02 am

My understanding was that "EAS" is the upstream version of "HMP", so EAS should be favored if possible eg.

User avatar
memeka
Posts: 4420
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 2 times
Been thanked: 57 times
Contact:

Re: Kernel 5.0 development thread

Unread post by memeka » Fri Mar 08, 2019 9:44 am

elatllat wrote:
Fri Mar 08, 2019 9:02 am
My understanding was that "EAS" is the upstream version of "HMP", so EAS should be favored if possible eg.
From the cpufreq driver:

Code: Select all

#ifndef CONFIG_BL_SWITCHER
        { .compatible = "samsung,exynos5800", },
#endif
So I think the 5422 (which uses exynos5800 cpufreq driver) won't work with all 8 CPUs with EAS.
Also, for EAS, I guess you need to add the power consumption details in the DT at the very least (or add the exynos energy model to the kernel yourself).

User avatar
odroid
Site Admin
Posts: 33615
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English, Korean, Japanese
ODROIDs: ODROID
Has thanked: 491 times
Been thanked: 500 times
Contact:

Re: Kernel 5.0 development thread

Unread post by odroid » Fri Mar 08, 2019 11:17 am

I've compiled 5.0 Kernel and it booted nicely with Ubuntu 18.04 image. :D

Code: Select all

odroid@odroid:~$ uname -a
Linux odroid 5.0.0+ #1 SMP PREEMPT Fri Mar 8 01:24:36 UTC 2019 armv7l armv7l armv7l GNU/Linux
HDMI sound works find with Kodi 17.6 and ffplay.

I met some weird things.
Chromium Youtube video sound played too much faster. I felt x2 or more.
Firefox couldn't play any video. I found this message.

Code: Select all

[  934.852246] vidioc_try_fmt:407: Unsupported format for destination.
I will test more this weekend.

Post Reply

Return to “Ubuntu”

Who is online

Users browsing this forum: No registered users and 8 guests