Playing with upstream (Exynos4412)

Share here your ideas for new projects
LiquidAcid
Posts: 1087
Joined: Fri Oct 11, 2013 11:07 pm
languages_spoken: english
ODROIDs: X2
Contact:

Re: Playing with upstream

Unread post by LiquidAcid » Sat Nov 22, 2014 10:03 am

- rebased onto stable/linux-3.17.4
- upstream u-boot now works again (properly detects SDHC, etc.)

EDIT: Guess I should read the u-boot ml more often. The "odroid: set MPLL clock to 880MHz" patch was quickly reverted after it was applied and currently the MPLL is running again with 800MHz. Discussion about the reasons can be found here.

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

Re: Playing with upstream

Unread post by LiquidAcid » Tue Jan 20, 2015 5:33 am

A bit of an update:
- odroid-3.17.y is rebased on stable/linux-3.17.y (which is EOL)

I'm skipping linux-3.18.y completly and head straight to 3.19.y (rc5 at the moment). First bits can be found in my repository, but nothing really works yet. I hope we'll see some of the larger patch sets hitting 3.20.y when the merge window opens. The L2 cache support and the HDMI ones, would be nice to have.

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

Re: Playing with upstream

Unread post by LiquidAcid » Sat Jan 24, 2015 2:01 am

I've cleaned up odroid-3.19.y a bit and it works quite satisfactory for me at the moment.

Some comments:
- had to remove the patches moving cpufreq functionality to cpufreq-dt, since they clash with the thermal framework rework (and I currently lack the time/expertise to resolve the merge conflicts)
- upon loading the mfc module the system locks up, probably i did something wrong when rebasing the patches
- mali is still barely untouched and needs lots of love

I pondered long and hard if I should add a defconfig to the kernel, but now it's there. I've just thinned out my personal config a bit though. Should at least boot the board... I guess.

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

Re: Playing with upstream

Unread post by LiquidAcid » Sun Feb 08, 2015 5:55 am

odroid-3.19.y is now the default branch, since I'm not planning on updating 3.17.y anymore (the upstream branch is EOL anyway).

The usual comments:
- haven't looked into the mfc issue yet
- looked a bit into mali and got at least probing working
- imported a bit of code from Tizen which could be useful in getting mali dvfs working

Apart from that: cpufreq, usb, hdmi, sdhci working. emmc, hwcrypto supposedly working. Someone should check if that new upstream CEC driver functions properly.

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

Re: Playing with upstream

Unread post by LiquidAcid » Sun Feb 15, 2015 6:00 am

odroid-3.19.y is now rebased on top of stable/linux-3.19.y and is going to be rebased during the lifetime of the stable branch.

Comments:
- removed exynos4412_odroid_defconfig again, it was a stupid idea to add it in the first place
- added patches to enable dwc2 support in gadget mode

I'm unsure about whether host mode of the dwc2 controller is always supported. IIRC then it depends on the board hardware revision.

I was made aware that fan control via the thermal subsystem is beginning to work. One should at least need CONFIG_SENSORS_PWM_FAN and CONFIG_THERMAL_DEFAULT_GOV_STEP_WISE and also make sure that the (then deprecated) userspace fan service is not interfering.

A small tool to check the thermal subsystem can be found here. Be aware that this can easily trigger the thermal safety shutdown, if for whatever reasons, the fan does not kick in.

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

Re: Playing with upstream

Unread post by LiquidAcid » Mon Feb 16, 2015 9:42 pm

I have confirmation from Robert Gadsdon that the thermal subsystem is working properly on the U3 now (so fan control works).

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

Re: Playing with upstream

Unread post by Panzerknacker » Mon Feb 16, 2015 10:02 pm

+1
yes, works.
rg is just wrong with the hysteresis, that is 10K (70°C on, 60°C off).

I used (apt-get install) stress to heat.

User avatar
pyromaniac
Posts: 6
Joined: Mon Feb 16, 2015 11:38 pm
languages_spoken: English, German
ODROIDs: U3
Contact:

Re: Playing with upstream

Unread post by pyromaniac » Tue Feb 17, 2015 2:11 am

I am trying to get liquicAcid's 3.19.y to work on my U3. So far I am using the 3.8.13.29 kernel from archlinux. I can boot the 3.19 kernel, but the USB subsystem doesn't work with that kernel, so I can't get network access.

dmesg|grep usb with 3.8:

Code: Select all

[    0.000000] sclk_csis: source is xusbxti (1), rate is 1500000
[    0.000000] sclk_csis: source is xusbxti (1), rate is 1500000
[    0.000000] sclk_cam0: source is xusbxti (1), rate is 1500000
[    0.000000] sclk_cam1: source is xusbxti (1), rate is 1500000
[    0.000000] sclk_fimc: source is xusbxti (1), rate is 1500000
[    0.000000] sclk_fimc: source is xusbxti (1), rate is 1500000
[    0.000000] sclk_fimc: source is xusbxti (1), rate is 1500000
[    0.000000] sclk_fimc: source is xusbxti (1), rate is 1500000
[    0.000000] sclk_fimd: source is xusbxti (1), rate is 1500000
[    0.214555] usbcore: registered new interface driver usbfs
[    0.214609] usbcore: registered new interface driver hub
[    0.214689] usbcore: registered new device driver usb
[    1.700412] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.706859] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.714072] usb usb1: Product: S5P EHCI Host Controller
[    1.719210] usb usb1: Manufacturer: Linux 3.8.13.29-2-ARCH ehci_hcd
[    1.725437] usb usb1: SerialNumber: s5p-ehci
[    1.824927] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[    1.830144] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.837361] usb usb2: Product: EXYNOS OHCI Host Controller
[    1.842792] usb usb2: Manufacturer: Linux 3.8.13.29-2-ARCH ohci_hcd
[    1.849034] usb usb2: SerialNumber: exynos-ohci
[    1.865996] usbcore: registered new interface driver usb-storage
[    1.876498] usbcore: registered new interface driver ums-alauda
[    1.882413] usbcore: registered new interface driver ums-cypress
[    1.888356] usbcore: registered new interface driver ums-datafab
[    1.894316] usbcore: registered new interface driver ums_eneub6250
[    1.900413] usbcore: registered new interface driver ums-freecom
[    1.906306] usbcore: registered new interface driver ums-isd200
[    1.912145] usbcore: registered new interface driver ums-jumpshot
[    1.918130] usbcore: registered new interface driver ums-realtek
[    1.924017] usbcore: registered new interface driver ums-sddr09
[    1.929870] usbcore: registered new interface driver ums-sddr55
[    1.935643] usbcore: registered new interface driver ums-usbat
[    2.050889] usb 1-2: new high-speed USB device number 2 using s5p-ehci
[    2.061041] usb3503 0-0008: USB3503_SP_ILOCK = 0x32
[    2.165882] usb3503 0-0008: switched to HUB mode
[    2.169043] usb3503 0-0008: usb3503_probe: probed on  hub mode
[    2.181316] usb 1-2: New USB device found, idVendor=0424, idProduct=9730
[    2.185497] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.426815] usb 1-3: new high-speed USB device number 3 using s5p-ehci
[    2.646313] usb 1-3: New USB device found, idVendor=0424, idProduct=3503
[    2.651074] usb 1-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.666302] usbcore: registered new interface driver usbhid
[    2.666304] usbhid: USB HID core driver
[    5.656208] smsc95xx 1-2:1.0 eth0: register 'smsc95xx' at usb-s5p-ehci-2, smsc95xx USe
[    5.665237] usbcore: registered new interface driver smsc95x
dmesg from 3.19:

Code: Select all

[    0.173608] usbcore: registered new interface driver usbfs
[    0.173696] usbcore: registered new interface driver hub
[    0.173809] usbcore: registered new device driver usb
[    0.187908] vdd_usb_otg_3.3V: 3300 mV 
[    0.273040] samsung-usb2-phy 125b0000.exynos-usbphy: Looking up phy-supply from device
[    0.273056] samsung-usb2-phy 125b0000.exynos-usbphy: Looking up phy-supply property id
[    0.273230] samsung-usb2-phy 125b0000.exynos-usbphy: Looking up phy-supply from device
[    0.273245] samsung-usb2-phy 125b0000.exynos-usbphy: Looking up phy-supply property id
[    0.273379] samsung-usb2-phy 125b0000.exynos-usbphy: Looking up phy-supply from device
[    0.273393] samsung-usb2-phy 125b0000.exynos-usbphy: Looking up phy-supply property id
[    0.273517] samsung-usb2-phy 125b0000.exynos-usbphy: Looking up phy-supply from device
[    0.273530] samsung-usb2-phy 125b0000.exynos-usbphy: Looking up phy-supply property id
[    1.001635] usbcore: registered new interface driver smsc95xx
[    1.042723] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.049314] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.056516] usb usb1: Product: EHCI Host Controller
[    1.061378] usb usb1: Manufacturer: Linux 3.19.0+ ehci_hcd
[    1.066845] usb usb1: SerialNumber: 12580000.ehci
[    1.090078] usb3503 0-0008: Looking up ext-supply from device tree
[    1.307161] usb3503 0-0008: switched to HUB mode
[    1.307219] usb3503 0-0008: usb3503_probe: probed in hub mode
[    1.417110] usb 1-3: new high-speed USB device number 2 using exynos-ehci
[    1.598377] usbcore: registered new interface driver usbhid
[    1.603773] usbhid: USB HID core driver
The difference that I see is that the first time, the usb3503 gets probed and comes back with the root-hub, the USB1.1-root-hub and the network device. With the 3.19 Kernel, the 3505 gets probed but it does not report any USB devices. After a few days of trying I am pretty sure to have all the relevant config-options enabled for the 3.19 kernel. Does anyone have an Idea why my USB devices could be missing?

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

Re: Playing with upstream

Unread post by Panzerknacker » Tue Feb 17, 2015 3:49 am

You might want to try the config
http://www.fivetechno.de/download/odroid_u3_config
from
http://forum.odroid.com/viewtopic.php?f=81&t=9342
This works for me (eth and wlan).

User avatar
pyromaniac
Posts: 6
Joined: Mon Feb 16, 2015 11:38 pm
languages_spoken: English, German
ODROIDs: U3
Contact:

Re: Playing with upstream

Unread post by pyromaniac » Tue Feb 17, 2015 4:30 am

No, only slightly better. Instead it spams my dmesg with

Code: Select all

[  127.784585] exynos-memory-bus memory_bus@0: failed to set voltage
[  127.789183] vdd_mif: operation not allowed
[  127.793137] devfreq memory_bus@0: dvfs failed with (-1) error
[  127.799039] vdd_int: operation not allowed
[  127.802941] exynos-memory-bus memory_bus@1: failed to set voltage
[  127.809168] vdd_int: operation not allowed
[  127.813097] devfreq memory_bus@1: dvfs failed with (-1) error
dmesg|grep usb:

Code: Select all

[    0.139281] usbcore: registered new interface driver usbfs
[    0.139339] usbcore: registered new interface driver hub
[    0.139428] usbcore: registered new device driver usb
[    1.060262] usbcore: registered new interface driver asix
[    1.065142] usbcore: registered new interface driver ax88179_178a
[    1.071209] usbcore: registered new interface driver cdc_ether
[    1.077039] usbcore: registered new interface driver smsc95xx
[    1.082753] usbcore: registered new interface driver net1080
[    1.088395] usbcore: registered new interface driver cdc_subset
[    1.094294] usbcore: registered new interface driver zaurus
[    1.099897] usbcore: registered new interface driver cdc_ncm
[    1.144976] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.151613] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.158815] usb usb1: Product: EHCI Host Controller
[    1.163675] usb usb1: Manufacturer: Linux 3.19.0-81676-g542fb07 ehci_hcd
[    1.170359] usb usb1: SerialNumber: 12580000.ehci
[    1.409445] usb3503 0-0008: switched to HUB mode
[    1.409504] usb3503 0-0008: usb3503_probe: probed in hub mode
[    1.519403] usb 1-3: new high-speed USB device number 2 using exynos-ehci
[    1.679070] usbcore: registered new interface driver usbhid
[    1.684508] usbhid: USB HID core driver
So, I am still sure it's not the config. I use the devicetree from arch/arm/boot/dts/exynos4412-odroidu3.dtb, could that cause problems? As I understand it, the devicetree is only used to find the 3503?

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

Re: Playing with upstream

Unread post by Panzerknacker » Tue Feb 17, 2015 4:40 am

Sorry, you need the DT, too.
Didn't you get it from Tobias' git repo, it enables the memory bus voltages.

You can try use mine from thread above, just I2C, W1 and SPI added.

User avatar
pyromaniac
Posts: 6
Joined: Mon Feb 16, 2015 11:38 pm
languages_spoken: English, German
ODROIDs: U3
Contact:

Re: Playing with upstream

Unread post by pyromaniac » Wed Feb 18, 2015 3:05 am

Panzerknacker wrote:Sorry, you need the DT, too.
Didn't you get it from Tobias' git repo, it enables the memory bus voltages.
In Tobias' kernel tree there are a number of *.dts files which get compiled into a dtb file during kernel make, that one I used. Is that not the correct one?

Edit: I just pulled & rebuild the sources again, now the devfreq memory_bus problem is gone, but still no USB.
Is there some magic that has to happen in u-boot, or some kernel command line parameters that are needed for the activation of the 3503 chip?

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

Re: Playing with upstream

Unread post by Panzerknacker » Wed Feb 18, 2015 5:28 am

Use exynos4412-odroidu3.dtb for U3.

Nothing special in Uboot, just the def config.

Do you have this?
<*> USB3503 HSIC to USB20 Driver

Again, you might try my .config., just works.

User avatar
pyromaniac
Posts: 6
Joined: Mon Feb 16, 2015 11:38 pm
languages_spoken: English, German
ODROIDs: U3
Contact:

Re: Playing with upstream

Unread post by pyromaniac » Wed Feb 18, 2015 5:31 am

Panzerknacker wrote:Use exynos4412-odroidu3.dtb for U3.

Nothing special in Uboot, just the def config.

Do you have this?
<*> USB3503 HSIC to USB20 Driver

Again, you might try my .config., just works.
Yes, I have USB3505 configured and yes, I tried your config and no, it did not work.

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

Re: Playing with upstream

Unread post by Panzerknacker » Wed Feb 18, 2015 5:54 am

Here is my dmesg for comparison:

Code: Select all

root@odroid-u3-wheezy:~# 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 3.19.0-g4d7072b-dirty (root@odroid-u3-wheezy) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP PREEMPT Tue Feb 17 17:08:15 CET 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] On node 0 totalpages: 524032
[    0.000000] free_area_init_node: node 0, pgdat c066dec0, node_mem_map ee7f4000
[    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 9 pages/cpu @ee79b000 s7808 r8192 d20864 u36864
[    0.000000] pcpu-alloc: s7808 r8192 d20864 u36864 alloc=9*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 tty1 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: 1905900K/2096128K available (4641K kernel code, 187K rwdata, 1496K rodata, 228K init, 229K bss, 59156K reserved, 131072K 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 - 0xc060685c   (6139 kB)
[    0.000000]       .init : 0xc0607000 - 0xc0640000   ( 228 kB)
[    0.000000]       .data : 0xc0640000 - 0xc066ee00   ( 188 kB)
[    0.000000]        .bss : 0xc066ee00 - 0xc06a82f8   ( 230 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 1 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
[    0.000000]  sclk_epll = 96000000, sclk_vpll = 350000000, arm_clk = 1000000000
[    0.000000] Switching to timer-based delay loop, resolution 41ns
[    0.000005] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956969942ns
[    0.000209] Console: colour dummy device 80x30
[    0.000701] console [tty0] enabled
[    0.000724] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=120000)
[    0.000750] pid_max: default: 32768 minimum: 301
[    0.000845] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000866] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001351] Initializing cgroup subsys devices
[    0.001384] CPU: Testing write buffer coherency: ok
[    0.001655] CPU0: thread -1, cpu 0, socket 10, mpidr 80000a00
[    0.002048] Setting up static identity map for 0x40465890 - 0x404658e8
[    0.030477] CPU1: thread -1, cpu 1, socket 10, mpidr 80000a01
[    0.040462] CPU2: thread -1, cpu 2, socket 10, mpidr 80000a02
[    0.050454] CPU3: thread -1, cpu 3, socket 10, mpidr 80000a03
[    0.050501] Brought up 4 CPUs
[    0.050549] SMP: Total of 4 processors activated (192.00 BogoMIPS).
[    0.050563] CPU: All CPU(s) started in SVC mode.
[    0.051106] devtmpfs: initialized
[    0.051945] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.059119] pinctrl core: initialized pinctrl subsystem
[    0.071207] NET: Registered protocol family 16
[    0.072753] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.085491] cpuidle: using governor ladder
[    0.100487] cpuidle: using governor menu
[    0.106097] exynos-audss-clk 3810000.clock-controller: setup completed
[    0.122816] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.122849] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.123381] lcd0-power-domain has as child subdomain: tv-power-domain.
[    0.130764] SCSI subsystem initialized
[    0.131058] usbcore: registered new interface driver usbfs
[    0.131130] usbcore: registered new interface driver hub
[    0.131222] usbcore: registered new device driver usb
[    0.131732] s3c-i2c 13860000.i2c: slave address 0x10
[    0.131755] s3c-i2c 13860000.i2c: bus frequency set to 390 KHz
[    0.160307] s3c-i2c 13860000.i2c: i2c-0: S3C I2C adapter
[    0.160541] s3c-i2c 13870000.i2c: slave address 0x10
[    0.160563] s3c-i2c 13870000.i2c: bus frequency set to 390 KHz
[    0.160956] s3c-i2c 13870000.i2c: i2c-1: S3C I2C adapter
[    0.161107] s3c-i2c 13880000.i2c: slave address 0x00
[    0.161127] s3c-i2c 13880000.i2c: bus frequency set to 97 KHz
[    0.161283] s3c-i2c 13880000.i2c: i2c-2: S3C I2C adapter
[    0.161383] s3c-i2c 138e0000.i2c: slave address 0x00
[    0.161403] s3c-i2c 138e0000.i2c: bus frequency set to 97 KHz
[    0.161762] s3c-i2c 138e0000.i2c: i2c-8: S3C I2C adapter
[    0.161955] Linux video capture interface: v2.00
[    0.162408] Advanced Linux Sound Architecture Driver Initialized.
[    0.163038] Switched to clocksource mct-frc
[    0.172114] NET: Registered protocol family 2
[    0.172679] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.172758] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.172881] TCP: Hash tables configured (established 8192 bind 8192)
[    0.172946] TCP: reno registered
[    0.172965] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.173019] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.173250] NET: Registered protocol family 1
[    0.173639] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[    0.174886] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.175054] audit: initializing netlink subsys (disabled)
[    0.175101] audit: type=2000 audit(0.170:1): initialized
[    0.184443] bounce: pool size: 64 pages
[    0.184647] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[    0.184675] io scheduler noop registered
[    0.184694] io scheduler deadline registered
[    0.184732] io scheduler cfq registered (default)
[    0.185158] exynos-mipi-video-phy 10020710.video-phy: can't request region for resource [mem 0x10020710-0x10020717]
[    0.185193] exynos-mipi-video-phy: probe of 10020710.video-phy failed with error -16
[    0.189974] dma-pl330 12680000.pdma: Loaded driver for PL330 DMAC-141330
[    0.190004] dma-pl330 12680000.pdma:         DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    0.192686] dma-pl330 12690000.pdma: Loaded driver for PL330 DMAC-141330
[    0.192715] dma-pl330 12690000.pdma:         DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    0.193633] dma-pl330 12850000.mdma: Loaded driver for PL330 DMAC-141330
[    0.193660] dma-pl330 12850000.mdma:         DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32
[    0.251279] 13800000.serial: ttySAC0 at MMIO 0x13800000 (irq = 70, base_baud = 0) is a S3C6400/10
[    0.251652] 13810000.serial: ttySAC1 at MMIO 0x13810000 (irq = 71, base_baud = 0) is a S3C6400/10
[    0.982549] console [ttySAC1] enabled
[    0.986852] [drm] Initialized drm 1.1.0 20060810
[    0.992372] 12d00000.hdmi supply hdmi-en not found, using dummy regulator
[    0.998840] s5p-g2d 10800000.g2d: The exynos g2d(ver 4.1) successfully probed
[    1.005872] tv-power-domain: Power-off latency exceeded, new value 256792 ns
[    1.011977] lcd0-power-domain: Power-off latency exceeded, new value 252917 ns
[    1.019273] lcd0-power-domain: Power-on latency exceeded, new value 352375 ns
[    1.026388] tv-power-domain: Power-on latency exceeded, new value 357875 ns
[    1.033004] exynos-drm exynos-drm: bound 12c10000.mixer (ops mixer_component_ops)
[    1.040610] exynos-drm exynos-drm: bound 12d00000.hdmi (ops hdmi_component_ops)
[    1.047732] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.054320] [drm] No driver support for vblank timestamp query.
[    1.060600] [drm] Initialized exynos 1.0.0 20110530 on minor 0
[    1.067834] loop: module loaded
[    1.070432] usbcore: registered new interface driver asix
[    1.074610] usbcore: registered new interface driver ax88179_178a
[    1.080669] usbcore: registered new interface driver cdc_ether
[    1.086500] usbcore: registered new interface driver smsc95xx
[    1.092212] usbcore: registered new interface driver net1080
[    1.097864] usbcore: registered new interface driver cdc_subset
[    1.103760] usbcore: registered new interface driver zaurus
[    1.109347] usbcore: registered new interface driver cdc_ncm
[    1.115096] dwc2 12480000.hsotg: registering common handler for irq67
[    1.115153] dwc2 12480000.hsotg: mapped PA 12480000 to VA f0200000
[    1.115164] dwc2 12480000.hsotg: DWC OTG HCD INIT
[    1.115173] dwc2 12480000.hsotg: Bad value for GSNPSID: 0x00000000
[    1.121421] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.127588] ehci-exynos: EHCI EXYNOS driver
[    1.132352] exynos-ehci 12580000.ehci: EHCI Host Controller
[    1.137471] exynos-ehci 12580000.ehci: new USB bus registered, assigned bus number 1
[    1.145226] exynos-ehci 12580000.ehci: irq 68, io mem 0x12580000
[    1.158068] exynos-ehci 12580000.ehci: USB 2.0 started, EHCI 1.00
[    1.158655] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.165307] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.172514] usb usb1: Product: EHCI Host Controller
[    1.177368] usb usb1: Manufacturer: Linux 3.19.0-g4d7072b-dirty ehci_hcd
[    1.184053] usb usb1: SerialNumber: 12580000.ehci
[    1.189225] hub 1-0:1.0: USB hub found
[    1.192479] hub 1-0:1.0: 3 ports detected
[    1.197018] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.202642] ohci-exynos: OHCI EXYNOS driver
[    1.423067] usb3503 0-0008: switched to HUB mode
[    1.423139] usb3503 0-0008: usb3503_probe: probed in hub mode
[    1.428315] mousedev: PS/2 mouse device common for all mice
[    1.433865] max77686-rtc max77686-rtc: max77686_rtc_probe
[    1.503088] usb 1-2: new high-speed USB device number 2 using exynos-ehci
[    1.538565] max77686-rtc max77686-rtc: rtc core: registered max77686-rtc as rtc0
[    1.540969] s3c-rtc 10070000.rtc: rtc disabled, re-enabling
[    1.545955] rtc (null): read_time: fail to read
[    1.550568] s3c-rtc 10070000.rtc: rtc core: registered s3c as rtc1
[    1.556637] s3c-rtc 10070000.rtc: warning: invalid RTC value so initializing it
[    1.566153] device-mapper: ioctl: 4.29.0-ioctl (2014-10-28) initialised: dm-devel@redhat.com
[    1.574099] Driver 'mmcblk' needs updating - please use bus_type methods
[    1.578987] sdhci: Secure Digital Host Controller Interface driver
[    1.585117] sdhci: Copyright(c) Pierre Ossman
[    1.589699] s3c-sdhci 12530000.sdhci: clock source 2: mmc_busclk.2 (50000000 Hz)
[    1.596875] s3c-sdhci 12530000.sdhci: Got CD GPIO
[    1.628158] mmc0: SDHCI controller on samsung-hsmmc [12530000.sdhci] using ADMA
[    1.629946] Synopsys Designware Multimedia Card Interface Driver
[    1.636042] usb 1-2: New USB device found, idVendor=0424, idProduct=9730
[    1.636405] dwmmc_exynos 12550000.mmc: IDMAC supports 32-bit address mode.
[    1.636543] dwmmc_exynos 12550000.mmc: Using internal DMA controller.
[    1.636551] dwmmc_exynos 12550000.mmc: Version ID is 240a
[    1.636579] dwmmc_exynos 12550000.mmc: DW MMC controller at irq 114, 32 bit host data width, 128 deep fifo
[    1.663108] dwmmc_exynos 12550000.mmc: 1 slots initialized
[    1.663159] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.663642] s5p-sss driver registered
[    1.663752] hidraw: raw HID events driver (C) Jiri Kosina
[    1.663854] usbcore: registered new interface driver usbhid
[    1.663855] usbhid: USB HID core driver
[    1.664399] exynos-memory-bus memory_bus@0: unable to get devfreq-event device : ppmu-event3-dmc0
[    1.664441] exynos-memory-bus memory_bus@0: failed to initialize memory-bus
[    1.664471] platform memory_bus@0: Driver exynos-memory-bus requests probe deferral
[    1.664675] exynos-memory-bus memory_bus@1: unable to get devfreq-event device : ppmu-event3-leftbus
[    1.664709] exynos-memory-bus memory_bus@1: failed to initialize memory-bus
[    1.664732] platform memory_bus@1: Driver exynos-memory-bus requests probe deferral
[    1.666161] platform sound: Driver asoc-simple-card requests probe deferral
[    1.667042] TCP: cubic registered
[    1.667051] NET: Registered protocol family 17
[    1.667153] ThumbEE CPU extension supported.
[    1.667163] Registering SWP/SWPB emulation handler
[    1.693218] max98090 1-0010: MAX98090 REVID=0x43
[    1.717483] asoc-simple-card sound: HiFi <-> 3830000.i2s mapping ok
[    1.719107] input: gpio_keys as /devices/platform/gpio_keys/input/input0
[    1.719410] gps-alive-power-domain: Power-off latency exceeded, new value 224917 ns
[    1.719474] gps-power-domain: Power-off latency exceeded, new value 237583 ns
[    1.719519] g3d-power-domain: Power-off latency exceeded, new value 230375 ns
[    1.735751] mmc1: BKOPS_EN bit is not set
[    1.737012] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 52000000Hz, actual 50000000HZ div = 0)
[    1.737817] mmc_host mmc1: Bus speed (slot 0) = 100000000Hz (slot req 52000000Hz, actual 50000000HZ div = 1)
[    1.738153] mmc1: new DDR MMC card at address 0001
[    1.738355] mmcblk0: mmc1:0001 064GE2 58.2 GiB 
[    1.738407] mmcblk0boot0: mmc1:0001 064GE2 partition 1 4.00 MiB
[    1.738461] mmcblk0boot1: mmc1:0001 064GE2 partition 2 4.00 MiB
[    1.738511] mmcblk0rpmb: mmc1:0001 064GE2 partition 3 4.00 MiB
[    1.739263]  mmcblk0: p1 p2
[    1.747449] max77686-rtc max77686-rtc: setting system clock to 2015-02-17 20:15:37 UTC (1424204137)
[    1.756270] vdd_g3d: disabling
[    1.757527] vdd_hdmi_1.0V: disabling
[    1.758837] ALSA device list:
[    1.758841]   #0: Odroid-U3
[    1.885137] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.892656] smsc95xx v1.0.4
[    1.942629] smsc95xx 1-2:1.0 eth0: register 'smsc95xx' at usb-12580000.ehci-2, smsc95xx USB 2.0 Ethernet, 56:e8:f8:57:8c:62
[    1.949423] EXT4-fs (mmcblk0p2): couldn't mount as ext3 due to feature incompatibilities
[    1.956722] EXT4-fs (mmcblk0p2): couldn't mount as ext2 due to feature incompatibilities
[    1.972666] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    1.975231] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[    1.982429] Freeing unused kernel memory: 228K (c0607000 - c0640000)
[    2.178302] usb 1-3: new high-speed USB device number 3 using exynos-ehci
[    2.308564] usb 1-3: New USB device found, idVendor=0424, idProduct=3503
[    2.309664] usb 1-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    2.317419] hub 1-3:1.0: USB hub found
[    2.320675] hub 1-3:1.0: 3 ports detected
[    2.608189] usb 1-3.1: new high-speed USB device number 4 using exynos-ehci
[    2.712486] i2c-gpio i2c_gpio: using pins 221 (SDA) and 220 (SCL)
[    2.734321] usb 1-3.1: New USB device found, idVendor=0cf3, idProduct=9271
[    2.735610] usb 1-3.1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
[    2.743374] usb 1-3.1: Product: USB2.0 WLAN
[    2.747311] usb 1-3.1: Manufacturer: ATHEROS
[    2.771373] usb 1-3.1: SerialNumber: 12345
[    3.004115] cfg80211: Calling CRDA to update world regulatory domain
[    3.008840] random: alsactl urandom read with 72 bits of entropy available
[    3.036307] usb 1-3.1: ath9k_htc: Firmware htc_9271.fw requested
[    3.036879] usbcore: registered new interface driver ath9k_htc
[    3.071380] cfg80211: World regulatory domain updated:
[    3.071477] cfg80211:  DFS Master region: unset
[    3.075239] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[    3.084972] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[    3.092947] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[    3.100935] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[    3.108917] cfg80211:   (5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A, 2000 mBm), (N/A)
[    3.116990] cfg80211:   (5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[    3.125061] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[    3.133132] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[    3.141122] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[    3.333827] usb 1-3.1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
[    3.570320] ath9k_htc 1-3.1:1.0: ath9k_htc: HTC initialized with 33 credits
[    3.668299] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    3.775458] i2c /dev entries driver
[    3.815674] ath9k_htc 1-3.1:1.0: ath9k_htc: FW Version: 1.3
[    3.815781] ath: EEPROM regdomain: 0x809c
[    3.815784] ath: EEPROM indicates we should expect a country code
[    3.815788] ath: doing EEPROM country->regdmn map search
[    3.815792] ath: country maps to regdmn code: 0x52
[    3.815796] ath: Country alpha2 being used: CN
[    3.815803] ath: Regpair used: 0x52
[    3.830664] ieee80211 phy0: Atheros AR9271 Rev:1
[    3.830918] cfg80211: Calling CRDA for country: CN
[    3.835594] cfg80211: Calling CRDA for country: CN
[    3.850184] ath9k_htc 1-3.1:1.0 wlan4: renamed from wlan0
[    3.868690] cfg80211: Current regulatory domain intersected:
[    3.868817] cfg80211:  DFS Master region: unset
[    3.874700] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[    3.882900] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[    3.890842] cfg80211:   (2457000 KHz - 2482000 KHz @ 25000 KHz), (N/A, 2000 mBm), (N/A)
[    3.898838] cfg80211:   (2474000 KHz - 2482000 KHz @ 8000 KHz), (N/A, 2000 mBm), (N/A)
[    3.906716] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[    3.914694] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz), (N/A, 2000 mBm), (0 s)
[    3.922675] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[    3.930648] cfg80211:   (57240000 KHz - 59400000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[    3.938717] cfg80211:   (59400000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[    4.535540] FAT-fs (mmcblk0p1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[    4.545807] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[    6.517548] random: nonblocking pool is initialized
[    6.528173] NET: Registered protocol family 10
[    6.913711] pca953x 3-0020: failed reading register
[    6.913878] i2c i2c-3: new_device: Instantiated device tca6416 at 0x20
[    6.922315] pca953x 3-0021: failed reading register
[    6.924462] i2c i2c-3: new_device: Instantiated device tca6416 at 0x21
[    6.931400] i2c i2c-3: new_device: Instantiated device ads7830 at 0x48
[    6.981856] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    7.265148] IPv6: ADDRCONF(NETDEV_UP): wlan4: link is not ready
[   10.184421] wlan4: authenticate with bc:05:43:52:3b:8c
[   10.503974] wlan4: send auth to bc:05:43:52:3b:8c (try 1/3)
[   10.506782] wlan4: authenticated
[   10.508327] wlan4: associate with bc:05:43:52:3b:8c (try 1/3)
[   10.516909] wlan4: RX AssocResp from bc:05:43:52:3b:8c (capab=0x431 status=0 aid=2)
[   10.529593] IPv6: ADDRCONF(NETDEV_CHANGE): wlan4: link becomes ready
[   10.530865] wlan4: associated

User avatar
pyromaniac
Posts: 6
Joined: Mon Feb 16, 2015 11:38 pm
languages_spoken: English, German
ODROIDs: U3
Contact:

Re: Playing with upstream

Unread post by pyromaniac » Wed Feb 18, 2015 7:01 am

So I did a line-by line comparison with Panzerknacker's dmesg, I am missing the following lines:

Code: Select all

[    1.115164 ] dwc2 12480000.hsotg: DWC OTG HCD INIT
[    1.115173 ] dwc2 12480000.hsotg: Bad value for GSNPSID: 0x00000000

…

[    1.545955 ] rtc (null): read_time: fail to read
[    1.556637 ] s3c-rtc 10070000.rtc: warning: invalid RTC value so initializing it

…

[    1.636042 ] usb 1-2: New USB device found, idVendor=0424, idProduct=9730

…

[    1.885137 ] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.892656 ] smsc95xx v1.0.4
[    1.942629 ] smsc95xx 1-2:1.0 eth0: register 'smsc95xx' at usb-12580000.ehci-2, smsc95xx USB 2.0 Ethernet, 56:e8:f8:57:8c:62
So the only difference between our logs ist the discovery of the network device. And mine boots about 1/100 sec faster than yours.

User avatar
memeka
Posts: 4075
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

Unread post by memeka » Wed Feb 18, 2015 7:16 am

are you using the same dts?

MastaG
Posts: 226
Joined: Mon Aug 26, 2013 6:05 pm
languages_spoken: english
Contact:

Re: Playing with upstream

Unread post by MastaG » Wed Feb 18, 2015 8:23 pm

So will the 3.19.y kernel also work on the older XU (5410)?
If yes, does anyone have a defconfig for this?

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

Re: Playing with upstream

Unread post by Panzerknacker » Wed Feb 18, 2015 10:07 pm

@pyromaniac:
I can provoke your problem by issuing 'usb start' at the U-Boot prompt before booting. Even a 'usb stop' does not help then.
Do you use U-Boot with default config and default environment?

User avatar
pyromaniac
Posts: 6
Joined: Mon Feb 16, 2015 11:38 pm
languages_spoken: English, German
ODROIDs: U3
Contact:

Re: Playing with upstream

Unread post by pyromaniac » Wed Feb 18, 2015 10:59 pm

Panzerknacker wrote:@pyromaniac:
I can provoke your problem by issuing 'usb start' at the U-Boot prompt before booting. Even a 'usb stop' does not help then.
Do you use U-Boot with default config and default environment?
No I don't, I actually stole u-boot from archlinux, and they do run 'usb start'. I removed it, and now it works, thank you!

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

Re: Playing with upstream

Unread post by LiquidAcid » Thu Feb 19, 2015 12:17 am

I've told you explicitly to use upstream uboot and even provided you with the necessary uboot env. That's what you get for not following instructions. Seriously, this just wastes everyone's time.

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

Re: Playing with upstream

Unread post by LiquidAcid » Thu Mar 19, 2015 12:38 am

- rebased odroid-3.19.y on stable/linux-3.19.2
- rebased odroid-4.0.y on torvalds/master (4.0.0-rc4 plus eps)

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

Re: Playing with upstream

Unread post by LiquidAcid » Wed Apr 01, 2015 11:36 pm

The usual rebasing:
- odroid-3.19.y on stable/linux-3.19.3
- odroid-4.0.y on torvalds/master (4.0.0-rc6 plus eps)

No major issues with 4.0.y, except for the 'sleeping while atomic' warnings (sdhci).

I've investigated the MFC probe oops a bit, and got at least some nice output:

Code: Select all

[  102.925560] platform 13400000.codec:left: assigned reserved memory node region@77000000
[  102.928139] platform 13400000.codec:right: assigned reserved memory node region@78000000
[  102.938833] s5p-mfc 13400000.codec: decoder registered as /dev/video2
[  102.942634] s5p-mfc 13400000.codec: encoder registered as /dev/video3
[  102.976378] PAGE FAULT occurred at 0x77000100 by 13620000.sysmmu(Page table base: 0x6e2bc000)
[  102.979261]  Lv1 entry: 0x6e0f2401
[  102.982666] ------------[ cut here ]------------
[  102.987246] kernel BUG at drivers/iommu/exynos-iommu.c:358!
[  102.992801] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
[  102.998616] Modules linked in: s5p_mfc ecb bridge stp llc bnep btrfs xor xor_neon zlib_inflate zlib_deflate raid6_pq btusb bluetooth usb_storage s5p_jpeg videobuf2_dma_contig videobuf2_memops v4l2_mem2mem videobuf2_core
[  103.018064] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W       4.0.0-rc5-debug+ #4
[  103.026045] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[  103.032123] task: c06b55a8 ti: c06b0000 task.ti: c06b0000
[  103.037511] PC is at exynos_sysmmu_irq+0x2a0/0x2a8
[  103.042283] LR is at vprintk_emit+0x268/0x594
[  103.046619] pc : [<c0273844>]    lr : [<c00650c4>]    psr: a00001d3
[  103.046619] sp : c06b1d88  ip : 00000000  fp : c06b1dc4
[  103.058075] r10: ffffffda  r9 : ee206528  r8 : ee28d610
[  103.063283] r7 : 77000100  r6 : 00000000  r5 : 00000770  r4 : ee206510
[  103.069793] r3 : c06e86c0  r2 : 00000000  r1 : 00000000  r0 : ee23a500
[  103.076304] Flags: NzCv  IRQs off  FIQs off  Mode SVC_32  ISA ARM  Segment kernel
[  103.083768] Control: 10c5387d  Table: 6c27804a  DAC: 00000015
[  103.089497] Process swapper/0 (pid: 0, stack limit = 0xc06b0218)
[  103.095486] Stack: (0xc06b1d88 to 0xc06b2000)
[  103.099829] 1d80:                   c06b1d94 c070b840 c06b1dac 6e2bc000 c0075e28 ee209000
[  103.107989] 1da0: ee04a660 00000026 ee007000 00000000 00000000 c06e6e9c c06b1e0c c06b1dc8
[  103.116148] 1dc0: c0066a28 c02735b0 c04d87fc c0048fe0 c06b1e2c c06e6c6f ee04a600 c06e6e88
[  103.124307] 1de0: c070c268 ee04a600 ee04a660 ee209000 ee007000 00000015 c06b1ef8 ee008000
[  103.132466] 1e00: c06b1e2c c06b1e10 c0066c84 c00669d4 00020000 ee04a600 ee04a660 00002000
[  103.140625] 1e20: c06b1e44 c06b1e30 c0069c60 c0066c4c 00000026 ee004450 c06b1e5c c06b1e48
[  103.148785] 1e40: c006601c c0069ba0 000000a0 c06cd974 c06b1e84 c06b1e60 c021ecdc c0065ff4
[  103.156943] 1e60: c021ec40 00000015 00000000 00000015 00000000 00000001 c06b1e9c c06b1e88
[  103.165103] 1e80: c006601c c021ec4c 00000089 c06acc54 c06b1ecc c06b1ea0 c0066330 c0065ff4
[  103.173262] 1ea0: c06b1ef8 f002000c 00000025 00000015 c06b2808 c06b1ef8 f0020000 c06e7414
[  103.181421] 1ec0: c06b1ef4 c06b1ed0 c000867c c00662b8 c000f830 60000053 ffffffff c06b1f2c
[  103.189580] 1ee0: c06addc0 00000001 c06b1f4c c06b1ef8 c0013240 c0008650 00000001 00000000
[  103.197739] 1f00: 00000000 c00206c0 c06b2518 c04dd3a4 00000000 00000000 c06addc0 00000001
[  103.205899] 1f20: c06e7414 c06b1f4c c06b1f50 c06b1f40 c000f82c c000f830 60000053 ffffffff
[  103.214058] 1f40: c06b1f8c c06b1f50 c005b6dc c000f7fc 00000000 00000001 c06b1f7c c06ae800
[  103.222218] 1f60: c004b008 c004af24 c06e6c6d c06b2520 c06b2688 c06ae800 c04d3df0 ffffffff
[  103.230377] 1f80: c06b1fa4 c06b1f90 c04cccf4 c005b3d0 c06b0000 c06b2614 c06b1ff4 c06b1fa8
[  103.238536] 1fa0: c067bcfc c04ccc74 ffffffff ffffffff c067b6d0 00000000 00000000 ef7fc900
[  103.246694] 1fc0: 00000000 c069f230 00000000 c06e9054 c06b24b8 c069f22c c06b67ac 4000406a
[  103.254854] 1fe0: 413fc090 00000000 00000000 c06b1ff8 40008070 c067b968 00000000 00000000
[  103.263008] Backtrace: 
[  103.265448] [<c02735a4>] (exynos_sysmmu_irq) from [<c0066a28>] (handle_irq_event_percpu+0x60/0x278)
[  103.274467]  r10:c06e6e9c r9:00000000 r8:00000000 r7:ee007000 r6:00000026 r5:ee04a660
[  103.282278]  r4:ee209000
[  103.284803] [<c00669c8>] (handle_irq_event_percpu) from [<c0066c84>] (handle_irq_event+0x44/0x64)
[  103.293649]  r10:ee008000 r9:c06b1ef8 r8:00000015 r7:ee007000 r6:ee209000 r5:ee04a660
[  103.301461]  r4:ee04a600
[  103.303986] [<c0066c40>] (handle_irq_event) from [<c0069c60>] (handle_level_irq+0xcc/0x144)
[  103.312311]  r6:00002000 r5:ee04a660 r4:ee04a600 r3:00020000
[  103.317959] [<c0069b94>] (handle_level_irq) from [<c006601c>] (generic_handle_irq+0x34/0x44)
[  103.326372]  r5:ee004450 r4:00000026
[  103.329939] [<c0065fe8>] (generic_handle_irq) from [<c021ecdc>] (combiner_handle_cascade_irq+0x9c/0x108)
[  103.339392]  r4:c06cd974 r3:000000a0
[  103.342957] [<c021ec40>] (combiner_handle_cascade_irq) from [<c006601c>] (generic_handle_irq+0x34/0x44)
[  103.352326]  r8:00000001 r7:00000000 r6:00000015 r5:00000000 r4:00000015 r3:c021ec40
[  103.360057] [<c0065fe8>] (generic_handle_irq) from [<c0066330>] (__handle_domain_irq+0x84/0xf0)
[  103.368731]  r4:c06acc54 r3:00000089
[  103.372296] [<c00662ac>] (__handle_domain_irq) from [<c000867c>] (gic_handle_irq+0x38/0x70)
[  103.380622]  r10:c06e7414 r9:f0020000 r8:c06b1ef8 r7:c06b2808 r6:00000015 r5:00000025
[  103.388434]  r4:f002000c r3:c06b1ef8
[  103.392002] [<c0008644>] (gic_handle_irq) from [<c0013240>] (__irq_svc+0x40/0x74)
[  103.399459] Exception stack(0xc06b1ef8 to 0xc06b1f40)
[  103.404495] 1ee0:                                                       00000001 00000000
[  103.412656] 1f00: 00000000 c00206c0 c06b2518 c04dd3a4 00000000 00000000 c06addc0 00000001
[  103.420816] 1f20: c06e7414 c06b1f4c c06b1f50 c06b1f40 c000f82c c000f830 60000053 ffffffff
[  103.428970]  r9:00000001 r8:c06addc0 r7:c06b1f2c r6:ffffffff r5:60000053 r4:c000f830
[  103.436706] [<c000f7f0>] (arch_cpu_idle) from [<c005b6dc>] (cpu_startup_entry+0x318/0x4ec)
[  103.444951] [<c005b3c4>] (cpu_startup_entry) from [<c04cccf4>] (rest_init+0x8c/0x90)
[  103.452667]  r7:ffffffff
[  103.455192] [<c04ccc68>] (rest_init) from [<c067bcfc>] (start_kernel+0x3a0/0x3ac)
[  103.462648]  r4:c06b2614 r3:c06b0000
[  103.466215] [<c067b95c>] (start_kernel) from [<40008070>] (0x40008070)
[  103.472721] Code: e3130002 0affffaf eb098137 eaffffad (e7f001f2) 
[  103.478798] ---[ end trace 1a71dac0bfe14c2c ]---
[  103.483396] Kernel panic - not syncing: Fatal exception in interrupt
[  103.489735] CPU2: stopping
[  103.492427] CPU: 2 PID: 0 Comm: swapper/2 Tainted: G      D W       4.0.0-rc5-debug+ #4
[  103.500407] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[  103.506482] Backtrace: 
[  103.508925] [<c0012484>] (dump_backtrace) from [<c001269c>] (show_stack+0x18/0x1c)
[  103.516465]  r6:c06cd554 r5:ffffffff r4:00000000 r3:dc8ba200
[  103.522115] [<c0012684>] (show_stack) from [<c04d1d18>] (dump_stack+0x88/0xc8)
[  103.529318] [<c04d1c90>] (dump_stack) from [<c0014894>] (handle_IPI+0x1c8/0x2c4)
[  103.536689]  r6:c06acc54 r5:c06acc54 r4:00000005 r3:ee0b0000
[  103.542336] [<c00146cc>] (handle_IPI) from [<c00086b0>] (gic_handle_irq+0x6c/0x70)
[  103.549883]  r9:f0028000 r8:ee0b1f48 r7:c06b2808 r6:fffffff5 r5:00000005 r4:f002800c
[  103.557614] [<c0008644>] (gic_handle_irq) from [<c0013240>] (__irq_svc+0x40/0x74)
[  103.565074] Exception stack(0xee0b1f48 to 0xee0b1f90)
[  103.570112] 1f40:                   00000001 00000000 00000000 c00206c0 c06b2518 c04dd3a4
[  103.578272] 1f60: 00000000 00000000 c06addc0 00000001 c06e7414 ee0b1f9c ee0b1fa0 ee0b1f90
[  103.586428] 1f80: c000f82c c000f830 600f0053 ffffffff
[  103.591460]  r9:00000001 r8:c06addc0 r7:ee0b1f7c r6:ffffffff r5:600f0053 r4:c000f830
[  103.599193] [<c000f7f0>] (arch_cpu_idle) from [<c005b6dc>] (cpu_startup_entry+0x318/0x4ec)
[  103.607437] [<c005b3c4>] (cpu_startup_entry) from [<c00144d0>] (secondary_start_kernel+0xf4/0x100)
[  103.616371]  r7:c06e90c0
[  103.618895] [<c00143dc>] (secondary_start_kernel) from [<40008744>] (0x40008744)
[  103.626267]  r4:6e09006a r3:c000872c
[  103.629827] CPU3: stopping
[  103.632522] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G      D W       4.0.0-rc5-debug+ #4
[  103.640502] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[  103.646577] Backtrace: 
[  103.649019] [<c0012484>] (dump_backtrace) from [<c001269c>] (show_stack+0x18/0x1c)
[  103.656560]  r6:c06cd554 r5:ffffffff r4:00000000 r3:dc8ba200
[  103.662210] [<c0012684>] (show_stack) from [<c04d1d18>] (dump_stack+0x88/0xc8)
[  103.669412] [<c04d1c90>] (dump_stack) from [<c0014894>] (handle_IPI+0x1c8/0x2c4)
[  103.676784]  r6:c06acc54 r5:c06acc54 r4:00000005 r3:ee0b2000
[  103.682431] [<c00146cc>] (handle_IPI) from [<c00086b0>] (gic_handle_irq+0x6c/0x70)
[  103.689977]  r9:f002c000 r8:ee0b3f48 r7:c06b2808 r6:fffffff5 r5:00000005 r4:f002c00c
[  103.697709] [<c0008644>] (gic_handle_irq) from [<c0013240>] (__irq_svc+0x40/0x74)
[  103.705169] Exception stack(0xee0b3f48 to 0xee0b3f90)
[  103.710207] 3f40:                   00000001 00000000 00000000 c00206c0 c06b2518 c04dd3a4
[  103.718366] 3f60: 00000000 00000000 c06addc0 00000001 c06e7414 ee0b3f9c ee0b3fa0 ee0b3f90
[  103.726523] 3f80: c000f82c c000f830 60070053 ffffffff
[  103.731554]  r9:00000001 r8:c06addc0 r7:ee0b3f7c r6:ffffffff r5:60070053 r4:c000f830
[  103.739288] [<c000f7f0>] (arch_cpu_idle) from [<c005b6dc>] (cpu_startup_entry+0x318/0x4ec)
[  103.747532] [<c005b3c4>] (cpu_startup_entry) from [<c00144d0>] (secondary_start_kernel+0xf4/0x100)
[  103.756466]  r7:c06e90c0
[  103.758990] [<c00143dc>] (secondary_start_kernel) from [<40008744>] (0x40008744)
[  103.766362]  r4:6e09006a r3:c000872c
[  103.769922] CPU1: stopping
[  103.772616] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G      D W       4.0.0-rc5-debug+ #4
[  103.780597] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[  103.786672] Backtrace: 
[  103.789114] [<c0012484>] (dump_backtrace) from [<c001269c>] (show_stack+0x18/0x1c)
[  103.796655]  r6:c06cd554 r5:ffffffff r4:00000000 r3:dc8ba200
[  103.802305] [<c0012684>] (show_stack) from [<c04d1d18>] (dump_stack+0x88/0xc8)
[  103.809507] [<c04d1c90>] (dump_stack) from [<c0014894>] (handle_IPI+0x1c8/0x2c4)
[  103.816879]  r6:c06acc54 r5:c06acc54 r4:00000005 r3:ee0ae000
[  103.822526] [<c00146cc>] (handle_IPI) from [<c00086b0>] (gic_handle_irq+0x6c/0x70)
[  103.830073]  r9:f0024000 r8:ee0aff48 r7:c06b2808 r6:fffffff5 r5:00000005 r4:f002400c
[  103.837804] [<c0008644>] (gic_handle_irq) from [<c0013240>] (__irq_svc+0x40/0x74)
[  103.845264] Exception stack(0xee0aff48 to 0xee0aff90)
[  103.850302] ff40:                   00000001 00000000 00000000 c00206c0 c06b2518 c04dd3a4
[  103.858461] ff60: 00000000 00000000 c06addc0 00000001 c06e7414 ee0aff9c ee0affa0 ee0aff90
[  103.866618] ff80: c000f82c c000f830 600f0053 ffffffff
[  103.871650]  r9:00000001 r8:c06addc0 r7:ee0aff7c r6:ffffffff r5:600f0053 r4:c000f830
[  103.879383] [<c000f7f0>] (arch_cpu_idle) from [<c005b6dc>] (cpu_startup_entry+0x318/0x4ec)
[  103.887628] [<c005b3c4>] (cpu_startup_entry) from [<c00144d0>] (secondary_start_kernel+0xf4/0x100)
[  103.896561]  r7:c06e90c0
[  103.899085] [<c00143dc>] (secondary_start_kernel) from [<40008744>] (0x40008744)
[  103.906457]  r4:6e09006a r3:c000872c
[  103.910021] ---[ end Kernel panic - not syncing: Fatal exception in interrupt
My guess is that the pagefault is triggered by fw loading, but I have to triage this further.

Tuxuser
Posts: 5
Joined: Sat Feb 07, 2015 10:06 am
languages_spoken: english, german
ODROIDs: ODROID C1
Contact:

Re: Playing with upstream

Unread post by Tuxuser » Sat Apr 04, 2015 12:00 am

Hey,

Thanks for the work on upstream.

Can you give a word about support for C1? Thanks.

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

Re: Playing with upstream

Unread post by LiquidAcid » Sat Apr 04, 2015 12:21 am

Tuxuser wrote:Can you give a word about support for C1? Thanks.
I've adjusted the thread title to make it more clear that this is about Exynos4412-based devices.

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

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Wed Apr 15, 2015 11:43 pm

Again the usual rebasing:
- odroid-3.19.y on stable/linux-3.19.4
- odroid-4.0.y on stable/linux-4.0

My guess is that we're going to see a 3.19.5 before 3.19.y goes EOL.

I'm currently working on exposing more pixel formats in drm/exynos, in particular what the mixer and the VP (video processor) gives us. Plan is to expose NV12/NV21 together with its MT (tiled) variants and use this directly to display video data (I'm working on a simple exynos backend for mpv).

This would drastically reduce bandwidth requierements when playing back e.g. 1080p material. The current (accelerated) decoding pipeline (in Kodi) is setup like this:
MFC -> FIMC -> EGL texture -> framebuffer

I'd rather have this:
MFC -> framebuffer

Or in the unaccelerated path:
sw decoder (NV12/21) -> framebuffer

The recent additional of FB modifiers (currently only used by the i915 DRM) should enable us to add the MT variants without resorting to pixel format hacks (which were previously present).

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

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Sun Apr 26, 2015 12:48 am

I've written a small guide on the linux-exynos wiki describing on how to run my tree on the X2. It should be easily adapted to the U2/U3 just by using the corresponding DTB. In fact one can probably modify the boot script so that it works for both boards (since u-boot exposes the board name).

marlemion
Posts: 232
Joined: Sun Mar 31, 2013 7:33 pm
languages_spoken: english
ODROIDs: Odroid U2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by marlemion » Sun Apr 26, 2015 5:21 pm

Thanks for wrapping this up. Just a short question: I saw several mali related commits in your tree. Does it mean that you did some work on supporting mali already? In any case, thanks a lot for your work!

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

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Sun Apr 26, 2015 8:04 pm

marlemion wrote:Does it mean that you did some work on supporting mali already?
No, I just enjoy doing random commits with Mali in the description.

marlemion
Posts: 232
Joined: Sun Mar 31, 2013 7:33 pm
languages_spoken: english
ODROIDs: Odroid U2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by marlemion » Sun Apr 26, 2015 9:05 pm

Well, it could have meant that you applied mali patches without doing further testing/enabling. E.g. I still don't know anything about the current work, especially your work as regards mali from your comment yet. So appyling patches does not mean that actual work happened or anything has been enabled yet. No need for being pseudo-ironic.

User avatar
meveric
Posts: 9597
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 » Sun Apr 26, 2015 9:30 pm

if you check the page right on top it says:
Support

This feature matrix shows hardware support of the ODROID-X2 when using the kernel fork by Tobias Jakobi (currently based on vanilla-3.19.y).

Code: Select all

Feature 	                    Forked Linux Kernel
Serial 	                     Yes
USB 	                        Yes
Network 	                    Yes
MMC 	                        Yes
eMMC 	                       Yes
HDMI 	                       Yes
Audio 	                      Yes
IOMMU 	                      ? (needs testing)
CPUFreq 	                    Yes (including Boost)
G2D (2D acceleration)          Yes
Mali (3D Acceleration)         Yes
MFC (Video encoding/decoding)  No/Broken 
So for me that reads, that execpt from MFC and IOMMU everything seems to work..
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.

marlemion
Posts: 232
Joined: Sun Mar 31, 2013 7:33 pm
languages_spoken: english
ODROIDs: Odroid U2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by marlemion » Sun Apr 26, 2015 10:00 pm

Thanks. I missed that. Possibly because I wasn't expecting that mali work has even been finished already. Outstanding!

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

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Sun Apr 26, 2015 10:12 pm

marlemion wrote:No need for being pseudo-ironic.
Not being pseudo-ironic at all. I was just fully-ironic.

marlemion
Posts: 232
Joined: Sun Mar 31, 2013 7:33 pm
languages_spoken: english
ODROIDs: Odroid U2
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by marlemion » Mon Apr 27, 2015 1:42 am

LiquidAcid wrote:
marlemion wrote:No need for being pseudo-ironic.
Not being pseudo-ironic at all. I was just fully-ironic.
http://www.thefreedictionary.com/pseudo

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

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Mon Apr 27, 2015 2:51 am

marlemion wrote:
LiquidAcid wrote:
marlemion wrote:No need for being pseudo-ironic.
Not being pseudo-ironic at all. I was just fully-ironic.
http://www.thefreedictionary.com/pseudo
Yep, you should probably read that one.

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

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Wed May 06, 2015 7:19 am

Being the ironic being I am, I ironed out some more issues:
- odroid-3.19.y is dead, which means that I'm not planning to rebase it onto stable-3.19.6
- odroid-4.0.y is now the default branch, currently based on stable-4.0.1 (*)
- odroid-4.1.y is the new development branch, currently based on torvald's rc2 (**)

(*) If you plan to use the armsoc DDX with this branch, then be aware that this might no longer work due to massive changes in DRM code. prahal has done some adjustments to the plane configuration code here. Not tested by me, since I don't use X11.
(**) At this moment the branch should properly compile (tested with this config).

I also fixed a nasty bug in the guide on the linux-exynos Wiki.
Last edited by LiquidAcid on Thu Jun 11, 2015 9:07 pm, edited 1 time in total.

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

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Thu May 21, 2015 4:27 am

Some boring updates:
- odroid-3.19.y was removed (and it's EOL by now)
- odroid-4.0.y rebased on stable-4.0.4
- odroid-4.1.y rebased on torvalds's rc4

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 » Fri Jun 05, 2015 10:13 pm

Hi, i've compiled the 4.0.1 and 4.1 rc4 kernels (using for base the vanilla config provided on https://github.com/tobiasjakobi/odroid- ... de/system/), the "Support for hot-pluggable CPUs" is enabled but seems that i've always 4 cpu online (using ondemand, conservative or powersave governor).
With 3.8.13.30 kernel with idle system only 2 cpu are on.

I've to enable something else to make the hot-pluggable CPUs works?

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

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Fri Jun 05, 2015 10:50 pm

gulp wrote:I've to enable something else to make the hot-pluggable CPUs works?

Code: Select all

for arg in /sys/devices/system/cpu/cpu[1-9]*; do echo -n 0 > $arg/online; done

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 » Fri Jun 05, 2015 11:59 pm

LiquidAcid wrote:
gulp wrote:I've to enable something else to make the hot-pluggable CPUs works?

Code: Select all

for arg in /sys/devices/system/cpu/cpu[1-9]*; do echo -n 0 > $arg/online; done
ok, this is for disabling them manually, but usually the kernel (with conservative/ondemand governor) take cpu on/off automatically, so if the system is idle there is 1 cpu active, under full load all 4 cpu are online.
(This is not an important feature, but i ask only to know if is a my fault on config or a kernel problem)

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

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Sat Jun 06, 2015 12:30 am

No cpufreq governor in the mainline Linux kernel takes cores offline, neither the conservative nor ondemand does. What you probably mean is the DVFS hotplug driver, which was never submitted to mainline anyway.

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 » Sat Jun 06, 2015 3:06 am

LiquidAcid wrote:No cpufreq governor in the mainline Linux kernel takes cores offline, neither the conservative nor ondemand does. What you probably mean is the DVFS hotplug driver, which was never submitted to mainline anyway.
Ok, thanks, now is clear what i'm "missing" :)

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

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Thu Jun 11, 2015 8:35 pm

The usual rebasing:
- odroid-4.0.y rebased on stable-4.0.5
- odroid-4.1.y rebased on torvalds's rc7

I applied some more Mali cleanups and also added the option to disable fbdev emulation to odroid-4.1.y.

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

Re: Playing with upstream (Exynos4412)

Unread post by OverSun » Thu Jun 11, 2015 8:44 pm

The day I find a new place to live I'll start looking at MFC, if it is not fixed already.
I hope soon.

daviessm
Posts: 110
Joined: Thu Jul 25, 2013 2:14 am
languages_spoken: English, German
ODROIDs: X2, XU4
Location: Belfast, UK
Contact:

Re: Playing with upstream

Unread post by daviessm » Thu Jun 18, 2015 2:56 am

LiquidAcid wrote:Haven't had too much success with the USB stuff. With cpu_idle disabled, I still get this from eth:

Code: Select all

[  115.530000] ------------[ cut here ]------------
[  115.530000] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:264 dev_watchdog+0x25c/0x27c()
[  115.530000] NETDEV WATCHDOG: eth0 (smsc95xx): transmit queue 0 timed out
[  115.530000] Modules linked in: bridge stp llc usb_storage bnep rfcomm btusb bluetooth s5p_mfc videobuf2_dma_contig videobuf2_memops videobuf2_core
[  115.530000] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.13.3+ #27
[  115.530000] Backtrace: 
[  115.530000] [<c0012018>] (dump_backtrace+0x0/0x10c) from [<c00121b4>] (show_stack+0x18/0x1c)
[  115.530000]  r6:00000108 r5:00000009 r4:00000000 r3:00000000
[  115.530000] [<c001219c>] (show_stack+0x0/0x1c) from [<c041078c>] (dump_stack+0x84/0xd0)
[  115.530000] [<c0410708>] (dump_stack+0x0/0xd0) from [<c002172c>] (warn_slowpath_common+0x6c/0x90)
[  115.530000]  r4:c057fdc0 r3:c057e000
[  115.530000] [<c00216c0>] (warn_slowpath_common+0x0/0x90) from [<c00217f4>] (warn_slowpath_fmt+0x38/0x40)
[  115.530000]  r8:c05800c0 r7:e701ca14 r6:e71f7b00 r5:e701c800 r4:00000000
[  115.530000] [<c00217bc>] (warn_slowpath_fmt+0x0/0x40) from [<c03b36a4>] (dev_watchdog+0x25c/0x27c)
[  115.530000]  r3:e701c800 r2:c0526ef0
[  115.530000] [<c03b3448>] (dev_watchdog+0x0/0x27c) from [<c002b92c>] (call_timer_fn.isra.27+0x2c/0x8c)
[  115.530000] [<c002b900>] (call_timer_fn.isra.27+0x0/0x8c) from [<c002bb0c>] (run_timer_softirq+0x180/0x208)
[  115.530000]  r7:00200200 r6:00000000 r5:c057fe48 r4:c05b2500
[  115.530000] [<c002b98c>] (run_timer_softirq+0x0/0x208) from [<c0025850>] (__do_softirq+0xf4/0x228)
[  115.530000] [<c002575c>] (__do_softirq+0x0/0x228) from [<c0025cf8>] (irq_exit+0xa8/0xf8)
[  115.530000] [<c0025c50>] (irq_exit+0x0/0xf8) from [<c000f33c>] (handle_IRQ+0x44/0x9c)
[  115.530000]  r4:c057be40 r3:00000142
[  115.530000] [<c000f2f8>] (handle_IRQ+0x0/0x9c) from [<c0008560>] (gic_handle_irq+0x3c/0x70)
[  115.530000]  r6:c057ff28 r5:c0586878 r4:f881000c r3:000000a0
[  115.530000] [<c0008524>] (gic_handle_irq+0x0/0x70) from [<c0012cc0>] (__irq_svc+0x40/0x70)
[  115.530000] Exception stack(0xc057ff28 to 0xc057ff70)
[  115.530000] ff20:                   c070d6a0 00000000 0009edbe 00000000 c05864a0 c0586448
[  115.530000] ff40: c05b14e8 00000001 c05b14e8 c057e000 c0417dcc c057ff7c c057ff80 c057ff70
[  115.530000] ff60: c000f6d0 c000f6d4 60000053 ffffffff
[  115.530000]  r7:c057ff5c r6:ffffffff r5:60000053 r4:c000f6d4
[  115.530000] [<c000f6a4>] (arch_cpu_idle+0x0/0x38) from [<c0059c00>] (cpu_startup_entry+0x68/0x13c)
[  115.530000] [<c0059b98>] (cpu_startup_entry+0x0/0x13c) from [<c040d8c0>] (rest_init+0x78/0x90)
[  115.530000]  r7:c057147c r3:c0418180
[  115.530000] [<c040d848>] (rest_init+0x0/0x90) from [<c0552a5c>] (start_kernel+0x2a4/0x2e8)
[  115.530000]  r4:c0586540 r3:c057e000
[  115.530000] [<c05527b8>] (start_kernel+0x0/0x2e8) from [<40008070>] (0x40008070)
[  115.530000] ---[ end trace a8234d1b2a22e755 ]---
Hi LiquidAcid, do you recall what it was that fixed the above backtrace? I'm seeing this on 4.0.y now:

Code: Select all

Jun 17 08:29:59 bang kernel: [124136.741496] ------------[ cut here ]------------
Jun 17 08:29:59 bang kernel: [124136.741671] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:303 dev_watchdog+0x258/0x264()
Jun 17 08:29:59 bang kernel: [124136.741728] NETDEV WATCHDOG: eth0 (smsc95xx): transmit queue 0 timed out
Jun 17 08:29:59 bang kernel: [124136.741767] Modules linked in: smsc95xx
Jun 17 08:29:59 bang kernel: [124136.741858] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W       4.0.5+ #3
Jun 17 08:29:59 bang kernel: [124136.741904] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
Jun 17 08:29:59 bang kernel: [124136.741944] Backtrace:
Jun 17 08:29:59 bang kernel: [124136.742059] [<c00123a4>] (dump_backtrace) from [<c00125bc>] (show_stack+0x18/0x1c)
Jun 17 08:29:59 bang kernel: [124136.742103]  r6:c0bd1a9c r5:00000000 r4:c0c95f20 r3:dc8ba205
Jun 17 08:29:59 bang kernel: [124136.742247] [<c00125a4>] (show_stack) from [<c0970e48>] (dump_stack+0x98/0xd8)
Jun 17 08:29:59 bang kernel: [124136.742341] [<c0970db0>] (dump_stack) from [<c002dae8>] (warn_slowpath_common+0x88/0xb8)
Jun 17 08:29:59 bang kernel: [124136.742383]  r5:0000012f r4:c0c6fd68
Jun 17 08:29:59 bang kernel: [124136.742473] [<c002da60>] (warn_slowpath_common) from [<c002db50>] (warn_slowpath_fmt+0x38/0x40)
Jun 17 08:29:59 bang kernel: [124136.742516]  r8:c0c70100 r7:ed138a54 r6:ee280100 r5:ed138800 r4:00000000
Jun 17 08:29:59 bang kernel: [124136.742649] [<c002db1c>] (warn_slowpath_fmt) from [<c06e0c64>] (dev_watchdog+0x258/0x264)
Jun 17 08:29:59 bang kernel: [124136.742690]  r3:ed138800 r2:c0bd1ab4
Jun 17 08:29:59 bang kernel: [124136.742793] [<c06e0a0c>] (dev_watchdog) from [<c007c398>] (call_timer_fn.isra.32+0x2c/0xa0)
Jun 17 08:29:59 bang kernel: [124136.742835]  r10:c0c70100 r9:00000000 r8:c0c6fe00 r7:ed138800 r6:c06e0a0c r5:00000101
Jun 17 08:29:59 bang kernel: [124136.742941]  r4:ed138a74
Jun 17 08:29:59 bang kernel: [124136.743015] [<c007c36c>] (call_timer_fn.isra.32) from [<c007c5dc>] (run_timer_softirq+0x1d0/0x27c)
Jun 17 08:29:59 bang kernel: [124136.743056]  r6:c06e0a0c r5:c0d13680 r4:ed138a74
Jun 17 08:29:59 bang kernel: [124136.743162] [<c007c40c>] (run_timer_softirq) from [<c0031040>] (__do_softirq+0x118/0x264)
Jun 17 08:29:59 bang kernel: [124136.743204]  r10:c0c70080 r9:00000001 r8:c0c6e000 r7:40000001 r6:00000101 r5:c0c70084
Jun 17 08:29:59 bang kernel: [124136.743308]  r4:000000a0
Jun 17 08:29:59 bang kernel: [124136.743383] [<c0030f28>] (__do_softirq) from [<c0031468>] (irq_exit+0xb8/0x120)
Jun 17 08:29:59 bang kernel: [124136.743425]  r10:c0c6ff58 r9:f0020000 r8:ee008000 r7:00000001 r6:00000000 r5:00000000
Jun 17 08:29:59 bang kernel: [124136.743529]  r4:c0c6acb0
Jun 17 08:29:59 bang kernel: [124136.743628] [<c00313b0>] (irq_exit) from [<c006da24>] (__handle_domain_irq+0x68/0xb8)
Jun 17 08:29:59 bang kernel: [124136.743670]  r4:c0c6acb0 r3:00000089
Jun 17 08:29:59 bang kernel: [124136.743761] [<c006d9bc>] (__handle_domain_irq) from [<c00085dc>] (gic_handle_irq+0x38/0x70)
Jun 17 08:29:59 bang kernel: [124136.743803]  r8:c0c6ff00 r7:c0c76058 r6:0000000c r5:0000001c r4:f002000c r3:c0c6ff00
Jun 17 08:29:59 bang kernel: [124136.743926] [<c00085a4>] (gic_handle_irq) from [<c0013180>] (__irq_svc+0x40/0x74)
Jun 17 08:29:59 bang kernel: [124136.743975] Exception stack(0xc0c6ff00 to 0xc0c6ff48)
Jun 17 08:29:59 bang kernel: [124136.744038] ff00: 00000001 00000000 00000000 c0020620 c0c6e000 c0c7550c 00000000 00000000
Jun 17 08:29:59 bang kernel: [124136.744101] ff20: 00000001 c0c75570 c0c6ff58 c0c6ff54 c0c6ff58 c0c6ff48 c000f724 c000f728
Jun 17 08:29:59 bang kernel: [124136.744147] ff40: 600e0053 ffffffff
Jun 17 08:29:59 bang kernel: [124136.744187]  r9:c0c75570 r8:00000001 r7:c0c6ff34 r6:ffffffff r5:600e0053 r4:c000f728
Jun 17 08:29:59 bang kernel: [124136.744348] [<c000f6e8>] (arch_cpu_idle) from [<c005f8c0>] (cpu_startup_entry+0x288/0x2f4)
Jun 17 08:29:59 bang kernel: [124136.744428] [<c005f638>] (cpu_startup_entry) from [<c096a9d4>] (rest_init+0x8c/0x90)
Jun 17 08:29:59 bang kernel: [124136.744469]  r7:ffffffff
Jun 17 08:29:59 bang kernel: [124136.744566] [<c096a948>] (rest_init) from [<c0c24d2c>] (start_kernel+0x3d0/0x3dc)
Jun 17 08:29:59 bang kernel: [124136.744608]  r4:c0c75e58 r3:c0c6e000
Jun 17 08:29:59 bang kernel: [124136.744694] [<c0c2495c>] (start_kernel) from [<40008070>] (0x40008070)
Jun 17 08:29:59 bang kernel: [124136.744739] ---[ end trace a293e305c7eff08a ]---
Jun 17 08:29:59 bang kernel: [124136.748735] smsc95xx 1-2.1.1:1.0 eth0: kevent 0 may have been dropped
Jun 17 08:29:59 bang kernel: [124136.748889] smsc95xx 1-2.1.1:1.0 eth0: kevent 0 may have been dropped
Jun 17 08:29:59 bang kernel: [124136.748951] smsc95xx 1-2.1.1:1.0 eth0: kevent 0 may have been dropped
Jun 17 08:29:59 bang kernel: [124136.749301] smsc95xx 1-2.1.1:1.0 eth0: kevent 0 may have been dropped
Jun 17 08:29:59 bang kernel: [124136.749703] smsc95xx 1-2.1.1:1.0 eth0: kevent 0 may have been dropped
Jun 17 08:29:59 bang kernel: [124136.750079] smsc95xx 1-2.1.1:1.0 eth0: kevent 0 may have been dropped
Jun 17 08:29:59 bang kernel: [124136.872185] smsc95xx 1-2.1.1:1.0 eth0: kevent 0 may have been dropped
Jun 17 08:30:01 bang cron[8557]: (root) CMD (nice /usr/bin/php /var/www/steev.me.uk/htdocs/serverstats/update.php >/dev/null 2>&1)
Jun 17 08:30:01 bang cron[8556]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons)
Jun 17 08:30:02 bang kernel: [124139.872621] smsc95xx 1-2.1.1:1.0 eth0: kevent 0 may have been dropped
I have turned turbo_mode to N based on suggestions around the web to fix the "smsc95xx 1-1.1:1.0: eth0: kevent 2 may have been dropped" line that comes up in syslog a lot.

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

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Fri Jun 19, 2015 8:17 pm

This "error" (which is only a warning) was totally unrelated to the real issue back then. Also the "kevent 0 may have been dropped" message are harmless since the overlying network layer initiates a retransmit when this happens.

I don't see the warnings that often, so I never bothered to tweak network settings. If you really care you should post this on linux-samsung-soc or even on the kernel bugtracker (I wouldn't be surprised though if such a bug report already exists).

daviessm
Posts: 110
Joined: Thu Jul 25, 2013 2:14 am
languages_spoken: English, German
ODROIDs: X2, XU4
Location: Belfast, UK
Contact:

Re: Playing with upstream (Exynos4412)

Unread post by daviessm » Fri Jun 19, 2015 8:28 pm

Interesting, I saw it on the 17th and immediately afterwards the network interface stopped responding and the system needed a reboot to get it back. Have you seen anything similar?

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

Re: Playing with upstream (Exynos4412)

Unread post by Panzerknacker » Fri Jun 19, 2015 8:47 pm

Yes, have seen this twice since March on a continuously running U3. Needs reboot to get ethernet up again.

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

Re: Playing with upstream (Exynos4412)

Unread post by LiquidAcid » Fri Jun 19, 2015 11:01 pm

Well, at least I didn't encounter it, but I also don't let the board run more than like 4hrs or so. You should make some noise on the ml then I guess.

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 1:33 am

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.

Post Reply

Return to “The Ideas”

Who is online

Users browsing this forum: No registered users and 1 guest