[S905/S905X] LE 7.0.x Boot issue test images

    ok - couldn`t stop tinkering...

    gc3e054b on nand, g5207357 on sd card
    got freezes on both.
    somehow gc3e054b started working from nand - didn`t change anything. g5207357 boots occasionally.

    I tried it countless times, almost all the time since my last post. 40 minutes of constant rebooting, turning the thing off and on, rebooting from sd, rebooting from nand, rebooting with and without usb attached.
    This is so weird...
    gc3e054b booted ~60% of all tries, g5207357 10% at most. USB connected or not does not seem to make any difference, not if connected or not and neither which port.

    one last edit before heading to bed:
    It doesn`t always hang at the same point. Sometimes the splash screen will stay forever, sometimes it hangs right after the splash screen with a blackscreen.

    Edited once, last by puked (January 2, 2017 at 11:34 PM).

    MiniMX 2GB/16GB with Broadcom Wifi
    DTB file: gxbb_p200_2G_1Gbit.dtb

    g5207357 fresh installed to NAND

    USB Airmouse Connected - used Kitty with autologin and shutdown - c, hung at Welcome Hi! Teddy Bear Logo Screen after 15 reboots
    NO USB Airmouse Connected - used Kitty with autologin and shutdown - c, hung at Welcome Hi! Teddy Bear Logo Screen after 3 reboots

    I have now reverted to 7.0.2.009 (not Nov 19th) build to do a boot test on it to get a baseline and confirm that boot issues do not occur at all.
    [hr]
    Just to provide an update on my boot testing:

    MiniMX 2GB/16GB with Broadcom Wifi
    DTB file: gxbb_p200_2G_1Gbit.dtb

    7.0.2.009 fresh installed to NAND

    USB Airmouse Connected - used Kitty with autologin and shutdown - c, hung at Welcome Hi! Teddy Bear Logo Screen after 8 reboots
    NO USB Airmouse Connected - used Kitty with autologin and shutdown - c, over 25 reboots and still going

    i will let it run the reboot test for 100 reboots, if it doesn't hang we can def say that is the golden image for boot stability as long as no USB devices are plugged in

    Edited once, last by kashmoney (January 3, 2017 at 4:02 AM).

    Nexbox A95X S905 1GB/8GB
    SD Card LE Installation.
    As well as internal on same box.
    Updated from gc9b399e.img
    To g5207357
    gxbb_p200_1G_100M_RealtekWiFi.dtb 18-Dec-2016 16:54 39375
    USB Mouse receiver plugged into USB Port
    Box using LAN
    Random Freezing
    BUT I AM PRETTY SURE I HAVE FOUND WHAT IS CAUSING IT AFTER 4 HOURS OF DIFFERENT VARIABLES
    Including making all u-boot variables go back to default values and thus disable SD and USB booting, none of which helped or made any difference.

    I can now confidently say that there is a pattern in when the box will freeze.

    If you turn off/reboot the box and then immediately turn it off/reboot
    YOU WILL GET A FREEZE MOST OF THE TIME.

    However if you you successfully boot up and WAIT for say 1 minute and then reboot through your power menu you will have a 90% chance of the box booting up.

    I have also picked something up with the Confluence skin now having a new sub-menu tab called Events.
    I have no idea when this was introduced as i only just noticed it.
    I have opened that tab menu and noticed it always reads that kodi successfully started with the same
    Date 01/01/2015 11:00:13 AM.
    UPDATE: To fix the Date to be read properly i went to LE Settings/Network and enabled Wait for network before starting Kodi 10 seconds.

    This triggered my suspicion that we have a bug that may be caused by the guisettings.xml file getting corrupted - possibly the system being shut down during a write.
    Or kodi thinking this file is corrupted, it fails to replace it with the default and hence a freeze.

    The problem i believe is caused during the process of Powering off and Rebooting.
    If you wait a minute or more and slowly go through to your power menu and choose reboot,
    the box rarely freezes.
    I could be wrong but i hope i am not.

    log that may be useful .

    kodi_crashlog_20170103122959.log.zip

    Edited once, last by kostaman (January 3, 2017 at 6:06 AM).

    2nd image was good for about 6 boots
    After that got stuck whether rebooting or booting from off

    Trying the next image . . .

    Edited once, last by Poida (January 3, 2017 at 9:12 AM).

    Quote from Poida


    After that got stuck whether rebooting on booting from off

    I can't power off and then on because of the Nexbox A95x s905 not able to power on via remote.

    You will have Boot Freeze after a Freeze. It is a Kodi/LE system looking for previous shut down settings.
    I could be talking rubbish but there is a pattern as i pointed out in my post above.
    I am very confident the issue is with the system not writing correctly when rebooting or powering off.

    Don't know if this is helpful.. I have an m8sII mini 1/8gb when i compile SX05-bringup i always end up with a blank screen and the following in dmesg
    ------------[ cut here ]------------
    [ 8.466625@3] WARNING: CPU: 3 PID: 2283 at /home/mark/src/s905x/build.LibreELEC-S905.arm-8.0-devel/qca9377-aml-8b729b7/AIO/drivers/backports/net/wireless/core.c:466 wiphy_register+0xf0/0x6d0 [cfg80211]()
    [ 8.466649@3] Modules linked in: 8189fs(+) cfg80211(O) compat(O) 8021q wifi_dummy mali(O) amlvideodri(O) videobuf_res(O) videobuf_core(O) videodev(O) media(O) aml_nftl_dev(P) fbcon bitblit softcursor font
    [ 8.466655@3] CPU: 3 PID: 2283 Comm: systemd-udevd Tainted: P W O 3.14.29 #1
    [ 8.466657@3] Call trace:
    [ 8.466665@3] [<ffffffc001087e10>] dump_backtrace+0x0/0x128
    [ 8.466669@3] [<ffffffc001087f58>] show_stack+0x20/0x30
    [ 8.466674@3] [<ffffffc0017cc78c>] dump_stack+0x78/0x94
    [ 8.466679@3] [<ffffffc001095794>] warn_slowpath_common+0x94/0xc0
    [ 8.466683@3] [<ffffffc0010958f0>] warn_slowpath_null+0x38/0x50
    [ 8.466693@3] [<ffffffbffc0dd97c>] wiphy_register+0xec/0x6d0 [cfg80211]
    [ 8.466751@3] [<ffffffbffc1c24ec>] rtw_wiphy_register+0x24/0x34 [8189fs]
    [ 8.466801@3] [<ffffffbffc1c27bc>] rtw_cfg80211_ndev_res_register+0x1c/0x34 [8189fs]
    [ 8.466847@3] [<ffffffbffc1ad948>] rtw_os_ndev_register+0x28/0xa4 [8189fs]
    [ 8.466893@3] [<ffffffbffc1ae490>] rtw_os_ndevs_register+0xf4/0x178 [8189fs]
    [ 8.466938@3] [<ffffffbffc1ae5a8>] rtw_os_ndevs_init+0x30/0x60 [8189fs]
    [ 8.466982@3] [<ffffffbffc1af950>] rtw_drv_init+0x78/0x108 [8189fs]
    [ 8.466988@3] [<ffffffc00151e724>] sdio_bus_probe+0x13c/0x158
    [ 8.466993@3] [<ffffffc001406004>] driver_probe_device+0x84/0x250
    [ 8.466997@3] [<ffffffc0014062d8>] __driver_attach+0xa8/0xb0
    [ 8.467001@3] [<ffffffc0014040dc>] bus_for_each_dev+0x6c/0xb0
    [ 8.467005@3] [<ffffffc001405a5c>] driver_attach+0x2c/0x40
    [ 8.467008@3] [<ffffffc001405644>] bus_add_driver+0x15c/0x218
    [ 8.467012@3] [<ffffffc001406a24>] driver_register+0x64/0x128
    [ 8.467015@3] [<ffffffc00151e464>] sdio_register_driver+0x2c/0x40
    [ 8.467057@3] [<ffffffbffc251058>] $x+0x58/0xa8 [8189fs]
    [ 8.467061@3] [<ffffffc001081698>] do_one_initcall+0xd8/0x140
    [ 8.467067@3] [<ffffffc00110c8ac>] load_module+0x17ac/0x1f28
    [ 8.467071@3] [<ffffffc00110d1f4>] SyS_finit_module+0xb4/0xc8
    [ 8.467073@3] ---[ end trace b49d54a8d623f758 ]---

    If i change the following from linux.arm.conf
    CONFIG_RTL8189FS=m
    to
    CONFIG_RTL8189FS=n

    box works fine !

    Quote from Gendo


    Don't know if this is helpful.. I have an m8sII mini 1/8gb when i compile SX05-bringup i always end up with a blank screen and the following in dmesg

    Not really helpful until you post a full zip log - what is the reason why RTL8189FS drivers is loaded in the first place?

    Quote from kszaq


    Thanks. Please also get udevadm info /sys/bus/sdio/devices/sdio*.


    My Mini M8S II has 2GB/16GB

    Edited once, last by Pelican (January 3, 2017 at 9:26 AM).

    Quote from Poida


    LibreELEC-S905.arm-7.0-devel-20170102194735-r23609-g5207357.img.gz froze on reboot number 7 (leaving at least 1 minute between reboots)

    I got 18 consecutive reboots without freeze after leaving box on and walking past every 5 to 10 minutes and rebooting whilst i was home.
    I rebooted the box straight after it booted up without waiting over 1 minute and it froze the 19th time. :idea:
    [hr]

    Quote from kostaman


    However if you you successfully boot up and WAIT for say 1 minute and then reboot through your power menu you will have a 90% chance of the box booting up.

    Edited once, last by kostaman (January 3, 2017 at 10:27 AM).

    LibreELEC-S905.arm-7.0-devel-20170102194735-r23609-g5207357.img.gz froze on cold boot number 10 (leaving at least 1 minute between reboots) on the Mini MX-G

    kostaman I don't think that it should make any difference if the box is shutdown immediately or not. Sometimes this happens. If it does, that shouldn't affect whether the box can boot next time but, just to help check your theory, I have waited at least 1 minute before changing the status of the box ;)

    Edited once, last by Poida (January 3, 2017 at 11:16 AM).

    Quote from Poida


    LibreELEC-S905.arm-7.0-devel-20170102194735-r23609-g5207357.img.gz froze on cold boot number 10 (leaving at least 1 minute between reboots) on the Mini MX-G

    kostaman I don't think that it should make any difference if the box is shutdown immediately or not. Sometimes this happens. If it happens, that shouldn't affect whether the box can boot next time but, just to help check your theory, I have waited at least 1 minute before changing the status of the box ;)

    I am probably creating the theory in the hope i am right.
    I have convinced myself that when Kodi first boots up successfully , all system processes are being carried out and by disrupting that with a power off or a reboot, it causes the freeze more times than not.
    I collected the zipped log in my post via file manager which i see one part in particular below.
    I again repeat i am getting desperate to solve this before Christmas and i could be showing early signs of delusional disorder.

    NOTICE: ## LibreELEC Addon ## 0.7.5
    11:00:10 T:3963614112 WARNING: CSkinInfo: failed to load skin settings
    11:00:12 T:4047225760 ERROR: CecLogMessage - Write: write failed !
    12:29:56 T:4113232448 ERROR: Previous line repeats 23 times.

    Quote from kostaman


    I again repeat i am getting desperate to solve this before Christmas and i could be showing early signs of delusional disorder.

    Good on ya champ! I, for one, am still hanging in there that you do get this solved before Christmas! LOL

    Thank you. I'll look into fixing this.

    OP updated with a new image to test. This time I left the kernel unmodified, I disabled temperature sensor.