rock64 not responsive / doesn't boot, but LEDs light up

[jebivetar]

maybe i'm missing something obvious - extremely possible - but my board is unusable since upgrade to the 195 kernel from 188

there is simply no hdmi output and the board does not connect to the network. the leds turn on, with ethernet connected both ethernet leds turn on after a few seconds, and without ethernet just the green ethernet led

this happens on both the original sdcard with ayufan's stretch, and another sdcard with a number of different distros (ayufan 6.27 stretch, ayufan xenial, armbian ubuntu, armbian stretch nightly) copied over a number different ways (suse image studio, dd, etcher)

i've tried different sd cards, different sd->usb adapters, different power sources, different network switches and different displays

additionally, i have no uart output, except some gibberish when power or tx is connected - although i haven't used uart before so i can't really expand too much on this [this is most likely due to incompat uart adapter (c2102), new ones are in transit]

hope i'm proven idiot on this one

[ayufan]

You are not. The 0.6.26 is completely broken, because of broken kernel init. It is having crash loop.

This issue is fixed in 0.6.27.

[jebivetar]

issue persists with 6.27

[jebivetar]

to clarify, the issue isn't that i can't boot 6.26 - it's that i can't boot anything

[ayufan]

I don't understand. So, after writing the 0.6.27 is it still not working, or working?

[jebivetar]

after upgrading to 0.6.26, the board is unusable - no images boot or display any kind of life except for led lights

i am about to try .0.6.21

[jebivetar]

.0.6.21 doesn't work either

[rocckyman]

Hi, I am facing the same issue after upgrading to 195. Now the board can only boot from Emmc and it just keep rebooting. And I am no longer able to boot from SD to flash Emmc again (https://forum.pine64.org/showthread.php?tid=4924). Any instruction to recover the board in this situation?

[ayufan]

I just booted the 0.6.28 easily. It worked OK.

[rocckyman]

Thx for ur reply. I don’t hv the usb->Emmc adapter. I used to follow the tutorial in the previous post to flash Emmc again if the upgrade fail to boot. Any instruction that can allow me to boot from SD again then flash the latest image?

[ayufan]

Remove eMMC, and use SD only.

[rocckyman]

Hi, I tried another SD card and managed to boot now. Flashing latest image now. Thx

[jebivetar]

Why is this closed again?

[ghost]

It seems, the problem has something to do with HDMI. when i switched the resolution, i lost the screen entirely. I had to disconnect power for 1 minute before i could get the screen back and i got a rose stripe on the left screen side. Could be display driver...

[jebivetar]

board looks like it's dead...there is nothing on uart with ch340g adapter

power usage looks to be ~.05A on power-on, jumping to ~.065A when the ethernet LEDs turn on, which probably means the entire power draw are the various LEDs

[boffemmyer]

my board appears dead today. all led's are on except ethernet wil not light up. was running emmc 4 gig openmedia vault flawlessly for about 3 months. came home today frozen. will not boot. tried various sd card images. same result. am i doing something wrong?

[KargJonas]

Similar thing happened to me. I was unable to boot anything since i purchased it.

[KargJonas]

32GB SanDisk micro SD Standard power cable 2A Powerbrick Rock64 Tried multiple different OSs (last try was Raspbian latest)

When connected to power (With every OS I tried): All led's light up statically. No HDMI output.

Me and a friend bought two units from the official store. His worked. Mine didn't. (He used the exact same configuration)

[chandupreetham]

32GB SanDisk micro SD Standard power cable 2A Powerbrick Rock64 Tried multiple different OSs (last try was Raspbian latest)

When connected to power (With every OS I tried): All led's light up statically. No HDMI output.

Me and a friend bought two units from the official store. His worked. Mine didn't. (He used the exact same configuration)

I bought ROCKPRO64 and I have the same issue with that , did you get it

[ayufan]

Strange. Się you try to connect uart?

On Fri, 12 Oct 2018 at 08:28, Danielcunn123 notifications@github.com wrote:

Same here, Brought a ROCK64 4G back in April and recently got an RMA board which took like a month to return once I sent off my old one. That is also not working with literately ANYTHING, tried different SD cards, EMMC modules, Power Supplies, HDMI Cables, Monitors just everything. Biggest waste of money tbh..

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/ayufan-rock64/linux-build/issues/145#issuecomment-429218518, or mute the thread https://github.com/notifications/unsubscribe-auth/ACTpQXQrFl2waHRruQ1XHI1zfZLkO5xGks5ukDaRgaJpZM4TA09d .

[ayufan]

I have 4 of them. Each works :)

On Fri, 12 Oct 2018 at 09:22, Kamil Trzciński ayufan@ayufan.eu wrote:

Strange. Się you try to connect uart?

On Fri, 12 Oct 2018 at 08:28, Danielcunn123 notifications@github.com wrote:

Same here, Brought a ROCK64 4G back in April and recently got an RMA board which took like a month to return once I sent off my old one. That is also not working with literately ANYTHING, tried different SD cards, EMMC modules, Power Supplies, HDMI Cables, Monitors just everything. Biggest waste of money tbh..

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/ayufan-rock64/linux-build/issues/145#issuecomment-429218518, or mute the thread https://github.com/notifications/unsubscribe-auth/ACTpQXQrFl2waHRruQ1XHI1zfZLkO5xGks5ukDaRgaJpZM4TA09d .

[michaeldexter]

32GB SanDisk micro SD Standard power cable 2A Powerbrick Rock64 Tried multiple different OSs (last try was Raspbian latest) When connected to power (With every OS I tried): All led's light up statically. No HDMI output. Me and a friend bought two units from the official store. His worked. Mine didn't. (He used the exact same configuration)

I bought ROCKPRO64 and I have the same issue with that , did you get it

Any success? I am in the same boat, having tried xubuntu, bionic-minimal and RaspBSD. At most I get a green LED and the network port LEDs.

[ayufan]

Connect UART. See what is failure.

Use your friends SD card.

On Sun, Oct 28, 2018 at 9:23 PM Michael Dexter notifications@github.com wrote:

32GB SanDisk micro SD Standard power cable 2A Powerbrick Rock64 Tried multiple different OSs (last try was Raspbian latest) When connected to power (With every OS I tried): All led's light up statically. No HDMI output. Me and a friend bought two units from the official store. His worked. Mine didn't. (He used the exact same configuration)

I bought ROCKPRO64 and I have the same issue with that , did you get it

Any success? I am in the same boat, having tried xubuntu, bionic-minimal and RaspBSD. At most I get a green LED and the network port LEDs.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/ayufan-rock64/linux-build/issues/145#issuecomment-433738166, or mute the thread https://github.com/notifications/unsubscribe-auth/ACTpQQa5GeeuKA5N2P1lSCD1ZWlRHxVxks5uphJPgaJpZM4TA09d .

[ManuGithubSteam]

Hi Just to say im also affected: Rock64 not the pro version with 4 GIG ram. Noting boots or gives a live sign. Images i tried:

ROC-RK3328-CC-ubuntu18.04-LXDE_20180920.img ROC-RK3328-CC_Debian9-Arch64_20180525.img stretch-minimal-rock64-0.7.8-1061-arm64.img Armbian_5.65_Rock64_Debian_stretch_default_4.4.162_desktop stretch-minimal-rock64-0.7.9-1067-arm64.img

[llybin]

I have same problem. rockpro64 / 4g / emmc / 12v/4A / pci-e usb expansion card. Tried all roms. The first boot - everything good. After some time, board is stuck. Sometimes stucking reproduced when send "poweroff" command on board. And board looks like died. Nothing help. Power LED and ethernet are lighted only. No white LED. Refreshing emmc rarely helps. Helps wait some time. And boot works. I have UART but when I getting this problem - a board shows only on every reset: DDR Version 1.12 20180518
In

[llybin]

Once I saved this log, may be it can help: https://p.devtrue.net/ihx6ta3/

[ManuGithubSteam]

Update: I was able to boot the openmediavault jessi armhf build. After that i installed u-boot and now i can boot Armbian images without changeing anything.

I packed the whole thing in a little guide for octoprint as this is my use case for the rock:

-> https://github.com/foosel/OctoPrint/wiki/Setup-on-Rock64-running-Armbian

Hopes this helps some of you :-)

[chandupreetham]

It worked for me openmedia and am running ubuntuu 18.04 LTS and wifi is also working. but had problem with video, it’s playing fast

On Mon, Nov 5, 2018 at 12:00 PM Manuel notifications@github.com wrote:

Update: I was able to boot the openmediavault jessi armhf build. After that i installed u-boot and now i can boot Armbian images without changeing anything.

I packed the whole thing in a little guide for octoprint as this is my use case for the rock:

-> https://github.com/foosel/OctoPrint/wiki/Setup-on-Rock64-running-Armbian

Hopes this helps some of you :-)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ayufan-rock64/linux-build/issues/145#issuecomment-435951553, or mute the thread https://github.com/notifications/unsubscribe-auth/Am8N1K8IgrlgjJ7V8zcvzckmmz90z6q-ks5usG6qgaJpZM4TA09d .

[llybin]

Really, only under openmediavault rock64_write_spi_flash.sh works, there is a difference, on others: libmtd: error!: MEMERASE64 ioctl failed for eraseblock 10 (mtd0) error 110 (Connection timed out)

P.S. nope, stuck again Writing /dev/mtd0 with content of /usr/lib/u-boot-rockpro64/rkspi_loader.img Erasing 4 Kibyte @ 52000 -- 8 % complete libmtd: error!: MEMERASE64 ioctl failed for eraseblock 82 (mtd0) error 110 (Connection timed out) flash_erase: error!: /dev/mtd0: MTD Erase failure error 110 (Connection timed out)

[ 15.192901] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [ 178.355776] m25p80 spi32766.0: flash operation timed out [ 179.188217] rk_gmac-dwmac fe300000.ethernet eth0: Link is Down [ 191.193717] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [ 217.200159] rk_gmac-dwmac fe300000.ethernet eth0: Link is Down [ 218.360121] m25p80 spi32766.0: flash operation timed out [ 229.218602] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [ 239.229004] rk_gmac-dwmac fe300000.ethernet eth0: Link is Down [ 252.231454] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [ 272.250703] rk_gmac-dwmac fe300000.ethernet eth0: Link is Down [ 285.269446] rk_gmac-dwmac fe300000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [ 348.542957] m25p80 spi32766.0: flash operation timed out

And once, I got crash: https://p.devtrue.net/ucp6psr/

[chandupreetham]

flash openmediafault arm64 image and attach to hdmi display

you will get terminal screen where u can run ur commands

sudo apt-get upgrade

sudo apt-get update

sudo apt-get install aptitude tasksel

tasksel

now choose operating system that u want to install

install ubuntu , u will get success

On Wed, Nov 7, 2018 at 3:11 AM Lev Lybin notifications@github.com wrote:

Really, only under openmediavault rock64_write_spi_flash.sh works, there is a difference, on others: libmtd: error!: MEMERASE64 ioctl failed for eraseblock 10 (mtd0) error 110 (Connection timed out)

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ayufan-rock64/linux-build/issues/145#issuecomment-436539246, or mute the thread https://github.com/notifications/unsubscribe-auth/Am8N1C-6KqdRB-kCJHWEH3fY0cZE369qks5uspWggaJpZM4TA09d .

[llybin]

Thx, I can install and I can boot. But if do power off(not always reproduced), or await - board doesn't will respond, boot doesn't work again.

On pine64 / armbian / dietpi forums I found same issues, no answers, because not all have trouble. https://forum.pine64.org/showthread.php?tid=5258 I have Forsesee 16 gb too from official store.

UART shows in this time: DDR Version 1.12 20180518 In

Logs on emmc empty - nothing strange before stuck.

I turn off power supply, await 20-30 minutes, turn on, and a board works again, white LED lighted up.

I have only two logs attached above with kernel crash.

Under all images (rockpro64) I can't flash spi, m25p80 spi32766.0: flash operation timed out I just experimented and notice that.

I was able to flash spi only under LibreELEC, also https://github.com/ayufan-rock64/linux-u-boot/releases , but under linux in this repository - I got errors.

[llybin]

I turn off devices after stuck, dmesg: https://p.devtrue.net/f6ijjor/

Linux on emmc is same as when board were not booting (no white led light)

[llybin]

MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 400MHz 0,1
channel 0
CS = 0
MR0=0x98
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x98
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 800MHz 1,0
ch 0 ddrconfig = 0x101, ddrsize = 0x2020
ch 1 ddrconfig = 0x101, ddrsize = 0x2020
pmugrf_os_reg[2] = 0x3AA1FAA1, stride = 0xD
OUT  
U-Boot SPL board init

U-Boot SPL 2017.09-rockchip-ayufan-1025-g482cd6ec8b (Jul 26 2018 - 08:18:48)
booted from eMMC
Trying to boot from MMC1
NOTICE:  BL31: v1.3(debug):d98d16e
NOTICE:  BL31: Built : 15:03:07, May 10 2018
NOTICE:  BL31: Rockchip release version: v1.1
INFO:    GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 0
INFO:    plat_rockchip_pmu_init(1151): pd status 3e
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x200000
INFO:    SPSR = 0x3c9

U-Boot 2017.09-rockchip-ayufan-1025-g482cd6ec8b (Jul 26 2018 - 08:18:55 +0000)

Model: Pine64 RockPro64
DRAM:  3.9 GiB
DCDC_REG1@vdd_center: ; enabling
DCDC_REG2@vdd_cpu_l: ; enabling
DCDC_REG3@vcc_ddr: ; enabling (ret: -38)
DCDC_REG4@vcc_1v8: set 1800000 uV; enabling
LDO_REG1@vcc1v8_dvp: set 1800000 uV; enabling
LDO_REG2@vcc3v0_touch: set 3000000 uV; enabling
LDO_REG3@vcc1v8_pmu: set 1800000 uV; enabling
LDO_REG4@vcc_sd: set 3300000 uV; enabling
LDO_REG5@vcca3v0_codec: set 3000000 uV; enabling
LDO_REG6@vcc_1v5: set 1500000 uV; enabling
LDO_REG7@vcca1v8_codec: set 1800000 uV; enabling
LDO_REG8@vcc_3v0: set 3000000 uV; enabling
SWITCH_REG1@vcc3v3_s3: ; enabling (ret: -38)
SWITCH_REG2@vcc3v3_s0: ; enabling (ret: -38)
vcc1v8-s0@vcc1v8_s0: set 1800000 uV; enabling (ret: -38)
dc-12v@dc_12v: set 12000000 uV; enabling (ret: -38)
vcc-sys@vcc_sys: set 5000000 uV; enabling (ret: -38)
vcc3v3-sys@vcc3v3_sys: set 3300000 uV; enabling (ret: -38)
vcc-phy-regulator@vcc_phy: ; enabling (ret: -38)
vdd-log@vdd_log: ; enabling (ret: -38)
MMC:   sdhci@fe330000: 0, dwmmc@fe320000: 1
SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment

In:    serial@ff1a0000
Out:   serial@ff1a0000
Err:   serial@ff1a0000
Model: Pine64 RockPro64
Net:   eth0: ethernet@fe300000

[chandupreetham]

in tasksel try to install ubuntuu desktop

On Fri, Nov 9, 2018 at 1:31 AM Lev Lybin notifications@github.com wrote:

MR24=0x8 MR25=0x0 CS = 1 MR0=0x18 MR4=0x2 MR5=0xFF MR8=0x8 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! change freq to 400MHz 0,1 channel 0 CS = 0 MR0=0x98 MR4=0x2 MR5=0xFF MR8=0x8 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 CS = 1 MR0=0x18 MR4=0x2 MR5=0xFF MR8=0x8 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 1 CS = 0 MR0=0x98 MR4=0x2 MR5=0xFF MR8=0x8 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 CS = 1 MR0=0x18 MR4=0x2 MR5=0xFF MR8=0x8 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0x0 channel 0 training pass! channel 1 training pass! change freq to 800MHz 1,0 ch 0 ddrconfig = 0x101, ddrsize = 0x2020 ch 1 ddrconfig = 0x101, ddrsize = 0x2020 pmugrf_os_reg[2] = 0x3AA1FAA1, stride = 0xD OUT U-Boot SPL board init

U-Boot SPL 2017.09-rockchip-ayufan-1025-g482cd6ec8b (Jul 26 2018 - 08:18:48) booted from eMMC Trying to boot from MMC1 NOTICE: BL31: v1.3(debug):d98d16e NOTICE: BL31: Built : 15:03:07, May 10 2018 NOTICE: BL31: Rockchip release version: v1.1 INFO: GICv3 with legacy support detected. ARM GICV3 driver initialized in EL3 INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 0 INFO: plat_rockchip_pmu_init(1151): pd status 3e INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9

U-Boot 2017.09-rockchip-ayufan-1025-g482cd6ec8b (Jul 26 2018 - 08:18:55 +0000)

Model: Pine64 RockPro64 DRAM: 3.9 GiB DCDC_REG1@vdd_center: ; enabling DCDC_REG2@vdd_cpu_l: ; enabling DCDC_REG3@vcc_ddr: ; enabling (ret: -38) DCDC_REG4@vcc_1v8: set 1800000 uV; enabling LDO_REG1@vcc1v8_dvp: set 1800000 uV; enabling LDO_REG2@vcc3v0_touch: set 3000000 uV; enabling LDO_REG3@vcc1v8_pmu: set 1800000 uV; enabling LDO_REG4@vcc_sd: set 3300000 uV; enabling LDO_REG5@vcca3v0_codec: set 3000000 uV; enabling LDO_REG6@vcc_1v5: set 1500000 uV; enabling LDO_REG7@vcca1v8_codec: set 1800000 uV; enabling LDO_REG8@vcc_3v0: set 3000000 uV; enabling SWITCH_REG1@vcc3v3_s3: ; enabling (ret: -38) SWITCH_REG2@vcc3v3_s0: ; enabling (ret: -38) vcc1v8-s0@vcc1v8_s0: set 1800000 uV; enabling (ret: -38) dc-12v@dc_12v: set 12000000 uV; enabling (ret: -38) vcc-sys@vcc_sys: set 5000000 uV; enabling (ret: -38) vcc3v3-sys@vcc3v3_sys: set 3300000 uV; enabling (ret: -38) vcc-phy-regulator@vcc_phy: ; enabling (ret: -38) vdd-log@vdd_log: ; enabling (ret: -38) MMC: sdhci@fe330000: 0, dwmmc@fe320000: 1 SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB *** Warning - bad CRC, using default environment

In: serial@ff1a0000 Out: serial@ff1a0000 Err: serial@ff1a0000 Model: Pine64 RockPro64 Net: eth0: ethernet@fe300000

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ayufan-rock64/linux-build/issues/145#issuecomment-437264110, or mute the thread https://github.com/notifications/unsubscribe-auth/Am8N1GFGfn5GgrMVr1Qgu0YD_nrqSIA0ks5utSE8gaJpZM4TA09d .

[llybin]

It is strange, but, really, one day without crashes with bionic-lxde-rockpro64. I removed additional packages by https://github.com/ayufan-rock64/linux-package/blob/master/root/usr/local/sbin/install_desktop.sh

Why under bionic-lxde-rockpro64 works, but under others kernel crashes...

I don't see in logs now:

[ 3966.656954] usb 10-3: reset SuperSpeed USB device number 3 using xhci_hcd
[ 3969.286859] usb 10-3: reset SuperSpeed USB device number 3 using xhci_hcd
[ 3971.284889] usb 10-3: reset SuperSpeed USB device number 3 using xhci_hcd
[ 3973.738677] usb 10-3: reset SuperSpeed USB device number 3 using xhci_hcd
[ 4007.029496] usb 10-3: reset SuperSpeed USB device number 3 using xhci_hcd
[ 4009.548435] xhci_hcd 0000:01:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued?
[ 4042.996762] usb 10-3: reset SuperSpeed USB device number 3 using xhci_hcd
[ 4045.515788] xhci_hcd 0000:01:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued?
[ 4079.018244] usb 10-3: reset SuperSpeed USB device number 3 using xhci_hcd
[ 4081.538333] xhci_hcd 0000:01:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued?
[ 4094.056556] EXT4-fs error (device sdf1): ext4_find_extent:910: inode #302082: comm scavenger: pblk 438336000 bad header/extent: invalid magic - magic f39, entries 17478, max 20872(0), depth 26550(0)
[ 4125.045784] usb 10-3: reset SuperSpeed USB device number 3 using xhci_hcd
[ 4158.064591] usb 10-3: reset SuperSpeed USB device number 3 using xhci_hcd
[ 4158.082063] xhci_hcd 0000:01:00.0: WARN Event TRB for slot 2 ep 2 with no TDs queued?
[ 4189.052740] usb 10-3: reset SuperSpeed USB device number 3 using xhci_hcd
[ 4222.070111] usb 10-3: reset SuperSpeed USB device number 3 using xhci_hcd
[ 4224.589439] sd 2:0:0:0: timing out command, waited 180s
[ 4224.590309] sd 2:0:0:0: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
[ 4224.590339] sd 2:0:0:0: [sde] tag#0 Sense Key : 0x4 [current] 
[ 4224.590365] sd 2:0:0:0: [sde] tag#0 ASC=0x40 <<vendor>>ASCQ=0x99 
[ 4224.590396] sd 2:0:0:0: [sde] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 d6 45 b1 e0 00 00 00 20 00 00
[ 4224.590417] blk_update_request: I/O error, dev sde, sector 3594891744
[ 4255.043288] usb 10-3: reset SuperSpeed USB device number 3 using xhci_hcd

Nov 09 16:08:15 rockpro64 kernel: usb 8-2: reset SuperSpeed USB device number 3 using xhci_hcd
Nov 09 16:08:17 rockpro64 kernel: xhci_hcd 0000:01:00.0: WARN Event TRB for slot 1 ep 2 with no TDs queued?
Nov 09 16:08:50 rockpro64 kernel: usb 8-2: reset SuperSpeed USB device number 3 using xhci_hcd
Nov 09 16:08:53 rockpro64 kernel: xhci_hcd 0000:01:00.0: WARN Event TRB for slot 1 ep 2 with no TDs queued?
Nov 09 16:09:06 rockpro64 kernel: EXT4-fs error (device sde1): ext4_find_extent:916: inode #302082: comm scavenger: pblk 851474688 bad header/extent: invalid magic - magic c19c, entries 4923, max 17809(0), depth 19583(0)
Nov 09 16:09:36 rockpro64 kernel: usb 8-2: reset SuperSpeed USB device number 3 using xhci_hcd
Nov 09 16:10:01 rockpro64 CRON[1399]: pam_unix(cron:session): session opened for user root by (uid=0)
Nov 09 16:10:01 rockpro64 CRON[1400]: (root) CMD (/home/rock64/stat.sh | /home/rock64/ansi2html.sh > /var/www/html/index.html)
Nov 09 16:10:01 rockpro64 CRON[1399]: pam_unix(cron:session): session closed for user root
Nov 09 16:10:10 rockpro64 kernel: usb 8-2: reset SuperSpeed USB device number 3 using xhci_hcd
Nov 09 16:10:10 rockpro64 kernel: xhci_hcd 0000:01:00.0: WARN Event TRB for slot 1 ep 2 with no TDs queued?
Nov 09 16:10:41 rockpro64 kernel: usb 8-2: reset SuperSpeed USB device number 3 using xhci_hcd
Nov 09 16:11:14 rockpro64 kernel: usb 8-2: reset SuperSpeed USB device number 3 using xhci_hcd
Nov 09 16:11:47 rockpro64 kernel: usb 8-2: reset SuperSpeed USB device number 3 using xhci_hcd
Nov 09 16:11:47 rockpro64 kernel: sd 2:0:0:0: timing out command, waited 180s
Nov 09 16:11:47 rockpro64 kernel: sd 2:0:0:0: [sdd] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
Nov 09 16:11:47 rockpro64 kernel: sd 2:0:0:0: [sdd] tag#0 CDB: opcode=0x88 88 00 00 00 00 01 9d 99 11 e0 00 00 00 20 00 00
Nov 09 16:11:47 rockpro64 kernel: blk_update_request: I/O error, dev sdd, sector 6939021792
Nov 09 16:12:19 rockpro64 kernel: usb 8-2: reset SuperSpeed USB device number 3 using xhci_hcd
Nov 09 16:12:20 rockpro64 kernel: sd 2:0:0:1: [sde] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x05 driverbyte=0x00
Nov 09 16:12:20 rockpro64 kernel: sd 2:0:0:1: [sde] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 08 00 00 00 00 08 00 00
Nov 09 16:12:20 rockpro64 kernel: blk_update_request: I/O error, dev sde, sector 2048
Nov 09 16:12:20 rockpro64 kernel: Buffer I/O error on dev sde1, logical block 0, lost sync page write
Nov 09 16:12:20 rockpro64 kernel: EXT4-fs error (device sde1): ext4_find_extent:916: inode #302082: comm scavenger: pblk 851474688 bad header/extent: invalid magic - magic c19c, entries 4923, max 17809(0), depth 19583(0)
Nov 09 16:12:20 rockpro64 kernel: EXT4-fs (sde1): previous I/O error to superblock detected
Nov 09 16:12:53 rockpro64 kernel: usb 8-2: reset SuperSpeed USB device number 3 using xhci_hcd
Nov 09 16:13:26 rockpro64 kernel: usb 8-2: reset SuperSpeed USB device number 3 using xhci_hcd
Nov 09 16:13:57 rockpro64 kernel: usb 8-2: reset SuperSpeed USB device number 3 using xhci_hcd
Nov 09 16:14:27 rockpro64 kernel: usb 8-2: reset SuperSpeed USB device number 3 using xhci_hcd

I think I found solution: add in /etc/default/extlinux systemd.gpt_auto=0 usbcore.autosuspend=-1

sudo update-extlinux.sh and reboot

But still have question what diffrent between minimal and desktop, why problem is not reproduced under desktop version, I found one diffrence only $SIZE, hm...

[llybin]

Crashed again on bionic-lxde, it's good, no weirdness ) Works stable only with usbcore.autosuspend=-1 When kernel crashes - board stuck, need turn off power and wait 10-60mins.

[mohalaci]

Crashed again on bionic-lxde, it's good, no weirdness ) Works stable only with usbcore.autosuspend=-1 When kernel crashes - board stuck, need turn off power and wait 10-60mins.

@llybin Did you simply add this line:

systemd.gpt_auto=0 usbcore.autosuspend=-1

to the end of the /etc/default/extlinux file?

[llybin]

Crashed again on bionic-lxde, it's good, no weirdness ) Works stable only with usbcore.autosuspend=-1 When kernel crashes - board stuck, need turn off power and wait 10-60mins.

@llybin Did you simply add this line:

systemd.gpt_auto=0 usbcore.autosuspend=-1

to the end of the /etc/default/extlinux file?

Board is still stuck sometimes, but less often. Need to try more recent mainline kernels. Look on https://www.armbian.com/rockpro64/ Community there is more active.

[Godje]

Same issue as described in the original post version (Latest Release) rockpro64 0.7.9

[ayufan]

Please gry 0.8.0rc12

On Sun, 2 Jun 2019 at 22:22, Daniel Mayovskiy notifications@github.com wrote:

Same issue as described in the original post version (Latest Release) rockpro64 0.7.9

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/ayufan-rock64/linux-build/issues/145?email_source=notifications&email_token=AASOSQJBE2AY2DW7XRTYNH3PYQTVHA5CNFSM4EYDJ5O2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWX5HTY#issuecomment-498062287, or mute the thread https://github.com/notifications/unsubscribe-auth/AASOSQJOOSGF4VDS634ZKGLPYQTVHANCNFSM4EYDJ5OQ .