Playing with upstream (Exynos4412)

Share here your ideas for new projects
Post Reply
gulp
Posts: 18
Joined: Mon Apr 14, 2014 4:58 am
languages_spoken: Italian,english
ODROIDs: Odroid U3
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by gulp » Sun Jun 28, 2015 1:58 am

mikewhatever wrote:Hi, ...so what do you use to compile 4.0.5? I've tried following the wiki steps, and got the following:

Code: Select all

 CC      kernel/bounds.s
  GEN     include/generated/bounds.h
  CC      arch/arm/kernel/asm-offsets.s
arch/arm/kernel/asm-offsets.c:53:2: error: #error Your compiler is too buggy; it is known to miscompile kernels
 #error Your compiler is too buggy; it is known to miscompile kernels
  ^
arch/arm/kernel/asm-offsets.c:54:2: error: #error and result in filesystem corruption and oopses.
 #error and result in filesystem corruption and oopses.
  ^
make[1]: *** [arch/arm/kernel/asm-offsets.s] Error 1
make: *** [prepare0] Error 2
make: *** Waiting for unfinished jobs....
I have a U3 with Ubuntu server, gcc is version 4.8.2 (Ubuntu/Linaro 4.8.2-19ubuntu1). I've searched this forum, as well as online for that error, but found nothing related to odroid.
I've resolved installing gcc/g++ 5.x from compiler testing ppa

User avatar
Panzerknacker
Posts: 247
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Sun Jun 28, 2015 2:59 am

You can use 4.7 or 4.9.
http://choorucode.com/2015/02/26/how-to ... ernatives/
or google: gcc alternative ubuntu

pcangelo
Posts: 11
Joined: Tue Jul 23, 2013 8:35 am
languages_spoken: english
ODROIDs: U2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by pcangelo » Sun Jun 28, 2015 4:02 am

Hi,
I try to use the 4.0.5 kernel on my X2 board but without success.
I try to boot with the latest uboot ( I tried all and the result is the same) from eMMC 64Gb a fedora 22 linux. In the last uboot I tried also to change the MSPLL speed to 880 but nothing change either.
I compiled the kernel with default config from exynos4412 page with gcc 5.1 from fedora arm and also with a gcc 4.6... from a custom kali linux from sdcard and the result is the same.
Sometimes it boot completely but in several seconds the board freeze and i need to reboot (reset button)
Most of time i suspect a initialization issue because last lines are most often:

Code: Select all

[    1.753287] max98090 1-0010: MAX98090 REVID=0x43
[    1.767973] asoc-simple-card sound: HiFi <-> 3830000.i2s mapping ok
[    1.768038] mmc_host mmc1: Bus speed (slot 0) = 44000000Hz (slot req 52000000Hz, actual 44000000HZ div = 0)
[    1.783920] mmc_host mmc1: Bus speed (slot 0) = 73333333Hz (slot req 52000000Hz, actual 36666666HZ div = 1)
[    1.784331] input: gpio_keys as /devices/platform/gpio_keys/input/input0
[    1.784639] gps-alive-power-domain: Power-off latency exceeded, new value 232041 ns
[    1.784690] gps-power-domain: Power-off latency exceeded, new value 228167 ns
[    1.784884] g3d-power-domain: Power-off latency exceeded, new value 230625 ns
[    1.784926] vdd_g3d: disabling
[    1.786115] unused_2.8V: disabling
[    1.787304] vdd_hdmi_1.0V: disabling
[  [    1.836882] Waiting for root device /dev/mmcblk0p3...
[    1.837277] mmc1: new DDR MMC card at address 0001
[    1.841357] mmcblk0: mmc1:0001 064G93 58.2 GiB
[    1.845654] mmcblk0boot0: mmc1:0001 064G93 partition 1 4.00 MiB
[    1.851545] mmcblk0boot1: mmc1:0001 064G93 partition 2 4.00 MiB
[    1.857438] mmcblk0rpmb: mmc1:0001 064G93 partition 3 512 KiB
[    1.863906]  mmcblk0: p1 p2 p3
[    1.923227] usb 1-2.1: new high-speed USB device number 3 using exynos-ehci
Once the kernel compiled with the older gcc (4.6) given me extra info:

Code: Select all

[    1.908230] usb 1-2.1: new high-speed USB device number 3 using exynos-ehci
[   53.979127] INFO: rcu_preempt detected stalls on CPUs/tasks: { 0} (detected                                                                                                                                              by 3, t=12002 jiffies, g=-207, c=-208, q=2)
[   53.984257] Task dump for CPU 0:
[   53.987465] swapper/0       R running      0     0      0 0x00000002
[   53.993796] Backtrace:
[   53.996230] [<c065e4c0>] (0xc065e4c0) from [<c065e518>] (0xc065e518)
[   54.002555] Backtrace aborted due to bad frame pointer <c00589f0>
[   55.047152] INFO: rcu_preempt detected stalls on CPUs/tasks: { 0} (detected                                                                                                                                              by 3, t=48007 jiffies, g=-207, c=-208, q=2)
[   55.052271] Task dump for CPU 0:
[   55.055480] swapper/0       R running      0     0      0 0x00000002
[   55.061810] Backtrace:
[   55.064242] [<c065e4c0>] (0xc065e4c0) from [<c065e518>] (0xc065e518)
[   55.070570] Backtrace aborted due to bad frame pointer <c00589f0>
I suspect that could be related to other usb issues but maybe I am wrong. usually when I boot there is no device connected to the X2. I have only a hardkernel camera that is plugged in (never recognized) but even if i detach it the result is the same.
Would you know what could I do to have a proper kernel that boots completely ?

thanx a lot!

pcangelo
Posts: 11
Joined: Tue Jul 23, 2013 8:35 am
languages_spoken: english
ODROIDs: U2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by pcangelo » Sun Jun 28, 2015 4:05 am

Here is a complete boot sequence log:

Code: Select all

U-Boot 2015.07-rc2-00133-g325849f-dirty (Jun 25 2015 - 19:59:20 -0400)

CPU:    Exynos4412@1000MHz
Model: Odroid based on Exynos4412
DRAM:  2 GiB
ldo20@VDDQ_EMMC_1.8V: set 1800000 uV; enabling
ldo22@VDDQ_EMMC_2.8V: set 2800000 uV; enabling
ldo21@TFLASH_2.8V: set 2800000 uV; enabling
MMC:   EXYNOS DWMMC: 0, SAMSUNG SDHCI: 1
Net:   No ethernet found.
Hit any key to stop autoboot:  0
1077 bytes read in 6 ms (174.8 KiB/s)
## Executing script at 40408000
2375632 bytes read in 248 ms (9.1 MiB/s)
54906 bytes read in 22 ms (2.4 MiB/s)
Kernel image @ 0x40008000 [ 0x000000 - 0x243fd0 ]
## Flattened Device Tree blob at 41f00000
   Booting using the fdt blob at 0x41f00000
   reserving fdt memory region: addr=41f00000 size=e000
   Using Device Tree in place at 41f00000, end 41f10fff

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0xa00
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.0.5 (root@armtest) (gcc version 4.6.3 (Debian 4.6.3-14) ) #4 SMP PREEMPT Sat Jun 27 20:25:19 UTC 2015
[    0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Hardkernel ODROID-X2 board based on Exynos4412
[    0.000000] Reserved memory: created CMA memory pool at 0x77000000, size 16 MiB
[    0.000000] Reserved memory: initialized node region@77000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created CMA memory pool at 0x78000000, size 16 MiB
[    0.000000] Reserved memory: initialized node region@78000000, compatible id shared-dma-pool
[    0.000000] cma: Reserved 128 MiB at 0xb7c00000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] Samsung CPU ID: 0xe4412220
[    0.000000] Running under secure firmware.
[    0.000000] PERCPU: Embedded 11 pages/cpu @ee795000 s12544 r8192 d24320 u45056
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 522512
[    0.000000] Kernel command line: video=HDMI-A-1:1920x1080M@60 console=ttySAC1,115200n8 root=/dev/mmcblk0p3 rootfstype=ext4 rootwait ro
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    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: 1907756K/2096128K available (4827K kernel code, 157K rwdata, 1440K rodata, 212K init, 231K bss, 24532K reserved, 163840K cma-reserved, 1154048K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc0626fe4   (6268 kB)
[    0.000000]       .init : 0xc0627000 - 0xc065c000   ( 212 kB)
[    0.000000]       .data : 0xc065c000 - 0xc06834c0   ( 158 kB)
[    0.000000]        .bss : 0xc06834c0 - 0xc06bd374   ( 232 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] L2C: platform modifies aux control register: 0x02070000 -> 0x3e470001
[    0.000000] L2C: platform provided aux values permit register corruption.
[    0.000000] L2C: DT/platform modifies aux control register: 0x02070000 -> 0x3e470001
[    0.000000] L2C-310 enabling early BRESP for Cortex-A9
[    0.000000] L2C-310: enabling full line of zeros but not enabled in Cortex-A9
[    0.000000] L2C-310 ID prefetch enabled, offset 8 lines
[    0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[    0.000000] L2C-310 cache controller enabled, 16 ways, 1024 kB
[    0.000000] L2C-310: CACHE_ID 0x4100c4c8, AUX_CTRL 0x7e470001
[    0.000000] Exynos4x12 clocks: sclk_apll = 1000000000, sclk_mpll = 880000000
[    0.000000]  sclk_epll = 96000000, sclk_vpll = 350000000, arm_clk = 1000000000
[    0.000000] Switching to timer-based delay loop, resolution 41ns
[    0.000004] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956969942ns
[    0.000182] Console: colour dummy device 80x30
[    0.000201] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=120000)
[    0.000211] pid_max: default: 32768 minimum: 301
[    0.000285] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000294] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000700] Initializing cgroup subsys devices
[    0.000728] CPU: Testing write buffer coherency: ok
[    0.000981] CPU0: thread -1, cpu 0, socket 10, mpidr 80000a00
[    0.001349] Setting up static identity map for 0x404bc748 - 0x404bc7a0
[    0.030460] CPU1: thread -1, cpu 1, socket 10, mpidr 80000a01
[    0.040431] CPU2: thread -1, cpu 2, socket 10, mpidr 80000a02
[    0.050439] CPU3: thread -1, cpu 3, socket 10, mpidr 80000a03
[    0.050486] Brought up 4 CPUs
[    0.050503] SMP: Total of 4 processors activated (192.00 BogoMIPS).
[    0.050509] CPU: All CPU(s) started in SVC mode.
[    0.050917] devtmpfs: initialized
[    0.051639] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.057015] pinctrl core: initialized pinctrl subsystem
[    0.068581] NET: Registered protocol family 16
[    0.070218] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.085472] cpuidle: using governor ladder
[    0.100468] cpuidle: using governor menu
[    0.105689] exynos-audss-clk 3810000.clock-controller: setup completed
[    0.121142] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.121153] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.121598] lcd0-power-domain has as child subdomain: tv-power-domain.
[    0.128661] SCSI subsystem initialized
[    0.128784] usbcore: registered new interface driver usbfs
[    0.128838] usbcore: registered new interface driver hub
[    0.128920] usbcore: registered new device driver usb
[    0.129368] s3c-i2c 13860000.i2c: slave address 0x10
[    0.129381] s3c-i2c 13860000.i2c: bus frequency set to 214 KHz
[    0.165879] s3c-i2c 13860000.i2c: i2c-0: S3C I2C adapter
[    0.166077] s3c-i2c 13870000.i2c: slave address 0x10
[    0.166090] s3c-i2c 13870000.i2c: bus frequency set to 214 KHz
[    0.166326] s3c-i2c 13870000.i2c: i2c-1: S3C I2C adapter
[    0.166445] s3c-i2c 13880000.i2c: slave address 0x00
[    0.166456] s3c-i2c 13880000.i2c: bus frequency set to 71 KHz
[    0.166588] s3c-i2c 13880000.i2c: i2c-2: S3C I2C adapter
[    0.166673] s3c-i2c 138e0000.i2c: slave address 0x00
[    0.166684] s3c-i2c 138e0000.i2c: bus frequency set to 71 KHz
[    0.166896] s3c-i2c 138e0000.i2c: i2c-8: S3C I2C adapter
[    0.167069] Linux video capture interface: v2.00
[    0.167502] Advanced Linux Sound Architecture Driver Initialized.
[    0.168062] Switched to clocksource mct-frc
[    0.176701] NET: Registered protocol family 2
[    0.177239] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.177304] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.177418] TCP: Hash tables configured (established 8192 bind 8192)
[    0.177467] TCP: reno registered
[    0.177479] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.177506] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.177648] NET: Registered protocol family 1
[    0.178024] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[    0.179521] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.179641] audit: initializing netlink subsys (disabled)
[    0.179680] audit: type=2000 audit(0.175:1): initialized
[    0.186376] bounce: pool size: 64 pages
[    0.186526] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    0.186543] io scheduler noop registered
[    0.186553] io scheduler deadline registered
[    0.186581] io scheduler cfq registered (default)
[    0.190593] dma-pl330 12680000.pdma: Loaded driver for PL330 DMAC-141330
[    0.190607] dma-pl330 12680000.pdma:         DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    0.193047] dma-pl330 12690000.pdma: Loaded driver for PL330 DMAC-141330
[    0.193087] dma-pl330 12690000.pdma:         DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    0.193920] dma-pl330 12850000.mdma: Loaded driver for PL330 DMAC-141330
[    0.193932] dma-pl330 12850000.mdma:         DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32
[    0.194558] 13800000.serial: ttySAC0 at MMIO 0x13800000 (irq = 70, base_baud = 0) is a S3C6400/10
[    0.194882] 13810000.serial: ttySAC1 at MMIO 0x13810000 (irq = 71, base_baud = 0) is a S3C6400/10
[    0.909861] console [ttySAC1] enabled
[    0.913842] 13820000.serial: ttySAC2 at MMIO 0x13820000 (irq = 72, base_baud = 0) is a S3C6400/10
[    0.922652] 13830000.serial: ttySAC3 at MMIO 0x13830000 (irq = 73, base_baud = 0) is a S3C6400/10
[    0.931872] [drm] Initialized drm 1.1.0 20060810
[    0.937792] 12d00000.hdmi supply hdmi-en not found, using dummy regulator
[    0.943662] s5p-g2d 10800000.g2d: The exynos g2d(ver 4.1) successfully probed
[    0.950370] exynos-drm-fimc 11820000.fimc: drm fimc registered successfully.
[    0.956993] exynos-drm-fimc 11830000.fimc: drm fimc registered successfully.
[    0.964145] exynos-drm-ipp exynos-drm-ipp: drm ipp registered successfully.
[    0.971632] tv-power-domain: Power-off latency exceeded, new value 248125 ns
[    0.978033] tv-power-domain: Power-on latency exceeded, new value 349125 ns
[    0.984642] exynos-drm exynos-drm: bound 12c10000.mixer (ops mixer_component_ops)
[    0.992201] exynos-drm exynos-drm: bound 12d00000.hdmi (ops hdmi_component_ops)
[    0.999359] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.005935] [drm] No driver support for vblank timestamp query.
[    1.012237] [drm] Initialized exynos 1.0.0 20110530 on minor 0
[    1.019850] loop: module loaded
[    1.021370] usbcore: registered new interface driver smsc95xx
[    1.053100] dwc2 12480000.hsotg: EPs: 16, dedicated fifos, 7808 entries in SPRAM
[    1.055036] dwc2 12480000.hsotg: cannot create debug root
[    1.060407] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.066754] ehci-exynos: EHCI EXYNOS driver
[    1.071321] exynos-ehci 12580000.ehci: EHCI Host Controller
[    1.076478] exynos-ehci 12580000.ehci: new USB bus registered, assigned bus number 1
[    1.084350] exynos-ehci 12580000.ehci: irq 68, io mem 0x12580000
[    1.098092] exynos-ehci 12580000.ehci: USB 2.0 started, EHCI 1.00
[    1.098655] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.105314] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.112509] usb usb1: Product: EHCI Host Controller
[    1.117364] usb usb1: Manufacturer: Linux 4.0.5 ehci_hcd
[    1.122656] usb usb1: SerialNumber: 12580000.ehci
[    1.127818] hub 1-0:1.0: USB hub found
[    1.131092] hub 1-0:1.0: 3 ports detected
[    1.135589] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.141222] ohci-exynos: OHCI EXYNOS driver
[    1.363153] usb3503 0-0008: switched to HUB mode
[    1.363206] usb3503 0-0008: usb3503_probe: probed in hub mode
[    1.368357] max77686-rtc max77686-rtc: max77686_rtc_probe
[    1.473117] usb 1-2: new high-speed USB device number 2 using exynos-ehci
[    1.474866] max77686-rtc max77686-rtc: rtc core: registered max77686-rtc as rtc0
[    1.482415] s3c-rtc 10070000.rtc: failed to find rtc source clock
[    1.487731] platform 10070000.rtc: Driver s3c-rtc requests probe deferral
[    1.494668] i2c /dev entries driver
[    1.500001] s3c2410-wdt 10060000.watchdog: watchdog inactive, reset disabled, irq disabled
[    1.506645] device-mapper: ioctl: 4.30.0-ioctl (2014-12-22) initialised: dm-devel@redhat.com
[    1.516756] Driver 'mmcblk' needs updating - please use bus_type methods
[    1.521292] sdhci: Secure Digital Host Controller Interface driver
[    1.527422] sdhci: Copyright(c) Pierre Ossman
[    1.532091] s3c-sdhci 12530000.sdhci: clock source 2: mmc_busclk.2 (55000000 Hz)
[    1.539166] s3c-sdhci 12530000.sdhci: Got CD GPIO
[    1.573175] mmc0: SDHCI controller on samsung-hsmmc [12530000.sdhci] using ADMA
[    1.574935] Synopsys Designware Multimedia Card Interface Driver
[    1.581347] dwmmc_exynos 12550000.mmc: IDMAC supports 32-bit address mode.
[    1.587754] dwmmc_exynos 12550000.mmc: Using internal DMA controller.
[    1.594117] dwmmc_exynos 12550000.mmc: Version ID is 240a
[    1.599496] dwmmc_exynos 12550000.mmc: DW MMC controller at irq 119, 32 bit host data width, 128 deep fifo
[    1.609226] dwmmc_exynos 12550000.mmc: allocated mmc-pwrseq
[    1.623464] usb 1-2: New USB device found, idVendor=0424, idProduct=3503
[    1.624515] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.632049] hub 1-2:1.0: USB hub found
[    1.635464] hub 1-2:1.0: 3 ports detected
[    1.648108] dwmmc_exynos 12550000.mmc: 1 slots initialized
[    1.648805] s5p-sss driver registered
[    1.651678] hidraw: raw HID events driver (C) Jiri Kosina
[    1.657069] usbcore: registered new interface driver usbhid
[    1.662519] usbhid: USB HID core driver
[    1.666914] exynos-memory-bus memory_bus@0: unable to get devfreq-event device : ppmu-event3-dmc0
[    1.675220] exynos-memory-bus memory_bus@0: failed to initialize memory-bus
[    1.682133] platform memory_bus@0: Driver exynos-memory-bus requests probe deferral
[    1.690055] exynos-memory-bus memory_bus@1: unable to get devfreq-event device : ppmu-event3-leftbus
[    1.698933] exynos-memory-bus memory_bus@1: failed to initialize memory-bus
[    1.705839] platform memory_bus@1: Driver exynos-memory-bus requests probe deferral
[    1.714791] platform sound: Driver asoc-simple-card requests probe deferral
[    1.721201] TCP: cubic registered
[    1.723902] NET: Registered protocol family 10
[    1.728106] mmc1: MAN_BKOPS_EN bit is not set
[    1.728561] sit: IPv6 over IPv4 tunneling driver
[    1.728892] NET: Registered protocol family 17
[    1.728991] ThumbEE CPU extension supported.
[    1.729000] Registering SWP/SWPB emulation handler
[    1.729840] s3c-rtc 10070000.rtc: rtc disabled, re-enabling
[    1.729985] s3c-rtc 10070000.rtc: rtc core: registered s3c as rtc1
[    1.753287] max98090 1-0010: MAX98090 REVID=0x43
[    1.767973] asoc-simple-card sound: HiFi <-> 3830000.i2s mapping ok
[    1.768038] mmc_host mmc1: Bus speed (slot 0) = 44000000Hz (slot req 52000000Hz, actual 44000000HZ div = 0)
[    1.783920] mmc_host mmc1: Bus speed (slot 0) = 73333333Hz (slot req 52000000Hz, actual 36666666HZ div = 1)
[    1.784331] input: gpio_keys as /devices/platform/gpio_keys/input/input0
[    1.784639] gps-alive-power-domain: Power-off latency exceeded, new value 232041 ns
[    1.784690] gps-power-domain: Power-off latency exceeded, new value 228167 ns
[    1.784884] g3d-power-domain: Power-off latency exceeded, new value 230625 ns
[    1.784926] vdd_g3d: disabling
[    1.786115] unused_2.8V: disabling
[    1.787304] vdd_hdmi_1.0V: disabling
[  [    1.836882] Waiting for root device /dev/mmcblk0p3...
[    1.837277] mmc1: new DDR MMC card at address 0001
[    1.841357] mmcblk0: mmc1:0001 064G93 58.2 GiB
[    1.845654] mmcblk0boot0: mmc1:0001 064G93 partition 1 4.00 MiB
[    1.851545] mmcblk0boot1: mmc1:0001 064G93 partition 2 4.00 MiB
[    1.857438] mmcblk0rpmb: mmc1:0001 064G93 partition 3 512 KiB
[    1.863906]  mmcblk0: p1 p2 p3
[    1.923227] usb 1-2.1: new high-speed USB device number 3 using exynos-ehci


mikewhatever
Posts: 21
Joined: Sat Feb 08, 2014 6:41 pm
languages_spoken: english
ODROIDs: u-3
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by mikewhatever » Sun Jun 28, 2015 4:25 am

Panzerknacker wrote:You can use 4.7 or 4.9.
http://choorucode.com/2015/02/26/how-to ... ernatives/
or google: gcc alternative ubuntu
Thanks for replying. Do you know that 4.7 and 4.9 actually work? Which one have you used to build 4.0.x for odroid?
I suppose I could blindly poke around, and try different gcc versions, but I was hoping to save myself the trouble by tapping into this community's wisdom and experience.

gulp
Posts: 18
Joined: Mon Apr 14, 2014 4:58 am
languages_spoken: Italian,english
ODROIDs: Odroid U3
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by gulp » Sun Jun 28, 2015 5:37 am

With gcc 5.1 i've no problem. Uboot and kernel compiles perfectly.

mikewhatever
Posts: 21
Joined: Sat Feb 08, 2014 6:41 pm
languages_spoken: english
ODROIDs: u-3
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by mikewhatever » Sun Jun 28, 2015 6:15 am

gulp wrote:With gcc 5.1 i've no problem. Uboot and kernel compiles perfectly.
I'll try gcc 5.1, thanks.

LiquidAcid
Posts: 1091
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Mon Jun 29, 2015 1:59 am

gcc-4.8.3 and previous releases have some major bugs which break both kernel and AFAIK also glibc (search the bugtracker for details). That's why the kernel compilation bails out early when detecting such a configuration. In general it's recommend to keep the compiler at the most recent patch level (this would be gcc-4.8.5 for the 4.8.y series).

LiquidAcid
Posts: 1091
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Sun Jul 12, 2015 3:09 am

More of the usual rebasing:
- odroid-4.0.y rebased on stable-4.0.8
- odroid-4.1.y rebased on stable-4.1.2

Still working on integrating some more patchsets into odroid-4.2.y. Maybe going to push something once rc4 or so hits.

Tuigje
Posts: 60
Joined: Thu Jun 20, 2013 1:00 am
languages_spoken: english dutch german
ODROIDs: Odroid X2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Tuigje » Fri Jul 31, 2015 5:49 am

Hi,

This looks awesome, I'd love to try it out.

I'm struggling with the dtb-boot. Which u-boot should I use, and which bootloaders ?
I've built u-boot from [url]git://git.denx.de/u-boot.git[/url], which gives a 442kb u-boot-dtb.bin.

I've cat-ed arch/arm/boot/dts/exynos4412-odroidx2.dtb to the zImage.
The sd_fusing.sh works fine with the original u-boot.bin, but doesn't boot with the new u-boot + kernel.

LiquidAcid
Posts: 1091
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Tue Aug 04, 2015 2:11 am

Update:
- odroid-4.0.y rebased on stable-4.0.9 (which is EOL)
- odroid-4.1.y rebased on stable-4.1.3
- added odroid-4.2.y based on torvalds's rc5

I'm keeping 4.0.y for the moment since vsync is broken on 4.1.y (probably due to the atomic conversion). 4.2.y is barely tested atm, but it boots and cpufreq should be working (the newer cpufreq-dt is now used for the Exynos4412).

User avatar
meveric
Posts: 9762
Joined: Mon Feb 25, 2013 2:41 pm
languages_spoken: german, english
ODROIDs: X2, U2, U3, XU-Lite, XU3, XU3-Lite, C1, XU4, C2, C1+, XU4Q, HC1, N1, Go
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by meveric » Tue Aug 04, 2015 2:37 am

any news about MFC support? Any progress?
Donate to support my work on the ODROID GameStation Turbo Image for U2/U3 XU3/XU4 X2 X C1 as well as many other releases.
Check out the Games and Emulators section to find some of my work or check the files in my repository to find the software i build for ODROIDs.
If you want to add my repository to your image read my HOWTO integrate my repo into your image.

User avatar
OverSun
Posts: 1432
Joined: Mon Apr 29, 2013 5:12 pm
languages_spoken: english
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by OverSun » Tue Aug 04, 2015 2:43 am

I personally wasn't able to boot the kernel properly on my U2.
Nor 4.0, nor 4.1, 4.2 wasn't there at the moment.
I had to do a lot of stuff like u-boot upgrade, etc, etc, etc and in the end it was still bad as shit. Kernel oopses while booting, panics and stuff...
It wasn't also very easy to do all the stuff, searching through this topic for all the things that was needed and wasn't needed anymore. Maybe a comprehensive guide would help.
So no, no news yet.

User avatar
meveric
Posts: 9762
Joined: Mon Feb 25, 2013 2:41 pm
languages_spoken: german, english
ODROIDs: X2, U2, U3, XU-Lite, XU3, XU3-Lite, C1, XU4, C2, C1+, XU4Q, HC1, N1, Go
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by meveric » Tue Aug 04, 2015 2:54 am

OverSun wrote:I personally wasn't able to boot the kernel properly on my U2.
Nor 4.0, nor 4.1, 4.2 wasn't there at the moment.
I had to do a lot of stuff like u-boot upgrade, etc, etc, etc and in the end it was still bad as shit. Kernel oopses while booting, panics and stuff...
It wasn't also very easy to do all the stuff, searching through this topic for all the things that was needed and wasn't needed anymore. Maybe a comprehensive guide would help.
So no, no news yet.
Have you tried following: http://forum.odroid.com/viewtopic.php?p=86489#p86489
Donate to support my work on the ODROID GameStation Turbo Image for U2/U3 XU3/XU4 X2 X C1 as well as many other releases.
Check out the Games and Emulators section to find some of my work or check the files in my repository to find the software i build for ODROIDs.
If you want to add my repository to your image read my HOWTO integrate my repo into your image.

User avatar
Panzerknacker
Posts: 247
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Tue Aug 04, 2015 3:11 am

4.2.0 boots on U3 (Server, no X):

Code: Select all

root@odroidu3:/# dmesg
[    0.000000] Booting Linux on physical CPU 0xa00
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.2.0-rc5-120129-g847e8fb (root@odroidu3) (gcc version 4.9.2 (Debian 4.9.2-10) ) #3 SMP PREEMPT Mon Aug 3 20:00:58 CEST 2015
[    0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: Hardkernel ODROID-U3 board based on Exynos4412
[    0.000000] Reserved memory: created CMA memory pool at 0x77000000, size 16 MiB
[    0.000000] Reserved memory: initialized node region@77000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created CMA memory pool at 0x78000000, size 16 MiB
[    0.000000] Reserved memory: initialized node region@78000000, compatible id shared-dma-pool
[    0.000000] cma: Reserved 128 MiB at 0xb7c00000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] Samsung CPU ID: 0xe4412220
[    0.000000] On node 0 totalpages: 524032
[    0.000000] free_area_init_node: node 0, pgdat c067d740, node_mem_map ee7f5000
[    0.000000]   Normal zone: 1520 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 194560 pages, LIFO batch:31
[    0.000000]   HighMem zone: 329472 pages, LIFO batch:31
[    0.000000] Running under secure firmware.
[    0.000000] PERCPU: Embedded 11 pages/cpu @ee794000 s14848 r8192 d22016 u45056
[    0.000000] pcpu-alloc: s14848 r8192 d22016 u45056 alloc=11*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 522512
[    0.000000] Kernel command line: root=/dev/mmcblk0p2 rootwait console=ttySAC1,115200n8
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    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: 1905352K/2096128K available (4660K kernel code, 161K rwdata, 1488K rodata, 304K init, 231K bss, 26936K reserved, 163840K cma-reserved, 1154048K highmem)
[    0.000000] Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
    lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc06095e0   (6150 kB)
      .init : 0xc060a000 - 0xc0656000   ( 304 kB)
      .data : 0xc0656000 - 0xc067e6a0   ( 162 kB)
       .bss : 0xc0681000 - 0xc06bafb4   ( 232 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]  Build-time adjustment of leaf fanout to 32.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] L2C: platform modifies aux control register: 0x02070000 -> 0x3e470001
[    0.000000] L2C: platform provided aux values permit register corruption.
[    0.000000] L2C: DT/platform modifies aux control register: 0x02070000 -> 0x3e470001
[    0.000000] L2C-310 enabling early BRESP for Cortex-A9
[    0.000000] L2C-310: enabling full line of zeros but not enabled in Cortex-A9
[    0.000000] L2C-310 ID prefetch enabled, offset 8 lines
[    0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[    0.000000] L2C-310 cache controller enabled, 16 ways, 1024 kB
[    0.000000] L2C-310: CACHE_ID 0x4100c4c8, AUX_CTRL 0x7e470001
[    0.000000] Exynos4x12 clocks: sclk_apll = 1000000000, sclk_mpll = 800000000
        sclk_epll = 96000000, sclk_vpll = 350000000, arm_clk = 1000000000
[    0.000000] Switching to timer-based delay loop, resolution 41ns
[    0.000000] clocksource: mct-frc: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[    0.000004] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
[    0.000189] Console: colour dummy device 80x30
[    0.000207] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=120000)
[    0.000218] pid_max: default: 32768 minimum: 301
[    0.000290] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000299] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000725] Initializing cgroup subsys devices
[    0.000745] CPU: Testing write buffer coherency: ok
[    0.001003] CPU0: thread -1, cpu 0, socket 10, mpidr 80000a00
[    0.001359] Setting up static identity map for 0x400082c0 - 0x40008318
[    0.020504] CPU1: thread -1, cpu 1, socket 10, mpidr 80000a01
[    0.025480] CPU2: thread -1, cpu 2, socket 10, mpidr 80000a02
[    0.030461] CPU3: thread -1, cpu 3, socket 10, mpidr 80000a03
[    0.030511] Brought up 4 CPUs
[    0.030528] SMP: Total of 4 processors activated (192.00 BogoMIPS).
[    0.030534] CPU: All CPU(s) started in SVC mode.
[    0.031017] devtmpfs: initialized
[    0.043039] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.043401] lcd0-power-domain@10023C80 has as child subdomain: tv-power-domain@10023C20.
[    0.043819] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302231375000 ns
[    0.048210] pinctrl core: initialized pinctrl subsystem
[    0.049004] NET: Registered protocol family 16
[    0.050712] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.064999] cpuidle: using governor ladder
[    0.075517] cpuidle: using governor menu
[    0.081161] exynos-audss-clk 3810000.clock-controller: setup completed
[    0.083790] iommu: Adding device 11800000.fimc to group 0
[    0.084119] iommu: Adding device 11810000.fimc to group 1
[    0.084436] iommu: Adding device 11820000.fimc to group 2
[    0.084755] iommu: Adding device 11830000.fimc to group 3
[    0.088513] iommu: Adding device 12c10000.mixer to group 4
[    0.089552] gpiochip_add: registered GPIOs 0 to 7 on device: gpa0
[    0.089644] gpiochip_add: registered GPIOs 8 to 13 on device: gpa1
[    0.089726] gpiochip_add: registered GPIOs 14 to 21 on device: gpb
[    0.089814] gpiochip_add: registered GPIOs 22 to 26 on device: gpc0
[    0.089896] gpiochip_add: registered GPIOs 27 to 31 on device: gpc1
[    0.089972] gpiochip_add: registered GPIOs 32 to 35 on device: gpd0
[    0.090047] gpiochip_add: registered GPIOs 36 to 39 on device: gpd1
[    0.090122] gpiochip_add: registered GPIOs 40 to 47 on device: gpf0
[    0.090204] gpiochip_add: registered GPIOs 48 to 55 on device: gpf1
[    0.090278] gpiochip_add: registered GPIOs 56 to 63 on device: gpf2
[    0.090353] gpiochip_add: registered GPIOs 64 to 69 on device: gpf3
[    0.090434] gpiochip_add: registered GPIOs 70 to 77 on device: gpj0
[    0.090579] gpiochip_add: registered GPIOs 78 to 82 on device: gpj1
[    0.091377] gpiochip_add: registered GPIOs 83 to 89 on device: gpk0
[    0.091467] gpiochip_add: registered GPIOs 90 to 96 on device: gpk1
[    0.091550] gpiochip_add: registered GPIOs 97 to 103 on device: gpk2
[    0.091636] gpiochip_add: registered GPIOs 104 to 110 on device: gpk3
[    0.091713] gpiochip_add: registered GPIOs 111 to 117 on device: gpl0
[    0.091796] gpiochip_add: registered GPIOs 118 to 119 on device: gpl1
[    0.091872] gpiochip_add: registered GPIOs 120 to 127 on device: gpl2
[    0.091949] gpiochip_add: registered GPIOs 128 to 135 on device: gpm0
[    0.092031] gpiochip_add: registered GPIOs 136 to 142 on device: gpm1
[    0.092107] gpiochip_add: registered GPIOs 143 to 147 on device: gpm2
[    0.092183] gpiochip_add: registered GPIOs 148 to 155 on device: gpm3
[    0.092263] gpiochip_add: registered GPIOs 156 to 163 on device: gpm4
[    0.092348] gpiochip_add: registered GPIOs 164 to 169 on device: gpy0
[    0.092427] gpiochip_add: registered GPIOs 170 to 173 on device: gpy1
[    0.092510] gpiochip_add: registered GPIOs 174 to 179 on device: gpy2
[    0.092588] gpiochip_add: registered GPIOs 180 to 187 on device: gpy3
[    0.092673] gpiochip_add: registered GPIOs 188 to 195 on device: gpy4
[    0.092751] gpiochip_add: registered GPIOs 196 to 203 on device: gpy5
[    0.092829] gpiochip_add: registered GPIOs 204 to 211 on device: gpy6
[    0.092917] gpiochip_add: registered GPIOs 212 to 219 on device: gpx0
[    0.092997] gpiochip_add: registered GPIOs 220 to 227 on device: gpx1
[    0.093075] gpiochip_add: registered GPIOs 228 to 235 on device: gpx2
[    0.093155] gpiochip_add: registered GPIOs 236 to 243 on device: gpx3
[    0.094168] gpiochip_add: registered GPIOs 244 to 250 on device: gpz
[    0.094586] gpiochip_add: registered GPIOs 251 to 258 on device: gpv0
[    0.094670] gpiochip_add: registered GPIOs 259 to 266 on device: gpv1
[    0.094751] gpiochip_add: registered GPIOs 267 to 274 on device: gpv2
[    0.094837] gpiochip_add: registered GPIOs 275 to 282 on device: gpv3
[    0.094925] gpiochip_add: registered GPIOs 283 to 284 on device: gpv4
[    0.096593] iommu: Adding device 10800000.g2d to group 5
[    0.098236] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.098246] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.103649] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/regulators/regulator@0[0]'
[    0.103887] of_get_named_gpiod_flags: parsed 'gpio' property of node '/regulators/regulator@1[0]' - status (0)
[    0.104646] SCSI subsystem initialized
[    0.104773] usbcore: registered new interface driver usbfs
[    0.104829] usbcore: registered new interface driver hub
[    0.104915] usbcore: registered new device driver usb
[    0.105423] s3c-i2c 13860000.i2c: slave address 0x10
[    0.105436] s3c-i2c 13860000.i2c: bus frequency set to 390 KHz
[    0.118031] of_get_named_gpiod_flags: can't parse 'maxim,ena-gpios' property of node '/i2c@13860000/pmic@09/voltage-regulators/LDO20[0]'
[    0.118743] of_get_named_gpiod_flags: can't parse 'maxim,ena-gpios' property of node '/i2c@13860000/pmic@09/voltage-regulators/LDO21[0]'
[    0.119482] of_get_named_gpiod_flags: can't parse 'maxim,ena-gpios' property of node '/i2c@13860000/pmic@09/voltage-regulators/LDO22[0]'
[    0.126950] of_get_named_gpiod_flags: can't parse 'maxim,ena-gpios' property of node '/i2c@13860000/pmic@09/voltage-regulators/BUCK8[0]'
[    0.127431] of_get_named_gpiod_flags: can't parse 'maxim,ena-gpios' property of node '/i2c@13860000/pmic@09/voltage-regulators/BUCK9[0]'
[    0.128169] s3c-i2c 13860000.i2c: i2c-0: S3C I2C adapter
[    0.128387] s3c-i2c 13870000.i2c: slave address 0x10
[    0.128399] s3c-i2c 13870000.i2c: bus frequency set to 390 KHz
[    0.128649] s3c-i2c 13870000.i2c: i2c-1: S3C I2C adapter
[    0.128774] s3c-i2c 13880000.i2c: slave address 0x00
[    0.128785] s3c-i2c 13880000.i2c: bus frequency set to 97 KHz
[    0.128936] s3c-i2c 13880000.i2c: i2c-2: S3C I2C adapter
[    0.129025] s3c-i2c 138e0000.i2c: slave address 0x00
[    0.129036] s3c-i2c 138e0000.i2c: bus frequency set to 97 KHz
[    0.129279] s3c-i2c 138e0000.i2c: i2c-8: S3C I2C adapter
[    0.129848] Advanced Linux Sound Architecture Driver Initialized.
[    0.130461] clocksource: Switched to clocksource mct-frc
[    0.139255] NET: Registered protocol family 2
[    0.139724] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.139793] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.139891] TCP: Hash tables configured (established 8192 bind 8192)
[    0.139948] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.139977] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.140123] NET: Registered protocol family 1
[    0.140317] Unpacking initramfs...
[    0.257698] Freeing initrd memory: 2408K (cfda6000 - d0000000)
[    0.258024] hw perfevents: Failed to parse /pmu/interrupt-affinity[0]
[    0.258070] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[    0.259615] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.259753] audit: initializing netlink subsys (disabled)
[    0.259796] audit: type=2000 audit(0.255:1): initialized
[    0.268471] bounce: pool size: 64 pages
[    0.268487] io scheduler noop registered
[    0.268499] io scheduler deadline registered
[    0.268532] io scheduler cfq registered (default)
[    0.273653] dma-pl330 12680000.pdma: Loaded driver for PL330 DMAC-141330
[    0.273667] dma-pl330 12680000.pdma:         DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    0.276172] dma-pl330 12690000.pdma: Loaded driver for PL330 DMAC-141330
[    0.276186] dma-pl330 12690000.pdma:         DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    0.276994] dma-pl330 12850000.mdma: Loaded driver for PL330 DMAC-141330
[    0.277006] dma-pl330 12850000.mdma:         DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32
[    0.329474] 13800000.serial: ttySAC0 at MMIO 0x13800000 (irq = 69, base_baud = 0) is a S3C6400/10
[    0.329808] 13810000.serial: ttySAC1 at MMIO 0x13810000 (irq = 70, base_baud = 0) is a S3C6400/10
[    1.102692] console [ttySAC1] enabled
[    1.107121] [drm] Initialized drm 1.1.0 20060810
[    1.112197] of_get_named_gpiod_flags: parsed 'hpd-gpio' property of node '/hdmi@12D00000[0]' - status (0)
[    1.112491] 12d00000.hdmi supply hdmi-en not found, using dummy regulator
[    1.118853] s5p-g2d 10800000.g2d: The exynos g2d(ver 4.1) successfully probed
[    1.127858] exynos-drm exynos-drm: bound 12c10000.mixer (ops mixer_component_ops)
[    1.132425] exynos-drm exynos-drm: bound 12d00000.hdmi (ops hdmi_component_ops)
[    1.139557] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.146145] [drm] No driver support for vblank timestamp query.
[    1.152432] [drm] Initialized exynos 1.0.0 20110530 on minor 0
[    1.160154] loop: module loaded
[    1.161616] usbcore: registered new interface driver smsc95xx
[    1.467320] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.468208] ehci-exynos: EHCI EXYNOS driver
[    1.472530] of_get_named_gpiod_flags: can't parse 'samsung,vbus-gpio' property of node '/ehci@12580000[0]'
[    1.472931] exynos-ehci 12580000.ehci: EHCI Host Controller
[    1.477967] exynos-ehci 12580000.ehci: new USB bus registered, assigned bus number 1
[    1.485847] exynos-ehci 12580000.ehci: irq 68, io mem 0x12580000
[    1.500494] exynos-ehci 12580000.ehci: USB 2.0 started, EHCI 1.00
[    1.501091] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.507730] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.514929] usb usb1: Product: EHCI Host Controller
[    1.519787] usb usb1: Manufacturer: Linux 4.2.0-rc5-120129-g847e8fb ehci_hcd
[    1.526818] usb usb1: SerialNumber: 12580000.ehci
[    1.532023] hub 1-0:1.0: USB hub found
[    1.535251] hub 1-0:1.0: 3 ports detected
[    1.539767] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.545414] ohci-exynos: OHCI EXYNOS driver
[    1.549907] of_get_named_gpiod_flags: parsed 'intn-gpios' property of node '/i2c@13860000/usb3503@08[0]' - status (0)
[    1.549928] of_get_named_gpiod_flags: parsed 'connect-gpios' property of node '/i2c@13860000/usb3503@08[0]' - status (0)
[    1.549946] of_get_named_gpiod_flags: parsed 'reset-gpios' property of node '/i2c@13860000/usb3503@08[0]' - status (0)
[    1.770492] usb3503 0-0008: switched to HUB mode
[    1.770553] usb3503 0-0008: usb3503_probe: probed in hub mode
[    1.775780] max77686-rtc max77686-rtc: max77686_rtc_probe
[    1.845492] usb 1-2: new high-speed USB device number 2 using exynos-ehci
[    1.880984] max77686-rtc max77686-rtc: rtc core: registered max77686-rtc as rtc0
[    1.883387] s3c-rtc 10070000.rtc: failed to find rtc source clock
[    1.891207] device-mapper: ioctl: 4.32.0-ioctl (2015-6-26) initialised: dm-devel@redhat.com
[    1.899313] sdhci: Secure Digital Host Controller Interface driver
[    1.903317] sdhci: Copyright(c) Pierre Ossman
[    1.907883] of_get_named_gpiod_flags: parsed 'cd-gpios' property of node '/sdhci@12530000[0]' - status (0)
[    1.907931] s3c-sdhci 12530000.sdhci: clock source 2: mmc_busclk.2 (50000000 Hz)
[    1.915054] s3c-sdhci 12530000.sdhci: GPIO lookup for consumer cd
[    1.915060] s3c-sdhci 12530000.sdhci: using device tree for GPIO lookup
[    1.915073] of_get_named_gpiod_flags: parsed 'cd-gpios' property of node '/sdhci@12530000[0]' - status (0)
[    1.915084] s3c-sdhci 12530000.sdhci: Got CD GPIO
[    1.919726] s3c-sdhci 12530000.sdhci: GPIO lookup for consumer wp
[    1.919732] s3c-sdhci 12530000.sdhci: using device tree for GPIO lookup
[    1.919737] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/sdhci@12530000[0]'
[    1.919742] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/sdhci@12530000[0]'
[    1.919747] s3c-sdhci 12530000.sdhci: using lookup tables for GPIO lookup
[    1.919752] s3c-sdhci 12530000.sdhci: lookup for GPIO wp failed
[    1.950592] mmc0: SDHCI controller on samsung-hsmmc [12530000.sdhci] using ADMA
[    1.952372] Synopsys Designware Multimedia Card Interface Driver
[    1.958826] dwmmc_exynos 12550000.mmc: IDMAC supports 32-bit address mode.
[    1.965153] dwmmc_exynos 12550000.mmc: Using internal DMA controller.
[    1.971539] dwmmc_exynos 12550000.mmc: Version ID is 240a
[    1.976953] dwmmc_exynos 12550000.mmc: DW MMC controller at irq 114, 32 bit host data width, 128 deep fifo
[    1.986696] usb 1-2: New USB device found, idVendor=0424, idProduct=9730
[    1.986797] dwmmc_exynos 12550000.mmc: GPIO lookup for consumer cd
[    1.986799] dwmmc_exynos 12550000.mmc: using device tree for GPIO lookup
[    1.986804] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/mmc@12550000[0]'
[    1.986807] of_get_named_gpiod_flags: can't parse 'cd-gpio' property of node '/mmc@12550000[0]'
[    1.986809] dwmmc_exynos 12550000.mmc: using lookup tables for GPIO lookup
[    1.986812] dwmmc_exynos 12550000.mmc: lookup for GPIO cd failed
[    1.986816] dwmmc_exynos 12550000.mmc: GPIO lookup for consumer wp
[    1.986818] dwmmc_exynos 12550000.mmc: using device tree for GPIO lookup
[    1.986821] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/mmc@12550000[0]'
[    1.986824] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/mmc@12550000[0]'
[    1.986826] dwmmc_exynos 12550000.mmc: using lookup tables for GPIO lookup
[    1.986829] dwmmc_exynos 12550000.mmc: lookup for GPIO wp failed
[    1.986884] platform pwrseq: GPIO lookup for consumer reset
[    1.986887] platform pwrseq: using device tree for GPIO lookup
[    1.986898] of_get_named_gpiod_flags: parsed 'reset-gpios' property of node '/pwrseq[0]' - status (0)
[    1.986908] dwmmc_exynos 12550000.mmc: allocated mmc-pwrseq
[    1.998790] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.008273] smsc95xx v1.0.4
[    2.015531] dwmmc_exynos 12550000.mmc: 1 slots initialized
[    2.015642] sdhci-pltfm: SDHCI platform and OF driver helper
[    2.021178] of_get_named_gpiod_flags: parsed 'gpios' property of node '/leds/led1[0]' - status (0)
[    2.021396] ledtrig-cpu: registered to indicate activity on CPUs
[    2.027345] s5p-sss driver registered
[    2.030796] hidraw: raw HID events driver (C) Jiri Kosina
[    2.036137] usbcore: registered new interface driver usbhid
[    2.041594] usbhid: USB HID core driver
[    2.046006] exynos-memory-bus memory_bus@0: unable to get devfreq-event device : ppmu-event3-dmc0
[    2.054322] exynos-memory-bus memory_bus@0: failed to initialize memory-bus                                                                                                                  
[    2.061487] exynos-memory-bus memory_bus@1: unable to get devfreq-event device : ppmu-event3-leftbus                                                                                         
[    2.070375] exynos-memory-bus memory_bus@1: failed to initialize memory-bus                                                                                                                  
[    2.079861] NET: Registered protocol family 17
[    2.081832] ThumbEE CPU extension supported.
[    2.085995] Registering SWP/SWPB emulation handler
[    2.091781] s3c-rtc 10070000.rtc: rtc core: registered s3c as rtc1
[    2.098077] of_get_named_gpiod_flags: can't parse 'simple-audio-card,hp-det-gpio' property of node '/sound[0]'
[    2.098084] of_get_named_gpiod_flags: can't parse 'simple-audio-card,mic-det-gpio' property of node '/sound[0]'
[    2.099992] smsc95xx 1-2:1.0 eth0: register 'smsc95xx' at usb-12580000.ehci-2, smsc95xx USB 2.0 Ethernet, fe:8c:f7:49:5b:5d
[    2.113237] mmc1: MAN_BKOPS_EN bit is not set
[    2.114497] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 52000000Hz, actual 50000000HZ div = 0)
[    2.120621] max98090 1-0010: MAX98090 REVID=0x43
[    2.121206] max98090 1-0010: use default 2.8v micbias
[    2.132749] mmc_host mmc1: Bus speed (slot 0) = 100000000Hz (slot req 52000000Hz, actual 50000000HZ div = 1)
[    2.139832] asoc-simple-card sound: HiFi <-> 3830000.i2s mapping ok
[    2.141246] of_get_named_gpiod_flags: parsed 'gpios' property of node '/gpio_keys/power_key[0]' - status (0)
[    2.141293] gpio-223 (power key): gpiod_set_debounce: missing set() or set_debounce() operations
[    2.141440] input: gpio_keys as /devices/platform/gpio_keys/input/input0
[    2.154728] mmc1: new DDR MMC card at address 0001
[    2.159417] mmcblk0: mmc1:0001 064G93 58.2 GiB 
[    2.163793] mmcblk0boot0: mmc1:0001 064G93 partition 1 4.00 MiB
[    2.169622] max77686-rtc max77686-rtc: setting system clock to 2015-08-03 18:04:27 UTC (1438625067)
[    2.178779] mmcblk0boot1: mmc1:0001 064G93 partition 2 4.00 MiB
[    2.179465] ALSA device list:
[    2.179467]   #0: Odroid-U3
[    2.190361] mmcblk0rpmb: mmc1:0001 064G93 partition 3 4.00 MiB
[    2.191058] Freeing unused kernel memory: 304K (c060a000 - c0656000)
[    2.203395]  mmcblk0: p1 p2
[    2.230213] systemd-udevd[1321]: starting version 215
[    2.231416] random: systemd-udevd urandom read with 14 bits of entropy available
[    2.335508] usb 1-3: new high-speed USB device number 3 using exynos-ehci
[    2.465812] usb 1-3: New USB device found, idVendor=0424, idProduct=3503
[    2.466867] usb 1-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.474396] hub 1-3:1.0: USB hub found
[    2.477810] hub 1-3:1.0: 3 ports detected
[    2.586356] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    2.709367] systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
[    2.717228] systemd[1]: Detected architecture 'arm'.
[    2.751117] systemd[1]: Failed to insert module 'autofs4'
[    2.766441] NET: Registered protocol family 10
[    2.766994] systemd[1]: Inserted module 'ipv6'
[    2.770558] systemd[1]: Set hostname to <odroidu3>.
[    2.775495] usb 1-3.1: new full-speed USB device number 4 using exynos-ehci
[    2.886456] usb 1-3.1: New USB device found, idVendor=04fa, idProduct=2490
[    2.887683] usb 1-3.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.922752] systemd[1]: Expecting device dev-ttySAC1.device...
[    2.935626] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[    2.937804] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    2.945268] systemd[1]: Starting Remote File Systems (Pre).
[    2.970563] systemd[1]: Reached target Remote File Systems (Pre).
[    2.971089] systemd[1]: Starting Encrypted Volumes.
[    2.980496] usb 1-3.2: new high-speed USB device number 5 using exynos-ehci
[    2.995660] systemd[1]: Reached target Encrypted Volumes.
[    2.995921] systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
[    3.003725] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[    3.011546] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[    3.020775] systemd[1]: Starting Swap.
[    3.035585] systemd[1]: Reached target Swap.
[    3.035741] systemd[1]: Expecting device dev-mmcblk0p1.device...
[    3.050583] systemd[1]: Starting Root Slice.
[    3.060557] systemd[1]: Created slice Root Slice.
[    3.060704] systemd[1]: Starting User and Session Slice.
[    3.080615] systemd[1]: Created slice User and Session Slice.
[    3.080800] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[    3.090212] usb 1-3.2: New USB device found, idVendor=0403, idProduct=6010
[    3.094189] usb 1-3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.101482] usb 1-3.2: Product: USB <-> Serial Cable
[    3.106422] usb 1-3.2: Manufacturer: FTDI
[    3.110399] usb 1-3.2: SerialNumber: FTXIGIZL
[    3.130650] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[    3.132069] systemd[1]: Starting Delayed Shutdown Socket.
[    3.155575] systemd[1]: Listening on Delayed Shutdown Socket.
[    3.155769] systemd[1]: Starting Journal Socket (/dev/log).
[    3.180574] systemd[1]: Listening on Journal Socket (/dev/log).
[    3.180953] systemd[1]: Starting udev Control Socket.
[    3.200507] usb 1-3.3: new full-speed USB device number 6 using exynos-ehci
[    3.200744] systemd[1]: Listening on udev Control Socket.
[    3.200816] systemd[1]: Starting udev Kernel Socket.
[    3.225610] systemd[1]: Listening on udev Kernel Socket.
[    3.225872] systemd[1]: Starting Journal Socket.
[    3.240591] systemd[1]: Listening on Journal Socket.
[    3.240938] systemd[1]: Starting System Slice.
[    3.255587] systemd[1]: Created slice System Slice.
[    3.257180] systemd[1]: Mounting Temporary Directory...
[    3.273543] systemd[1]: Starting system-systemd\x2dfsck.slice.
[    3.291052] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[    3.291993] systemd[1]: Starting system-getty.slice.
[    3.310756] systemd[1]: Created slice system-getty.slice.
[    3.311002] systemd[1]: Starting system-serial\x2dgetty.slice.
[    3.316780] usb 1-3.3: New USB device found, idVendor=04fa, idProduct=2490
[    3.323238] usb 1-3.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.345758] systemd[1]: Created slice system-serial\x2dgetty.slice.
[    3.346673] systemd[1]: Starting Increase datagram queue length...
[    3.374221] systemd[1]: Starting Load Kernel Modules...
[    3.390714] systemd[1]: Started Set Up Additional Binary Formats.
[    3.391465] systemd[1]: Mounting POSIX Message Queue File System...
[    3.408356] i2c /dev entries driver
[    3.415739] Driver for 1-wire Dallas network protocol.
[    3.431624] systemd[1]: Starting udev Coldplug all Devices...
[    3.446863] systemd[1]: Starting Create list of required static device nodes for the current kernel...
[    3.471750] systemd[1]: Mounted Huge Pages File System.
[    3.471926] systemd[1]: Starting LSB: controls configuration of serial ports...
[    3.496580] systemd[1]: Starting Slices.
[    3.505586] systemd[1]: Reached target Slices.
[    3.520607] systemd[1]: Mounted POSIX Message Queue File System.
[    3.535547] systemd[1]: Mounted Temporary Directory.
[    3.550593] systemd[1]: Started Increase datagram queue length.
[    3.551645] systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
[    3.590558] systemd[1]: Failed to start Load Kernel Modules.
[    3.590697] systemd[1]: Unit systemd-modules-load.service entered failed state.
[    3.616066] systemd[1]: Started Create list of required static device nodes for the current kernel.
[    3.636070] systemd[1]: Started LSB: controls configuration of serial ports.
[    3.686034] systemd[1]: Started udev Coldplug all Devices.
[    3.709667] systemd[1]: Starting Create Static Device Nodes in /dev...
[    3.726764] systemd[1]: Starting Apply Kernel Variables...
[    3.741897] systemd[1]: Mounted FUSE Control File System.
[    3.742231] systemd[1]: Mounted Configuration File System.
[    3.747234] systemd[1]: Starting Syslog Socket.
[    3.765629] systemd[1]: Listening on Syslog Socket.
[    3.765783] systemd[1]: Starting Journal Service...
[    3.790581] systemd[1]: Started Journal Service.
[    3.843064] systemd-udevd[1411]: starting version 215
[    3.975325] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    4.469161] FAT-fs (mmcblk0p1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[    4.627742] systemd-journald[1410]: Received request to flush runtime journal from PID 1
[    5.080070] usbcore: registered new interface driver DS9490R
[    5.141201] usbcore: registered new interface driver usbserial
[    5.141573] usbcore: registered new interface driver usbserial_generic
[    5.154574] usbserial: USB Serial support registered for generic
[    5.172298] usbcore: registered new interface driver ftdi_sio
[    5.172450] usbserial: USB Serial support registered for FTDI USB Serial Device
[    5.180150] ftdi_sio 1-3.2:1.0: FTDI USB Serial Device converter detected
[    5.186618] usb 1-3.2: Detected FT2232H
[    5.190705] usb 1-3.2: FTDI USB Serial Device converter now attached to ttyUSB0
[    5.197684] ftdi_sio 1-3.2:1.1: FTDI USB Serial Device converter detected
[    5.204634] usb 1-3.2: Detected FT2232H
[    5.208665] usb 1-3.2: FTDI USB Serial Device converter now attached to ttyUSB1
[    6.379145] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    7.905764] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    7.907578] smsc95xx 1-2:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
[   13.689092] random: nonblocking pool is initialized
[   15.227392] warning: process `colord-sane' used the deprecated sysctl system call with 8.1.2.
Thanks.

LiquidAcid
Posts: 1091
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Tue Aug 04, 2015 5:13 am

meveric wrote:any news about MFC support? Any progress?
I hereby ban such questions from this thread.
The next time someone should ask this, you immediately end up on my ignore list (the list where OverSun already is, so don't bother posting here, I won't read your bullshit anyway).

If you want to know if something works, then check if it works (and report it).
If you want something to work, then work on it (and publish the results).

Panzerknacker wrote:4.2.0 boots on U3
Thanks for the confirmation! You didn't happen to encounter some issues when rebooting?

User avatar
memeka
Posts: 4235
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by memeka » Tue Aug 04, 2015 8:00 am

LiquidAcid wrote:
meveric wrote:any news about MFC support? Any progress?
I hereby ban such questions from this thread.
The next time someone should ask this, you immediately end up on my ignore list (the list where OverSun already is, so don't bother posting here, I won't read your bullshit anyway).

If you want to know if something works, then check if it works (and report it).
If you want something to work, then work on it (and publish the results).

Panzerknacker wrote:4.2.0 boots on U3
Thanks for the confirmation! You didn't happen to encounter some issues when rebooting?
Lol :)
According to your own words, if you wanna know if there are issues when rebooting, keep rebooting. If you want rebooting to work with no issues, work on it.

LiquidAcid
Posts: 1091
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Tue Aug 04, 2015 8:41 am

*plonk*

User avatar
Panzerknacker
Posts: 247
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Tue Aug 04, 2015 4:28 pm

LiquidAcid wrote:
Panzerknacker wrote:4.2.0 boots on U3
Thanks for the confirmation! You didn't happen to encounter some issues when rebooting?
Did not have to reboot yet, as it worked from start.
Server is remote, will test reboot tonight.

User avatar
Panzerknacker
Posts: 247
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Wed Aug 05, 2015 3:00 am

No problem with "reboot" over ssh.

LiquidAcid
Posts: 1091
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Sat Aug 15, 2015 1:35 am

Trivial update:
- odroid-4.1.y rebased on stable-4.1.5
- odroid-4.2.y rebased on torvalds's rc6

Fixed a bug in the DRM code which was introduced by my layer blending rewrite. RetroLess (which is my RA fork) should work again. Currently on the menu: Lunar 2: Eternal Blue Complete

kernel config for odroid-4.2.y

User avatar
Panzerknacker
Posts: 247
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Mon Aug 17, 2015 8:26 pm

Get the following compile error with 4.2.y, gcc 4.9.2 (Debian 8) with vanilla-4.2-debug.conf:

Code: Select all

drivers/gpu/arm/mali/linux/mali_kernel_linux.c: In function ‘mali_module_init’:
drivers/gpu/arm/mali/linux/mali_kernel_linux.c:315:71: error: macro "__DATE__" might prevent reproducible builds [-Werror=date-time]
  MALI_DEBUG_PRINT(2, ("Compiled: %s, time: %s.\n", __DATE__, __TIME__));
                                                                       ^
drivers/gpu/arm/mali/linux/mali_kernel_linux.c:315:1: error: macro "__TIME__" might prevent reproducible builds [-Werror=date-time]
  MALI_DEBUG_PRINT(2, ("Compiled: %s, time: %s.\n", __DATE__, __TIME__));
 ^
On a headless server with a minimal .config it boots and reboots fine.
Had one freezer after 8h with boost=1, no logs.
With boost=0 system is up 1 day, 16:06.

LiquidAcid
Posts: 1091
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Tue Aug 18, 2015 2:14 am

The __DATE__ and __TIME__ error should be fixed now, I just removed the printk.

Panzerknacker wrote:On a headless server with a minimal .config it boots and reboots fine.
Had one freezer after 8h with boost=1, no logs.
With boost=0 system is up 1 day, 16:06.
Can you check if the instability goes away (with boost enabled) when you fix the devfreq governor to performance?

Code: Select all

echo -n performance > /sys/class/devfreq/memory_bus\@0/governor
echo -n performance > /sys/class/devfreq/memory_bus\@1/governor

User avatar
Panzerknacker
Posts: 247
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Tue Aug 18, 2015 2:38 am

LiquidAcid wrote: Can you check if the instability goes away (with boost enabled) when you fix the devfreq governor to performance?

Code: Select all

echo -n performance > /sys/class/devfreq/memory_bus\@0/governor
echo -n performance > /sys/class/devfreq/memory_bus\@1/governor
Thanks, have set it, will come back, if sth. happens.

User avatar
Panzerknacker
Posts: 247
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Tue Aug 18, 2015 2:45 am

Can not pull your repo any more, was ok before introduction of 4.2.
Had to clone it some day ago.
Now again:

Code: Select all

root@odroidu3:/usr/src/linux-tobias# git pull
remote: Counting objects: 1558, done.
remote: Compressing objects: 100% (1151/1151), done.
remote: Total 1558 (delta 1178), reused 282 (delta 282), pack-reused 125
Empfange Objekte: 100% (1558/1558), 444.25 KiB | 322.00 KiB/s, Fertig.
Löse Unterschiede auf: 100% (1217/1217), abgeschlossen mit 134 lokalen Objekten.
Von https://github.com/tobiasjakobi/linux-odroid
 + a5c699f...f6d272f odroid-4.2.y -> origin/odroid-4.2.y  (Aktualisierung erzwungen)
automatischer Merge von drivers/gpu/drm/exynos/exynos_drm_g2d.c
KONFLIKT (Inhalt): Merge-Konflikt in drivers/gpu/drm/exynos/exynos_drm_g2d.c
automatischer Merge von drivers/gpu/arm/mali/linux/mali_kernel_linux.c
KONFLIKT (hinzufügen/hinzufügen): Merge-Konflikt in drivers/gpu/arm/mali/linux/mali_kernel_linux.c
automatischer Merge von arch/arm/mach-exynos/pm_domains.c
automatischer Merge von MAINTAINERS
Automatischer Merge fehlgeschlagen; beheben Sie die Konflikte und committen Sie dann das Ergebnis.
Did not change sources, just checked-out 4.2.

LiquidAcid
Posts: 1091
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Tue Aug 18, 2015 3:28 am

All the branches are rebasing, so your procedure is wrong here (git pull won't work on rebasing branches):

Code: Select all

git fetch origin
git reset --hard origin/odroid-4.2.y

User avatar
Panzerknacker
Posts: 247
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Tue Aug 18, 2015 4:37 pm

Thanks.

User avatar
Panzerknacker
Posts: 247
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Wed Aug 19, 2015 4:39 pm

Panzerknacker wrote:
LiquidAcid wrote: Can you check if the instability goes away (with boost enabled) when you fix the devfreq governor to performance?

Code: Select all

echo -n performance > /sys/class/devfreq/memory_bus\@0/governor
echo -n performance > /sys/class/devfreq/memory_bus\@1/governor
Thanks, have set it, will come back, if sth. happens.
Got a freeze today morning, will go back to boost=0.

LiquidAcid
Posts: 1091
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Wed Aug 19, 2015 9:19 pm

Thanks, I guess it's not related to MIF/INT voltage then. I'm not going to investigate this further for now, since the boost supports is going to be changed anyway in 4.3.y (operation-points-v2 framework). Maybe the issue resolves itself when that happens.

LiquidAcid
Posts: 1091
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Thu Aug 20, 2015 1:27 am

Panzerknacker wrote:Got a freeze today morning, will go back to boost=0.
On second thought, does running this (with boost enabled) trigger the lockup?

User avatar
Panzerknacker
Posts: 247
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Thu Aug 20, 2015 4:52 pm

LiquidAcid wrote:
Panzerknacker wrote:Got a freeze today morning, will go back to boost=0.
On second thought, does running this (with boost enabled) trigger the lockup?
Not within 15min. Temp was around 90°C.

LiquidAcid
Posts: 1091
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Thu Aug 20, 2015 8:21 pm

Hmm, consider me clueless at the moment. :(

Moricio78
Posts: 24
Joined: Wed Oct 22, 2014 11:43 pm
languages_spoken: french
ODROIDs: U3
Location: France, Pays de Loire
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Moricio78 » Tue Sep 01, 2015 1:12 am

Hello,

This discussion is very interresting but overly technical for me for me.

I wish I had tried to compile but there are many files that are no longer online.
And there are many versions, I do not know which to choose.
My skills are limited but I've recompiled on Intel.

My U3 turns on Archlinux, kernel 3.8.13 (8GB eMMC and SD for /home).
I need a 3.14 or higher kernel (with USB, ffmpeg, X11 support).

Which version is right for a fully functional kernel?

For example: Can I use vanilla-4.1.conf without modification?
Where to find the kernel source directory 4.1.5, this one contains all necessary files?

Thanks

LiquidAcid
Posts: 1091
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Tue Sep 01, 2015 4:17 am

Moricio78 wrote:Which version is right for a fully functional kernel?
None. This thread is about kernel development, so consider everything broken by default. Patches are always welcomed!

LiquidAcid
Posts: 1091
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Mon Sep 07, 2015 11:37 pm

To comment a bit on my question about reboot issues to Panzerknacker. Seems like Marek found out where the reboot issue originates from:
http://www.spinics.net/lists/linux-sams ... 47140.html

I haven't applied this to odroid-4.2.y yet, so if you use non-performance cpufreq governors, make sure to set it to performance on reboot. If the oppv2 stuff should show up in 4.3-rc1 this issue should resolve itself then.

User avatar
Panzerknacker
Posts: 247
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Tue Sep 08, 2015 2:05 am

Got first freeze with boost=0 two weeks ago.
mmc0-triggered blue LED is always on after freezing.
Went back to a 4.0.0-rc5-next-20150312 kernel to keep the server
running over my vacation.
Has been up for 15 days without problems.
So some bug must be in 4.2.y.
Will change to 4.3 as soon as it shines up on your git.

LiquidAcid
Posts: 1091
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Tue Sep 08, 2015 3:06 am

Could you gather anything from the UART when this happens?

I wouldn't be surprised if this is still cpufreq related. odroid-4.0.y still uses the old cpufreq (exynos4x12-cpufreq) driver while odroid-4.2.y uses the newer (cpufreq-dt) driver.

User avatar
Panzerknacker
Posts: 247
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Tue Sep 08, 2015 3:15 am

Yes, cpufreq-exynos vc -generic might make the difference.
Unfortunately the server is mounted in the Heizungskeller and cabled with a bunch of sensors.
Not easy to connect the debug-UART and put a laptop there.
Will setup another U3 at work next week permanently running 4.2 and report about.

LiquidAcid
Posts: 1091
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Tue Sep 08, 2015 4:08 am

I see. This is of course tricky to capture, especially when you have no way to reliably trigger the lockup.

LiquidAcid
Posts: 1091
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Mon Sep 21, 2015 11:21 pm

I pushed odroid-4.3.y (based on 4.3-rc2). Booting works but apart from that I haven't checked much yet. Still need to apply some fixes to the prime OPPs.

User avatar
Panzerknacker
Posts: 247
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Wed Sep 23, 2015 8:26 pm

Put odroid-4.3.y on the 24h headless U3 server. Will report if any issues.

LiquidAcid
Posts: 1091
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Thu Sep 24, 2015 9:53 pm

Cool, if you have some additional time could you also check recent upstream u-boot (boot from SD card though)? I was made aware that the X2 apparantly fails to boot with the recent version, but I'm not sure if this issue also applies to the U3 (issue seems related to CD gpio).

Anyway, in case you test this and under the condition that upstream u-boot doesn't work, here are some fixes which might help:
u-boot/stable

User avatar
Panzerknacker
Posts: 247
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Thu Sep 24, 2015 10:18 pm

Currently my U3s and one XU4 are running upstrem u-boot v2015.10-rc3 fine.
All are on mmc, I can't test µSD easily.

Interesting:
The old U3 (the server from above) never has reboot problems.
The U3+ get's often stuck on reboot.
Both U3s run your odroid-4.3.y headless with minor .config changes, ondemand and boost=0.

LiquidAcid
Posts: 1091
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Fri Sep 25, 2015 6:08 pm

Can you try changing the cpufreq governor to performance on reboot (if you're not doing that already?).

User avatar
Panzerknacker
Posts: 247
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Fri Sep 25, 2015 6:40 pm

LiquidAcid wrote:Can you try changing the cpufreq governor to performance on reboot (if you're not doing that already?).
Yes, this does the job on the U3+.
I remember this was an old issue, wasn't there a patch on ml to fix this some months ago.
And did this not land in mainline/4412 yet?
Could you include it in your repo?

User avatar
Panzerknacker
Posts: 247
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Fri Sep 25, 2015 6:46 pm

Looks like
[PATCH v2] cpufreq-dt: add suspend frequency support
would be an interim fix until OPP2.
Do you like it?

LiquidAcid
Posts: 1091
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Fri Sep 25, 2015 7:04 pm

Panzerknacker wrote:Looks like
[PATCH v2] cpufreq-dt: add suspend frequency support
would be an interim fix until OPP2.
Do you like it?
Both the suspend freq support and OPPv2 have already landed upstream. My impression is that suspend freq doesn't cure all of the reboot issues we are seeing.
Last edited by LiquidAcid on Mon Sep 28, 2015 6:56 pm, edited 1 time in total.

User avatar
Panzerknacker
Posts: 247
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Fri Sep 25, 2015 8:05 pm

I see, thanks.

User avatar
Panzerknacker
Posts: 247
Joined: Sat Feb 22, 2014 10:08 pm
languages_spoken: German, English
ODROIDs: U3, X2, XU3, XU4, W
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Mon Sep 28, 2015 6:27 pm

Linux odroidu3 4.3.0-rc2-132385-gd977398 #5 SMP PREEMPT Tue Sep 22 16:02:18 CEST 2015 armv7l GNU/Linux
11:17:15 up 5 days, 18:43, 1 user, load average: 0,05, 0,14, 0,24
With boost=1 and ondemand governor.
Looks like 4.3 ist quite stable now.
Server is at:
https://akdy.ddns.net/s4-charts.html
https://akdy.ddns.net/schemadsp.php

Thanks for keeping and sharing this repo.
Would like to have a similar good maintained one for the XU4.
Would help testing it.

LiquidAcid
Posts: 1091
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Mon Sep 28, 2015 9:53 pm

Panzerknacker wrote:Linux odroidu3 4.3.0-rc2-132385-gd977398 #5 SMP PREEMPT Tue Sep 22 16:02:18 CEST 2015 armv7l GNU/Linux
11:17:15 up 5 days, 18:43, 1 user, load average: 0,05, 0,14, 0,24
With boost=1 and ondemand governor.
Looks like 4.3 ist quite stable now.
Server is at:
https://akdy.ddns.net/s4-charts.html
https://akdy.ddns.net/schemadsp.php
Thanks for the longterm test. I've only just updated the default kernel on my X2 to odroid-4.2.y. At least for my emulation purpose it works satisfactory. And I'm still struggling to improve performance for userptr.
Panzerknacker wrote:Thanks for keeping and sharing this repo.
Would like to have a similar good maintained one for the XU4.
Would help testing it.
I currently won't touch the XU4 with a ten foot pole. Too many problems:
- lousy thermal design
- broken BL firmware (see u-boot ml)
- broken cpuidle (due the firmware)

Post Reply

Return to “The Ideas”

Who is online

Users browsing this forum: No registered users and 2 guests