Jump to content

Johnny on the couch

Members
  • Posts

    10
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. Hi, I was not expecting someone to debug some old experimental kernel just for me. I've trying to report bug, give back something to the community. It is not build problem, so Github says use forums for that. I've spent more than a week to have latest and greatest experimental kernel (6.14.5, 6.14.8) or not so experimental (6.12.9, 6.12.23, 6.12.30) with DKMS. Did many rebuilds, reinstalls and reflashes. I was using INSTALL_HEADERS=yes in CLI args or config. DKMS drivers (zfs and aic8800) does not work. I am suspecting that problem is in sunxi headers like reported month ago in github issue. There, the same DKMS driver works on same version on the kernel on RaspiOS where it was working. When that person tried to do it on Armbian it doesn't work. If I was skillful enough I would try to fix it by myself, but I am not. Therefore I am reporting this bug here.
  2. If I understood correctly, Github job is running on amd64 platform, your test is on rockchip kernel. I am talking about sunxi kernel. Latest sunxi kernel where zfs-dkms worked (on Allwinner H618) was 6.11.2-edge. My RK356x board is on the way, but it would be nice to make this small LonganPi-3H with H618 usable
  3. Hi, I could try to help with maintenance, but first we should find where the problem is. Even if we ignore aic8800 driver (I can confirm that when it is working it is indeed shiet and there are occasional USB disconnections of WLAN card), zfs-dkms still doesn't work. Latest version where both drivers were working was 6.11.2. Currently compiling 6.11.9 to see if there DKMS drivers work. I am suspecting that kernel headers for 6.12 and later kernels are to blame
  4. Sometimes panic is after reboot, sometimes is after few hours of uptime. Panic1 from the previous post is while doing apt update. 2nd was while compiling zfs-dkms and 3rd I don't rember. The same Noble image works on eMMC, without panic, for now. I'll try to reproduce it with another SD card.
  5. Even booting image built with compile.sh and trying to load module doesn't work: root@longanpi-3h:~# modprobe aic_btusb_usb modprobe: ERROR: could not insert 'aic_btusb_usb': Exec format error root@longanpi-3h:~# dmesg | tail [ 7.172720] systemd[1]: Started systemd-rfkill.service - Load/Save RF Kill Switch Status. [ 7.390663] systemd[1]: Finished armbian-ramlog.service - Armbian memory supported logging. [ 7.437995] systemd[1]: Starting systemd-journald.service - Journal Service... [ 7.445699] systemd[1]: Finished ldconfig.service - Rebuild Dynamic Linker Cache. [ 7.497556] systemd-journald[412]: Collecting audit messages is disabled. [ 7.588956] systemd[1]: Started systemd-journald.service - Journal Service. [ 7.646152] systemd-journald[412]: Received client request to flush runtime journal. [ 9.628132] EXT4-fs (mmcblk0p1): resizing filesystem from 446464 to 932864 blocks [ 9.725518] EXT4-fs (mmcblk0p1): resized filesystem to 932864 [ 92.076404] module aic_btusb: .gnu.linkonce.this_module section size must match the kernel's built struct module size at run time root@longanpi-3h:~# modinfo /lib/modules/6.12.30-current-sunxi64/updates/dkms/aic_btusb_usb.ko filename: /lib/modules/6.12.30-current-sunxi64/updates/dkms/aic_btusb_usb.ko license: GPL version: 2.1.0 description: AicSemi Bluetooth USB driver version author: AicSemi Corporation import_ns: VFS_internal_I_am_really_a_filesystem_and_am_NOT_a_driver srcversion: B6C3A1904D0AFEA27CE3E93 alias: usb:vA69Cp88DCd*dc*dsc*dp*icE0isc01ip01in* alias: usb:vA69Cp8D81d*dc*dsc*dp*icE0isc01ip01in* alias: usb:vA69Cp8801d*dc*dsc*dp*icE0isc01ip01in* depends: name: aic_btusb vermagic: 6.12.30-current-sunxi64 SMP mod_unload aarch64 parm: btdual:int parm: bt_support:int parm: mp_drv_mode:0: NORMAL; 1: MP MODE (int)
  6. How to compile DKMS on the board? I am trying this for the past week without success and starting to go crazy... The last kernel which worked is 6.11.2. I tried with zfs-dkms (from apt's repositories and from manually build .deb from zfs git) and with aic8800 drivers. I've tried Bookworm image, tried Noble. Tried -current and -edge kernels. Tried many kernel revisions. Tried to build kernels (image & headers) with compile.sh with docker, without docker. Updated my x86 Debian to Trixie. Compilers are same on the build host and on the board: longanpi-3h# dpkg -l | grep -i gcc ii gcc 4:13.2.0-7ubuntu1 arm64 GNU C compiler ii gcc-13 13.3.0-6ubuntu2~24.04 arm64 GNU C compiler ii gcc-13-aarch64-linux-gnu 13.3.0-6ubuntu2~24.04 arm64 GNU C compiler for the aarch64-linux-gnu architecture ii gcc-13-base:arm64 13.3.0-6ubuntu2~24.04 arm64 GCC, the GNU Compiler Collection (base package) ... root@4585c06e2f54:/armbian# dpkg -l | grep -i gcc ii gcc 4:13.2.0-7ubuntu1 amd64 GNU C compiler ii gcc-13 13.3.0-6ubuntu2~24.04 amd64 GNU C compiler ii gcc-13-aarch64-linux-gnu 13.3.0-6ubuntu2~24.04cross1 amd64 GNU C compiler for the aarch64-linux-gnu architecture ii gcc-13-aarch64-linux-gnu-base:amd64 13.3.0-6ubuntu2~24.04cross1 amd64 GCC, the GNU Compiler Collection (base package) ... Or even better: Is it possible somehow to build those drivers on the host PC? 16x x86 CPUs are much, much faster than 4x A53.
  7. Hi, I am not aware of the older Longan image. I've used it for a few months with OrangePi Zero3 image without kernel panics. I've collected few more kernel crashes on the same image (latest Ubuntu Noble freshly installed on SD card): apt update on USB WiFi, LAN still connected, DKMS aic8800 built, freshly reinstalled image While doing apt install zfs-dkms panic3:
  8. Kernel crash on freshly installed image for LonganPi 3H. Image downloaded from: https://www.armbian.com/longanpi-3h/ Ubuntu 24.04 Noble. Sometimes it will crash few seconds after boot, before logging or doing anything. Didn't install or do anything, just apt-get update and upgrade. logs: https://paste.next.armbian.com/ocofepenup [ 1511.118664] Internal error: Oops: 0000000096000044 [#1] SMP [ 1511.124251] Modules linked in: sunrpc rtl8xxxu mac80211 cfg80211 sunxi_cedrus(C) rfkill libarc4 v4l2_mem2mem videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videodev videobuf2_common polyval_ce sun50i_h6_prcm_ppu mc polyval_generic dump_reg cpufreq_dt zram zsmalloc binfmt_misc sch_fq_codel fuse dm_mod realtek sun6i_rtc_ccu dwmac_sun8i mdio_mux [ 1511.155156] CPU: 1 UID: 0 PID: 2658 Comm: sshd Tainted: G WC 6.12.23-current-sunxi64 #1 [ 1511.164459] Tainted: [W]=WARN, [C]=CRAP [ 1511.168292] Hardware name: Sipeed Longan Pi 3H (DT) [ 1511.173166] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 1511.180124] pc : enqueue_timer+0x3c/0x150 [ 1511.184141] lr : __mod_timer+0x30c/0x370 [ 1511.188063] sp : ffff800085a13920 [ 1511.191376] x29: ffff800085a13920 x28: 00000000000005a8 x27: 0000000000000000 [ 1511.198514] x26: ffff8000821f6000 x25: 0000000000000001 x24: 0000000100049ec4 [ 1511.205652] x23: 000000000000000c x22: ffff0000ff760000 x21: 0000000100049ecc [ 1511.212789] x20: ffff0000ff760000 x19: 0000000100049ec4 x18: 0000000000000042 [ 1511.219926] x17: 85a0e7cbaf550a08 x16: 01010000d9864102 x15: 1880ada177e5cf73 [ 1511.227064] x14: 54c33ab316000103 x13: 6a5d85a0e7cbaf55 x12: 0a0801010000d986 [ 1511.234201] x11: 41021880ada177e5 x10: cf7354c33ab31600 x9 : ffff800080125244 [ 1511.241341] x8 : ffff800080b33870 x7 : ffff0000ff7600d0 x6 : ffff800082201980 [ 1511.248479] x5 : 000000000000000c x4 : 000000000000000c x3 : 0000000100049ecc [ 1511.255617] x2 : ffff0000ff760070 x1 : 0000000000000000 x0 : ffff0000ff760000 [ 1511.262756] Call trace: [ 1511.265204] enqueue_timer+0x3c/0x150 [ 1511.268868] __mod_timer+0x30c/0x370 [ 1511.272444] mod_timer+0x1c/0x30 [ 1511.275673] sk_reset_timer+0x28/0x98 [ 1511.279339] tcp_schedule_loss_probe.part.0+0x13c/0x270 [ 1511.284567] tcp_write_xmit+0x320/0x1390 [ 1511.288492] __tcp_push_pending_frames+0x44/0x108 [ 1511.293197] tcp_push+0xbc/0x168 [ 1511.296431] tcp_sendmsg_locked+0xa14/0xc38 [ 1511.300616] tcp_sendmsg+0x40/0x70 [ 1511.304021] inet6_sendmsg+0x4c/0x78 [ 1511.307599] __sock_sendmsg+0x64/0xc0 [ 1511.311265] sock_write_iter+0xa8/0x118 [ 1511.315102] vfs_write+0x334/0x3b8 [ 1511.318508] ksys_write+0xf8/0x120 [ 1511.321911] __arm64_sys_write+0x24/0x38 [ 1511.325835] invoke_syscall+0x50/0x120 [ 1511.329590] el0_svc_common.constprop.0+0x48/0xf0 [ 1511.334296] do_el0_svc+0x24/0x38 [ 1511.337615] el0_svc+0x30/0xd0 [ 1511.340675] el0t_64_sync_handler+0x120/0x130 [ 1511.345034] el0t_64_sync+0x190/0x198 [ 1511.348703] Code: a9025bf5 aa0003f6 aa0303f5 f8657841 (f9000261) [ 1511.354794] ---[ end trace 0000000000000000 ]--- [ 1511.359410] note: sshd[2658] exited with irqs disabled [ 1571.130516] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 1571.136471] rcu: 1-...0: (7 GPs behind) idle=ad6c/1/0x4000000000000000 softirq=10876/10876 fqs=6851 [ 1571.145603] rcu: (detected by 2, t=15004 jiffies, g=19153, q=1042 ncpus=4) [ 1571.152564] Sending NMI from CPU 2 to CPUs 1: [ 1581.152989] rcu: rcu_sched kthread starved for 555 jiffies! g19153 f0x0 RCU_GP_DOING_FQS(6) ->state=0x0 ->cpu=0 [ 1581.167420] rcu: Unless rcu_sched kthread gets sufficient CPU time, OOM is now expected behavior. [ 1581.176371] rcu: RCU grace-period kthread stack dump: [ 1581.181418] task:rcu_sched state:R running task stack:0 pid:17 tgid:17 ppid:2 flags:0x00000008 [ 1581.192290] Call trace: [ 1581.194738] __switch_to+0xe8/0x150 [ 1581.198235] 0x0 [ 1581.200080] rcu: Stack dump where RCU GP kthread last ran: [ 1581.205561] Sending NMI from CPU 2 to CPUs 0:
  9. ZFS-DKMS doesn't work on vanilla image https://dl.armbian.com/longanpi-3h/Bookworm_current_minimal Image is freshly burnt to the SD card. root@longanpi-3h:~# apt update root@longanpi-3h:~# apt install zfs-dkms root@longanpi-3h:~# modprobe zfs modprobe: ERROR: could not insert 'zfs': Exec format error root@longanpi-3h:~# modinfo zfs | grep -v parm filename: /lib/modules/6.12.23-current-sunxi64/updates/dkms/zfs.ko version: 2.3.1-1~bpo12+1 license: CDDL license: Dual BSD/GPL license: Dual MIT/GPL author: OpenZFS description: ZFS alias: zzstd alias: zcommon alias: zunicode alias: znvpair alias: zlua alias: icp alias: zavl alias: devname:zfs alias: char-major-10-249 srcversion: 2742833EE1C14D857611F06 depends: spl name: zfs vermagic: 6.12.23-current-sunxi64 SMP mod_unload aarch64 root@longanpi-3h:~# file /lib/modules/6.12.23-current-sunxi64/updates/dkms/zfs.ko /lib/modules/6.12.23-current-sunxi64/updates/dkms/zfs.ko: ELF 64-bit LSB relocatable, ARM aarch64, version 1 (SYSV), BuildID[sha1]=f87455b001529d816f09e1498e63a902d1af9be5, not stripped root@longanpi-3h:~# uname -a Linux longanpi-3h 6.12.23-current-sunxi64 #1 SMP Thu Apr 10 12:39:41 UTC 2025 aarch64 GNU/Linux logs After doing apt upgrade, reinstalling dkms module result is the same.
  10. I was trying to do the same thing and this was the post which duckduck go lead me to. For the future searchers: you'll need format_partitions__func_name() function (notice "partitions" vs "partition"). You have 2 options: create separate file in extensions with your function and enable it in board config file or just create function in board config file (eg config/boards/orangepizero3.csc), like: function format_partitions__fstab() { echo "# something custom for fstab" >> $SDCARD/etc/fstab } Rerun compile.sh and you'll have your custom fstab I did try all the hooks but only modifications done in format_partitions will end up not overwritten.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines