Jump to content

Race666

Members
  • Posts

    2
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Six days ago i installed Armbian Buster mainline based kernel 5.3.y, Armbian 19.11.3, Welcome to Armbian Buster with Linux 5.3.9-sunxi and latest update on an Orange PI R1. I have multiple kernel panics during some network operations: Starting OpenVPN or set a interface (wlan0) up down. Are there any known issues? Message from syslogd@localhost at Nov 26 09:06:13 ... kernel:[48503.690394] Internal error: Oops: 5 [#1] SMP THUMB2 kernel:[48503.799195] Process RTW_CMD_THREAD (pid: 1040, stack limit = 0x4f9a57 f2) kernel:[48503.805886] Stack: (0xc74eff28 to 0xc74f0000) kernel:[48503.810233] ff20: c85d5a00 d0a99518 d0a99518 cf184a 00 d0a98000 bfa95058 kernel:[48503.818402] ff40: d0a99518 bfa29827 d0a98000 c85d5640 d0a99518 bfa126 6b 00b7e151 cf184a00 kernel:[48503.826570] ff60: c74eff78 c8777cc0 c85d0c00 00000000 c74ee000 d0a980 00 bfa1257f ce667914 kernel:[48503.834738] ff80: c8777cdc c013339d 00000035 c85d0c00 c01332a1 000000 00 00000000 00000000 kernel:[48503.842905] ffa0: 00000000 00000000 00000000 c01010f9 00000000 000000 00 00000000 00000000 kernel:[48503.851073] ffc0: 00000000 00000000 00000000 00000000 00000000 000000 00 00000000 00000000 kernel:[48503.859240] ffe0: 00000000 00000000 00000000 00000000 00000013 000000 00 00000000 00000000 kernel:[48503.931490] Code: f43f af2d f8d4 2d3a (6e43) 429a kernel:[48503.941146] Kernel panic - not syncing: Fatal exception in interrupt
  2. I've recently bought a Rock Pi 4a Board and can't get running armbian (The Image provided by Radxa works) but I want to get running the latest version. I've tried both nightly builds Armbian Bionic nightly development branch 4.20.y (22.05.2019)and Armbian Stretch nightly development branch 4.20.y Both Image boots U-Boot but cannot start the kernel: U-Boot 2017.09-armbian (May 22 2019 - 04:11:32 +0200) Model: RockPi-4B DRAM: 3.9 GiB DCDC_REG1@vdd_center: ; enabling DCDC_REG2@vdd_cpu_l: ; enabling DCDC_REG3@vcc_ddr: ; enabling (ret: -38) DCDC_REG4@vcc_1v8: set 1800000 uV; enabling LDO_REG1@vcc1v8_dvp: set 1800000 uV; enabling LDO_REG2@vcc3v0_touch: set 3000000 uV; enabling LDO_REG3@vcc1v8_pmu: set 1800000 uV; enabling LDO_REG4@vcc_sd: set 3300000 uV; enabling LDO_REG5@vcca3v0_codec: set 3000000 uV; enabling LDO_REG6@vcc_1v5: set 1500000 uV; enabling LDO_REG7@vcca1v8_codec: set 1800000 uV; enabling LDO_REG8@vcc_3v0: set 3000000 uV; enabling SWITCH_REG1@vcc3v3_s3: ; enabling (ret: -38) SWITCH_REG2@vcc3v3_s0: ; enabling (ret: -38) vcc1v8-s0@vcc1v8_s0: set 1800000 uV; enabling (ret: -38) dc-12v@dc_12v: set 12000000 uV; enabling (ret: -38) vcc-sys@vcc_sys: set 5000000 uV; enabling (ret: -38) vcc3v3-sys@vcc3v3_sys: set 3300000 uV; enabling (ret: -38) vcc-phy-regulator@vcc_phy: ; enabling (ret: -38) vdd-log@vdd_log: ; enabling (ret: -38) MMC: sdhci@fe330000: 0, dwmmc@fe320000: 1 SF: unrecognized JEDEC id bytes: ff, ff, ff *** Warning - spi_flash_probe_bus_cs() failed, using default environment In: serial@ff1a0000 Out: serial@ff1a0000 Err: serial@ff1a0000 Model: RockPi-4B boot mode 5242c300. normal boot Net: eth0: ethernet@fe300000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! mmc_init: -95, time 19 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 2949 bytes read in 38 ms (75.2 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 102 bytes read in 31 ms (2.9 KiB/s) 8335365 bytes read in 937 ms (8.5 MiB/s) 14107136 bytes read in 1548 ms (8.7 MiB/s) 74997 bytes read in 103 ms (710.9 KiB/s) 1847 bytes read in 55 ms (32.2 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 39000000 ## Loading init Ramdisk from Legacy Image at 04000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 8335301 Bytes = 7.9 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 f570f000, end f5f01fc5 ... OK reserving fdt memory region: addr=1f00000 size=78000 Loading Device Tree to 00000000f5694000, end 00000000f570efff ... OK Starting kernel ... Then i tried to compile Armbian from scratch with vendor kernel BOARD=rockpi-4b BRANCH=default RELEASE=stretch BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no CLEAN_LEVEL=make ./compile.sh I flashed the image to the SD Card by dd if=Armbian.... of=/dev/mmcblk0 bs=4M With this image, U-boot starts and ends up in an reboot loop U-Boot 2017.09-armbian (Dec 10 2018 - 09:24:29 +0800) Model: Rockchip RK3399 Evaluation Board DRAM: 3.9 GiB Relocation Offset is: f5c0b000 PMIC: RK808 pwm-regulator(vdd-center): init 950000 uV vdd_center 950000 uV regulator(vdd-center) init 950000 uV MMC: dwmmc@fe320000: 1, sdhci@fe330000: 0 Using default environment Warn: can't find connect driver Failed to found available display route Warn: can't find connect driver Failed to found available display route In: serial Out: serial Err: serial Model: Rockchip RK3399 Evaluation Board RKPARM: Invalid parameter part table switch to partitions #0, OK mmc1 is current device do_rkimg_test found IDB in SDcard Boot from SDcard get part misc fail -1 Net: eth0: ethernet@fe300000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 2949 bytes read in 37 ms (77.1 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 102 bytes read in 31 ms (2.9 KiB/s) 4460205 bytes read in 247 ms (17.2 MiB/s) 18978824 bytes read in 877 ms (20.6 MiB/s) ** File not found /boot/dtb/rockchip/rockpi-4b-linux.dtb ** libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. It did not find /boot/dtb/rockchip/rockpi-4b-linux.dtb. I've copied /boot/dtb/rockchip/rk3399-rockpi4b.dtb to /boot/dtb/rockchip/rockpi-4b-linux.dtb but this ends in an kernel panic. Any hints?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines