Kernel 5.0 development thread

MastaG
Posts: 298
Joined: Mon Aug 26, 2013 6:05 pm
languages_spoken: english
Has thanked: 13 times
Been thanked: 3 times
Contact:

Re: Kernel 5.0 development thread

Unread post by MastaG » Tue Oct 29, 2019 10:43 pm

@memeka, unfirtnately the above 3 patches don't fix the emmc v5 issue.
But after debugging I also found it's the exact same reason why I cannot resume from suspend.

Code: Select all

[  533.354031] mmc0: tuning execution failed: -5                                
[  533.356912] mmc0: error -5 doing runtime resume                              
[  533.361753] blk_update_request: I/O error, dev mmcblk0, sector 28645880 op 00
[  533.372203] Read-error on swap-device (179:16:28645888)                      
[  533.377471] Read-error on swap-device (179:16:27204664)                      
[  533.397829] Read-error on swap-device (179:16:28776728)                      
[  533.440585] Read-error on swap-device (179:16:27729264)                      
[  533.444393] Read-error on swap-device (179:16:28907752)                      
[  533.484476] Read-error on swap-device (179:16:27466048)                      
[  533.497455] Read-error on swap-device (179:16:2960968)                       
[  533.504479] Read-error on swap-device (179:16:28776688)                      
[  533.508266] Read-error on swap-device (179:16:28776696)                      
[  533.513547] Read-error on swap-device (179:16:26811408)                      
[  533.518245] Read-error on swap-device (179:16:3352616)                       
[  533.518261] Read-error on swap-device (179:16:3352624)                       
[  533.518272] Read-error on swap-device (179:16:3352632)                       
[  533.518283] Read-error on swap-device (179:16:3352640)                       
[  533.518294] Read-error on swap-device (179:16:3352648)                       
[  533.566942] Read-error on swap-device (179:16:27596976)                      
[  533.572547] systemd-journald[477]: Failed to rotate /var/log/journal/d9da881r
[  533.586305] systemd-journald[477]: Failed to rotate /var/log/journal/d9da881r
[  533.601171] systemd-journald[477]: Failed to write entry (26 items, 727 bytee
[  533.612706] Read-error on swap-device (179:16:1911056)                       
[  533.623028] systemd-journald[477]: Failed to rotate /var/log/journal/d9da881r
[  533.634212] systemd-journald[477]: Failed to rotate /var/log/journal/d9da881r
[  533.654254] systemd-journald[477]: Failed to write entry (9 items, 241 bytesr
[  533.664551] systemd-journald[477]: Failed to rotate /var/log/journal/d9da881r
[  533.666897] Read-error on swap-device (179:16:863792)                        
[  533.676923] systemd-journald[477]: Failed to rotate /var/log/journal/d9da881r
[  534.878018] mmc0: tuning execution failed: -5                                
[  534.880898] mmc0: error -5 whilst initialising MMC card                      
[  535.150026] mmc0: tuning execution failed: -5                                
[  535.152906] mmc0: error -5 whilst initialising MMC card                      
[  535.498013] mmc0: tuning execution failed: -5                                
[  535.500889] mmc0: error -5 whilst initialising MMC card                      
[  535.902015] mmc0: tuning execution failed: -5                                
[  535.904888] mmc0: error -5 whilst initialising MMC card                      
[  539.013191] systemd-journald[477]: Failed to rotate /var/log/journal/d9da881r
[  539.024075] systemd-journald[477]: Failed to rotate /var/log/journal/d9da881r
......
Suspend works fine, but after I turn it on again.. it cannot re-initialize my eMMC again.. so it cant resume my rootfs..

citydweller
Posts: 4
Joined: Mon Mar 18, 2019 2:07 am
languages_spoken: english,german
ODROIDs: XU4, U3
Has thanked: 0
Been thanked: 0
Contact:

Re: Kernel 5.0 development thread

Unread post by citydweller » Mon Nov 04, 2019 12:22 am

MastaG wrote:
Tue Oct 29, 2019 10:43 pm
@memeka, unfirtnately the above 3 patches don't fix the emmc v5 issue.
But after debugging I also found it's the exact same reason why I cannot resume from suspend.

Code: Select all

[  533.354031] mmc0: tuning execution failed: -5                                
[  533.356912] mmc0: error -5 doing runtime resume                              
[  533.361753] blk_update_request: I/O error, dev mmcblk0, sector 28645880 op 00
[  533.372203] Read-error on swap-device (179:16:28645888)                      
[  533.377471] Read-error on swap-device (179:16:27204664)                      
[  533.397829] Read-error on swap-device (179:16:28776728)                      
[  533.440585] Read-error on swap-device (179:16:27729264)                      
[  533.444393] Read-error on swap-device (179:16:28907752)                      
[  533.484476] Read-error on swap-device (179:16:27466048)                      
[  533.497455] Read-error on swap-device (179:16:2960968)                       
[  533.504479] Read-error on swap-device (179:16:28776688)                      
[  533.508266] Read-error on swap-device (179:16:28776696)                      
[  533.513547] Read-error on swap-device (179:16:26811408)                      
[  533.518245] Read-error on swap-device (179:16:3352616)                       
[  533.518261] Read-error on swap-device (179:16:3352624)                       
[  533.518272] Read-error on swap-device (179:16:3352632)                       
[  533.518283] Read-error on swap-device (179:16:3352640)                       
[  533.518294] Read-error on swap-device (179:16:3352648)                       
[  533.566942] Read-error on swap-device (179:16:27596976)                      
[  533.572547] systemd-journald[477]: Failed to rotate /var/log/journal/d9da881r
[  533.586305] systemd-journald[477]: Failed to rotate /var/log/journal/d9da881r
[  533.601171] systemd-journald[477]: Failed to write entry (26 items, 727 bytee
[  533.612706] Read-error on swap-device (179:16:1911056)                       
[  533.623028] systemd-journald[477]: Failed to rotate /var/log/journal/d9da881r
[  533.634212] systemd-journald[477]: Failed to rotate /var/log/journal/d9da881r
[  533.654254] systemd-journald[477]: Failed to write entry (9 items, 241 bytesr
[  533.664551] systemd-journald[477]: Failed to rotate /var/log/journal/d9da881r
[  533.666897] Read-error on swap-device (179:16:863792)                        
[  533.676923] systemd-journald[477]: Failed to rotate /var/log/journal/d9da881r
[  534.878018] mmc0: tuning execution failed: -5                                
[  534.880898] mmc0: error -5 whilst initialising MMC card                      
[  535.150026] mmc0: tuning execution failed: -5                                
[  535.152906] mmc0: error -5 whilst initialising MMC card                      
[  535.498013] mmc0: tuning execution failed: -5                                
[  535.500889] mmc0: error -5 whilst initialising MMC card                      
[  535.902015] mmc0: tuning execution failed: -5                                
[  535.904888] mmc0: error -5 whilst initialising MMC card                      
[  539.013191] systemd-journald[477]: Failed to rotate /var/log/journal/d9da881r
[  539.024075] systemd-journald[477]: Failed to rotate /var/log/journal/d9da881r
......
Suspend works fine, but after I turn it on again.. it cannot re-initialize my eMMC again.. so it cant resume my rootfs..
Even still the same problem.

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

Re: Kernel 5.0 development thread

Unread post by odroid » Mon Nov 04, 2019 9:57 am

Is this issue a "Suspend to Disk" or "Suspend to RAM"?

MastaG
Posts: 298
Joined: Mon Aug 26, 2013 6:05 pm
languages_spoken: english
Has thanked: 13 times
Been thanked: 3 times
Contact:

Re: Kernel 5.0 development thread

Unread post by MastaG » Mon Nov 04, 2019 5:19 pm

I don't know which kind of suspend it uses, it's just the sleep button in Gnome.. it works like memeka says however after powering on again it fails to initialize the MMC controller so it cannot resume the mounted FS.
The same "Error -5" also happens on reboot.

But I believe it only happens with the faster eMMC v5.
It only seems to initialize when I completely power off the board.. wait 10 seconds.. and re-plug power.

So for the record, waking up from suspend and warm reboots should work fine when I'm running from regular sdcard or an older eMMC.

Other than that I'm enjoying the kernel, I'm using it with Fedora 31 for armv7 with Gnome 3.34 and RetroArch, Chromium and Kodi 18.4 running on wayland.

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

Re: Kernel 5.0 development thread

Unread post by memeka » Mon Nov 04, 2019 6:28 pm

it should be suspend to ram

MastaG
Posts: 298
Joined: Mon Aug 26, 2013 6:05 pm
languages_spoken: english
Has thanked: 13 times
Been thanked: 3 times
Contact:

Re: Kernel 5.0 development thread

Unread post by MastaG » Mon Nov 04, 2019 9:06 pm

memeka wrote:
Mon Nov 04, 2019 6:28 pm
it should be suspend to ram
yes but still when waking up from suspend to ram I get the same MMC -5 initialization error as when doing a warm reboot, hence why it locks up.
So suspend is good, it's just that the eMMC v5 is having trouble getting initialized on newer kernels.

citydweller
Posts: 4
Joined: Mon Mar 18, 2019 2:07 am
languages_spoken: english,german
ODROIDs: XU4, U3
Has thanked: 0
Been thanked: 0
Contact:

Re: Kernel 5.0 development thread

Unread post by citydweller » Mon Nov 04, 2019 10:23 pm

[/quote]
So suspend is good, it's just that the eMMC v5 is having trouble getting initialized on newer kernels.
[/quote]
That's my problem, too.

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

Re: Kernel 5.0 development thread

Unread post by memeka » Tue Nov 05, 2019 8:35 am

@MastaG, @citydweller - can you try different kernel versions and see what commit broke emmc v5?
e.g. try mainline 4.18 vs HK 4.18 (does it work on HK 4.18?), then try e.g. mainline 5.0 and zero-in on the offending commit - use exynos_defconfig and reboot to test.

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

Re: Kernel 5.0 development thread

Unread post by memeka » Thu Nov 07, 2019 9:33 am

Updated to rc6 with minor changes

glmark2 scores:

Code: Select all

onscreen (gnome3 mutter):

=======================================================
    glmark2 2014.03+git20150611.fa71af2d
=======================================================
    OpenGL Information
    GL_VENDOR:     ARM
    GL_RENDERER:   Mali-T628
    GL_VERSION:    OpenGL ES 3.1 v1.r12p0-04rel0.f9ea82e6bf7f0bb7544260636f375425
=======================================================
[build] use-vbo=false: FPS: 58 FrameTime: 17.241 ms
[build] use-vbo=true: FPS: 59 FrameTime: 16.949 ms
[texture] texture-filter=nearest: FPS: 60 FrameTime: 16.667 ms
[texture] texture-filter=linear: FPS: 60 FrameTime: 16.667 ms
[texture] texture-filter=mipmap: FPS: 60 FrameTime: 16.667 ms
[shading] shading=gouraud: FPS: 60 FrameTime: 16.667 ms
[shading] shading=blinn-phong-inf: FPS: 60 FrameTime: 16.667 ms
[shading] shading=phong: FPS: 59 FrameTime: 16.949 ms
[shading] shading=cel: FPS: 60 FrameTime: 16.667 ms
[bump] bump-render=high-poly: FPS: 60 FrameTime: 16.667 ms
[bump] bump-render=normals: FPS: 60 FrameTime: 16.667 ms
[bump] bump-render=height: FPS: 60 FrameTime: 16.667 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 60 FrameTime: 16.667 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 60 FrameTime: 16.667 ms
[pulsar] light=false:quads=5:texture=false: FPS: 60 FrameTime: 16.667 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 60 FrameTime: 16.667 ms
[desktop] effect=shadow:windows=4: FPS: 60 FrameTime: 16.667 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 60 FrameTime: 16.667 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 59 FrameTime: 16.949 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 59 FrameTime: 16.949 ms
[ideas] speed=duration: FPS: 60 FrameTime: 16.667 ms
[jellyfish] <default>: FPS: 60 FrameTime: 16.667 ms
[terrain] <default>: FPS: 39 FrameTime: 25.641 ms
[shadow] <default>: FPS: 60 FrameTime: 16.667 ms
[refract] <default>: FPS: 60 FrameTime: 16.667 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 60 FrameTime: 16.667 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 60 FrameTime: 16.667 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 60 FrameTime: 16.667 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 60 FrameTime: 16.667 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 60 FrameTime: 16.667 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 59 FrameTime: 16.949 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 60 FrameTime: 16.667 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 60 FrameTime: 16.667 ms
=======================================================
                                  glmark2 Score: 59
=======================================================


offscreen:

=======================================================
    glmark2 2014.03+git20150611.fa71af2d
=======================================================
    OpenGL Information
    GL_VENDOR:     ARM
    GL_RENDERER:   Mali-T628
    GL_VERSION:    OpenGL ES 3.1 v1.r12p0-04rel0.f9ea82e6bf7f0bb7544260636f375425
=======================================================
[build] use-vbo=false: FPS: 645 FrameTime: 1.550 ms
[build] use-vbo=true: FPS: 1000 FrameTime: 1.000 ms
[texture] texture-filter=nearest: FPS: 1094 FrameTime: 0.914 ms
[texture] texture-filter=linear: FPS: 1083 FrameTime: 0.923 ms
[texture] texture-filter=mipmap: FPS: 1096 FrameTime: 0.912 ms
[shading] shading=gouraud: FPS: 802 FrameTime: 1.247 ms
[shading] shading=blinn-phong-inf: FPS: 806 FrameTime: 1.241 ms
[shading] shading=phong: FPS: 733 FrameTime: 1.364 ms
[shading] shading=cel: FPS: 712 FrameTime: 1.404 ms
[bump] bump-render=high-poly: FPS: 414 FrameTime: 2.415 ms
[bump] bump-render=normals: FPS: 1182 FrameTime: 0.846 ms
[bump] bump-render=height: FPS: 1083 FrameTime: 0.923 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 784 FrameTime: 1.276 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 360 FrameTime: 2.778 ms
[pulsar] light=false:quads=5:texture=false: FPS: 1088 FrameTime: 0.919 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 227 FrameTime: 4.405 ms
[desktop] effect=shadow:windows=4: FPS: 534 FrameTime: 1.873 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 140 FrameTime: 7.143 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 140 FrameTime: 7.143 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 152 FrameTime: 6.579 ms
[ideas] speed=duration: FPS: 205 FrameTime: 4.878 ms
[jellyfish] <default>: FPS: 542 FrameTime: 1.845 ms
[terrain] <default>: FPS: 47 FrameTime: 21.277 ms
[shadow] <default>: FPS: 363 FrameTime: 2.755 ms
[refract] <default>: FPS: 92 FrameTime: 10.870 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 1007 FrameTime: 0.993 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 764 FrameTime: 1.309 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 992 FrameTime: 1.008 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 945 FrameTime: 1.058 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 707 FrameTime: 1.414 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 945 FrameTime: 1.058 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 945 FrameTime: 1.058 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 752 FrameTime: 1.330 ms
=======================================================
                                  glmark2 Score: 678
=======================================================


These users thanked the author memeka for the post (total 2):
odroid (Thu Nov 07, 2019 4:12 pm) • rooted (Sun Nov 10, 2019 11:55 pm)

MastaG
Posts: 298
Joined: Mon Aug 26, 2013 6:05 pm
languages_spoken: english
Has thanked: 13 times
Been thanked: 3 times
Contact:

Re: Kernel 5.0 development thread

Unread post by MastaG » Sun Nov 10, 2019 5:49 am

rc6 seems to crash for me..

Code: Select all

Starting kernel ...

[    0.172278] CPU4: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[    0.204251] CPU5: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[    0.236255] CPU6: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[    0.268255] CPU7: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[    9.519766] samsung-uart 12c00000.serial: IRQ index 1 not found
[    9.520242] samsung-uart 12c10000.serial: IRQ index 1 not found
[    9.520692] samsung-uart 12c20000.serial: IRQ index 1 not found
[    9.575228] samsung-uart 12c30000.serial: IRQ index 1 not found
[    9.595330] panfrost 11800000.gpu: failed to get regulator: -517
[    9.599901] panfrost 11800000.gpu: regulator init failed -517
[    9.606999] Power domain G3D disable failed
[    9.611173] 8<--- cut here ---
[    9.612773] Unhandled fault: imprecise external abort (0x1406) at 0x00000000
[    9.619792] pgd = (ptrval)
[    9.622475] [00000000] *pgd=00000000
[    9.626038] Internal error: : 1406 [#1] PREEMPT SMP THUMB2
[    9.631493] Modules linked in:
[    9.634527] CPU: 6 PID: 1 Comm: swapper/0 Not tainted 5.4.0-rc6+ #4
[    9.640765] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[    9.646837] PC is at kbase_reg_read+0x18/0x70
[    9.651164] LR is at kbase_backend_gpuprops_get+0x11/0x15c
[    9.656623] pc : [<c0629024>]    lr : [<c0629229>]    psr: 40000033
[    9.662862] sp : ee0fbca8  ip : a6aaaaab  fp : ee3f9c60
[    9.668060] r10: c0ca2e48  r9 : ed014000  r8 : c4009110
[    9.673260] r7 : 00000000  r6 : 00000000  r5 : 00000000  r4 : ed014000
[    9.679760] r3 : f1f58000  r2 : 00000000  r1 : 00000000  r0 : 00001590
[    9.686261] Flags: nZcv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb  Segment none
[    9.693541] Control: 50c5387d  Table: 4000406a  DAC: 00000051
[    9.699257] Process swapper/0 (pid: 1, stack limit = 0x(ptrval))
[    9.705237] Stack: (0xee0fbca8 to 0xee0fc000)
[    9.709571] bca0:                   c0a50050 c0a50050 c0a4ffd0 ed014ff0 ed014000 ee0fbce4
[    9.717722] bcc0: ed84c000 c0629229 ed014ff0 ed014000 ed014ff0 ed84c000 c4009110 c061403f
[    9.725867] bce0: 00000001 ff800000 c10445a8 ee0fbce0 f1f54000 ed862028 c0fde840 00000000
[    9.734013] bd00: c0fde840 f1f53000 c0007c78 0000065f f1f52fff ffe00000 aaaaaaab c2c89a00
[    9.742159] bd20: fffff000 c02379a1 f0800000 00001000 00000022 c2c89a00 00000cc0 ffffffff
[    9.750304] bd40: 00002cc2 00000001 ee3f9c60 c0224c0d c10445a8 c2c89c80 00000001 c0227305
[    9.758449] bd60: ff800000 ffffffff 00000cc0 c0628e81 c0ca49e8 c0cf4838 00000cc0 00000000
[    9.766594] bd80: ffffffff c0f04f8c 18711a00 00000000 ed014000 ed014ff0 ed84c000 c4009110
[    9.774740] bda0: ed014000 c0614199 c2c89980 c063e697 c0ff4ba8 00000000 ed014000 000016a4
[    9.782886] bdc0: ed84c000 c4009110 c2c89980 c0ca2e48 ee3f9c60 c062914f 000e0000 ed014000
[    9.791031] bde0: 00000000 c061f96d 00000000 c400914c c400914c ed84c010 00000000 00000000
[    9.799177] be00: ed84c010 c0f9f9a8 00000000 c1060c30 c0f9f9a8 c0ff5130 00000000 c0637b69
[    9.807322] be20: ed84c010 c1060c2c 00000000 c0636245 c0e7d6d4 c0f04f8c ed84c010 ed84c010
[    9.815467] be40: c0f9f9a8 c0f9f9a8 c0fa0050 00000000 c0e57854 c0e7d6d4 0000015c c063651f
[    9.823613] be60: ee0fbe78 00000000 c0e57854 c0e7d6d4 0000015c ed84c010 00000000 c0f9f9a8
[    9.831758] be80: c0fa0050 00000000 c0e57854 c0e7d6d4 0000015c c063679b 00000000 c0f9f9a8
[    9.839904] bea0: ed84c010 c063680d 00000000 c0f9f9a8 c06367a1 c0634cb7 ee2ba06c ee2ba058
[    9.848049] bec0: ee3f9cb4 c0f04f8c c0f9f9a8 c2c8e880 00000000 c0635817 c0ab7610 c0f9f9a8
[    9.856195] bee0: c0e34905 c0f9f9a8 c0e34905 ffffe000 c0e57834 c0636fed c0637701 c0fe3f80
[    9.864340] bf00: c0e34905 c0102c89 00000000 c014eeed c0da4b14 c0e00400 c0cd1d40 00000000
[    9.872486] bf20: 00000006 00000006 00000000 c0c0d1fc c0c040a8 c0c0405c 00000000 efffca3e
[    9.880631] bf40: 00000000 c0f04f8c 00000000 00000006 c1015200 c0f04f8c 00000007 c1015200
[    9.888776] bf60: c1015200 c0e57834 c0e0042d c0e00deb 00000006 00000006 00000000 c0e0042d
[    9.896921] bf80: 00000000 00000000 c09a19ed 00000000 00000000 00000000 00000000 00000000
[    9.905067] bfa0: 00000000 c09a19f3 00000000 c01010f9 00000000 00000000 00000000 00000000
[    9.913213] bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[    9.921358] bfe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000
[    9.929514] [<c0629024>] (kbase_reg_read) from [<c0629229>] (kbase_backend_gpuprops_get+0x11/0x15c)
[    9.938524] [<c0629229>] (kbase_backend_gpuprops_get) from [<c061403f>] (kbase_gpuprops_get_props+0x23/0xe0)
[    9.948313] [<c061403f>] (kbase_gpuprops_get_props) from [<c0614199>] (kbase_gpuprops_set+0x15/0x2b0)
[    9.957496] [<c0614199>] (kbase_gpuprops_set) from [<c062914f>] (kbase_backend_early_init+0x27/0x5c)
[    9.966597] [<c062914f>] (kbase_backend_early_init) from [<c061f96d>] (kbase_platform_device_probe+0x1dd/0x9c0)
[    9.976649] [<c061f96d>] (kbase_platform_device_probe) from [<c0637b69>] (platform_drv_probe+0x2d/0x64)
[    9.986009] [<c0637b69>] (platform_drv_probe) from [<c0636245>] (really_probe+0x18d/0x31c)
[    9.994239] [<c0636245>] (really_probe) from [<c063651f>] (driver_probe_device+0x4f/0x150)
[   10.002471] [<c063651f>] (driver_probe_device) from [<c063679b>] (device_driver_attach+0x37/0x3c)
[   10.011310] [<c063679b>] (device_driver_attach) from [<c063680d>] (__driver_attach+0x6d/0xe4)
[   10.019800] [<c063680d>] (__driver_attach) from [<c0634cb7>] (bus_for_each_dev+0x3f/0x70)
[   10.027946] [<c0634cb7>] (bus_for_each_dev) from [<c0635817>] (bus_add_driver+0xeb/0x15c)
[   10.036092] [<c0635817>] (bus_add_driver) from [<c0636fed>] (driver_register+0x35/0x9c)
[   10.044066] [<c0636fed>] (driver_register) from [<c0102c89>] (do_one_initcall+0x45/0x1e8)
[   10.052213] [<c0102c89>] (do_one_initcall) from [<c0e00deb>] (kernel_init_freeable+0x171/0x1de)
[   10.060877] [<c0e00deb>] (kernel_init_freeable) from [<c09a19f3>] (kernel_init+0x7/0xc8)
[   10.068934] [<c09a19f3>] (kernel_init) from [<c01010f9>] (ret_from_fork+0x11/0x38)
[   10.076465] Exception stack(0xee0fbfb0 to 0xee0fbff8)
[   10.081489] bfa0:                                     00000000 00000000 00000000 00000000
[   10.089640] bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[   10.097785] bfe0: 00000000 00000000 00000000 00000000 00000013 00000000
[   10.104371] Code: f3bf 8f4f f241 5090 (5c23) 4420 
[   10.109158] ---[ end trace fa1870927c5853f0 ]---
[   10.113788] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[   10.121378] CPU2: stopping
[   10.124062] CPU: 2 PID: 0 Comm: swapper/2 Tainted: G      D           5.4.0-rc6+ #4
[   10.131670] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[   10.137758] [<c010f195>] (unwind_backtrace) from [<c010b247>] (show_stack+0xb/0xc)
[   10.145288] [<c010b247>] (show_stack) from [<c09913d7>] (dump_stack+0x67/0x74)
[   10.152477] [<c09913d7>] (dump_stack) from [<c010deef>] (handle_IPI+0x2d7/0x2f8)
[   10.159847] [<c010deef>] (handle_IPI) from [<c0531b6b>] (gic_handle_irq+0x73/0x74)
[   10.167383] [<c0531b6b>] (gic_handle_irq) from [<c0101ae5>] (__irq_svc+0x65/0xac)
[   10.174825] Exception stack(0xee131f60 to 0xee131fa8)
[   10.179850] 1f60: 00000000 00000498 00000002 c0117cc1 ee130000 00000000 c0f04fac c0f04fec
[   10.188003] 1f80: c0e89568 00000000 ee131fb8 00000000 00000004 ee131fb0 c01088e1 c01088e2
[   10.196144] 1fa0: 40000033 ffffffff
[   10.199605] [<c0101ae5>] (__irq_svc) from [<c01088e2>] (arch_cpu_idle+0x32/0x34)
[   10.206983] [<c01088e2>] (arch_cpu_idle) from [<c0144247>] (do_idle+0x197/0x1e4)
[   10.214347] [<c0144247>] (do_idle) from [<c01444a7>] (cpu_startup_entry+0x13/0x14)
[   10.221885] [<c01444a7>] (cpu_startup_entry) from [<401025d1>] (0x401025d1)
[   10.228809] CPU0: stopping
[   10.231491] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G      D           5.4.0-rc6+ #4
[   10.239121] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[   10.245194] [<c010f195>] (unwind_backtrace) from [<c010b247>] (show_stack+0xb/0xc)
[   10.252735] [<c010b247>] (show_stack) from [<c09913d7>] (dump_stack+0x67/0x74)
[   10.259926] [<c09913d7>] (dump_stack) from [<c010deef>] (handle_IPI+0x2d7/0x2f8)
[   10.267293] [<c010deef>] (handle_IPI) from [<c0531b6b>] (gic_handle_irq+0x73/0x74)
[   10.274831] [<c0531b6b>] (gic_handle_irq) from [<c0101ae5>] (__irq_svc+0x65/0xac)
[   10.282275] Exception stack(0xc0f01f20 to 0xc0f01f68)
[   10.287301] 1f20: 00000000 00001f58 00000000 c0117cc1 c0f00000 00000000 c0f04fac c0f04fec
[   10.295454] 1f40: c0e89568 00000000 c0f01f78 00000000 00000007 c0f01f70 c01088e1 c01088e2
[   10.303594] 1f60: 40000033 ffffffff
[   10.307055] [<c0101ae5>] (__irq_svc) from [<c01088e2>] (arch_cpu_idle+0x32/0x34)
[   10.314431] [<c01088e2>] (arch_cpu_idle) from [<c0144247>] (do_idle+0x197/0x1e4)
[   10.321796] [<c0144247>] (do_idle) from [<c01444a7>] (cpu_startup_entry+0x13/0x14)
[   10.329342] [<c01444a7>] (cpu_startup_entry) from [<c0e00c61>] (start_kernel+0x42d/0x446)
[   10.337483] [<c0e00c61>] (start_kernel) from [<00000000>] (0x0)
[   10.343362] CPU3: stopping
[   10.346048] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G      D           5.4.0-rc6+ #4
[   10.353677] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[   10.359750] [<c010f195>] (unwind_backtrace) from [<c010b247>] (show_stack+0xb/0xc)
[   10.367292] [<c010b247>] (show_stack) from [<c09913d7>] (dump_stack+0x67/0x74)
[   10.374483] [<c09913d7>] (dump_stack) from [<c010deef>] (handle_IPI+0x2d7/0x2f8)
[   10.381850] [<c010deef>] (handle_IPI) from [<c0531b6b>] (gic_handle_irq+0x73/0x74)
[   10.389388] [<c0531b6b>] (gic_handle_irq) from [<c0101ae5>] (__irq_svc+0x65/0xac)
[   10.396832] Exception stack(0xee133f60 to 0xee133fa8)
[   10.401857] 3f60: 00000000 00000434 00000003 c0117cc1 ee132000 00000000 c0f04fac c0f04fec
[   10.410011] 3f80: c0e89568 00000000 ee133fb8 00000000 00000004 ee133fb0 c01088e1 c01088e2
[   10.418151] 3fa0: 40000033 ffffffff
[   10.421612] [<c0101ae5>] (__irq_svc) from [<c01088e2>] (arch_cpu_idle+0x32/0x34)
[   10.428987] [<c01088e2>] (arch_cpu_idle) from [<c0144247>] (do_idle+0x197/0x1e4)
[   10.436353] [<c0144247>] (do_idle) from [<c01444a7>] (cpu_startup_entry+0x13/0x14)
[   10.443891] [<c01444a7>] (cpu_startup_entry) from [<401025d1>] (0x401025d1)
[   10.450815] CPU4: stopping
[   10.453508] CPU: 4 PID: 0 Comm: swapper/4 Tainted: G      D           5.4.0-rc6+ #4
[   10.461132] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[   10.467209] [<c010f195>] (unwind_backtrace) from [<c010b247>] (show_stack+0xb/0xc)
[   10.474746] [<c010b247>] (show_stack) from [<c09913d7>] (dump_stack+0x67/0x74)
[   10.481936] [<c09913d7>] (dump_stack) from [<c010deef>] (handle_IPI+0x2d7/0x2f8)
[   10.489305] [<c010deef>] (handle_IPI) from [<c0531b6b>] (gic_handle_irq+0x73/0x74)
[   10.496840] [<c0531b6b>] (gic_handle_irq) from [<c0101ae5>] (__irq_svc+0x65/0xac)
[   10.504288] Exception stack(0xee135f60 to 0xee135fa8)
[   10.509314] 5f60: 00000000 00001540 00000004 c0117cc1 ee134000 00000000 c0f04fac c0f04fec
[   10.517462] 5f80: c0e89568 00000000 ee135fb8 00000000 00000007 ee135fb0 c01088e1 c01088e2
[   10.525604] 5fa0: 40000033 ffffffff
[   10.529071] [<c0101ae5>] (__irq_svc) from [<c01088e2>] (arch_cpu_idle+0x32/0x34)
[   10.536441] [<c01088e2>] (arch_cpu_idle) from [<c0144247>] (do_idle+0x197/0x1e4)
[   10.543807] [<c0144247>] (do_idle) from [<c01444a7>] (cpu_startup_entry+0x13/0x14)
[   10.551344] [<c01444a7>] (cpu_startup_entry) from [<401025d1>] (0x401025d1)
[   10.558272] CPU1: stopping
[   10.560964] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G      D           5.4.0-rc6+ #4
[   10.568579] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[   10.574652] [<c010f195>] (unwind_backtrace) from [<c010b247>] (show_stack+0xb/0xc)
[   10.582194] [<c010b247>] (show_stack) from [<c09913d7>] (dump_stack+0x67/0x74)
[   10.589385] [<c09913d7>] (dump_stack) from [<c010deef>] (handle_IPI+0x2d7/0x2f8)
[   10.596752] [<c010deef>] (handle_IPI) from [<c0531b6b>] (gic_handle_irq+0x73/0x74)
[   10.604290] [<c0531b6b>] (gic_handle_irq) from [<c0101ae5>] (__irq_svc+0x65/0xac)
[   10.611735] Exception stack(0xee12ff60 to 0xee12ffa8)
[   10.616759] ff60: 00000000 0000055c 00000001 c0117cc1 ee12e000 00000000 c0f04fac c0f04fec
[   10.624913] ff80: c0e89568 00000000 ee12ffb8 00000000 00000004 ee12ffb0 c01088e1 c01088e2
[   10.633053] ffa0: 40000033 ffffffff
[   10.636514] [<c0101ae5>] (__irq_svc) from [<c01088e2>] (arch_cpu_idle+0x32/0x34)
[   10.643890] [<c01088e2>] (arch_cpu_idle) from [<c0144247>] (do_idle+0x197/0x1e4)
[   10.651255] [<c0144247>] (do_idle) from [<c01444a7>] (cpu_startup_entry+0x13/0x14)
[   10.658794] [<c01444a7>] (cpu_startup_entry) from [<401025d1>] (0x401025d1)
[   10.665717] CPU5: stopping
[   10.668410] CPU: 5 PID: 0 Comm: swapper/5 Tainted: G      D           5.4.0-rc6+ #4
[   10.676035] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[   10.682109] [<c010f195>] (unwind_backtrace) from [<c010b247>] (show_stack+0xb/0xc)
[   10.689646] [<c010b247>] (show_stack) from [<c09913d7>] (dump_stack+0x67/0x74)
[   10.696838] [<c09913d7>] (dump_stack) from [<c010deef>] (handle_IPI+0x2d7/0x2f8)
[   10.704205] [<c010deef>] (handle_IPI) from [<c0531b6b>] (gic_handle_irq+0x73/0x74)
[   10.711741] [<c0531b6b>] (gic_handle_irq) from [<c0101ae5>] (__irq_svc+0x65/0xac)
[   10.719190] Exception stack(0xee137f60 to 0xee137fa8)
[   10.724215] 7f60: 00000000 000007c8 00000005 c0117cc1 ee136000 00000000 c0f04fac c0f04fec
[   10.732365] 7f80: c0e89568 00000000 ee137fb8 00000000 00000007 ee137fb0 c01088e1 c01088e2
[   10.740505] 7fa0: 40000033 ffffffff
[   10.743974] [<c0101ae5>] (__irq_svc) from [<c01088e2>] (arch_cpu_idle+0x32/0x34)
[   10.751342] [<c01088e2>] (arch_cpu_idle) from [<c0144247>] (do_idle+0x197/0x1e4)
[   10.758708] [<c0144247>] (do_idle) from [<c01444a7>] (cpu_startup_entry+0x13/0x14)
[   10.766246] [<c01444a7>] (cpu_startup_entry) from [<401025d1>] (0x401025d1)
[   10.773174] CPU7: stopping
[   10.775859] CPU: 7 PID: 0 Comm: swapper/7 Tainted: G      D           5.4.0-rc6+ #4
[   10.783486] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[   10.789559] [<c010f195>] (unwind_backtrace) from [<c010b247>] (show_stack+0xb/0xc)
[   10.797098] [<c010b247>] (show_stack) from [<c09913d7>] (dump_stack+0x67/0x74)
[   10.804289] [<c09913d7>] (dump_stack) from [<c010deef>] (handle_IPI+0x2d7/0x2f8)
[   10.811656] [<c010deef>] (handle_IPI) from [<c0531b6b>] (gic_handle_irq+0x73/0x74)
[   10.819192] [<c0531b6b>] (gic_handle_irq) from [<c0101ae5>] (__irq_svc+0x65/0xac)
[   10.826640] Exception stack(0xee13bf60 to 0xee13bfa8)
[   10.831665] bf60: 00000000 000004d8 00000007 c0117cc1 ee13a000 00000000 c0f04fac c0f04fec
[   10.839815] bf80: c0e89568 00000000 ee13bfb8 00000000 00000000 ee13bfb0 c01088e1 c01088e2
[   10.847955] bfa0: 40040033 ffffffff
[   10.851424] [<c0101ae5>] (__irq_svc) from [<c01088e2>] (arch_cpu_idle+0x32/0x34)
[   10.858792] [<c01088e2>] (arch_cpu_idle) from [<c0144247>] (do_idle+0x197/0x1e4)
[   10.866159] [<c0144247>] (do_idle) from [<c01444a7>] (cpu_startup_entry+0x13/0x14)
[   10.873697] [<c01444a7>] (cpu_startup_entry) from [<401025d1>] (0x401025d1)
[   10.880650] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---
Probably because I built the kernel in thumb2 mode.. will try a regular build instead.
Thumb2 was working for rc5 though...

EDIT: yes, removing panfrost, lima and building in ARM-mode instead of thumb2 makes it work again :)

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

Re: Kernel 5.0 development thread

Unread post by odroid » Wed Nov 13, 2019 6:33 pm

We've made a few patches against RC6.

1. Proper eMMC clock settings for the file system stability
2. Ethernet power cycling in the reboot process. Before applying this patch, GbE port disappeared randomly by warmbooting events.
3. SD card power cycling for a smooth reboot process with UHS grade SD cards.

Code: Select all

patch -p0 < emmc_pmic.patch_20191113.patch
emmc_pmic_20191113.zip
(1.28 KiB) Downloaded 16 times
We tested the suspend/resume function with a new Orange eMMC module after applying the patch.
It seemed to be working fine.
To enter in the suspend mode, we ran systemctl suspend command. The power consumption was near 50mA in the suspend mode. :o
To wakeup/resume, we just pressed the power button on the XU4 board.

We will try to implement the SPI driver for the CloudShell LCD function.
These users thanked the author odroid for the post:
AreaScout (Thu Nov 14, 2019 1:55 am)

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

Re: Kernel 5.0 development thread

Unread post by memeka » Wed Nov 13, 2019 8:21 pm

@odroid can you explain why 3) was needed? Also why is necessary on reboot and not after suspend wake up?

User avatar
AreaScout
Posts: 1128
Joined: Sun Jul 07, 2013 3:05 am
languages_spoken: german, english
ODROIDs: X2, U3, XU3, C2, HiFi Shield, XU4, XU4Q,
N1, Go, VU5A, Show2, CloudShell2,
H2, N2, VU7A, VuShell
Has thanked: 26 times
Been thanked: 76 times
Contact:

Re: Kernel 5.0 development thread

Unread post by AreaScout » Thu Nov 14, 2019 1:56 am

odroid wrote:
Wed Nov 13, 2019 6:33 pm
We will try to implement the SPI driver for the CloudShell LCD function.
Thank you :) I hope it will not be that difficult

After 5.4 that fbdev subsystem will change again ...

RG

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

Re: Kernel 5.0 development thread

Unread post by odroid » Thu Nov 14, 2019 9:15 am

memeka wrote:
Wed Nov 13, 2019 8:21 pm
@odroid can you explain why 3) was needed? Also why is necessary on reboot and not after suspend wake up?
SD card UHS mode runs at 1.8Volt after detecting/initialization process at default 3.3Volt .
Once the UHS mode is enabled, we can't go back to the initial state and have to issue an hardware reset( or power cycle) to the SD card.
In the suspend - resume process, we don't need to reset the SD card since the card file system information is still available in the DRAM.
SD card power rail is still alive in the suspend mode too.

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

Re: Kernel 5.0 development thread

Unread post by odroid » Thu Nov 14, 2019 9:16 am

AreaScout wrote:
Thu Nov 14, 2019 1:56 am
Thank you :) I hope it will not be that difficult
I hope so. 8-)

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

Re: Kernel 5.0 development thread

Unread post by memeka » Thu Nov 14, 2019 10:31 am

odroid wrote:
Thu Nov 14, 2019 9:15 am
memeka wrote:
Wed Nov 13, 2019 8:21 pm
@odroid can you explain why 3) was needed? Also why is necessary on reboot and not after suspend wake up?
SD card UHS mode runs at 1.8Volt after detecting/initialization process at default 3.3Volt .
Once the UHS mode is enabled, we can't go back to the initial state and have to issue an hardware reset( or power cycle) to the SD card.
In the suspend - resume process, we don't need to reset the SD card since the card file system information is still available in the DRAM.
SD card power rail is still alive in the suspend mode too.
after resume, regulators/clocks reset to the default value. for example, one of the new mali patches i had to add was to save the state of the mali clock on suspend and restore on resume, because after resume the gpu was reset to 400Mhz.
actually it was the same for the CPU, even if performance governor was active, after resume the clocks were set to 800Mhz and would not change. with latest patches, it resumes correctly to the values before suspend.
just wanted to make sure that you checked the SD/emmc clocks and regulators resume correctly in all cases.

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

Re: Kernel 5.0 development thread

Unread post by memeka » Thu Nov 14, 2019 12:09 pm

I have pushed the rebase on -rc7 with minor fixes, plus the fixes for SD, eth and emmc from @odroid.
I have kept the original eth and poweroff sequence patches from 4.x kernel, and added one extra patch for SD UHS voltage, and one for emmc.
I have also removed the patch to automatically set GPU governor to performance, it's now running the default simple_ondemand.

https://github.com/mihailescu2m/linux/c ... dxu4-5.4.y
These users thanked the author memeka for the post:
rooted (Fri Nov 15, 2019 1:01 am)

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

Re: Kernel 5.0 development thread

Unread post by odroid » Thu Nov 14, 2019 12:22 pm

Thank you for the update with merge.

We will check the SD & eMMC clock frequency and voltage before-after a few suspend/resume events.

joshua.yang
Posts: 296
Joined: Fri Sep 22, 2017 5:54 pm
languages_spoken: Korean, English
ODROIDs: XU4, XU4Q + Cloudshell2, H2, N2
Has thanked: 3 times
Been thanked: 43 times
Contact:

Re: Kernel 5.0 development thread

Unread post by joshua.yang » Thu Nov 14, 2019 3:50 pm

Hi @memeka,

We've been testing whether some core features work or not and this is the results so far.

Kernel version: 5.4.0-rc7+
- About the eMMC/SDMMC patch
eMMC: It does not wake up from suspend. SD is okay.
SD: reboot doesn't work

The patch has been tested again on the rc6 kernel today. It seems something goes wrong when the patch merges into the rc7 kernel source.

- About GPIO. With Shifter Shield, I have confirmed the listed items work.
Two I2C channels
One UART channel
Two ADC channels
WiringPi
RPi.GPIO

- Panfrost
We still need to disable panfrost kernel feature CONFIG_DRM_PANFROST to boot properly.

We're going to keep posting the progress here. :)

joshua.yang
Posts: 296
Joined: Fri Sep 22, 2017 5:54 pm
languages_spoken: Korean, English
ODROIDs: XU4, XU4Q + Cloudshell2, H2, N2
Has thanked: 3 times
Been thanked: 43 times
Contact:

Re: Kernel 5.0 development thread

Unread post by joshua.yang » Thu Nov 14, 2019 5:27 pm

Just confirmed SPI also works. :)

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

Re: Kernel 5.0 development thread

Unread post by odroid » Thu Nov 14, 2019 6:15 pm

@joshua.yang,
After implementing the SPI-LCD drivers, please compare the USB 3.0 storage and Gbit Ethernet performance with Kernel 4.14.

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

Re: Kernel 5.0 development thread

Unread post by memeka » Fri Nov 15, 2019 8:57 am

I removed the SD UHS mode patch (https://github.com/mihailescu2m/linux/c ... c891d32dc7 or https://pastebin.com/FGS763Lu), and reboot now works with SD-card.
Can you test if UHS speeds are supported before and after suspend? I only have class-10 sd-cards :(

EDIT: my card actually runs in SDR104 mode, which i think is 1.8V, so why was the patch required?

Code: Select all

[    4.272031] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    4.393671] mmc_host mmc1: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0)
[    4.412550] mmc1: new ultra high speed SDR104 SDHC card at address aaaa
[    4.424053] mmcblk1: mmc1:aaaa SC16G 14.8 GiB

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

Re: Kernel 5.0 development thread

Unread post by memeka » Fri Nov 15, 2019 10:14 am

and another question for @odroid - i know there was an issue in the past with ETH port dissapearing after reboot, and was fixed by the regulator patches, but was the same behaviour tested on 5.4 kernel? Did it dissapear on 5.4 as well?

joshua.yang
Posts: 296
Joined: Fri Sep 22, 2017 5:54 pm
languages_spoken: Korean, English
ODROIDs: XU4, XU4Q + Cloudshell2, H2, N2
Has thanked: 3 times
Been thanked: 43 times
Contact:

Re: Kernel 5.0 development thread

Unread post by joshua.yang » Fri Nov 15, 2019 5:22 pm

FYI,

I have tested with an 8GB SD card and 64GB eMMC to measure its performance before/after suspend.
Here are the results.

- 5.4.0-rc7+ (Read/Write)
- SD
Before suspend: 74 MB/s / 28 MB/s
After suspend: 75 MB/s / 28 MB/s
- eMMC
Before suspend: 120 MB/s / 53 MB/s
After suspend: 132 MB/s / 56 MB/s

- 4.14.150-170 (Read/Write) (systemctl suspend doesn't work)
- SD
78 MB/s / 30 MB/s
- eMMC
160 MB/s / 58 MB/s

oliver.claude
Posts: 3
Joined: Mon Sep 16, 2019 2:44 am
languages_spoken: english
ODROIDs: 2x N2, 5x HC2, 3x HC1
Has thanked: 1 time
Been thanked: 1 time
Contact:

Re: Kernel 5.0 development thread

Unread post by oliver.claude » Fri Nov 15, 2019 5:39 pm

Is there a specific build option I need to use to build rc6 and rc7. I normally use the default build and then add a bunch of options in to support lxd/lxc and ceph. All my builds succeed in building/compiling.

This last worked on rc5, but everything after has not booted for me. I'm using HC1 and HC2 SBC, so don't have a screen to see what is happening.

Here is my .config file
https://pastebin.com/bTz9fipc

Here is my build script.
https://pastebin.com/SduedQxi

And here is my install script.
https://pastebin.com/7P5w21jk

Thanks for the assist.

Regards,

joshua.yang
Posts: 296
Joined: Fri Sep 22, 2017 5:54 pm
languages_spoken: Korean, English
ODROIDs: XU4, XU4Q + Cloudshell2, H2, N2
Has thanked: 3 times
Been thanked: 43 times
Contact:

Re: Kernel 5.0 development thread

Unread post by joshua.yang » Tue Nov 19, 2019 9:57 am

oliver.claude wrote:
Fri Nov 15, 2019 5:39 pm
Is there a specific build option I need to use to build rc6 and rc7. I normally use the default build and then add a bunch of options in to support lxd/lxc and ceph. All my builds succeed in building/compiling.

This last worked on rc5, but everything after has not booted for me. I'm using HC1 and HC2 SBC, so don't have a screen to see what is happening.

Here is my .config file
https://pastebin.com/bTz9fipc

Here is my build script.
https://pastebin.com/SduedQxi

And here is my install script.
https://pastebin.com/7P5w21jk

Thanks for the assist.

Regards,
Hi.

Disable "CONFIG_DRM_PANFROST" kernel feature using menuconfig and try again. It should boot. :)
These users thanked the author joshua.yang for the post:
oliver.claude (Tue Nov 19, 2019 3:32 pm)

MastaG
Posts: 298
Joined: Mon Aug 26, 2013 6:05 pm
languages_spoken: english
Has thanked: 13 times
Been thanked: 3 times
Contact:

Re: Kernel 5.0 development thread

Unread post by MastaG » Wed Nov 20, 2019 4:58 am

Yeah, you can disable LIMA as well.. since we don't have this GPU.
Btw @memeka thanks for fixing the eMMC v5 issue :)

I can finally suspend and resume now!
You're the shit!

All stable for me, that's kodi with netflix + retroarch gaming + basic browsing on gnome 3 using Fedora 31.

EDIT: I was a bit too quick.. it does seem to segfault when I go into suspend:

Code: Select all

[  121.820383] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x30c/0x310
[  121.820397] NETDEV WATCHDOG: eth0 (smsc95xx): transmit queue 0 timed out
[  121.820415] Modules linked in: xt_CHECKSUM xt_MASQUERADE nf_nat_tftp nf_conntrack_tftp nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_REJECT nf_rejecty
[  121.820606] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.4.0-rc7+ #6
[  121.820614] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[  121.820687] [<c011397c>] (unwind_backtrace) from [<c010e490>] (show_stack+0x10/0x14)
[  121.820722] [<c010e490>] (show_stack) from [<c0cdd3b4>] (dump_stack+0x90/0xa4)
[  121.820756] [<c0cdd3b4>] (dump_stack) from [<c012c60c>] (__warn+0xd0/0xf8)
[  121.820772] [<c012c60c>] (__warn) from [<c012ca00>] (warn_slowpath_fmt+0x98/0xc4)
[  121.820786] [<c012ca00>] (warn_slowpath_fmt) from [<c0b6e5c0>] (dev_watchdog+0x30c/0x310)
[  121.820809] [<c0b6e5c0>] (dev_watchdog) from [<c019bb08>] (call_timer_fn+0x3c/0x204)
[  121.820826] [<c019bb08>] (call_timer_fn) from [<c019c268>] (run_timer_softirq+0x1e4/0x5b8)
[  121.820845] [<c019c268>] (run_timer_softirq) from [<c01022c0>] (__do_softirq+0x118/0x3f4)
[  121.820863] [<c01022c0>] (__do_softirq) from [<c01332d8>] (irq_exit+0xb0/0xd8)
[  121.820891] [<c01332d8>] (irq_exit) from [<c017f1e4>] (__handle_domain_irq+0x60/0xb0)
[  121.820923] [<c017f1e4>] (__handle_domain_irq) from [<c06f3034>] (gic_handle_irq+0x4c/0x90)
[  121.820941] [<c06f3034>] (gic_handle_irq) from [<c0101a8c>] (__irq_svc+0x6c/0xa8)
[  121.820950] Exception stack(0xc1201f20 to 0xc1201f68)
[  121.820964] 1f20: 00000000 000466b8 00000000 c011f500 c1200000 00000000 c1204fac c1204fec
[  121.820974] 1f40: c11a5568 00000000 c1201f78 00000000 c1205064 c1201f70 c010aaac c010aab0
[  121.820982] 1f60: 60010013 ffffffff
[  121.820997] [<c0101a8c>] (__irq_svc) from [<c010aab0>] (arch_cpu_idle+0x4c/0x50)
[  121.821020] [<c010aab0>] (arch_cpu_idle) from [<c015e280>] (do_idle+0x22c/0x29c)
[  121.821035] [<c015e280>] (do_idle) from [<c015e5e8>] (cpu_startup_entry+0x18/0x1c)
[  121.821070] [<c015e5e8>] (cpu_startup_entry) from [<c1100f98>] (start_kernel+0x500/0x540)
[  121.821092] ---[ end trace 93974abf21ea3ab3 ]---
[  200.522340] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
This is on a Odroid XU3 so perhaps it's related to the smsc95xx driver not playing nice.. the XU4 has a different ethernet chip.

EDIT 2: yes I think it's related to the smsc95xx ethernet driver because it only seems to happen on the XU3, on the XU4 suspend and resume is working flawlessly without any kernel crashes.
These users thanked the author MastaG for the post:
odroid (Wed Nov 20, 2019 9:31 am)

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

Re: Kernel 5.0 development thread

Unread post by odroid » Wed Nov 20, 2019 9:33 am

I think we can start an official debugging party from middle of the next week once the official Kernel 5.4 appears.
https://lwn.net/Articles/805037/

@MastaG,
Let's look into your XU3 issue together when we start the debugging party.
These users thanked the author odroid for the post (total 2):
rooted (Wed Nov 20, 2019 1:07 pm) • AreaScout (Fri Nov 22, 2019 5:37 am)

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

Re: Kernel 5.0 development thread

Unread post by memeka » Fri Nov 22, 2019 9:53 am

Confirmed working nicely on the HC1.

boot log: http://paste.ubuntu.com/p/8DFchKwG2h/
i did not test sleep, since there is no button to wake up the HC1 :)
using a UHS-1 card, it's running in SDR104 mode is this ok?

Code: Select all

[    2.715567] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    2.817386] mmc_host mmc0: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0)
[    2.835149] mmc0: new ultra high speed SDR104 SDHC card at address aaaa
[    2.846831] mmcblk0: mmc0:aaaa SA08G 7.40 GiB
I'll wait for the final release to push a couple of more patches and my updated config (with no kernel debug options, and options added for working docker)

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

Re: Kernel 5.0 development thread

Unread post by odroid » Fri Nov 22, 2019 1:27 pm

SDR104 looks okay with a UHS card.
If "dd" reading speed is over 50MB/s, there should be no problem.
Please run the following commands on the SD mount point.

Code: Select all

Write command
dd if=/dev/zero of=test oflag=direct bs=8M count=64
Read command 
dd if=test of=/dev/null iflag=direct bs=8M

Post Reply

Return to “Ubuntu”

Who is online

Users browsing this forum: No registered users and 1 guest