Issue has been fixed as the Rock Pi works fine until now.
Ubuntu server kernel issue
1 Like
Hi, we had the same issue every 4-7 days.
After updating kernel to [4.4.154-95] we got the same error after 24 days uptime:
Jan 07 17:04:47 linux kernel: dhd_open: Exit ret=0
Jan 07 17:04:47 linux kernel: dhd_set_mac_addr_handler: MACID is overwritten
Jan 07 17:04:47 linux NetworkManager[297]: [1578413087.9992] device (wlan0): supplicant interface state: inactive -> disabled
Jan 07 17:04:48 linux NetworkManager[297]: [1578413088.0000] device (wlan0): supplicant interface state: disabled -> inactive
Jan 07 17:04:48 linux wpa_supplicant[298]: wlan0: Reject scan trigger since one is already pending
Jan 07 17:09:03 linux kernel: dwmmc_rockchip fe310000.dwmmc: All phases bad!
Jan 07 17:09:03 linux kernel: mmc2: tuning execution failed
Jan 07 17:09:03 linux kernel: bcmsdh_sdmmc: Failed to Read byte F1:@0x1001f=ff, Err: -5
Jan 07 17:09:03 linux kernel: dwmmc_rockchip fe310000.dwmmc: All phases bad!
Jan 07 17:09:03 linux kernel: mmc2: tuning execution failed
Jan 07 17:09:03 linux kernel: bcmsdh_sdmmc: Failed to Read byte F1:@0x1001f=ff, Err: -5
Jan 07 17:09:03 linux kernel: dwmmc_rockchip fe310000.dwmmc: All phases bad!
Jan 07 17:09:03 linux kernel: mmc2: tuning execution failed
Jan 07 17:09:03 linux kernel: bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=00, Err: -5
Jan 07 17:09:03 linux kernel: dwmmc_rockchip fe310000.dwmmc: All phases bad!
Jan 07 17:09:03 linux kernel: mmc2: tuning execution failed
Jan 07 17:09:03 linux kernel: bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=00, Err: -5
Jan 07 17:09:03 linux kernel: dwmmc_rockchip fe310000.dwmmc: All phases bad!
Jan 07 17:09:03 linux kernel: mmc2: tuning execution failed
Jan 07 17:09:03 linux kernel: bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=00, Err: -5
Jan 07 17:09:03 linux kernel: dwmmc_rockchip fe310000.dwmmc: All phases bad!
Jan 07 17:09:03 linux kernel: mmc2: tuning execution failed
Jan 07 17:09:03 linux kernel: bcmsdh_sdmmc: Failed to Read byte F1:@0x1001f=ff, Err: -5
Jan 07 17:09:03 linux kernel: dwmmc_rockchip fe310000.dwmmc: All phases bad!
Jan 07 17:09:03 linux kernel: mmc2: tuning execution failed
Jan 07 17:09:03 linux kernel: bcmsdh_sdmmc: Failed to Read byte F1:@0x1001f=ff, Err: -5
Jan 07 17:09:03 linux kernel: dwmmc_rockchip fe310000.dwmmc: All phases bad!
Jan 07 17:09:03 linux kernel: mmc2: tuning execution failed
Jan 07 17:09:03 linux kernel: bcmsdh_sdmmc: Failed to Read byte F1:@0x1001f=ff, Err: -5
Jan 07 17:09:03 linux kernel: dwmmc_rockchip fe310000.dwmmc: All phases bad!
Jan 07 17:09:03 linux kernel: mmc2: tuning execution failed
Jan 07 17:09:03 linux kernel: bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=00, Err: -5
Jan 07 17:09:03 linux kernel: dwmmc_rockchip fe310000.dwmmc: All phases bad!
Jan 07 17:09:03 linux kernel: mmc2: tuning execution failed
Jan 07 17:09:03 linux kernel: bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=00, Err: -5
Jan 07 17:09:03 linux kernel: bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=00, Err: -5
Jan 07 17:09:03 linux kernel: bcmsdh_sdmmc: Failed to Read byte F1:@0x1001f=ff, Err: -5
Jan 07 17:09:03 linux kernel: bcmsdh_sdmmc: Failed to Read byte F1:@0x1001f=ff, Err: -5
Jan 07 17:09:03 linux kernel: bcmsdh_sdmmc: Failed to Read byte F1:@0x1001f=ff, Err: -5
…
The last message repeats for about 3 minutes until system crashes.
After restart the same happend again 1 day later.
The last normal message when crashing is always this:
linux wpa_supplicant[298]: wlan0: Reject scan trigger since one is already pending
Any ideas?
Hi @marcel, I also have this issue on my 32GB eMMC. I don’t understand why the issue is claimed as resolved above. I have not found a solution to the problem. I’m not enough of an expert to go into the bowels of the kernel. I’d like to see a fix deployed, I’d hate to have to dismantle the kit to replace the chip. I’d appreciate any update from anyone else on this topic, including Radxa, please?! Thanks.
Hi @jack, thanks for the hint, but if you scroll down to the very end of the discussion I hope you’ll find that the issue is not resolved even in the latest kernel, which I presume is the following (on my rock pi 4):
/boot$ uname -r
4.4.154-95-rockchip-gd2ab1f26e1b3
Really appreciate it if we could see this fixed because I’m forced to reboot every 24 hours to prevent it from hanging up the kit. Cheers!
I run this today:
$ sudo apt-get install linux-4.4-latest
Reading package lists… Done
Building dependency tree
Reading state information… Done
linux-4.4-latest is already the newest version (4.4.154-95-rockchip).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
So… not sure where you’re getting yours from?
I’m down to rebooting every 12 hours at the moment.
I’ll give it a go. Lots of issues with space on /boot though. Down to just 1 kernel at the moment, I hope I can install the test-repo one next to it. Cheers.
Just to let you all know, that indeed on this kernel I have no further issues:
uname -r
4.4.154-104-rockchip-g3037f71a0de7I have also problems with Rock Pi 4B running latest Ubuntu on NVME SSD. I get that errors and access over LAN stopped to device…
[107518.799111] bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=00, Err: -5
[107518.801251] Not tainted 4.4.154-95-rockchip-gd2ab1f26e1b3 #1
[107518.801351] bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=00, Err: -5
[107518.803624] bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=00, Err: -5
[107518.804841] bcmsdh_sdmmc: Failed to Read byte F1:@0x1001f=ff, Err: -5
[107518.809104] “echo 0 > /proc/sys/kernel/hung_task_timeout_secs” disables this message.
[107518.811323] wpa_supplicant D ffffff80080856f4 0 298 1 0x00000000
[107518.813620] Call trace:
[107518.815524] [] __switch_to+0x9c/0xc8
[107518.817638] [] __schedule+0x398/0x618
[107518.819127] bcmsdh_sdmmc: Failed to Read byte F1:@0x1001f=ff, Err: -5
[107518.821347] bcmsdh_sdmmc: Failed to Read byte F1:@0x1001f=ff, Err: -5
[107518.822380] bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=00, Err: -5
[107518.824439] bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=00, Err: -5
[107518.826413] bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=00, Err: -5
[107518.827536] bcmsdh_sdmmc: Failed to Read byte F1:@0x1001f=ff, Err: -5
[107518.829582] bcmsdh_sdmmc: Failed to Read byte F1:@0x1001f=ff, Err: -5
[107518.835171] bcmsdh_sdmmc: Failed to Read byte F1:@0x1001f=ff, Err: -5
[107518.836211] bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=00, Err: -5
[107518.838230] bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=00, Err: -5
[107518.840211] bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=00, Err: -5
[107518.841189] bcmsdh_sdmmc: Failed to Read byte F1:@0x1001f=ff, Err: -5
[107518.843184] bcmsdh_sdmmc: Failed to Read byte F1:@0x1001f=ff, Err: -5
[107518.845159] bcmsdh_sdmmc: Failed to Read byte F1:@0x1001f=ff, Err: -5
[107518.846186] bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=00, Err: -5
[107518.848122] bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=00, Err: -5
[107518.850065] bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=00, Err: -5
[107518.851177] bcmsdh_sdmmc: Failed to Read byte F1:@0x1001f=ff, Err: -5
[107518.853077] bcmsdh_sdmmc: Failed to Read byte F1:@0x1001f=ff, Err: -5
[107518.854977] bcmsdh_sdmmc: Failed to Read byte F1:@0x1001f=ff, Err: -5
[107518.855916] bcmsdh_sdmmc: Failed to Write byte F1:@0x1001f=00, Err: -5
I running 4.4.154-95-rockchip-gd2ab1f26e1b3 kernel and Im try update it to testing one 4.4.154-104-rockchip-g3037f71a0de7 but after reboot rockpi do not boot anymore from NVME… Im try also older kernel 4.4.154-99-rockchip but same hapen… I can then only boot if I plug sdcard with ubuntu in slot and then it boot(it boot to nvme system) then I can remove upgraded kernel, shutdown system, remove sd card and power it on and then it normaly boot to kernel version 95…
Are there some special upgrade instructions for NVME?
Thanks for any help.
Nobody cant help?
Im check fstab and looks ok:
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/nvme0n1p4 /boot vfat defaults 0 2
lsblk also looks ok:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mtdblock0 31:0 0 4M 0 disk
nvme0n1 259:0 0 238,5G 0 disk
├─nvme0n1p1 259:1 0 3,9M 0 part
├─nvme0n1p2 259:2 0 4M 0 part
├─nvme0n1p3 259:3 0 4M 0 part
├─nvme0n1p4 259:4 0 112M 0 part /boot
└─nvme0n1p5 259:5 0 238,4G 0 part /
Then Im run:
sudo apt-get install -y rockchip-overlay
sudo apt-get install -y linux-4.4-latest rockpi4-dtbo rockpi4b-rk-u-boot-latest
And it install without problems:
Branje seznama paketov ... Narejeno
Gradnja drevesa odvisnosti
Branje podatkov o stanju ... Narejeno
rockpi4-dtbo is already the newest version (4.1).
rockpi4b-rk-u-boot-latest is already the newest version (2017.09-2686-g18c70dba63).
The following additional packages will be installed:
linux-firmware-image-4.4.154-104-rockchip-g3037f71a0de7 linux-headers-4.4.154-104-rockchip-g3037f71a0de7 linux-image-4.4.154-104-rockchip-g3037f71a0de7
Naslednji NOVI paketi bodo nameščeni:
linux-4.4-latest linux-firmware-image-4.4.154-104-rockchip-g3037f71a0de7 linux-headers-4.4.154-104-rockchip-g3037f71a0de7
linux-image-4.4.154-104-rockchip-g3037f71a0de7
0 nadgrajenih, 4 na novo nameščenih, 0 bo odstranjenih in 0 ne nadgrajenih.
Potrebno je dobiti 0 B/25,5 MB arhivov.
Po tem opravilu bo porabljenega 155 MB dodatnega prostora.
Selecting previously unselected package linux-image-4.4.154-104-rockchip-g3037f71a0de7.
(Reading database ... 55994 files and directories currently installed.)
Preparing to unpack .../linux-image-4.4.154-104-rockchip-g3037f71a0de7_4.4.154-104-rockchip_all.deb ...
Unpacking linux-image-4.4.154-104-rockchip-g3037f71a0de7 (4.4.154-104-rockchip) ...
Selecting previously unselected package linux-firmware-image-4.4.154-104-rockchip-g3037f71a0de7.
Preparing to unpack .../linux-firmware-image-4.4.154-104-rockchip-g3037f71a0de7_4.4.154-104-rockchip_all.deb ...
Unpacking linux-firmware-image-4.4.154-104-rockchip-g3037f71a0de7 (4.4.154-104-rockchip) ...
Selecting previously unselected package linux-headers-4.4.154-104-rockchip-g3037f71a0de7.
Preparing to unpack .../linux-headers-4.4.154-104-rockchip-g3037f71a0de7_4.4.154-104-rockchip_all.deb ...
Unpacking linux-headers-4.4.154-104-rockchip-g3037f71a0de7 (4.4.154-104-rockchip) ...
Selecting previously unselected package linux-4.4-latest.
Preparing to unpack .../linux-4.4-latest_4.4.154-104-rockchip_all.deb ...
Unpacking linux-4.4-latest (4.4.154-104-rockchip) ...
Setting up linux-firmware-image-4.4.154-104-rockchip-g3037f71a0de7 (4.4.154-104-rockchip) ...
Setting up linux-headers-4.4.154-104-rockchip-g3037f71a0de7 (4.4.154-104-rockchip) ...
Setting up linux-image-4.4.154-104-rockchip-g3037f71a0de7 (4.4.154-104-rockchip) ...
Kernel configuration : earlyprintk console=ttyFIQ0,1500000n8 rw init=/sbin/init rootfstype=ext4 rootwait root=PARTUUID=B921B045-1DF0-41C3-AF44-4C6F280D3FAE
Im recheck /boot/hw_intfc.conf and it looks as must be.
My extlinux.conf looks ok:
timeout 10
menu title select kernel
label kernel-4.4.154-104-rockchip-g3037f71a0de7
kernel /vmlinuz-4.4.154-104-rockchip-g3037f71a0de7
devicetreedir /dtbs/4.4.154-104-rockchip-g3037f71a0de7
append earlyprintk console=ttyFIQ0,1500000n8 rw init=/sbin/init rootfstype=ext4 rootwait root=PARTUUID=B921B045-1DF0-41C3-AF44-4C6F280D3FAE
label kernel-4.4.154-95-rockchip-gd2ab1f26e1b3
kernel /vmlinuz-4.4.154-95-rockchip-gd2ab1f26e1b3
devicetreedir /dtbs/4.4.154-95-rockchip-gd2ab1f26e1b3
append earlyprintk console=ttyFIQ0,1500000n8 rw init=/sbin/init rootfstype=ext4 rootwait root=PARTUUID=B921B045-1DF0-41C3-AF44-4C6F280D3FAE
When I reboot device it do not boot anymore…
It’s before or after upgrade? If it’s after and you do not remember what happened before, then try root=/dev/nvme0n1p5
1 Like
@rua1 Thanks for your reply. It is after update. I don’t have extlinux.conf from original system before update so don’t know what is default setting for booting from nvme…
Im try add at the end of file:
default kernel-4.4.154-95-rockchip-gd2ab1f26e1b3
It still do not boot normaly. Im also try this:
timeout 10
menu title select kernel
label kernel-4.4.154-104-rockchip-g3037f71a0de7
kernel /vmlinuz-4.4.154-104-rockchip-g3037f71a0de7
devicetreedir /dtbs/4.4.154-104-rockchip-g3037f71a0de7
append earlyprintk console=ttyFIQ0,1500000n8 rw init=/sbin/init rootfstype=ext4 rootwait root=/dev/nvme0n1p5
label kernel-4.4.154-95-rockchip-gd2ab1f26e1b3
kernel /vmlinuz-4.4.154-95-rockchip-gd2ab1f26e1b3
devicetreedir /dtbs/4.4.154-95-rockchip-gd2ab1f26e1b3
append earlyprintk console=ttyFIQ0,1500000n8 rw init=/sbin/init rootfstype=ext4 rootwait root=PARTUUID=B921B045-1DF0-41C3-AF44-4C6F280D3FAE
But still do not boot. Now when I have updated kernel I can boot only if I plug sdcard it automaticly mount nvme as root and boot partition and I can remove latest kernel and then it normaly boot…
When I sucessfully boot with latest kernel and sd card inserted lsblk show this:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mtdblock0 31:0 0 4M 0 disk
mmcblk0 179:0 0 7,2G 0 disk
├─mmcblk0p1 179:1 0 3,9M 0 part
├─mmcblk0p2 179:2 0 4M 0 part
├─mmcblk0p3 179:3 0 4M 0 part
├─mmcblk0p4 179:4 0 112M 0 part
└─mmcblk0p5 179:5 0 7,1G 0 part
nvme0n1 259:0 0 238,5G 0 disk
├─nvme0n1p1 259:1 0 3,9M 0 part
├─nvme0n1p2 259:2 0 4M 0 part
├─nvme0n1p3 259:3 0 4M 0 part
├─nvme0n1p4 259:4 0 112M 0 part /boot
└─nvme0n1p5 259:5 0 238,4G 0 part /
Im right now make it work with comment of older kernel:
timeout 10
menu title select kernel
label kernel-4.4.154-104-rockchip-g3037f71a0de7
kernel /vmlinuz-4.4.154-104-rockchip-g3037f71a0de7
devicetreedir /dtbs/4.4.154-104-rockchip-g3037f71a0de7
append earlyprintk console=ttyFIQ0,1500000n8 rw init=/sbin/init rootfstype=ext4 rootwait root=/dev/nvme0n1p5
#label kernel-4.4.154-95-rockchip-gd2ab1f26e1b3
# kernel /vmlinuz-4.4.154-95-rockchip-gd2ab1f26e1b3
# devicetreedir /dtbs/4.4.154-95-rockchip-gd2ab1f26e1b3
# append earlyprintk console=ttyFIQ0,1500000n8 rw init=/sbin/init rootfstype=ext4 rootwait root=PARTUUID=B921B045-1DF0-41C3-AF44-4C6F280D3FAE
Will in next days try few reboots to see if work normaly and then run it few days to see if issue with freezing is resolved…
Thanks for your help.
It’s not nesseary. Copy worked extlinux.conf to extlinux.conf.my and when next time kernel was upgraded you edit extlinux.conf as extlinux.conf.my. Trough upgrade kernel radxa replaced extlinux.conf to default root partition.
2radxa: It’s difficult take root partition from previous conf ?
Now sometimes it doesn’t load in first time too. Early, with non modified M2 extender, system can be frieezed at any time. It’s work normally after biting the “ears” of a small board of extender
1 Like
Use blkid to gain IDs of the partitions.
@rua1 I have this extender board:
I have it together with case and RockPi B 1.4 only for 1 month and didn’t have any issues except that one that kernell start having errors and then board stop respond on network…
@pbies blkid do not work on my system it just do not output anything… But Im get partition ID’s with:
lsblk -o name,mountpoint,size,uuid
NAME MOUNTPOINT SIZE UUID
mtdblock0 4M
nvme0n1 238,5G
├─nvme0n1p1 3,9M
├─nvme0n1p2 4M
├─nvme0n1p3 4M
├─nvme0n1p4 /boot 112M 1121-C996
└─nvme0n1p5 / 238,4G 9d4f00d3-3731-4dac-a791-7dbd9cb156e2
I will try put that p5 UUID into extlinux.conf …
It’s don’t help. Look at my problem with M2 extension. https://forum.radxa.com/t/rock-pi-4x-m-2-extension-board-v1-4-problem/2798 May be you have same
Today Im try change extlinux.conf that use UUID 9d4f00d3-3731-4dac-a791-7dbd9cb156e2 but system failed to boot. It didtnt boot even I put sdcard to board so need to disconnect nvme, boot from sdcard and plug NVME to USB reader and fix extlinux.conf.
Im try to use that:
timeout 10
menu title select kernel
label kernel-4.4.154-104-rockchip-g3037f71a0de7
kernel /vmlinuz-4.4.154-104-rockchip-g3037f71a0de7
devicetreedir /dtbs/4.4.154-104-rockchip-g3037f71a0de7
append earlyprintk console=ttyFIQ0,1500000n8 rw init=/sbin/init rootfstype=ext4 rootwait root=PARTUUID=9d4f00d3-3731-4dac-a791-7dbd9cb156e2
Im also try use UUID in upper case like 9D4F00D3-3731-4DAC-A791-7DBD9CB156E2 but it do not boot using UUID …
Please try to add line after kernel:
initrd /initrd.img-4.4.154-104-rockchip-g3037f71a0de7
@pbies So like this:
timeout 10
menu title select kernel
label kernel-4.4.154-104-rockchip-g3037f71a0de7
kernel /vmlinuz-4.4.154-104-rockchip-g3037f71a0de7
initrd /initrd.img-4.4.154-104-rockchip-g3037f71a0de7
devicetreedir /dtbs/4.4.154-104-rockchip-g3037f71a0de7
append earlyprintk console=ttyFIQ0,1500000n8 rw init=/sbin/init rootfstype=ext4 rootwait root=PARTUUID=9D4F00D3-3731-4DAC-A791-7DBD9CB156E2
It doesn’t work …