Schwemmlandebene

Members
  • Content Count

    52
  • Joined

  • Last visited

About Schwemmlandebene

  • Rank
    Advanced Member

Recent Profile Visitors

689 profile views
  1. Are you sure? root@m2-bare:~# cat /proc/irq/181/smp_affinity f root@m2-bare:~# cat /proc/irq/42/smp_affinity 2 root@m2-bare:~# cat /proc/irq/31/smp_affinity 8 root@m2-bare:~# cat /proc/irq/30/smp_affinity 8 root@m2-bare:~# cat /proc/irq/29/smp_affinity 4 root@m2-bare:~# cat /proc/irq/28/smp_affinity 4 root@m2-bare:~# echo 2 > /proc/irq/181/smp_affinity -bash: echo: write error: Input/output error root@m2-bare:~#
  2. I don't use postebin, etc. I could post the whole output here. Here is a snippet: + ID='Banana Pi M2' + [[ Sinovoip BPI-M2 == *AMLOGIC* ]] + [[ Sinovoip BPI-M2 == *HummingBoard2* ]] + [[ -f /etc/armbian-release ]] + case ${HARDWARE} in + chmod 644 /etc/logrotate.d/armhwinfo ++ awk -F: '/eth0|brcmf_oob_intr/{print $1}' /proc/interrupts + for i in '$(awk -F'\'':'\'' '\''/eth0|brcmf_oob_intr/{print $1}'\'' /proc/interrupts)' + echo 2 + for i in '$(awk -F'\'':'\'' '\''/eth0|brcmf_oob_intr/{print $1}'\'' /proc/interrupts)' + echo 2 /etc/init.d/armhwinfo: line 233: echo: write error: Input/output error + '[' -f /var/log/armhwinfo.log ']' ++ awk -F: '/sunxi-mmc/{print $1}' /proc/interrupts ++ date + for i in '$(awk -F'\'':'\'' '\''/sunxi-mmc/{print $1}'\'' /proc/interrupts)' + echo 4 + for i in '$(awk -F'\'':'\'' '\''/sunxi-mmc/{print $1}'\'' /proc/interrupts)' + echo 4 + echo -e '\n\n\nSun Jun 12 14:21:33 CEST 2016 sun6i armv7l 4.5.4-sunxi Linux version 4.5.4-sunxi (root@ubuarm) (gcc version 4.8.4 (Ubuntu/Linaro 4.8.4-2ubuntu1~14.04.1) ) #2 SMP Sat Jun 11 13:05:21 CEST 2016' ++ awk -F: '/hcd:usb/{print $1}' /proc/interrupts + echo -e '\n### dmesg:\n' + cat /tmp/armhwinfo.OwXgVA + for i in '$(awk -F'\'':'\'' '\''/hcd:usb/{print $1}'\'' /proc/interrupts)' + echo 8 + for i in '$(awk -F'\'':'\'' '\''/hcd:usb/{print $1}'\'' /proc/interrupts)' + echo 8 + echo -e '\n### lsusb:' + '[' -f /boot/.verbose ']' Does armhwinfo do not exit? root@m2-bare:~# cat /proc/interrupts CPU0 CPU1 CPU2 CPU3 17: 0 0 0 0 GIC-0 29 Edge arch_timer 18: 3795 8165 75263 8169 GIC-0 30 Edge arch_timer 21: 0 0 0 0 GIC-0 50 Level sun4i_timer0 22: 0 0 0 0 GIC-0 83 Level sun5i_timer0 27: 0 0 0 0 GIC-0 82 Level 1c02000.dma-controller 28: 625 0 1910 0 GIC-0 92 Level sunxi-mmc 29: 8266 0 0 0 GIC-0 94 Level sunxi-mmc 30: 27 0 0 262 GIC-0 104 Level ehci_hcd:usb1 31: 0 0 0 0 GIC-0 105 Level ohci_hcd:usb2 40: 498 0 0 0 GIC-0 60 Level sun4i-ts 41: 430 0 0 0 GIC-0 32 Level serial 42: 31217 10822 0 0 GIC-0 114 Level eth0 48: 0 0 0 0 GIC-0 72 Level 1f00000.rtc 57: 0 0 0 0 sunxi_pio_edge 4 Edge 1c0f000.mmc cd 181: 44 0 0 0 sunxi_pio_level 0 Level brcmf_oob_intr IPI0: 0 0 0 0 CPU wakeup interrupts IPI1: 0 0 0 0 Timer broadcast interrupts IPI2: 4199 8013 14879 8066 Rescheduling interrupts IPI3: 9 9 6 4 Function call interrupts IPI4: 0 0 0 0 CPU stop interrupts IPI5: 0 0 0 0 IRQ work interrupts IPI6: 0 0 0 0 completion interrupts Err: 0 root@m2-bare:~#
  3. Hmm, I tried the lala version, too, and that's the output: root@m2-bare:~# journalctl --no-pager | grep armhwinfo Jun 12 14:09:52 m2-bare armhwinfo[645]: [ ok ] Setting noop I/O scheduler for mmcblk0 Jun 12 14:09:52 m2-bare armhwinfo[645]: [ ok ] Starting ARM hardware info: (Linux version 4.5.4-sunxi (root@ubuarm) (gcc version 4.8.4 (Ubuntu/Linaro 4.8.4-2ubuntu1~14.04.1) ) #2 SMP Sat Jun 11 13:05:21 CEST 2016) Jun 12 14:09:52 m2-bare armhwinfo[645]: /etc/init.d/armhwinfo: line 233: echo: write error: Input/output error Jun 12 14:09:52 m2-bare armhwinfo[645]: awk: cannot open lala.txt (No such file or directory) Jun 12 14:09:52 m2-bare armhwinfo[645]: awk: cannot open lala.txt (No such file or directory) root@m2-bare:~#
  4. Ahh, I didn't mind the awk syntax. But bash complains. root@m2-bare:/etc/init.d# /etc/init.d/armhwinfo start [ ok ] Setting noop I/O scheduler for mmcblk0 [ ok ] Starting ARM hardware info: (Linux version 4.5.4-sunxi (root@ubuarm) (gcc version 4.8.4 (Ubuntu/Linaro 4.8.4-2ubuntu1~14.04.1) ) #2 SMP Sat Jun 11 13:05:21 CEST 2016) /etc/init.d/armhwinfo: line 233: echo: write error: Input/output error sun6i) # Banana Pi M2: do network on cpu1, SDIO on cpu2, USB on cpu3 for i in $(awk -F':' '/eth0|brcmf_oob_intr/{print $1}' /proc/interrupts); do echo 2 >/proc/irq/$i/smp_affinity done for i in $(awk -F':' '/sunxi-mmc/{print $1}' /proc/interrupts); do echo 4 >/proc/irq/$i/smp_affinity done for i in $(awk -F':' '/hcd:usb/{print $1}' /proc/interrupts); do echo 8 >/proc/irq/$i/smp_affinity done ;;
  5. /proc/interrupts or </proc/interrupts? if </proc/interrupts, what about line 232?
  6. I did - copy armhwinfo - reboot - copy some GB over NFS root@m2-bare:~# cat /boot/.verbose 1465726540 sun6i armv7l 4.5.4-sunxi Linux version 4.5.4-sunxi (root@ubuarm) (gcc version 4.8.4 (Ubuntu/Linaro 4.8.4-2ubuntu1~14.04.1) ) #2 SMP Sat Jun 11 13:05:21 CEST 2016 root@m2-bare:~# cat /proc/interrupts CPU0 CPU1 CPU2 CPU3 17: 0 0 0 0 GIC-0 29 Edge arch_timer 18: 53622 41095 142718 94383 GIC-0 30 Edge arch_timer 21: 0 0 0 0 GIC-0 50 Level sun4i_timer0 22: 0 0 0 0 GIC-0 83 Level sun5i_timer0 27: 0 0 0 0 GIC-0 82 Level 1c02000.dma-controller 28: 2095 0 0 0 GIC-0 92 Level sunxi-mmc 29: 8580 0 0 0 GIC-0 94 Level sunxi-mmc 30: 27 0 0 0 GIC-0 104 Level ehci_hcd:usb1 31: 0 0 0 0 GIC-0 105 Level ohci_hcd:usb2 40: 932 0 0 0 GIC-0 60 Level sun4i-ts 41: 423 0 0 0 GIC-0 32 Level serial 42: 30792 257702 0 0 GIC-0 114 Level eth0 48: 0 0 0 0 GIC-0 72 Level 1f00000.rtc 57: 0 0 0 0 sunxi_pio_edge 4 Edge 1c0f000.mmc cd 181: 44 0 0 0 sunxi_pio_level 0 Level brcmf_oob_intr IPI0: 0 0 0 0 CPU wakeup interrupts IPI1: 0 0 0 0 Timer broadcast interrupts IPI2: 43231 21388 45126 41832 Rescheduling interrupts IPI3: 7 5 6 7 Function call interrupts IPI4: 0 0 0 0 CPU stop interrupts IPI5: 0 0 0 0 IRQ work interrupts IPI6: 0 0 0 0 completion interrupts Err: 0 root@m2-bare:~#
  7. Banana Pi M2 PS: I don't use the latest Armbian toolchain. I'm using the .ignore_changes feature. root@m2-bare:~# uname -a Linux m2-bare 4.5.4-sunxi #2 SMP Sat Jun 11 13:05:21 CEST 2016 armv7l GNU/Linux root@m2-bare:~# cat /proc/interrupts CPU0 CPU1 CPU2 CPU3 17: 0 0 0 0 GIC-0 29 Edge arch_timer 18: 11870 265608 31223 36550 GIC-0 30 Edge arch_timer 21: 0 0 0 0 GIC-0 50 Level sun4i_timer0 22: 0 0 0 0 GIC-0 83 Level sun5i_timer0 27: 0 0 0 0 GIC-0 82 Level 1c02000.dma-controller 28: 1653 0 0 0 GIC-0 92 Level sunxi-mmc 29: 8549 0 0 0 GIC-0 94 Level sunxi-mmc 30: 27 0 0 0 GIC-0 104 Level ehci_hcd:usb1 31: 0 0 0 0 GIC-0 105 Level ohci_hcd:usb2 40: 2251 0 0 0 GIC-0 60 Level sun4i-ts 41: 425 0 0 0 GIC-0 32 Level serial 42: 43646 0 0 0 GIC-0 114 Level eth0 48: 0 0 0 0 GIC-0 72 Level 1f00000.rtc 57: 0 0 0 0 sunxi_pio_edge 4 Edge 1c0f000.mmc cd 181: 43 0 0 0 sunxi_pio_level 0 Level brcmf_oob_intr IPI0: 0 0 0 0 CPU wakeup interrupts IPI1: 0 0 0 0 Timer broadcast interrupts IPI2: 3407 15690 13225 7318 Rescheduling interrupts IPI3: 6 8 3 6 Function call interrupts IPI4: 0 0 0 0 CPU stop interrupts IPI5: 0 0 0 0 IRQ work interrupts IPI6: 0 0 0 0 completion interrupts Err: 0 root@m2-bare:~#
  8. The DHCP configuration causes the problem. Solution 1: Make a change in /etc/network/interfaces to: iface eth0 inet manual Solution 2: If you want to send some settings via DHCP keep the original setting in /etc/network/interfaces iface eth0 inet dhcp and set the lease times in /etc/dhcp/dhcpd.conf to infinity. Infinity means a few years. Have a look at /var/lib/dhcp/dhclient.eth0.leases on the client. default-lease-time -1; max-lease-time -1; Check for typos and restart dhcpd. user:$ sudo dhcpd -t -cf /etc/dhcp/dhcpd.conf Internet Systems Consortium DHCP Server 4.3.1 Copyright 2004-2014 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Config file: /etc/dhcp/dhcpd.conf Database file: /var/lib/dhcp/dhcpd.leases PID file: /var/run/dhcpd.pid user:$ sudo systemctl restart isc-dhcp-server.service For some reason my client gets the DHCP ntp-server option but ntpd ignores it. Would be great, if someone has a hint. IHMO a line starting with /dev/nfs in /etc/fstab is an error and ignored because it doesn't fit the [host:dir] scheme. /dev/nfs / nfs defaults 0 0 root@m2-bare:~# journalctl --no-pager | grep mount Jun 12 10:05:49 m2-bare systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point. Jun 12 10:05:49 m2-bare systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. Jun 12 10:05:53 m2-bare systemd[1]: Starting Remount Root and Kernel File Systems... Jun 12 10:05:53 m2-bare systemd-remount-fs[330]: mount.nfs: remote share not in 'host:dir' format Jun 12 10:05:53 m2-bare systemd-remount-fs[330]: /bin/mount for / exited with exit status 32. Jun 12 10:05:53 m2-bare systemd[1]: systemd-remount-fs.service: main process exited, code=exited, status=1/FAILURE Jun 12 10:05:53 m2-bare systemd[1]: Failed to start Remount Root and Kernel File Systems. Jun 12 10:05:53 m2-bare systemd[1]: Unit systemd-remount-fs.service entered failed state. Jun 12 10:05:54 m2-bare kernel: EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: commit=600,errors=remount-ro The thread could be marked as solved and the topic to be changed to: [rootfs=nfs] nfs: server x.x.x.x not responding, still trying
  9. Well, that sounds very interesting and may open the possibility or make it easier to support 4.4.x LTS besides legacy, next and dev. (If there's a request for LTS support.) But at the moment I'm very busy. I will think about it in a few weeks when the actual project has finished.
  10. Well, I'm not a kernel developer nor very familiar with managing kernel patches. But for the next weeks I need a working Armbian toolchain and a working image. The method described above is a good work around for me. Maybe this will help someone with similar needs.
  11. Hallo, with EXTENDED_DEBOOTSTRAP="yes" and ROOTFS_TYPE="nfs"my bananapim2 (jessie, next) has its / on /dev/nfs. After a few minutes it hangs with the error message: nfs: server x.x.x.x not responding, still trying To extend the timeout period I add timeo=30 (3 seconds) to nfs-boot.cmd. The result is: ubuntu:~# grep timeo userpatches/nfs-boot.cmd setenv bootargs "console=tty1 console=ttyS0,115200 root=/dev/nfs ${net_setup} rw rootflags=noatime,nodiratime,timeo=30 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 enforcing=0 loglevel=6" # Banana Pi M2 root@m2-bare:~# journalctl --no-pager | grep nfs Jun 10 23:17:01 m2-bare kernel: Kernel command line: console=tty1 console=ttyS0,115200 root=/dev/nfs ip=dhcp rw rootflags=noatime,nodiratime,timeo=30 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 enforcing=0 loglevel=6 Jun 10 23:17:01 m2-bare kernel: nfs4filelayout_init: NFSv4 File Layout Driver Registering... root@m2-bare:~# mount | grep nfs x.x.x.x:/srv/nfs/root on / type nfs (rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,hard,nolock,proto=tcp,port=2049,timeo=7,retrans=10,sec=sys,local_lock=all,addr=x.x.x.x) Unfortunately / is mounted with timeo=7. Adding the timeo option to /etc/fstab brings no success, too. The mount command still shows timeo=7. I guessed /etc/fstab is ignored totally. But that is wrong. Changing the first column "/dev/nfs" to something like "x.x.x.x:/srv/nfs/testroot" will be recognized. How could / be mounted with additional options like a greater timeout period?
  12. Short update: Kernel 4.5.2 and commit 2a2e190 looks ok. cd lib/ sudo git checkout 2a2e190 cd .. touch .ignore_changes sudo echo "KERNELBRANCH=\"v4.5.2\"" >> userpatches/lib.config # add # KERNELTAG="v4.5.2" # to compile.sh Kernel 4.5.6 additionally needs: sudo touch userpatches/kernel/sunxi-next/crypto_ss_corruption_fix.patch No luck with 4.4.4, because I didn't find a proper linux-sunxi-next.config.
  13. Thank you for your answer Igor, but unfortunately I'm a bit confused now. One commit later the patch has been removed, but with two other sunxi-next patches. c788fc3 Update sunxi-next patches to 4.6.1 patch/kernel/sunxi-next/axp20x-sysfs-interface.patch patch/kernel/sunxi-next/crypto_ss_corruption_fix.patch patch/kernel/sunxi-next/stmmac-fix-v4.5.patch The patch was changed or added? at April 20, commit 78a5e92 "sunxi SS fix patch", I guess. Edit: just guessing: the patch was necessary for 4.5.1, but later at 4.5.x, 4.5.6 it was no more necessary, In Armbian it wasn't removed from 4.5.x because Armbian was preparing for the next kernel version 4.6.x and the patch could be deleted in this phase, too.
  14. This works partially. Now I get the warning: [ warn ] ... crypto_ss_corruption_fix.patch [ failed ] Maybe I have to chose an older commit or do I have to rename the patch to crypto_ss_corruption_fix.patch.disabled? I could even go back to a 4.4.x kernel for my lamabo-r1 and bananapim2 boards, but which commit do I have to choose in this case?