Jump to content

Issue with eMMC + NVMe


koftikes

Recommended Posts

Hello,

Devices: RockPi 4b v1.5 + remotable eMMC + NVMe KingSpec M.2 NMVe SSD NE 2280 512 GB

I am using instructions to erase SPI https://wiki.radxa.com/Rockpi4/dev/spi-install

$ sudo rkdeveloptool ld
DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=103 Maskrom

$ sudo rkdeveloptool db ./rk3399_loader_spinor_v1.20.126.bin
Downloading bootloader succeeded.

$ dd if=/dev/zero of=./zero.img bs=1M count=4
4+0 records in
4+0 records out
4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.0160027 s, 262 MB/s

$ sudo rkdeveloptool wl 0 ./zero.img
Write LBA from file (100%)

$ sudo rkdeveloptool td
Test Device OK.

$ sudo rkdeveloptool rd
Reset Device OK.

After that, insert eMMC and use instruction to write image to eMMChttps://wiki.radxa.com/Rockpi4/dev/usb-install

$ sudo rkdeveloptool ld
DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=103 Maskrom

$ sudo rkdeveloptool db ./rk3399_loader_v1.20.119.bin
Downloading bootloader succeeded.

$ sudo rkdeveloptool wl 0 ./Armbian_22.08.8_Rockpi-4b_bullseye_current_5.15.76.img
Write LBA from file (100%)

$ sudo rkdeveloptool rd
Reset Device OK.

After reboot device work fine.

But if I insert NVMe the system not booting, blue led just blinking and that all.

I tryed several images:

Armbian_22.11.0-trunk_Rockpi-4b_bullseye_current_5.15.76_minimal.img

Armbian_22.08.8_Rockpi-4b_bullseye_current_5.15.76.img

rockpi-4b-debian-bullseye-xfce4-arm64-20221101-0519-gpt.img

rockpi-4b-debian-buster-xfce4-arm64-20220401-0335-gpt.img

The main goal is system on eMMC and stored data on NVMe (like mini NAS)

Also if I use armbian-install have the same issue.


Any help with it ?

Link to comment
Share on other sites

On 11/23/2022 at 2:45 PM, Константин Литвинов said:

The main goal is system on eMMC and stored data on NVMe (like mini NAS)


It is difficult to say what is wrong, but if you are using Armbian you should follow Armbian documentation, not something in between. It can be very different. Vendors are usually using binary boot loaders and proprietary tools they got from chip vendor, while we use open source tools we and community developed.

After you erase or disable (connecting pin 23 and 25) SPI, you don't need to do anything else then booting from SD card and using standard armbian-install utility to flash to eMMC boot/eMMC root or eMMC boot/NVME root. We invested a lot of efforts to keep the same install procedure on very different methods ... If there are any hacks needed, they are exposed at download pages https://www.armbian.com/rockpi4/ 

 

If you have eMMC to SD card adaptor, that you flash directly and it should work. But like I said, without logs we are in the dark ...

Link to comment
Share on other sites

The method used to transfer an image byte by byte to a target device is not important. It does not change the function of the transferred code as long as no transmission errors occur. Due to the detailed description of the procedure and the confirmation

On 11/23/2022 at 2:45 PM, Константин Литвинов said:

After reboot device work fine.

 that the system is working, it is proven that nothing has been done wrong so far. The problem only arises when the NVME device comes into play. The use of different images also proves that there seems to be a fundamental issue that seems worth investigating further. But a basic prerequisite are meaningful logs, and without them it is hopeless from the beginning. The excuse of not having a suitable USB serial adapter available to provide logs is mood. Every reasonably assorted electronics shop offers these for little money. Choose whatever your host system with which you want to use the adapter supports, make sure that the operating voltage of the RX/TX lines matches that of the SBC and the adapter supports a baud rate of 1500000 and you are ready to go. Tinkering with SBCs sooner or later requires access to the serial console for one reason or another. If you don't want that and have a turnkey system, an SBC isn't the right choice.

Link to comment
Share on other sites

4 часа назад, usual user сказал:

Every reasonably assorted electronics shop offers these for little money.


I live in a small town in a not very normal country, so unfortunately I don't have the opportunity to go to any store and buy this cable. As well as ordering it inside the country via the Internet. So for now, I'll be waiting for him from China.
Sorry for that (

Link to comment
Share on other sites

18 часов назад, Igor сказал:

But like I said, without logs we are in the dark


Thanks for your reply. I understand the importance of console logs, but unfortunately I can't provide them yet... But

I continue research until cable come to me. I tried the next solutions:
Fully erase eMMC and NVMe

1. Use Armbian_22.08.8_Rockpi-4b_bullseye_current_5.15.76.img - write it to uSD; erase SPI, eMMC and NVMe
2. Remove NVMe and start boot from uSD
3. Install Armbian to eMMC, for file systen use btrfs (not sure if it matters)
4. Configure /boot/armbianEnv.txt to verbosity=7 
5. Reboot system and all work fine.
6. Power off the system from console - sudo poweroff.

Insert empty NVMe and try to start bourd: 
The board looks like start but start not complitle - blue lite just blinken, no HDMI output, keyboard like work (NumLock on/off)
So I remove power and remove NVMe and start system again.
After that I try to reserch logs 'journalctl -b' and find next issue:
```
Nov 25 10:44:14 rockpi-4b kernel: rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
Nov 25 10:44:14 rockpi-4b kernel: rockchip-pcie: probe of f8000000.pcie failed with error -110
```

Going to search in internet and find next MR: https://github.com/armbian/build/pull/4308
As I understand it's will applied only in 6.0.x so I try start with Armbian_22.11.0-trunk_Rockpi-4b_sid_edge_6.0.9.img
- boot from uSD with empty eMMC + empty NVMe

fdisk -l output: 

Disk /dev/mmcblk0: 59.48 GiB, 63864569856 bytes, 124735488 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x08f2b9a2

Device         Boot Start       End   Sectors  Size Id Type
/dev/mmcblk0p1      32768 123469824 123437057 58.9G 83 Linux


Disk /dev/mmcblk1: 57.62 GiB, 61865984000 bytes, 120832000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk1boot0: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mmcblk1boot1: 4 MiB, 4194304 bytes, 8192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: NE-512                                  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

 

So we can figure out the system is working and all devices are working too. A trable in detect of NVMe during boot. 

I was happy before I try to reboot. Then system rebooting I have the same issue - blue light just blinking, no HDMI output, keyboard like work (NumLock on/off)

Any new ideas?

Link to comment
Share on other sites

39 minutes ago, Константин Литвинов said:

Any new ideas?

 

We came this far, we tried with workaround, it doesn't work well, but from here on a slow and painful research needs to be done. We have done our part, more we can't afford. 

Link to comment
Share on other sites

4 часа назад, Igor сказал:

We came this far, we tried with workaround, it doesn't work well, but from here on a slow and painful research needs to be done. We have done our part, more we can't afford.


I didn't quite understand your answer. Will the console logs help or is this sufficient research and it 's just unclear what to do next ?

Link to comment
Share on other sites

20 minutes ago, Константин Литвинов said:

Will the console logs help


No, problem is identified, but we don't have resources / money to proceed from here. For us, this is 24/7, for you - when something breaks down. 

Link to comment
Share on other sites

25.11.2022 в 20:30, Igor сказал:

we don't have resources / money to proceed from here


So I got serial console cable and what I figured out:

From https://github.com/radxa-build/rock-pi-4b/releases/tag/20221201-0200
Image: Armbian_22.11.0-trunk_Rockpi-4b_bullseye_current_5.15.80_minimal.img
uname -a: Linux rockpi-4b 5.15.80-rockchip64 #trunk SMP PREEMPT Thu Dec 1 07:25:43 UTC 2022 aarch64 GNU/Linux


From https://imola.armbian.com/dl/rockpi-4b/archive/
Image: Armbian_22.11.1_Rockpi-4b_bullseye_current_5.15.80.img
uname -a: Linux rockpi-4b 5.15.80-rockchip64 #22.11.1 SMP PREEMPT Wed Nov 30 11:12:47 UTC 2022 aarch64 GNU/Linux


Works without NVMe, but when I insert NVMe, the system stuck on next:

[    2.450469] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges:
[    2.451172] rockchip-pcie f8000000.pcie:      MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000
[    2.452008] rockchip-pcie f8000000.pcie:       IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000
[    2.453746] rockchip-pcie f8000000.pcie: no bus scan delay, default to 0 ms
[    2.508191] rockchip-pcie f8000000.pcie: wait 0 ms (from device tree) before bus scan
[    2.509380] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00
[    2.509992] pci_bus 0000:00: root bus resource [bus 00-1f]
[    2.510502] pci_bus 0000:00: root bus resource [mem 0xfa000000-0xfbdfffff]
[    2.511135] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff] (bus address [0xfbe00000-0xfbefffff])
[    2.512088] pci 0000:00:00.0: [1d87:0100] type 01 class 0x060400
[    2.512819] pci 0000:00:00.0: supports D1
[    2.513195] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    2.520737] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    2.532997] Internal error: synchronous external abort: 96000210 [#1] PREEMPT SMP
[    2.533685] Modules linked in:
[    2.533980] CPU: 3 PID: 223 Comm: kworker/u12:4 Not tainted 5.15.80-rockchip64 #22.11.1
[    2.534711] Hardware name: Radxa ROCK Pi 4B (DT)
[    2.535136] Workqueue: events_unbound deferred_probe_work_func
[    2.535686] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[    2.536322] pc : rockchip_pcie_rd_conf+0xb0/0x230
[    2.536764] lr : rockchip_pcie_rd_conf+0xec/0x230
[    2.537203] sp : ffff80000a723830
[    2.537509] x29: ffff80000a723830 x28: 0000000000000000 x27: 0000000000000000
[    2.538172] x26: 0000000000000000 x25: 0000000000000000 x24: ffff80000a723974
[    2.538834] x23: ffff000005a8b000 x22: 0000000000000000 x21: 0000000000000004
[    2.539495] x20: ffff80000a7238b4 x19: ffff80000c100000 x18: 0000000000000000
[    2.540157] x17: 6572202c295d3030 x16: 2d3030207375625b x15: ffffffffffffffff
[    2.540818] x14: ffff80000954e228 x13: ffff000005a6ba1c x12: ffff000005a6b290
[    2.541480] x11: 0000000000000028 x10: 0000000000000001 x9 : 0000000001001d87
[    2.542142] x8 : 000000000000ea60 x7 : ffff80000a723800 x6 : 0000000000000001
[    2.542803] x5 : 0000000000000003 x4 : 0000000000000000 x3 : 0000000000c00008
[    2.543464] x2 : 000000000080000a x1 : ffff80000fc00008 x0 : ffff80000fc0000c
[    2.544127] Call trace:
[    2.544358]  rockchip_pcie_rd_conf+0xb0/0x230
[    2.544768]  pci_bus_read_config_dword+0x84/0xd8
[    2.545200]  pci_bus_generic_read_dev_vendor_id+0x34/0x1b0
[    2.545711]  pci_bus_read_dev_vendor_id+0x4c/0x70
[    2.546151]  pci_scan_single_device+0x84/0xd8
[    2.546560]  pci_scan_slot+0x38/0x120
[    2.546907]  pci_scan_child_bus_extend+0x58/0x330
[    2.547346]  pci_scan_bridge_extend+0x340/0x5a0
[    2.547771]  pci_scan_child_bus_extend+0x1fc/0x330
[    2.548219]  pci_scan_root_bus_bridge+0xd4/0xf0
[    2.548643]  pci_host_probe+0x18/0xb0
[    2.548991]  rockchip_pcie_probe+0x4a8/0x4c0
[    2.549392]  platform_probe+0x68/0xd8
[    2.549740]  really_probe+0xbc/0x428
[    2.550076]  __driver_probe_device+0x114/0x188
[    2.550490]  driver_probe_device+0xb0/0x110
[    2.550879]  __device_attach_driver+0xbc/0x158
[    2.551293]  bus_for_each_drv+0x7c/0xd0
[    2.551658]  __device_attach+0xec/0x1a8
[    2.552017]  device_initial_probe+0x14/0x20
[    2.552407]  bus_probe_device+0x9c/0xa8
[    2.552766]  deferred_probe_work_func+0x9c/0xf0
[    2.553186]  process_one_work+0x20c/0x4c8
[    2.553567]  worker_thread+0x208/0x478
[    2.553921]  kthread+0x138/0x150
[    2.554229]  ret_from_fork+0x10/0x20
[    2.554575] Code: f94013f5 a8c37bfd d50323bf d65f03c0 (b9400273) 
[    2.555132] ---[ end trace b08bc39ec7a1232e ]---
[    2.555557] note: kworker/u12:4[223] exited with preempt_count 1


I know you said no money for this but still, maybe it's will helpful

And also maybe someone can help me with it... 

 

Armbian_22.11.1_Rockpi-4b_bullseye_5.15.80.log Armbian_22.11.0-trunk_Rockpi-4b_bullseye_5.15.80.log

Link to comment
Share on other sites

The supplied logs prove that the kernel causes a "synchronous external abort" when the pcie sybsystem is initializing. The fact that both logs look similar is because both images use the same kernel and user space doesn't even come into play when the issue occurs. Since a rather old kernel is used, I would first switch to a more recent one to further identify the issue. With my rk3399 device I have been using NVME flawless for a long time. I therefore assume that there is no fundamental code problem. However, I am currently running 6.1.0, which contains improvements that were certainly not back-ported to 5.15.80. The rk3399 mainline kernel support is very advanced, so it doesn't make much sense to waste time analyzing a behaved kernel. Maybe the issue no longer exists with a kernel upgrade and that's all that's necessary.

Link to comment
Share on other sites

3 hours ago, koftikes said:

Please provide link to distributive what you use.

I run fedora as userspace but although fedora offers all mainline components available for the RockPi 4B, there is no out-of-the-box image. You need to know what is necessary to configure the system and how to set it up. Also, you have to add components that are not available in mainline yourself, such as firmware where the manufacturers think it is a good idea to formulate the distribution licenses in such a way that free software may not ship them out-of-the-box.

 

3 hours ago, koftikes said:

And additional question: Are Bluetooth work fine with this distributive?

The user space software components work fine, provided the kernel has the necessary mainline driver support. Out-of-mainline components like Wifi calibration parameter files must be added by yourself, i.e. YMMV.
I'm sure my configured microSD card would work out-of-the-box for your device also, but the only thing I can offer is my kernel build, which is then integrated into the Armbian image of your choice to find out if it works for you.

Link to comment
Share on other sites

6 hours ago, koftikes said:

I not so skill in linux for this...

I don't expect you to switch to fedora, but every Linux user should be able to execute basic cli commands to copy a kernel into position. In this way, we can at least determine whether it is just a configuration issue or whether a bugfix is really needed. At the very least, you meet the necessary requirements, an affected device, and serial console access to investigate the issue further.
I added my kernel build to the Armbian image for you and uploaded it here.  Because I do not have an identical to your device to test, I can not guarantee that the result works at all. So download it and post the serial console log while it boots.

Link to comment
Share on other sites

21 час назад, usual user сказал:

So download it and post the serial console log while it boots.


I download and try your build, got the same issue 

 

Starting kernel ...

[    2.047065] Internal error: synchronous external abort: 0000000096000210 [#1] SMP
[    2.047772] Modules linked in:
[    2.048070] CPU: 1 PID: 64 Comm: kworker/u12:2 Not tainted 6.1.0-65.fc37.aarch64 #1
[    2.048769] Hardware name: Radxa ROCK Pi 4B (DT)
[    2.049197] Workqueue: events_unbound deferred_probe_work_func
[    2.049754] pstate: 604000c5 (nZCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[    2.050392] pc : rockchip_pcie_rd_conf+0x128/0x164
[    2.050846] lr : rockchip_pcie_rd_conf+0x120/0x164
[    2.051294] sp : ffff80000c5db890
[    2.051601] x29: ffff80000c5db890 x28: ffff00000156b800 x27: 0000000000000000
[    2.052268] x26: ffff000001568800 x25: 0000000000000001 x24: 0000000000000000
[    2.052931] x23: ffff80000b386588 x22: 0000000000000000 x21: ffff80000c5db90c
[    2.053596] x20: 0000000000000004 x19: ffff80000e100000 x18: ffffffffffffffff
[    2.054259] x17: 000000005e80c22f x16: 000000002c060080 x15: ffff80000c5db788
[    2.054922] x14: ffff000001b55a1c x13: ffff000001b55290 x12: 00000000914f756d
[    2.055586] x11: 000000002f359453 x10: 0000000000000000 x9 : ffff8000088aacb0
[    2.056249] x8 : ffff80000c5db810 x7 : ffff0000074abb80 x6 : ffff000001568800
[    2.056912] x5 : ffff00000156b800 x4 : 0000000000c00008 x3 : ffff800011000000
[    2.057575] x2 : 000000000080000a x1 : ffff800011c00008 x0 : ffff800011c0000c
[    2.058239] Call trace:
[    2.058471]  rockchip_pcie_rd_conf+0x128/0x164
[    2.058892]  pci_bus_read_config_dword+0x70/0xcc
[    2.059325]  pci_bus_generic_read_dev_vendor_id+0x38/0x17c
[    2.059839]  pci_scan_single_device+0x84/0x100
[    2.060258]  pci_scan_slot+0x5c/0x200
[    2.060609]  pci_scan_child_bus_extend+0x50/0x2e0
[    2.061051]  pci_scan_bridge_extend+0x300/0x574
[    2.061478]  pci_scan_child_bus_extend+0x1c4/0x2e0
[    2.061928]  pci_scan_root_bus_bridge+0x6c/0xe0
[    2.062355]  pci_host_probe+0x20/0xd0
[    2.062705]  rockchip_pcie_probe+0x374/0x560
[    2.063110]  platform_probe+0x70/0xcc
[    2.063464]  really_probe+0xc8/0x3e0
[    2.063807]  __driver_probe_device+0x84/0x190
[    2.064221]  driver_probe_device+0x44/0x120
[    2.064619]  __device_attach_driver+0xc4/0x160
[    2.065040]  bus_for_each_drv+0x74/0xb4
[    2.065406]  __device_attach+0xa8/0x1c0
[    2.065773]  device_initial_probe+0x1c/0x30
[    2.066170]  bus_probe_device+0xa4/0xb0
[    2.066536]  deferred_probe_work_func+0xc0/0x114
[    2.066971]  process_one_work+0x1ec/0x470
[    2.067353]  worker_thread+0x200/0x410
[    2.067709]  kthread+0xec/0x100
[    2.068018]  ret_from_fork+0x10/0x20
[    2.068368] Code: 52800141 97fffa11 7100129f 54fffb41 (b9400273) 
[    2.068929] ---[ end trace 0000000000000000 ]---
[    2.069356] note: kworker/u12:2[64] exited with preempt_count 1
[    2.085324] mmc_host mmc2: Bus speed (slot 0) = 148500000Hz (slot req 150000000Hz, actual 148500000HZ div = 0)
[    2.293765] dwmmc_rockchip fe310000.mmc: Successfully tuned phase to 228
[    2.298632] mmc2: new ultra high speed SDR104 SDIO card at address 0001
[   90.443481] random: crng init done

 

Link to comment
Share on other sites

Some additional testing:
I try different images and some of them work for example -
1. Armbian_21.08.1_Rockpi-4b_bullseye_5.10.60 and Armbian_21.08.2_Rockpi-4b_bullseye_5.10.63 - works if kernel not updated 
see Armbian_21.08.1_Rockpi-4b_bullseye_5.10.60.log and Armbian_21.08.2_Rockpi-4b_bullseye_5.10.63.log
2. Randomly found resource https://sd-card-images.johang.se/boards/rock_pi_4.html with debian-bookworm works, but it's very minimal image and all even simple config need to be done by manual. It's will take so many time ((((
see debian-bookworm-minimal.log

If upgrade kernel to next release 

apt install armbian-firmware=21.08.6 linux-dtb-current-rockchip64=21.08.2 linux-image-current-rockchip64=21.08.2 linux-u-boot-rockpi-4b-current=21.08.1

Armbian_22.02.1_Rockpi-4b_bullseye_5.15.25 The system stop working correctly, see  Armbian_22.02.1_Rockpi-4b_bullseye_5.15.25.log

And it's not working on all next releases including 6.0.9 and 6.1.0

Armbian_21.08.1_Rockpi-4b_bullseye_5.10.60.log Armbian_21.08.2_Rockpi-4b_bullseye_5.10.63.log debian-bookworm-minimal.log Armbian_22.02.1_Rockpi-4b_bullseye_5.15.25.log

Edited by koftikes
Link to comment
Share on other sites

2 hours ago, koftikes said:

I download and try your build, got the same issue 

Here my final analysis. A kernel built with a completely different toolchain than Armbian's is now used. The kernel configuration varies in many respects from those of Armbian. My build is based on pure mainline sources where only these patches were applied, but these have no relevance for PCIe support. The test with my build has ruled out a shortcomming of Armbian due to their toolchain, configuration and applied patches. The difference between my rk3399 device and yours is the specific hardware and how it is wired via DTB. Since the PCIe support works for me, it can be assumed that the issue is triggered by your special hardware constellation. This suggests that a shortcomming exists in the kernel code. To analyze the problem further, someone familiar with the kernel PCIe code is now needed, but I doubt if anyone is available for free. There would have been a small chance for the DTB configuration as the cause, but since you preferred not to provide me with the full serial console log, I can not confirm this.

Link to comment
Share on other sites

1 час назад, usual user сказал:

The test with my build has ruled out a shortcomming of Armbian due to their toolchain, configuration and applied patches.

So I do erase my SPI, EMMc and NVMe devices, create new uSD and try again. 
And your build work from uSD !!!! See: console logs 
It's amazing and thank you for your investigations and help. 

as I understand this issue because some patches not include 
 

[    3.841967] systemd[233]: /usr/lib/systemd/system-generators/netplan failed with exit status 1.
[  OK  ] Found device /dev/ttyS2.
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password R…s to Plymouth Directory Watch.
[  OK  ] Reached target Local Encrypted Volumes.
[  OK  ] Reached target Paths.
[  OK  ] Finished Raise network interfaces.
[   14.748907] rockchip-pinctrl pinctrl: pin gpio3-29 already requested by leds; cannot claim for ff880000.i2s
[   14.749798] rockchip-pinctrl pinctrl: pin-125 (ff880000.i2s) status -22
[   14.750402] rockchip-pinctrl pinctrl: could not request pin 125 (gpio3-29) from group i2s0-8ch-bus-bclk-off  on device rockchip-pinctrl
[   14.751486] rockchip-i2s ff880000.i2s: Error applying setting, reverse things back
[   14.752163] rockchip-i2s ff880000.i2s: bclk disable failed -22
[   14.844258] rk_gmac-dwmac fe300000.ethernet: cannot get clock clk_mac_speed
[  OK  ] Listening on Load/Save RF …itch Status /dev/rfkill Watch.


Again thank you for help, what I can/should do next ? How I as noob can  propose fixing for Armbiam 

Armbian_22.11.0_bullseye_5.15.80_test.log

Link to comment
Share on other sites

1 hour ago, koftikes said:

as I understand this issue because some patches not include 

To analyze this further, I need a detailed serial console log. Please select the "linux verbose" boot option by entering a "3" on the serial console while the boot options are displayed and the countdown runs.
I also see that a different firmware is used and I don't know where it is loaded from as it is not the one included in the Armbian image. To identify the  firmware as the culprit for the PCIe problem, it would be interesting to also  see a log with the boot option "5.15.80-rockchip64" (4).

Link to comment
Share on other sites

19 часов назад, usual user сказал:

I also see that a different firmware is used and I don't know where it is loaded from as it is not the one included in the Armbian image.

Sorry my falls I do a bad erase for EMMC and I think a boot loader will taken from this, so I fix this and add a new console log. See: Armbian_22.11.0_bullseye_5.15.80_linux.log

Behavior is sometimes strange ((((
In most cases, booting and rebooting goes fine. But a couple of times I caught errors during verbose boot and linux reboot. See:  Armbian_22.11.0_bullseye_5.15.80_linux-reboot.log Armbian_22.11.0_bullseye_5.15.80_linux_verbose-error.log Armbian_22.11.0_bullseye_5.15.80_linux_verbose-error-2.log

Also as you ask I provide normal verbose loading log: Armbian_22.11.0_bullseye_5.15.80_linux_verbose.log

BUT one thing is stable, every time when I try start 5.15.80-rockchip64 it's fail... See: Armbian_22.11.0_bullseye_5.15.80_5.15.80-rockchip64.log
 

 

So this is my trying...  and again thank you for help!

Link to comment
Share on other sites

Hi! Got the same issue with same kernel, but I'm getting boot issues on soft reboot ONLY (power off/power on always boots for me). Booting from eMMC, got a NVMe drive.

Here is my log after soft rebooting:

 

$ sudo reboot

[  237.086162] watchdog: watchdog0: watchdog did not stop!

[  238.600532] reboot: Restarting system

DDR Version 1.20 20190314

In

soft reset

SRX

channel 0

CS = 0

MR0=0x19

MR4=0x3

MR5=0x6

MR8=0x10

MR12=0x72

MR14=0x72

MR18=0x0

MR19=0x0

MR24=0x8

MR25=0xFF

channel 1

CS = 0

MR0=0x19

MR4=0x3

MR5=0x6

MR8=0x10

MR12=0x72

MR14=0x72

MR18=0x0

MR19=0x0

MR24=0x8

MR25=0xFF

channel 0 training pass!

channel 1 training pass!

change freq to 400MHz 0,1

channel 0

CS = 0

MR0=0x19

MR4=0x3

MR5=0x6

MR8=0x10

MR12=0x72

MR14=0x72

MR18=0x0

MR19=0x0

MR24=0x8

MR25=0xFF

channel 1

CS = 0

MR0=0x19

MR4=0x3

MR5=0x6

MR8=0x10

MR12=0x72

MR14=0x72

MR18=0x0

MR19=0x0

MR24=0x8

MR25=0xFF

channel 0 training pass!

channel 1 training pass!

change freq to 800MHz 1,0

Channel 0: LPDDR4,800MHz

Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB

Channel 1: LPDDR4,800MHz

Bus Width=32 Col=10 Bank=8 Row=16 CS=1 Die Bus-Width=16 Size=2048MB

256B stride

ch 0 ddrconfig = 0x101, ddrsize = 0x40

ch 1 ddrconfig = 0x101, ddrsize = 0x40

pmugrf_os_reg[2] = 0x32C1F2C1, stride = 0xD

OUT

Boot1 Release Time: May 29 2020 17:36:36, version: 1.26

CPUId = 0x0

ChipType = 0x10, 436

SdmmcInit=2 0

BootCapSize=100000

UserCapSize=59000MB

FwPartOffset=2000 , 100000

mmc0:cmd8,20

mmc0:cmd5,20

mmc0:cmd55,20

mmc0:cmd1,20

mmc0:cmd8,20

mmc0:cmd5,20

mmc0:cmd55,20

mmc0:cmd1,20

mmc0:cmd8,20

mmc0:cmd5,20

mmc0:cmd55,20

mmc0:cmd1,20

SdmmcInit=0 1

StorageInit ok = 68932

SecureMode = 0

SecureInit read PBA: 0x4

SecureInit read PBA: 0x404

SecureInit read PBA: 0x804

SecureInit read PBA: 0xc04

SecureInit read PBA: 0x1004

SecureInit read PBA: 0x1404

SecureInit read PBA: 0x1804

SecureInit read PBA: 0x1c04

SecureInit ret = 0, SecureMode = 0

atags_set_bootdev: ret:(0)

GPT part:  0, name:          loader1, start:0x40, size:0x1f40

GPT part:  1, name:          loader2, start:0x4000, size:0x2000

GPT part:  2, name:            trust, start:0x6000, size:0x2000

GPT part:  3, name:             boot, start:0x8000, size:0x100000

GPT part:  4, name:           rootfs, start:0x108000, size:0x7233860

no find partition:uboot.

Trust Addr:0x4000, 0x58334c42

No find bl30.bin

No find bl32.bin

Load uboot, ReadLba = 2000

Load OK, addr=0x200000, size=0xdc6f0

RunBL31 0x40000 @ 101881 us

NOTICE:  BL31: v1.3(release):845ee93

NOTICE:  BL31: Built : 15:51:11, Jul 22 2020

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:    If lpddr4 need support multi frequency,

INFO:    please update loader!

INFO:    Current ctl index[0] freq=400MHz

INFO:    Current ctl index[1] freq=800MHz

INFO:    plat_rockchip_pmu_init(1196): 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 2022.07-armbian (Nov 30 2022 - 10:46:43 +0000)

 

SoC: Rockchip rk3399

Reset cause: RST

Model: Radxa ROCK Pi 4B

DRAM:  3.9 GiB

PMIC:  RK808

Core:  285 devices, 31 uclasses, devicetree: separate

MMC:   mmc@fe310000: 2, mmc@fe320000: 1, mmc@fe330000: 0

Loading Environment from SPIFlash... SF: Detected XT25F32B with page size 256 Bytes, erase size 4 KiB, total 4 MiB

*** Warning - bad CRC, using default environment

 

In:    serial

Out:   serial

Err:   serial

Model: Radxa ROCK Pi 4B

Net:   eth0: ethernet@fe300000

Hit any key to stop autoboot:  0

starting USB...

Bus usb@fe380000: ehci_generic usb@fe380000: Failed to get clocks (ret=-19)

Port not available.

Bus usb@fe3c0000: ehci_generic usb@fe3c0000: Failed to get clocks (ret=-19)

Port not available.

Bus usb@fe800000: Register 2000140 NbrPorts 2

Starting the controller

USB XHCI 1.10

Bus usb@fe900000: Register 2000140 NbrPorts 2

Starting the controller

USB XHCI 1.10

scanning bus usb@fe800000 for devices... 1 USB Device(s) found

scanning bus usb@fe900000 for devices... 1 USB Device(s) found

       scanning usb for storage devices... 0 Storage Device(s) found

 

Device 0: unknown device

Card did not respond to voltage select! : -110

switch to partitions #0, OK

mmc0(part 0) is current device

Scanning mmc 0:1...

Found U-Boot script /boot/boot.scr

3252 bytes read in 19 ms (167 KiB/s)

## Executing script at 00500000

Boot script loaded from mmc 0

204 bytes read in 15 ms (12.7 KiB/s)

22787516 bytes read in 2179 ms (10 MiB/s)

30607872 bytes read in 2920 ms (10 MiB/s)

76139 bytes read in 46 ms (1.6 MiB/s)

2698 bytes read in 34 ms (77.1 KiB/s)

Applying kernel provided DT fixup script (rockchip-fixup.scr)

## Executing script at 09000000

Unknown command 'kaslrseed' - try 'help'

Moving Image from 0x2080000 to 0x2200000, end=3fd0000

## Loading init Ramdisk from Legacy Image at 06000000 ...

   Image Name:   uInitrd

   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)

   Data Size:    22787452 Bytes = 21.7 MiB

   Load Address: 00000000

   Entry Point:  00000000

   Verifying Checksum ... OK

## Flattened Device Tree blob at 01f00000

   Booting using the fdt blob at 0x1f00000

   Loading Ramdisk to f0950000, end f1f0b57c ... OK

   Loading Device Tree to 00000000f08d5000, end 00000000f094ffff ... OK

 

Starting kernel ...

 

efi_free_pool: illegal free 0x00000000f0f0d040

efi_free_pool: illegal 00000f0f0a040

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]

[    0.000000] Linux version 5.15.80-rockchip64 (root@746a5325a2a9) (aarch64-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0, GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 2.32.0.20190321) #22.11.1 SMP PREEMPT Wed Nov 30 11:12:47 UTC 2022

[    0.000000] Machine model: Radxa ROCK Pi 4B

[    0.000000] efi: UEFI not found.

[    0.000000] NUMA: No NUMA configuration found

[    0.000000] NUMA: Faking a node at [mem 0x0000000000200000-0x00000000f7ffffff]

[    0.000000] NUMA: NODE_DATA [mem 0xf77d6100-0xf77d7fff]

[    0.000000] Zone ranges:

[    0.000000]   DMA      [mem 0x0000000000200000-0x00000000f7ffffff]

[    0.000000]   DMA32    empty

[    0.000000]   Normal   empty

[    0.000000] Movable zone start for each node

[    0.000000] Early memory node ranges

[    0.000000]   node   0: [mem 0x0000000000200000-0x00000000f7ffffff]

[    0.000000] Initmem setup node 0 [mem 0x0000000000200000-0x00000000f7ffffff]

[    0.000000] On node 0, zone DMA: 512 pages in unavailable ranges

[    0.000000] cma: Reserved 128 MiB at 0x00000000e8800000

[    0.000000] psci: probing for conduit method from DT.

[    0.000000] psci: PSCIv1.0 detected in firmware.

[    0.000000] psci: Using standard PSCI v0.2 function IDs

[    0.000000] psci: MIGRATE_INFO_TYPE not supported.

[    0.000000] psci: SMC Calling Convention v1.0

[    0.000000] percpu: Embedded 29 pages/cpu s80984 r8192 d29608 u118784

[    0.000000] Detected VIPT I-cache on CPU0

[    0.000000] CPU features: detected: GIC system register CPU interface

[    0.000000] CPU features: detected: ARM erratum 845719

[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 999432

[    0.000000] Policy zone: DMA

[    0.000000] Kernel command line: root=UUID=86029bc2-ee89-4d51-a8f2-0ffcad13472f rootwait rootfstype=ext4 splash plymouth.ignore-serial-consoles console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=7 ubootpart=7ff3d104-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u   cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1

[    0.000000] Unknown kernel command line parameters "splash ubootpart=7ff3d104-01 cgroup_enable=memory cgroup_memory=1", will be passed to user space.

[    0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)

[    0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)

[    0.000000] mem auto-init: stack:off, heap alloc:on, heap free:off

[    0.000000] Memory: 3798564K/4061184K available (16000K kernel code, 2690K rwdata, 6696K rodata, 4352K init, 593K bss, 131548K reserved, 131072K cma-reserved)

[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1

[    0.000000] trace event string verifier disabled

[    0.000000] rcu: Preemptible hierarchical RCU implementation.

[    0.000000] rcu: RCU event tracing is enabled.

[    0.000000] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=6.

[    0.000000] Trampoline variant of Tasks RCU enabled.

[    0.000000] Rude variant of Tasks RCU enabled.

[    0.000000] Tracing variant of Tasks RCU enabled.

[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.

[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=6

[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0

[    0.000000] GICv3: GIC: Using split EOI/Deactivate mode

[    0.000000] GICv3: 256 SPIs implemented

[    0.000000] GICv3: 0 Extended SPIs implemented

[    0.000000] GICv3: Distributor has no Range Selector support

[    0.000000] Root IRQ handler: gic_handle_irq

[    0.000000] GICv3: 16 PPIs implemented

[    0.000000] GICv3: CPU0: found redistributor 0 region 0:0x00000000fef00000

[    0.000000] ITS [mem 0xfee20000-0xfee3ffff]

[    0.000000] ITS@0x00000000fee20000: allocated 65536 Devices @500000 (flat, esz 8, psz 64K, shr 0)

[    0.000000] ITS: using cache flushing for cmd queue

[    0.000000] GICv3: using LPI property table @0x00000000004d0000

[    0.000000] GIC: using cache flushing for LPI property table

[    0.000000] GICv3: CPU0: using allocated LPI pending table @0x00000000004e0000

[    0.000000] GICv3: GIC: PPI partition interrupt-partition-0[0] { /cpus/cpu@0[0] /cpus/cpu@1[1] /cpus/cpu@2[2] /cpus/cpu@3[3] }

[    0.000000] GICv3: GIC: PPI partition interrupt-partition-1[1] { /cpus/cpu@100[4] /cpus/cpu@101[5] }

[    0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).

[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns

[    0.000000] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns

[    0.001982] Console: colour dummy device 80x25

[    0.003067] printk: console [tty1] enabled

[    0.003201] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)

[    0.003250] pid_max: default: 32768 minimum: 301

[    0.003401] LSM: Security Framework initializing

[    0.003458] Yama: becoming mindful.

[    0.003661] AppArmor: AppArmor initialized

[    0.003828] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)

[    0.003887] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)

[    0.008098] rcu: Hierarchical SRCU implementation.

[    0.009718] Platform MSI: interrupt-controller@fee20000 domain created

[    0.010263] PCI/MSI: /interrupt-controller@fee00000/interrupt-controller@fee20000 domain created

[    0.012494] EFI services will not be available.

[    0.013319] smp: Bringing up secondary CPUs ...

[    0.014424] Detected VIPT I-cache on CPU1

[    0.014474] GICv3: CPU1: found redistributor 1 region 0:0x00000000fef20000

[    0.014497] GICv3: CPU1: using allocated LPI pending table @0x00000000004f0000

[    0.014567] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]

[    0.015791] Detected VIPT I-cache on CPU2

[    0.015831] GICv3: CPU2: found redistributor 2 region 0:0x00000000fef40000

[    0.015850] GICv3: CPU2: using allocated LPI pending table @0x0000000000580000

[    0.015899] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]

[    0.017144] Detected VIPT I-cache on CPU3

[    0.017183] GICv3: CPU3: found redistributor 3 region 0:0x00000000fef60000

[    0.017203] GICv3: CPU3: using allocated LPI pending table @0x0000000000590000

[    0.017248] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]

[    0.018396] CPU features: detected: Spectre-v2

[    0.018409] CPU features: detected: Spectre-v3a

[    0.018415] CPU features: detected: Spectre-v4

[    0.018421] CPU features: detected: Spectre-BHB

[    0.018429] CPU features: detected: ARM erratum 1742098

[    0.018436] CPU features: detected: ARM errata 1165522, 1319367, or 1530923

[    0.018442] Detected PIPT I-cache on CPU4

[    0.018479] GICv3: CPU4: found redistributor 100 region 0:0x00000000fef80000

[    0.018497] GICv3: CPU4: using allocated LPI pending table @0x00000000005a0000

[    0.018543] CPU4: Booted secondary processor 0x0000000100 [0x410fd082]

[    0.019692] Detected PIPT I-cache on CPU5

[    0.019725] GICv3: CPU5: found redistributor 101 region 0:0x00000000fefa0000

[    0.019743] GICv3: CPU5: using allocated LPI pending table @0x00000000005b0000

[    0.019781] CPU5: Booted secondary processor 0x0000000101 [0x410fd082]

[    0.019944] smp: Brought up 1 node, 6 CPUs

[    0.020434] SMP: Total of 6 processors activated.

[    0.020458] CPU features: detected: 32-bit EL0 Support

[    0.020479] CPU features: detected: 32-bit EL1 Support

[    0.020504] CPU features: detected: CRC32 instructions

[    0.047130] CPU: All CPU(s) started at EL2

[    0.047259] alternatives: patching kernel code

[    0.050432] devtmpfs: initialized

[    0.064798] Registered cp15_barrier emulation handler

[    0.064842] Registered setend emulation handler

[    0.064864] KASLR disabled due to lack of seed

[    0.065085] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns

[    0.065179] futex hash table entries: 2048 (order: 5, 131072 bytes, linear)

[    0.068216] pinctrl core: initialized pinctrl subsystem

[    0.068912] DMI not present or invalid.

[    0.069776] NET: Registered PF_NETLINK/PF_ROUTE protocol family

[    0.074430] DMA: preallocated 2048 KiB GFP_KERNEL pool for atomic allocations

[    0.076158] DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations

[    0.078970] DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations

[    0.079081] audit: initializing netlink subsys (disabled)

[    0.079353] audit: type=2000 audit(0.076:1): state=initialized audit_enabled=0 res=1

[    0.080627] thermal_sys: Registered thermal governor 'fair_share'

[    0.080636] thermal_sys: Registered thermal governor 'bang_bang'

[    0.080657] thermal_sys: Registered thermal governor 'step_wise'

[    0.080672] thermal_sys: Registered thermal governor 'user_space'

[    0.081196] cpuidle: using governor menu

[    0.081530] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.

[    0.081773] ASID allocator initialised with 65536 entries

[    0.082986] Serial: AMBA PL011 UART driver

[    0.110672] platform ff770000.syscon:phy@f780: Fixing up cyclic dependency with fe330000.mmc

[    0.118275] platform ff940000.hdmi: Fixing up cyclic dependency with ff8f0000.vop

[    0.118384] platform ff940000.hdmi: Fixing up cyclic dependency with ff900000.vop

[    0.129121] rockchip-gpio ff720000.gpio0: probed /pinctrl/gpio0@ff720000

[    0.129970] rockchip-gpio ff730000.gpio1: probed /pinctrl/gpio1@ff730000

[    0.130769] rockchip-gpio ff780000.gpio2: probed /pinctrl/gpio2@ff780000

[    0.131617] rockchip-gpio ff788000.gpio3: probed /pinctrl/gpio3@ff788000

[    0.132422] rockchip-gpio ff790000.gpio4: probed /pinctrl/gpio4@ff790000

[    0.149838] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages

[    0.149869] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages

[    0.149888] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages

[    0.149906] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages

[    0.155271] cryptd: max_cpu_qlen set to 1000

[    0.232889] raid6: neonx8   gen()  1667 MB/s

[    0.301051] raid6: neonx8   xor()  1204 MB/s

[    0.369221] raid6: neonx4   gen()  1719 MB/s

[    0.437378] raid6: neonx4   xor()  1240 MB/s

[    0.505546] raid6: neonx2   gen()  1532 MB/s

[    0.573702] raid6: neonx2   xor()  1148 MB/s

[    0.641870] raid6: neonx1   gen()  1200 MB/s

[    0.710035] raid6: neonx1   xor()   926 MB/s

[    0.778187] raid6: int64x8  gen()  1001 MB/s

[    0.846393] raid6: int64x8  xor()   577 MB/s

[    0.914519] raid6: int64x4  gen()  1002 MB/s

[    0.982677] raid6: int64x4  xor()   591 MB/s

[    1.050836] raid6: int64x2  gen()   943 MB/s

[    1.119005] raid6: int64x2  xor()   524 MB/s

[    1.187156] raid6: int64x1  gen()   723 MB/s

[    1.255316] raid6: int64x1  xor()   390 MB/s

[    1.255331] raid6: using algorithm neonx4 gen() 1719 MB/s

[    1.255347] raid6: .... xor() 1240 MB/s, rmw enabled

[    1.255361] raid6: using neon recovery algorithm

[    1.256976] vcc5v0_sys: supplied by vcc12v_dcin

[    1.257490] vcc3v3_pcie: supplied by vcc5v0_sys

[    1.257900] vcc3v3_sys: supplied by vcc5v0_sys

[    1.258353] vcc5v0_host: supplied by vcc5v0_sys

[    1.258797] vcc5v0_typec: supplied by vcc5v0_sys

[    1.259670] iommu: Default domain type: Translated

[    1.259690] iommu: DMA domain TLB invalidation policy: strict mode

[    1.262881] vgaarb: loaded

[    1.263378] SCSI subsystem initialized

[    1.264183] usbcore: registered new interface driver usbfs

[    1.264244] usbcore: registered new interface driver hub

[    1.264302] usbcore: registered new device driver usb

[    1.265039] pps_core: LinuxPPS API ver. 1 registered

[    1.265058] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>

[    1.265089] PTP clock support registered

[    1.265399] EDAC MC: Ver: 3.0.0

[    1.266721] NetLabel: Initializing

[    1.266741] NetLabel:  domain hash size = 128

[    1.266755] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO

[    1.266837] NetLabel:  unlabeled traffic allowed by default

[    1.267430] clocksource: Switched to clocksource arch_sys_counter

[    1.319340] VFS: Disk quotas dquot_6.6.0

[    1.319477] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)

[    1.320349] AppArmor: AppArmor Filesystem Enabled

[    1.331291] NET: Registered PF_INET protocol family

[    1.331681] IP idents hash table entries: 65536 (order: 7, 524288 bytes, linear)

[    1.334882] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear)

[    1.335091] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)

[    1.335221] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear)

[    1.335794] TCP bind hash table entries: 32768 (order: 7, 524288 bytes, linear)

[    1.336479] TCP: Hash tables configured (established 32768 bind 32768)

[    1.336687] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear)

[    1.336869] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear)

[    1.337226] NET: Registered PF_UNIX/PF_LOCAL protocol family

[    1.337281] NET: Registered PF_XDP protocol family

[    1.337305] PCI: CLS 0 bytes, default 64

[    1.338058] Trying to unpack rootfs image as initramfs...

[    1.338709] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available

[    1.339241] hw perfevents: enabled with armv8_cortex_a72 PMU driver, 7 counters available

[    1.339988] kvm [1]: IPA Size Limit: 40 bits

[    1.341311] kvm [1]: vgic-v2@fff20000

[    1.341356] kvm [1]: GIC system register CPU interface enabled

[    1.341666] kvm [1]: vgic interrupt IRQ18

[    1.342005] kvm [1]: Hyp mode initialized successfully

[    1.354460] Initialise system trusted keyrings

[    1.354549] Key type blacklist registered

[    1.354866] workingset: timestamp_bits=44 max_order=20 bucket_order=0

[    1.361685] zbud: loaded

[    1.363534] squashfs: version 4.0 (2009/01/31) Phillip Lougher

[    1.364500] fuse: init (API version 7.34)

[    1.367276] integrity: Platform Keyring initialized

[    1.432734] xor: measuring software checksum speed

[    1.440941]    8regs           :  1220 MB/sec

[    1.444351]    32regs          :  2932 MB/sec

[    1.448666]    arm64_neon      :  2298 MB/sec

[    1.448684] xor: using function: 32regs (2932 MB/sec)

[    1.448706] Key type asymmetric registered

[    1.448720] Asymmetric key parser 'x509' registered

[    1.448858] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)

[    1.449119] io scheduler mq-deadline registered

[    1.449139] io scheduler kyber registered

[    1.449365] io scheduler bfq registered

[    1.475684] dma-pl330 ff6d0000.dma-controller: Loaded driver for PL330 DMAC-241330

[    1.475723] dma-pl330 ff6d0000.dma-controller: DBUFF-32x8bytes Num_Chans-6 Num_Peri-12 Num_Events-12

[    1.477212] dma-pl330 ff6e0000.dma-controller: Loaded driver for PL330 DMAC-241330

[    1.477241] dma-pl330 ff6e0000.dma-controller: DBUFF-128x8bytes Num_Chans-8 Num_Peri-20 Num_Events-16

[    1.482013] vdd_log: supplied by regulator-dummy

[    1.483622] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled

[    1.487218] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 42, base_baud = 1500000) is a 16550A

[    1.487468] serial serial0: tty port ttyS0 registered

[    1.488499] ff1a0000.serial: ttyS2 at MMIO 0xff1a0000 (irq = 43, base_baud = 1500000) is a 16550A

[    1.609480] printk: console [ttyS2] enabled

[    1.611271] Serial: AMBA driver

[    1.613575] rockchip-vop ff8f0000.vop: Adding to iommu group 2

[    1.615071] rockchip-vop ff900000.vop: Adding to iommu group 3

[    1.623944] rockchip-drm display-subsystem: bound ff8f0000.vop (ops vop_component_ops)

[    1.624777] [drm] unsupported AFBC format[3231564e]

[    1.627132] rockchip-drm display-subsystem: bound ff900000.vop (ops vop_component_ops)

[    1.628815] cacheinfo: Unable to detect cache hierarchy for CPU 0

[    1.639495] loop: module loaded

[    1.646014] tun: Universal TUN/TAP device driver, 1.6

[    1.647744] thunder_xcv, ver 1.0

[    1.648087] thunder_bgx, ver 1.0

[    1.648429] nicpf, ver 1.0

[    1.649763] e1000e: Intel(R) PRO/1000 Network Driver

[    1.650212] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.

[    1.650790] igb: Intel(R) Gigabit Ethernet Network Driver

[    1.651275] igb: Copyright (c) 2007-2014 Intel Corporation.

[    1.651829] igbvf: Intel(R) Gigabit Virtual Function Network Driver

[    1.652391] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.

[    1.653210] sky2: driver version 1.30

[    1.654260] VFIO - User Level meta-driver version: 0.3

[    1.671065] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

[    1.671706] ehci-pci: EHCI PCI platform driver

[    1.672153] ehci-platform: EHCI generic platform driver

[    1.675054] ehci-platform fe380000.usb: EHCI Host Controller

[    1.675606] ehci-platform fe380000.usb: new USB bus registered, assigned bus number 1

[    1.676465] ehci-platform fe380000.usb: irq 35, io mem 0xfe380000

[    1.691478] ehci-platform fe380000.usb: USB 2.0 started, EHCI 1.00

[    1.692350] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15

[    1.693098] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1

[    1.693747] usb usb1: Product: EHCI Host Controller

[    1.694186] usb usb1: Manufacturer: Linux 5.15.80-rockchip64 ehci_hcd

[    1.694762] usb usb1: SerialNumber: fe380000.usb

[    1.695818] hub 1-0:1.0: USB hub found

[    1.696201] hub 1-0:1.0: 1 port detected

[    1.699380] ehci-platform fe3c0000.usb: EHCI Host Controller

[    1.699938] ehci-platform fe3c0000.usb: new USB bus registered, assigned bus number 2

[    1.700787] ehci-platform fe3c0000.usb: irq 37, io mem 0xfe3c0000

[    1.715467] ehci-platform fe3c0000.usb: USB 2.0 started, EHCI 1.00

[    1.716300] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15

[    1.717048] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1

[    1.717695] usb usb2: Product: EHCI Host Controller

[    1.718135] usb usb2: Manufacturer: Linux 5.15.80-rockchip64 ehci_hcd

[    1.718711] usb usb2: SerialNumber: fe3c0000.usb

[    1.719906] hub 2-0:1.0: USB hub found

[    1.720372] hub 2-0:1.0: 1 port detected

[    1.721510] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver

[    1.722102] ohci-pci: OHCI PCI platform driver

[    1.722585] ohci-platform: OHCI generic platform driver

[    1.723409] ohci-platform fe3a0000.usb: Generic Platform OHCI controller

[    1.724059] ohci-platform fe3a0000.usb: new USB bus registered, assigned bus number 3

[    1.724887] ohci-platform fe3a0000.usb: irq 36, io mem 0xfe3a0000

[    1.787720] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.15

[    1.788473] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1

[    1.789122] usb usb3: Product: Generic Platform OHCI controller

[    1.789653] usb usb3: Manufacturer: Linux 5.15.80-rockchip64 ohci_hcd

[    1.790230] usb usb3: SerialNumber: fe3a0000.usb

[    1.791213] hub 3-0:1.0: USB hub found

[    1.791616] hub 3-0:1.0: 1 port detected

[    1.792660] ohci-platform fe3e0000.usb: Generic Platform OHCI controller

[    1.793280] ohci-platform fe3e0000.usb: new USB bus registered, assigned bus number 4

[    1.794111] ohci-platform fe3e0000.usb: irq 38, io mem 0xfe3e0000

[    1.855676] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.15

[    1.856430] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1

[    1.857078] usb usb4: Product: Generic Platform OHCI controller

[    1.857610] usb usb4: Manufacturer: Linux 5.15.80-rockchip64 ohci_hcd

[    1.858185] usb usb4: SerialNumber: fe3e0000.usb

[    1.859181] hub 4-0:1.0: USB hub found

[    1.859593] hub 4-0:1.0: 1 port detected

[    1.861538] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller

[    1.862056] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 5

[    1.862919] xhci-hcd xhci-hcd.0.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x8000000002010010

[    1.863848] xhci-hcd xhci-hcd.0.auto: irq 77, io mem 0xfe800000

[    1.864616] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller

[    1.865119] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 6

[    1.865814] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed

[    1.866602] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15

[    1.867347] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1

[    1.868155] usb usb5: Product: xHCI Host Controller

[    1.868600] usb usb5: Manufacturer: Linux 5.15.80-rockchip64 xhci-hcd

[    1.869176] usb usb5: SerialNumber: xhci-hcd.0.auto

[    1.870160] hub 5-0:1.0: USB hub found

[    1.870542] hub 5-0:1.0: 1 port detected

[    1.871353] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.

[    1.872269] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.15

[    1.873014] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1

[    1.873662] usb usb6: Product: xHCI Host Controller

[    1.874101] usb usb6: Manufacturer: Linux 5.15.80-rockchip64 xhci-hcd

[    1.874677] usb usb6: SerialNumber: xhci-hcd.0.auto

[    1.875682] hub 6-0:1.0: USB hub found

[    1.876064] hub 6-0:1.0: 1 port detected

[    1.877043] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller

[    1.877555] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 7

[    1.878408] xhci-hcd xhci-hcd.1.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x8000000002010010

[    1.879305] xhci-hcd xhci-hcd.1.auto: irq 78, io mem 0xfe900000

[    1.880105] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller

[    1.880610] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 8

[    1.881305] xhci-hcd xhci-hcd.1.auto: Host supports USB 3.0 SuperSpeed

[    1.882086] usb usb7: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15

[    1.882831] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1

[    1.883495] usb usb7: Product: xHCI Host Controller

[    1.883936] usb usb7: Manufacturer: Linux 5.15.80-rockchip64 xhci-hcd

[    1.884511] usb usb7: SerialNumber: xhci-hcd.1.auto

[    1.885508] hub 7-0:1.0: USB hub found

[    1.885888] hub 7-0:1.0: 1 port detected

[    1.886683] usb usb8: We don't know the algorithms for LPM for this host, disabling LPM.

[    1.887579] usb usb8: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.15

[    1.888324] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1

[    1.888969] usb usb8: Product: xHCI Host Controller

[    1.889409] usb usb8: Manufacturer: Linux 5.15.80-rockchip64 xhci-hcd

[    1.889985] usb usb8: SerialNumber: xhci-hcd.1.auto

[    1.890985] hub 8-0:1.0: USB hub found

[    1.891364] hub 8-0:1.0: 1 port detected

[    1.892444] usbcore: registered new interface driver usb-storage

[    1.895639] mousedev: PS/2 mouse device common for all mice

[    1.897567] i2c_dev: i2c /dev entries driver

[    1.898921] i2c 1-0011: Fixing up cyclic dependency with ff880000.i2s

[    1.903343] rk808 0-001b: chip id: 0x0

[    1.907940] rk808-regulator rk808-regulator: there is no dvs0 gpio

[    1.908529] rk808-regulator rk808-regulator: there is no dvs1 gpio

[    1.909087] rk808-regulator rk808-regulator: max buck steps per change: 8

[    1.910241] vdd_center: supplied by vcc5v0_sys

[    1.911452] vdd_cpu_l: supplied by vcc5v0_sys

[    1.912169] vcc_ddr: supplied by vcc5v0_sys

[    1.913143] vcc_1v8: supplied by vcc5v0_sys

[    1.914159] vcc1v8_codec: supplied by vcc5v0_sys

[    1.915752] vcc1v8_hdmi: supplied by vcc5v0_sys

[    1.917317] vcca_1v8: supplied by vcc5v0_sys

[    1.918867] vcc_sdio: supplied by vcc5v0_sys

[    1.920256] vcca3v0_codec: supplied by vcc5v0_sys

[    1.921819] vcc_1v5: supplied by vcc5v0_sys

[    1.923224] vcc0v9_hdmi: supplied by vcc5v0_sys

[    1.925074] vcc_3v0: supplied by vcc5v0_sys

[    1.926411] vcc_cam: supplied by vcc3v3_sys

[    1.927144] vcc_mipi: supplied by vcc3v3_sys

[    1.931483] rk808-rtc rk808-rtc: registered as rtc0

[    1.932491] rk808-rtc rk808-rtc: setting system clock to 2022-12-22T16:41:53 UTC (1671727313)

[    1.934844] fan53555-regulator 0-0040: FAN53555 Option[8] Rev[1] Detected!

[    1.935968] vdd_cpu_b: supplied by vcc5v0_sys

[    1.939160] fan53555-regulator 0-0041: FAN53555 Option[8] Rev[1] Detected!

[    1.940556] vdd_gpu: supplied by vcc5v0_sys

[    1.947499] dw_wdt ff848000.watchdog: No valid TOPs array specified

[    1.950514] sdhci: Secure Digital Host Controller Interface driver

[    1.951079] sdhci: Copyright(c) Pierre Ossman

[    1.951539] Synopsys Designware Multimedia Card Interface Driver

[    1.953401] sdhci-pltfm: SDHCI platform and OF driver helper

[    1.954196] dwmmc_rockchip fe310000.mmc: IDMAC supports 32-bit address mode.

[    1.954668] dwmmc_rockchip fe320000.mmc: IDMAC supports 32-bit address mode.

[    1.954891] dwmmc_rockchip fe310000.mmc: Using internal DMA controller.

[    1.955551] dwmmc_rockchip fe320000.mmc: Using internal DMA controller.

[    1.956131] dwmmc_rockchip fe310000.mmc: Version ID is 270a

[    1.956613] mmc1: CQHCI version 5.10

[    1.956725] dwmmc_rockchip fe320000.mmc: Version ID is 270a

[    1.957398] dwmmc_rockchip fe310000.mmc: DW MMC controller at irq 32,32 bit host data width,256 deep fifo

[    1.957663] dwmmc_rockchip fe320000.mmc: DW MMC controller at irq 33,32 bit host data width,256 deep fifo

[    1.957708] ledtrig-cpu: registered to indicate activity on CPUs

[    1.958543] dwmmc_rockchip fe310000.mmc: allocated mmc-pwrseq

[    1.959018] hid: raw HID events driver (C) Jiri Kosina

[    1.959231] dwmmc_rockchip fe320000.mmc: Got CD GPIO

[    1.959796] mmc_host mmc2: card is non-removable.

[    1.960490] usbcore: registered new interface driver usbhid

[    1.962660] usbhid: USB HID core driver

[    1.968867] drop_monitor: Initializing network drop monitor service

[    1.970214] NET: Registered PF_INET6 protocol family

[    1.972331] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)

[    1.974061] mmc_host mmc2: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)

[    1.983056] mmc1: SDHCI controller on fe330000.mmc [fe330000.mmc] using ADMA

[    2.081567] mmc1: Command Queue Engine enabled

[    2.082021] mmc1: new HS400 Enhanced strobe MMC card at address 0001

[    2.083829] mmcblk1: mmc1:0001 SLD64G 57.6 GiB

[    2.084964] mmc_host mmc2: Bus speed (slot 0) = 148500000Hz (slot req 150000000Hz, actual 148500000HZ div = 0)

[    2.114829]  mmcblk1: p1

[    2.115977] mmcblk1boot0: mmc1:0001 SLD64G 4.00 MiB

[    2.119198] mmcblk1boot1: mmc1:0001 SLD64G 4.00 MiB

[    2.122252] mmcblk1rpmb: mmc1:0001 SLD64G 4.00 MiB, chardev (241:0)

[    2.407630] dwmmc_rockchip fe310000.mmc: Successfully tuned phase to 223

[    2.411219] mmc2: new ultra high speed SDR104 SDIO card at address 0001

[    2.967832] Freeing initrd memory: 22252K

[    3.016854] Segment Routing with IPv6

[    3.017288] In-situ OAM (IOAM) with IPv6

[    3.017760] NET: Registered PF_PACKET protocol family

[    3.018416] 8021q: 802.1Q VLAN Support v1.8

[    3.018859] Key type dns_resolver registered

[    3.020988] registered taskstats version 1

[    3.021383] Loading compiled-in X.509 certificates

[    3.025411] Loaded X.509 cert 'Build time autogenerated kernel key: 61795ddb143ee60eb525e7adfa85249853099ba1'

[    3.033108] zswap: loaded using pool zstd/z3fold

[    3.034543] Key type .fscrypt registered

[    3.034905] Key type fscrypt-provisioning registered

[    3.038460] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, fsverity=yes

[    3.062461] Key type encrypted registered

[    3.062842] AppArmor: AppArmor sha1 policy hashing enabled

[    3.111821] vcc_0v9: supplied by vcc3v3_sys

[    3.113359] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges:

[    3.114063] rockchip-pcie f8000000.pcie:      MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000

[    3.114853] rockchip-pcie f8000000.pcie:       IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000

[    3.116609] rockchip-pcie f8000000.pcie: no bus scan delay, default to 0 ms

[    3.160295] rockchip-pcie f8000000.pcie: wait 0 ms (from device tree) before bus scan

[    3.161498] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00

[    3.162111] pci_bus 0000:00: root bus resource [bus 00-1f]

[    3.162620] pci_bus 0000:00: root bus resource [mem 0xfa000000-0xfbdfffff]

[    3.163253] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff] (bus address [0xfbe00000-0xfbefffff])

[    3.164206] pci 0000:00:00.0: [1d87:0100] type 01 class 0x060400

[    3.164938] pci 0000:00:00.0: supports D1

[    3.165315] pci 0000:00:00.0: PME# supported from D0 D1 D3hot

[    3.172878] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring

[    3.173823] Internal error: synchronous external abort: 96000210 [#1] PREEMPT SMP

[    3.174511] Modules linked in:

[    3.174805] CPU: 3 PID: 223 Comm: kworker/u12:4 Not tainted 5.15.80-rockchip64 #22.11.1

[    3.175535] Hardware name: Radxa ROCK Pi 4B (DT)

[    3.175960] Workqueue: events_unbound deferred_probe_work_func

[    3.176509] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--)

[    3.177147] pc : rockchip_pcie_rd_conf+0xb0/0x230

[    3.177589] lr : rockchip_pcie_rd_conf+0xec/0x230

[    3.178027] sp : ffff80000aa23830

[    3.178334] x29: ffff80000aa23830 x28: 0000000000000000 x27: 0000000000000000

[    3.178996] x26: 0000000000000000 x25: 0000000000000000 x24: ffff80000aa23974

[    3.179658] x23: ffff000001a75800 x22: 0000000000000000 x21: 0000000000000004

[    3.180319] x20: ffff80000aa238b4 x19: ffff80000c100000 x18: 0000000000000000

[    3.180981] x17: 6572202c295d3030 x16: 2d3030207375625b x15: ffffffffffffffff

[    3.181643] x14: ffff80000954e228 x13: ffff000006120a1c x12: ffff000006120290

[    3.182304] x11: 0000000000000028 x10: 0000000000000001 x9 : 0000000001001d87

[    3.182965] x8 : 000000000000ea60 x7 : ffff80000aa23800 x6 : 0000000000000001

[    3.183626] x5 : 0000000000000003 x4 : 0000000000000000 x3 : 0000000000c00008

[    3.184287] x2 : 000000000080000a x1 : ffff80000fc00008 x0 : ffff80000fc0000c

[    3.184950] Call trace:

[    3.185180]  rockchip_pcie_rd_conf+0xb0/0x230

[    3.185590]  pci_bus_read_config_dword+0x84/0xd8

[    3.186023]  pci_bus_generic_read_dev_vendor_id+0x34/0x1b0

[    3.186532]  pci_bus_read_dev_vendor_id+0x4c/0x70

[    3.186973]  pci_scan_single_device+0x84/0xd8

[    3.187381]  pci_scan_slot+0x38/0x120

[    3.187727]  pci_scan_child_bus_extend+0x58/0x330

[    3.188167]  pci_scan_bridge_extend+0x340/0x5a0

[    3.188591]  pci_scan_child_bus_extend+0x1fc/0x330

[    3.189039]  pci_scan_root_bus_bridge+0xd4/0xf0

[    3.189465]  pci_host_probe+0x18/0xb0

[    3.189811]  rockchip_pcie_probe+0x4a8/0x4c0

[    3.190213]  platform_probe+0x68/0xd8

[    3.190560]  really_probe+0xbc/0x428

[    3.190897]  __driver_probe_device+0x114/0x188

[    3.191311]  driver_probe_device+0xb0/0x110

[    3.191701]  __device_attach_driver+0xbc/0x158

[    3.192115]  bus_for_each_drv+0x7c/0xd0

[    3.192480]  __device_attach+0xec/0x1a8

[    3.192839]  device_initial_probe+0x14/0x20

[    3.193229]  bus_probe_device+0x9c/0xa8

[    3.193588]  deferred_probe_work_func+0x9c/0xf0

[    3.194008]  process_one_work+0x20c/0x4c8

[    3.194389]  worker_thread+0x208/0x478

[    3.194743]  kthread+0x138/0x150

[    3.195051]  ret_from_fork+0x10/0x20

[    3.195398] Code: f94013f5 a8c37bfd d50323bf d65f03c0 (b9400273)

[    3.195955] ---[ end trace b920595b4649d435 ]---

[    3.196380] note: kworker/u12:4[223] exited with preempt_count 1

 

Link to comment
Share on other sites

Switching to 6.0.10 kernel via armbian-config didn't help.

EDIT: Just built 6.1.1 mainline kernel and installed it, and it won't soft reboot either -  "Kernel panic - not syncing: Asynchronous SError Interrupt" 

So again, it boots ok for the first time (when powering on), it fails booting on soft reboot only.

Attaching serial console output

 

kernel_6.0.10_output kernel_6.1.1_output

Edited by desperex
Link to comment
Share on other sites

17 hours ago, koftikes said:

So this is my trying...  and again thank you for help!

Thank you for collecting the diverse logs. Unfortunately, they only confirm my initial analysis. The issue occurs when the NVME initialization should take place. The first part of the PCI client initialization succeeds:

[    2.216527] pci 0000:00:00.0: [1d87:0100] type 01 class 0x060400
[    2.217239] pci 0000:00:00.0: supports D1
[    2.217613] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    2.221587] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring

while the next one:

[    2.222558] pci 0000:01:00.0: [1e4b:1202] type 00 class 0x010802
[    2.223199] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
[    2.223977] pci 0000:01:00.0: Max Payload Size set to 256 (was 128, max 512)
[    2.225062] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
[    2.226049] pci 0000:01:00.0: 8.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x4 link at 0000:00:00.0 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link)

triggers the issue in the event of an error. The cause remains unclear, but since two autonomous devices interact via a complex PCI protocol, further analysis can be very time-consuming. In any case, this requires a kernel developer who is familiar with the PCIe subsystem.
It is known that not all conceivable hardware combinations will work, so other SBC manufacturers collect test reports to give their customers a guide which combinations can be used. This is the economically most favorable way to get a functioning system, development costs are usually way higher than the purchase of a suitable NVME SSD.
But this is only a workaround solution. The fact that the error situation seems to depend on the runtime behavior does not make fixing any easier.

In this case, a completely different cause may also be responsible. From the logs it can also be seen that even the firmware does not recognize the SPI flash on a case-by-case basis:

Loading Environment from SPIFlash... jedec_spi_nor flash@0: unrecognized JEDEC id bytes: ff, ff, ff
*** Warning - spi_flash_probe_bus_cs() failed, using default environment

 

Link to comment
Share on other sites

@koftikesI guess I found the solution, at least for me, try it.

My config, just for reference:

- Armbian 23.02.0-trunk Jammy with bleeding edge Linux 6.1.1-rockchip64, though this would work with any kernel

- Booting from eMMC, no SDcard

- NVMe (Crucial P2) is used as an extra logical partition (not system)

 

The root cause in my case is zero pcie bus scan delay, I used to have manjaro on this SBC and they had a patch to address this issue, but they do not make any new releases for rockpi4b because of some kind of emmc boot issue, so I'd stick with armbian for now

 

Steps to fix this issue:

1. Download your kernel source code. It can be done with 'sudo armbian-config' and going to Software->Source_install

2. Patch pcie-gen2 overlay (the simplest way to make the fix), replace 6.1.1 with your kernel version:

cd /usr/src/linux-source-6.1.1-rockchip64/
sudo cp ../linux-headers-6.1.1-rockchip64/Module.symvers .
make oldconfig # it copies .config to ./
sudo nano /usr/src/linux-source-6.1.1-rockchip64/arch/arm64/boot/dts/rockchip/overlay/rockchip-pcie-gen2.dts

Make changes to DTS file so it looks like this, key thing here is bus-scan-delay-ms set to 1000ms, you can try to set it to a greater value in case 1000 doesn't work for you:

/dts-v1/;
/plugin/;

/ {
    compatible = "rockchip,rk3399";
    fragment@0 {
        target = <&pcie0>;
        __overlay__ {
            max-link-speed = <2>;
            bus-scan-delay-ms = <1000>;
        };
    };
};

3. Compile DTS and copy DTBO file to boot partition :

cd /usr/src/linux-source-6.1.1-rockchip64/
sudo make -j4 dtbs
sudo cp -rf /usr/src/linux-source-6.1.1-rockchip64/arch/arm64/boot/dts/rockchip/overlay/rockchip-pcie-gen2.dtbo /boot/dtb/rockchip/overlay/
sudo cp -rf /usr/src/linux-source-6.1.1-rockchip64/arch/arm64/boot/dts/rockchip/overlay/rockchip-pcie-gen2.dtbo /boot/dtb-6.1.1-rockchip64/rockchip/overlay/

4. Reboot

5. Profit! 

Link to comment
Share on other sites

25.11.2022 в 20:30, Igor сказал:

No, problem is identified, but we don't have resources / money to proceed from here. For us, this is 24/7, for you - when something breaks down. 

 

It wasn't easy, but it wasn't that difficult considering my minimum level ....
 

First of all. After analyzing the sources
https://github.com/torvalds/linux/blob/v5.10/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi
https://github.com/torvalds/linux/blob/v5.15/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi
https://github.com/torvalds/linux/blob/v6.1/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi

it became clear that the source code already has the part of changes:
 

&pcie0 {
	ep-gpios = <&gpio4 RK_PD3 GPIO_ACTIVE_HIGH>;
	num-lanes = <4>;
	pinctrl-0 = <&pcie_clkreqnb_cpm>;
	pinctrl-names = "default";
	vpcie0v9-supply = <&vcc_0v9>;
	vpcie1v8-supply = <&vcc_1v8>;
	vpcie3v3-supply = <&vcc3v3_pcie>;
	status = "okay";
};

&pcie_phy {
	status = "okay";
};


BUT board-rockpi4-0003-arm64-dts-pcie.patch --- creates a mess:
 

&pcie0 {
	ep-gpios = <&gpio4 RK_PD3 GPIO_ACTIVE_HIGH>;
	num-lanes = <4>;
	max-link-speed = <1>;
	pinctrl-names = "default";
	pinctrl-0 = <&pcie_clkreqnb_cpm>;
	vpcie12v-supply = <&vcc12v_dcin>;
	vpcie3v3-supply = <&vcc3v3_pcie>;
	status = "okay";
};

&pcie_phy {
	status = "okay";
};

&pmu_io_domains {
	status = "okay";

	pmu1830-supply = <&vcc_3v0>;
};

&pcie_phy {
	status = "okay";
};

&pcie0 {
	ep-gpios = <&gpio4 RK_PD3 GPIO_ACTIVE_HIGH>;
	num-lanes = <4>;
	pinctrl-0 = <&pcie_clkreqnb_cpm>;
	pinctrl-names = "default";
	vpcie0v9-supply = <&vcc_0v9>;
	vpcie1v8-supply = <&vcc_1v8>;
	vpcie3v3-supply = <&vcc3v3_pcie>;
	status = "okay";
};


 

An attempt to simply disable the patch provided a negative result.

Then I compared the source and the old patch and highlighted the following changes in a separate patch. Also based on the sources I added bus-scan-delay-ms = <1000>;

https://gitlab.manjaro.org/manjaro-arm/packages/core/linux/-/issues/10
https://www.spinics.net/lists/linux-pci/msg103349.html
https://www.spinics.net/lists/linux-pci/msg103351.html 
 

diff --git a/Documentation/devicetree/bindings/pci/rockchip-pcie-host.txt b/Documentation/devicetree/bindings/pci/rockchip-pcie-host.txt
index af34c6577..1829b442c 100644
--- a/Documentation/devicetree/bindings/pci/rockchip-pcie-host.txt
+++ b/Documentation/devicetree/bindings/pci/rockchip-pcie-host.txt
@@ -57,6 +57,8 @@ Optional Property:
 	using 24MHz OSC for RC's PHY.
 - ep-gpios: contain the entry for pre-reset GPIO
 - num-lanes: number of lanes to use
+- bus-scan-delay-ms: delay before PCIe bus scan in milliseconds.
+	Provides a workaround for some devices causing a crash in bus scan.
 - vpcie12v-supply: The phandle to the 12v regulator to use for PCIe.
 - vpcie3v3-supply: The phandle to the 3.3v regulator to use for PCIe.
 - vpcie1v8-supply: The phandle to the 1.8v regulator to use for PCIe.
diff --git a/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi b/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi
index 1f5101dac..c67528e23 100644
--- a/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi
+++ b/arch/arm64/boot/dts/rockchip/rk3399-rock-pi-4.dtsi
@@ -80,6 +80,8 @@ vcc3v3_pcie: vcc3v3-pcie-regulator {
 		regulator-name = "vcc3v3_pcie";
 		regulator-always-on;
 		regulator-boot-on;
+		regulator-min-microvolt = <3300000>;
+		regulator-max-microvolt = <3300000>;
 		vin-supply = <&vcc5v0_sys>;
 	};
 
@@ -525,11 +527,12 @@ &pcie_phy {
 &pcie0 {
 	ep-gpios = <&gpio4 RK_PD3 GPIO_ACTIVE_HIGH>;
 	num-lanes = <4>;
+	max-link-speed = <1>;
 	pinctrl-0 = <&pcie_clkreqnb_cpm>;
 	pinctrl-names = "default";
-	vpcie0v9-supply = <&vcc_0v9>;
-	vpcie1v8-supply = <&vcc_1v8>;
+	vpcie12v-supply = <&vcc12v_dcin>;
 	vpcie3v3-supply = <&vcc3v3_pcie>;
+	bus-scan-delay-ms = <1000>;
 	status = "okay";
 };


AND now it's working booting from uSD;  working "boot from eMMC system on eMMC"; working soft reboot too

 

root@rockpi-4b:~# uname -a 
Linux rockpi-4b 5.15.85-rockchip64 #trunk SMP PREEMPT Mon Dec 26 15:48:30 +03 2022 aarch64 GNU/Linux

root@rockpi-4b:~# fdisk -l
Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: NE-1TB                                  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mmcblk1: 57.62 GiB, 61865984000 bytes, 120832000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x425824f4

Device         Boot Start       End   Sectors Size Id Type
/dev/mmcblk1p1      32768 119603199 119570432  57G 83 Linux

Disk /dev/zram0: 1.89 GiB, 2025594880 bytes, 494530 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/zram1: 50 MiB, 52428800 bytes, 12800 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

root@rockpi-4b:~# dd if=/dev/nvme0n1 of=/dev/null bs=1M count=2048 iflag=direct status=progress
1118830592 bytes (1.1 GB, 1.0 GiB) copied, 1 s, 1.1 GB/s
2048+0 records in
2048+0 records out
2147483648 bytes (2.1 GB, 2.0 GiB) copied, 1.88694 s, 1.1 GB/s


Armbian_22.11.2-trunk_Rockpi-4b_bullseye_5.15.85.log  This is console log cool boot + soft reboot from uSD

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines