Ubuntu server kernel issue

#71

I 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.

#72

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…

#73

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
#74

@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.

#75

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
#76

Use blkid to gain IDs of the partitions.

#77

@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 …

#78

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

#79

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 …

#80

Please try to add line after kernel:

initrd /initrd.img-4.4.154-104-rockchip-g3037f71a0de7

#81

@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 …

#82

Is the mentioned file there?

#83

In boot partition is this file not present:

-rwxr-xr-x 1 root root   155578 jan  7 11:20 config-4.4.154-104-rockchip-g3037f71a0de7
-rwxr-xr-x 1 root root   155489 okt 21 08:43 config-4.4.154-95-rockchip-gd2ab1f26e1b3
drwxr-xr-x 4 root root     2048 feb 21 07:30 dtbs
drwxr-xr-x 2 root root     2048 feb 23 16:50 extlinux
-rwxr-xr-x 1 root root     1806 feb 22 08:12 hw_intfc.conf
drwxr-xr-x 2 root root     2048 nov 19 08:20 overlays
-rwxr-xr-x 1 root root  4561892 jan  7 11:20 System.map-4.4.154-104-rockchip-g3037f71a0de7
-rwxr-xr-x 1 root root  4567572 okt 21 08:43 System.map-4.4.154-95-rockchip-gd2ab1f26e1b3
-rwxr-xr-x 1 root root 19494920 jan  7 11:20 vmlinuz-4.4.154-104-rockchip-g3037f71a0de7
-rwxr-xr-x 1 root root 19496968 okt 21 08:43 vmlinuz-4.4.154-95-rockchip-gd2ab1f26e1b3
#84

So you are missing the file. Put it there and have fun with running OS.

#85

@pbies I really don’t know why I need to install something which I really don’t need and will in future need to patch… Im make run OS with setting root=/dev/nvme0n1p5 system with that boot normally to new updated kernel and run without any issues… It only do not boot if I try to use UUID of that partition …

#86

That’s kernel ramdisk, a general and base code/data that the Linux runs on. You need it here or there. You want running OS so you need to configure/use it properly.

Awaiting resolution of the boot problem in your next post.

#87

As Im said I don’t have boot problem. I can normaly boot to old or to ne kernel…
Radxa has not probably put initrd image to system for some reason. I don’t have it on sdcard ubuntu and is also missing from nvme ubuntu system… Also Im not sure how to install that image and if it will fix freezing issue which if now with latest kernel little better but still freeze after few days(before upgrade it freeze every day…

When system run ok blue led blink twice every second. But when system freeze blue led is all time turned off…

#88

You have clearly said that the OS does not boot. You have changed your mind or the situation with the board has changed? If you are changing problems in the meantime there is no way to help you.

#89

I have in my first post in this thread boot issues after upgrade kernel. I did not change my mind and Im at least two times in two posts write that board boot. No boot issue we fix with user rua1 when I change in extlinux.conf from:

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

To:

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

So to be clear again. Board boot to system with latest kernel but only if I use for root /dev/nvme0n1p5 instead of UUID …

But with latest kernel I still have freezing issues which is not resolved.

#90

That is expected since there are no relevant changes between Oct. 21 - Jan 7th.