Turris Build issueshttps://gitlab.nic.cz/turris/os/build/-/issues2024-03-04T10:10:06+01:00https://gitlab.nic.cz/turris/os/build/-/issues/428Strongswan seems to misbehave2024-03-04T10:10:06+01:00Michal HruseckyStrongswan seems to misbehavehttps://forum.turris.cz/t/turris-os-7-0-is-in-rc/19755/20https://forum.turris.cz/t/turris-os-7-0-is-in-rc/19755/20Turris OS 7.0Richard MuzikRichard Muzikhttps://gitlab.nic.cz/turris/os/build/-/issues/395smartctl issues - upgrade smartmontools package and friends to latest release2022-12-24T12:22:45+01:00krisansmartctl issues - upgrade smartmontools package and friends to latest releaseMy system:
```less
# turris omnia:
Device Turris Omnia
reForis version 1.4.1
Turris OS version 6.1.0
Turris OS branch HBS
Kernel version 5.15.84
# Installed packages:
opkg list-installed | grep ^smart
smartd - 7.2-...My system:
```less
# turris omnia:
Device Turris Omnia
reForis version 1.4.1
Turris OS version 6.1.0
Turris OS branch HBS
Kernel version 5.15.84
# Installed packages:
opkg list-installed | grep ^smart
smartd - 7.2-1
smartmontools - 7.2-1
smartmontools-drivedb - 7.2-1
# /etc/init.d/smartd restart
Dec XX XX:XX:XX turris smartd[29041]: smartd 7.2 2020-12-30 r5155 [armv7l-linux-5.15.84] (localbuild)
```
Please upgrade these packages to latest versions.
Latest release for Today is version 7.3 from 2022-02-28: https://www.smartmontools.org/browser/tags/RELEASE_7_3/smartmontools/ChangeLog
related
---
Additional info.
Current version of __smartctl__ behaves odd after interrupting its execution by pressing Ctrl-C.
For example, the interrupted command was:
```shell
# /dev/sda - hard drive connected to Turris using mPCI-E card
smartctl -x /dev/sda # pressed Ctrl-C during execution
```
Since then, I get the following program issues (when using with switches: `-i`, `-a`), the same disk:
```less
smartctl -i /dev/sda
smartctl 7.2 2020-12-30 r5155 [armv7l-linux-5.15.84] (localbuild)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
Short INQUIRY response, skip product id
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
```https://gitlab.nic.cz/turris/os/build/-/issues/383Cannot open any Turris GUI administration after update, OpenVPN also, SSH wor...2022-11-10T09:36:17+01:00JoeKrenekCannot open any Turris GUI administration after update, OpenVPN also, SSH works only# Steps To Reproduce
1. Update from Turris OS 5 to the latest Turris OS 6
2. Try to login into Turris via turris.local or 192.168.1.1 (both http and https)
3. "web not available" tried in latest Chrome, Firefox, Safari in Windows and Mac...# Steps To Reproduce
1. Update from Turris OS 5 to the latest Turris OS 6
2. Try to login into Turris via turris.local or 192.168.1.1 (both http and https)
3. "web not available" tried in latest Chrome, Firefox, Safari in Windows and MacOS
# Expected Result
I should see login screen
# Actual Result
Internet and SSH works without access to Turris administration
Cannot connect via previously working OpenVPN
Log file: [diag.gz](/uploads/094736c689828290ce89604e2a2c6c90/diag.gz)
What old Turris 5 wanted to update: [Updater_žádá_o_autorizaci_akcí.txt](/uploads/67bd8611c11e348ea842731964c487e1/Updater_žádá_o_autorizaci_akcí.txt)
# Repeated steps
Tried to restart several times, wait, rollback, update again but same result.Turris OS 6.0.3https://gitlab.nic.cz/turris/os/build/-/issues/361Please fix UNICODE / wide character support in terminal2022-08-15T14:01:27+02:00Ghost UserPlease fix UNICODE / wide character support in terminalLocal terminal over UART and also remote terminal over SSH on all Turris routers stop working after sending some UTF-8 character. SSH shell is completely ignoring LC locale settings for UTF-8 support and treats every send byte separately...Local terminal over UART and also remote terminal over SSH on all Turris routers stop working after sending some UTF-8 character. SSH shell is completely ignoring LC locale settings for UTF-8 support and treats every send byte separately, ignoring UNICODE or wide character settings. This makes terminals unusable on modern systems.
Simple reproducer: Type `echo á` then press backspace and then press enter. It should not write anything on the terminal. But currently it prints back garbage `�`.Turris OS 5.4.1https://gitlab.nic.cz/turris/os/build/-/issues/338compile_pkgs unrecognized parameters2022-04-01T17:46:50+02:00Adam Konrádcompile_pkgs unrecognized parametersHello, I'd like to report an issue with the compile_pkgs script.
```
uname -srm
Linux 5.10.102-99.473.amzn2.aarch64 aarch64
```
This is a centos based distro.
I'm getting the following:
```
../build/compile_pkgs prepare_tools -t omni...Hello, I'd like to report an issue with the compile_pkgs script.
```
uname -srm
Linux 5.10.102-99.473.amzn2.aarch64 aarch64
```
This is a centos based distro.
I'm getting the following:
```
../build/compile_pkgs prepare_tools -t omnia
There is no such option or command: prepare_tools
```
```
../build/compile_pkgs -t omnia
...
Checking 'rsync'... ok.
make[1] diffconfig
Setting ccache paths
Compiling tools
../build/compile_pkgs: line 58: BUILD_ARGS[@]: unbound variable
```
I'm not sure if this is some tool version mismatch or a problem in the script.https://gitlab.nic.cz/turris/os/build/-/issues/314/dev mounted twice2022-01-03T15:06:18+01:00Ghost User/dev mounted twiceThis is only a minor annoyance, but /dev is mounted twice:
```
# mount | grep " on /dev "
devtmpfs on /dev type devtmpfs (rw,relatime,size=1033476k,nr_inodes=189059,mode=755)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,size=512k,mode=7...This is only a minor annoyance, but /dev is mounted twice:
```
# mount | grep " on /dev "
devtmpfs on /dev type devtmpfs (rw,relatime,size=1033476k,nr_inodes=189059,mode=755)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,size=512k,mode=755)
```
I believe the first (type devtmpfs) mount is coming from the kernel config option CONFIG_KERNEL_DEVTMPFS_MOUNT=y, while the second (type tmpfs) mount is coming from patches/openwrt/to-upstream/0022-procd-New-style-of-cgroups.patch:
```
+++ b/package/system/procd/patches/new-style-of-cgroup-hiearchy.patch
++++ b/initd/early.c
+ mount("tmpfs", "/dev", "tmpfs", MS_NOATIME | MS_NOSUID, "mode=0755,size=512K");
```
I believe that second mount (type tmpfs in early_mounts() from that patch) is redundant & should be removed (or made conditional on a check if /dev is already mounted, if we can't rely on CONFIG_KERNEL_DEVTMPFS_MOUNT=y always being set).
Thanks,
Conway S. SmithTurris OS 6.0https://gitlab.nic.cz/turris/os/build/-/issues/288Check-packages.py is not found2023-08-16T10:56:22+02:00Josef SchlehoferCheck-packages.py is not foundThis was reported by Jenkins (run 2215) on HBD branch for Turris 1.x router:
```
/tmp/hudson18271722316329023503.sh: 23: /tmp/hudson18271722316329023503.sh: ./helpers/check-packages.py: not found
+ echo Packages check reported some issu...This was reported by Jenkins (run 2215) on HBD branch for Turris 1.x router:
```
/tmp/hudson18271722316329023503.sh: 23: /tmp/hudson18271722316329023503.sh: ./helpers/check-packages.py: not found
+ echo Packages check reported some issues!
Packages check reported some issues!
FATAL: Remote call on slave08 failed
```https://gitlab.nic.cz/turris/os/build/-/issues/284Turris 1.x routers can not get kernel image on kernel 5.102023-08-16T10:57:14+02:00Josef SchlehoferTurris 1.x routers can not get kernel image on kernel 5.10It seems that there is something going on with kernel 5.10 on Turris 1.x routers.
Here is the log:
```
U-Boot 2015.04-04654-gbcfb33e-dirty (Jun 26 2015 - 12:50:49)
CPU0: P2020E, Version: 2.1, (0x80ea0021)
Core: e500, Version: 5.1, (0...It seems that there is something going on with kernel 5.10 on Turris 1.x routers.
Here is the log:
```
U-Boot 2015.04-04654-gbcfb33e-dirty (Jun 26 2015 - 12:50:49)
CPU0: P2020E, Version: 2.1, (0x80ea0021)
Core: e500, Version: 5.1, (0x80211051)
Clock Configuration:
CPU0:1200 MHz, CPU1:1200 MHz,
CCB:600 MHz,
DDR:400 MHz (800 MT/s data rate) (Asynchronous), LBC:37.500 MHz
L1: D-cache 32 KiB enabled
I-cache 32 KiB enabled
wdt status 00000005 reset
Watchdog enabled
Board: TURRIS CPLD: V4.1 PCBA: V4.0
Error, wrong i2c adapter 2 max 2 possible
in: 56
out: 0
io_config: 255
rom_loc: nor upper bank
SD/MMC : 4-bit Mode
eSPI : Enabled
I2C: Error, wrong i2c adapter 2 max 2 possible
ready
SPI: ready
DRAM: Error, wrong i2c adapter 2 max 2 possible
Detected UDIMM 9905594-003.A00G
WARNING: Calling __hwconfig without a buffer and before environment is ready
WARNING: Calling __hwconfig without a buffer and before environment is ready
2 GiB (DDR3, 64-bit, CL=6, ECC off)
Flash: 16 MiB
L2: 512 KiB enabled
NAND: 256 MiB
MMC: FSL_SDHC: 0
PCIe1: Root Complex of mini PCIe SLOT, no link, regs @ 0xffe0a000
PCIe1: Bus 00 - 00
PCIe2: Root Complex of PCIe SLOT, x1 gen1, regs @ 0xffe09000
02:00.0 - 168c:0030 - Network controller
PCIe2: Bus 01 - 02
PCIe3: Root Complex of PCIe SLOT, x1 gen1, regs @ 0xffe08000
04:00.0 - 104c:8241 - Serial bus controller
PCIe3: Bus 03 - 04
Error, wrong i2c adapter 2 max 2 possible
In: serial
Out: serial
Err: serial
Net: Phy 5 not found
PHY reset timed out
eTSEC1
Error: eTSEC1 address not set.
, eTSEC2
Error: eTSEC2 address not set.
, eTSEC3 [PRIME]
Error: eTSEC3 address not set.
Hit any key to stop autoboot: 0
BOOT NAND
reading zImage
8929664 bytes read in 389 ms (21.9 MiB/s)
wdt status 00000003
reading fdt
12147 bytes read in 13 ms (912.1 KiB/s)
WARNING: adjusting available memory to 30000000
Wrong Image Format for bootm command
ERROR: can't get kernel image!
```Turris OS 7.0https://gitlab.nic.cz/turris/os/build/-/issues/281Package python3-flask requires package python3-click that is not available2023-08-16T10:57:28+02:00Lukas JelinekPackage python3-flask requires package python3-click that is not availableAfter updating Turris Omnia to TOS 5.2.3 (in HBK), it displayed this error message twice:
```
Updater failed:
inconsistent: Package python3-flask requires package python3-click that is not available.
```After updating Turris Omnia to TOS 5.2.3 (in HBK), it displayed this error message twice:
```
Updater failed:
inconsistent: Package python3-flask requires package python3-click that is not available.
```Turris OS 6.0https://gitlab.nic.cz/turris/os/build/-/issues/278Standalone package wireguard was dropped in favor of kernel package2023-08-16T10:57:32+02:00Josef SchlehoferStandalone package wireguard was dropped in favor of kernel package@jbetik reported to me that while trying HBD branch on Turris 1.x router, he installed ``wireguard`` via opkg.
The thing is that wireguard is now part of kernel, but for kernel 5.4 it was backported there and since this commit https://g...@jbetik reported to me that while trying HBD branch on Turris 1.x router, he installed ``wireguard`` via opkg.
The thing is that wireguard is now part of kernel, but for kernel 5.4 it was backported there and since this commit https://github.com/openwrt/openwrt/commit/a701d4b8414db2e1fafa676fad232cc9a0bfeaab there is provided ``kmod-wireguard`` package.
I could not find any file in turris-build repository which would depend on ``wireguard`` standalone package itself and users can meet this warning:
```
inconsistent: Requested package wireguard that is not available.
```
In that case, it is suggested that users should take a look at ``/etc/updater/conf.d/opkg-auto.ua`` and replace ``wireguard`` by ``kmod-wireguard``.Turris OS 6.0https://gitlab.nic.cz/turris/os/build/-/issues/253Service umount is not enabled in medkit2021-06-07T19:42:51+02:00Karel KociService umount is not enabled in medkitThe service `umount` is in `/etc/services_wanted` and on update of package `base-files` that contains it is enabled and started but in medkit it is not.
This looks like issue of the chicken and an egg. The `base-files` packages is esse...The service `umount` is in `/etc/services_wanted` and on update of package `base-files` that contains it is enabled and started but in medkit it is not.
This looks like issue of the chicken and an egg. The `base-files` packages is essentially the first package to be installed and contains also `/etc/services_wanted`. It is likely that not all what is needed is available and thus service is not enabled.
This is not a big issue as the service only tries to correctly umount all mounted filesystems except of root. The same operation is automatically performed by kernel.https://gitlab.nic.cz/turris/os/build/-/issues/251ipcheck.py can not be found2021-04-16T11:19:13+02:00Josef Schlehoferipcheck.py can not be foundHonestly, I am not sure what I did, but I rollbacked to some older snapshot with HBD and then do pkgupdate, tried to startup kresd and it shows that ipcheck can not be found
```
root@turris:~# /etc/init.d/kresd start
/etc/rc.common: lin...Honestly, I am not sure what I did, but I rollbacked to some older snapshot with HBD and then do pkgupdate, tried to startup kresd and it shows that ipcheck can not be found
```
root@turris:~# /etc/init.d/kresd start
/etc/rc.common: line 96: ipcheck.py: not found
/etc/rc.common: line 99: ipcheck.py: not found
/etc/rc.common: line 96: ipcheck.py: not found
/etc/rc.common: line 99: ipcheck.py: not found
/etc/rc.common: line 96: ipcheck.py: not found
/etc/rc.common: line 99: ipcheck.py: not found
/etc/rc.common: line 96: ipcheck.py: not found
/etc/rc.common: line 99: ipcheck.py: not found
job 6 at Wed Mar 3 14:47:00 2021
```Turris OS 6.0https://gitlab.nic.cz/turris/os/build/-/issues/243Turris Omnia WiFi cards dectection sometimes fails2021-10-06T15:41:09+02:00Karel KociTurris Omnia WiFi cards dectection sometimes fails```
ls: /sys/bus/pci/devices/0000:00:01.0/000*/iee*/phy*: No such file or directory
```
This happens most likely because wifi cards are not yet detected at time of board script execution.
The `/etc/board.d` scripts are executed as one...```
ls: /sys/bus/pci/devices/0000:00:01.0/000*/iee*/phy*: No such file or directory
```
This happens most likely because wifi cards are not yet detected at time of board script execution.
The `/etc/board.d` scripts are executed as one of the last steps in preinit but all kernel modules are loaded right after preinit. The drivers are not built in so the devices are just not available.
The result of this is that led for wifi card is just not configured to blink with appropriate device. In effect it is set to not blink at all.Turris OS 5.3.0https://gitlab.nic.cz/turris/os/build/-/issues/231Generate medkits - pkgupdate can not be found as there are not enough depend...2021-10-14T11:42:50+02:00Josef SchlehoferGenerate medkits - pkgupdate can not be found as there are not enough dependencies installedI'm trying to use generate_medkits, but it seems I don't have installed required dependencies and it fails with such outputs:
```
configure: error: Package requirements (liburiparser >= 0.9) were not met:
No package 'liburiparser' found...I'm trying to use generate_medkits, but it seems I don't have installed required dependencies and it fails with such outputs:
```
configure: error: Package requirements (liburiparser >= 0.9) were not met:
No package 'liburiparser' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
```
and so on.
When I tried to run generate_medkits once again when I installed the dependency it fails with this output:
```
warning: redirecting to https://gitlab.nic.cz/turris/updater/updater.git/
/bin/bash: line 13: /foo/omnia-hbl/turris-tools/updater-ng/pkgupdate: No such file or directory
```
I know that correct solution would be install dependencies from this file https://gitlab.nic.cz/turris/updater/updater/-/blob/master/.gitlab-ci-docker/DockerFile_debian but I'm trying to document usage of generate medkits in README in this repository.
**It helps when I remove folder turris-tools and then I can use generate_medkits once again.**Turris OS 6.0https://gitlab.nic.cz/turris/os/build/-/issues/215LuCI: LXC containers are not listed after installation2021-04-09T11:19:44+02:00Karel KociLuCI: LXC containers are not listed after installationThe issue is that there are no containers listed in LuCI if there are any already or if they are created after that till the reboot is performed.
This happens only if you install LXC not when you remove and install it back on running ro...The issue is that there are no containers listed in LuCI if there are any already or if they are created after that till the reboot is performed.
This happens only if you install LXC not when you remove and install it back on running router. Boot of device has to be without LXC installed.
The cause is missing LXC in ubus. Any direct operation such as creation of container are successful but anything modifying existing containers uses ubus. LXC ubus support is provided by package `rpcd-mod-lxc`. This package clearly is not forcing rpcd reload.Turris OS 5.2.0https://gitlab.nic.cz/turris/os/build/-/issues/210Reporting statistics from compile_pkgs2023-08-16T10:58:31+02:00Josef SchlehoferReporting statistics from compile_pkgsWhile using: `./compile_pkgs stats`
I received this output:
```
Reporting statistics
Statistics of the build:
* 251 binary packages built
* 0find: ‘logs/package/’: No such file or directory
/0 source packages failed
```
While I do: ...While using: `./compile_pkgs stats`
I received this output:
```
Reporting statistics
Statistics of the build:
* 251 binary packages built
* 0find: ‘logs/package/’: No such file or directory
/0 source packages failed
```
While I do: cat build/logs/stats
It shows:
```
Statistics of the build:
* 251 binary packages built
* 0/0 source packages failed
```Turris OS 5.1.9https://gitlab.nic.cz/turris/os/build/-/issues/171MOX - INFO: rcu_sched detected stalls on CPUs/tasks2020-07-07T14:51:36+02:00Josef SchlehoferMOX - INFO: rcu_sched detected stalls on CPUs/tasksAfter a long time, I tried to use `HBD` from `HBK` branch, but MOX is not succesfully booted.
```
## Flattened Device Tre blob at 04f00000
Booting using the fdt blob at 0x4f00000
Loading Device Tree to 000000003bf14000, end 000000...After a long time, I tried to use `HBD` from `HBK` branch, but MOX is not succesfully booted.
```
## Flattened Device Tre blob at 04f00000
Booting using the fdt blob at 0x4f00000
Loading Device Tree to 000000003bf14000, end 000000003bf1bee0 .. OK
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 5.4.48 (packaging@turris.cz) (gcc version 8.4.0 (OpenWrt GCC 8.4.0 3b0f698)) #0 SMP Sat Jul 4 00:03:54 2020
[ 0.000000] Machine moel: CZ.NIC Turris Mox Board
[ 0.000000] earlycon: ar3700_uart0 at MMIO 0x00000000d0012000 (options '')
[ 0.000000] printk: bootconsole [ar3700_uart0] enabled
[ 0.000000] ps�K��ɽ�����for conduit method from DT.
[ 0.000000] psci: PSCIv.1 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.1
[ 0.000000] percpu: Embedded 16 pages/cpu s28440 r8192 d28904 u65536
[ 0.000000] Detected VIPT I-cache on CPU0
[ 0.000000] CPU features: detected: GIC system register CPU interface
[ 0.000000] Speculative Store Bypass Disable mitigation n��requirad
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 257536
[ 0.000000] Kernel command line: earlyprintk console=ttyMV0,115200 earlycon=ar3700_uart,0xd0�����j������}���btrfs root=PARTUUID=00000000-01 rootflags=commit=5,subvol=@ rootwait rw cfg80211.freg=
[ 0.000000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[ 0.000000] Inode-cache hash table entrie.'Ͳ����Bz�ɑ��� 7, 524288 bytes, linear)
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] Memory: 1014344K/1046528K available (8446K kernel code, 480K rwdata, 2112K rodata, 576K init, 300K bss, 32184K reserved, 0K cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] rcu: CONFIG_RCU_FANOUT set to non-default value of 32.
[ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[ 0.000000] GICv3: GIC: Using split EOI/Deactivate mode
[ 0.000000] GICv3: 192 SPIs implemented
[ 0.000000] GICv3: 0 Extended SPIs implemented
[ 0.000000] GICv3: Distributor has no Range Selector support
[ 0.000000] GICv3: 16 PPAs implemented
[ 0.000000] GICv3: no VLPI support, no direct LPI support
[ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x00000000d1d40000
[ 0.000000] random: get_random_bytes called from start_kernel+0x354/0x4cc with crng_init=0
[ 0.000000] arch_timer: cp15 timer(s) running at 12.50M@z (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycle.'ɂ��e2049cda, max_idle_ns: 440795202628 ns
[ 0.000004] sched_clock: 56 bips at 12MHz, resolution 80ns, wraps every 4398046511080ns
[ 0.008423] Console: colour dummy device 80x25
[ 0.012935] Calibrating delay loop (skipped), value calculated using timer frequency. �r�����5%AM�(lpj=125000)
[ 0.023582] pid_ma� default: 32768 minimum: 301
[ 0.028442] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
[ 0.035992] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes, linear)
[ 0.045304] ASID allocapor initialised with 32768 entries
[ 0.050894] rcu: Hierarchical SRCU implementation.
[ 0.056116] smp: Bringing up secondary CPUs ...
[ 0.061156] Detected VIPT I-cache on CPU1
[ 0.061186] GICv3: CPU1: found redistributor 1 region 0:0x00000000d1d60000
[ 0.061221] CPU1: Booted seconary processor 0x0000000001 [0x410fd034]
[ 0.061310] smp: Brought up 1 node, 2 CPUs
[ 0.083368] SMP: Total of 2 processors activated.
[ 0.088201] CPU features: detected: 32-bit EL0 Support
[ 0.093493] CPU features: detected: CRC32 instructions
[ 0.098815] CPU features: emulated: Privileged Access Never (PAN) using TTBR0_EL1 switching
[ 0.107383] CPU: All CPU(s) started at EL2
[ 0.111595] alternatives: patching kernel code
[ 0.117006] devtmpfs: initialized
[ 0.122792] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.132882] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[ 0.139965] xor: measuring software checksum speed
[ 0.244875] 8rYց : 1978.800 MB/sec
[ 0.3449遺� 32regs : 2270.400 MB/sec
[ 0.444942] arm64_neon: 2002.400 MB/sec
[ 0.449161] xor: using function: 32regs (2270.400 MB/sec)
[ 0.454725] pinctrl core: initialized pinctrl subsystem
[ 0.461015] NET: Registered protocol family 16
[ 0.465947] DMA: prellocated 256 KiB pool for atomic allocations
[ 0.473223] cpuidle: using governor ladder
[ 0.477678] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[ 0.500455] cryptd: max_cpu_qlen set to 1000
[ 0.506196] raid6: using algorithm neonx8 gen() 0 MB/s
[ 0.511441] raid6: .... xor() 0 MB/s, rmw en`bled
[ 0.516245] raid6: using neon recovery algorithm
[ 0.522045] SCSI subsystem initialized
[ 0.527134] usbcore: registered new interface driver usbfs
[ 0.532940] usbcore: registered new interface driver hub
[ 0.538387] usbcore: registered new device driver usb
[ 0.545257] clocksource: Switched to clocksource arch_sys_counterC�[ 0.558430] thermal_sys: Registered thermal governor 'step_wise'
[ 0.558710] NET: Registeped protocol family 2
[ 0.570114] tcp_listen_portaddr_hash h table entries: 512 (order: 1, 8192 bytes, linear)
[ 0.578820] TCP estblished hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.586790] TCP bind hash table entries: 8192 (orer: 5, 131072 bytes, linear)
[ 0.594279] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.600910] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 0.607670] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 0.615084] NET: Registered protocol family 1
%� (j���邕�ͱ default 64
[ 0.624112] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters available
[ 0.637292] workingset: timestamp_bits=46 max_order=18 bucket_order=0
[ 0.648540] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.654472] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 0.671661] mv_xor d0060900.xor: Marvell shared XOR drivar
[ 0.735922] mv_xor d0060900.xor: Marvell XOR (Descriptor Mode): ( xor cpy intr )
[ 0.805880] mv_xor d0060900.xor: Marvell XOR (Descriptor Mode): ( xor cp intr )
[ 0.813883] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[ 0.822445] cacheinfo: Unable to detect cache hierarchy for CPU 0
[ 0.832223] loop: module loaded
[ 0841411] random: fast init done
[ 0.850064] spi-nor spi0.0: w25q64dw (8192 Kbytes)
[ 0.855089] 5 fixed-partitions partitions found on MTD device spi0.0
[ 0.861565] Creating 5 MTD partitions on "spi0.0":
[ 0.866500] 0x000000000000-0x000000020000 : "secre-firmware"
[ 0.873257] 0x000000020000-0x000000180000 : "u-boot"
[ 0.879032] 0x000000180000-0x000000190000 : "u-boot-env"
[ 0.885140] 0x000000190000-0x0000007f0000 : "Rescue system"
[ 0.891624] 0x0000007f0000-0x000000800000 : "dtb"
[ 0.897483] moxtet pZr��2ҽ�չ��MOX A (CPU) module
[ 0)������ʁmoxtet spi0.1: Fou`d MOX C (4 port switch) module
[ 0.909331] libphy: Fixed MDIO Bus: probed
0 914007] orion-mdio d003204.mdio: IRQ index 0 not found j
[ 0.919821] libphy: orion_mdio_bus: probed ��*�141, revisio [ 0.945791] libphy mV�K��낽���5
[ 0.924919] mv88e6085 d0032004.mdio-mii:02: switch 0x3400 detected: Ma.W� [ r�ʺ������mvneta d0030000.ethernet eth0: Using device tree mac address d8:58:d7:00:b5:c6
[ 0.982170] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.988839] ehci-pci: EHCI PCI platform driver
[ 0.993447] ehci-platform: EHCI generic platform driver
[ 0.998940] ehci-orion: EHCI orion driver
[ 1.003167] orion-ehci d005e000.usb: EHCI Host Controller
[ 1.008671] orion-ehci d005e000.usb: new USB bus registered, assigned bus number 1
[ 1.016552] orion-ehci d005e000.usb: irq 15, io mem 0xd005e000
[ 1.055249] orion-ehci d005e000.usb: USB 2.0 started, EHCI 1.00
[ 1.061813] hub 1-0:1.0: USB hub �ꁫ��5
[ 1.065641] hub 1-0:1.0: 1 port detected
[ 1.070528] usbcore: registered new interface driver usb-storage
[ 1.076957] i2c /dev entries driver
[ 1.081331] armada_37xx_wdt d0008300.watchdog: Initial timeout 120 sec
[ 1.088637] sdhci: Secure Digital Host Controller Interface driver
[ 1.094924] sdhci: Copyright(c) Pierre Ossman
[ 1.099568] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.105672] xenon-sdhci d00d0000.sdhci: allocated mmc-pwrseq
[ 1.111634] xenon-sdhca d00d8000.sdhci: Got CD GPIO
[ 1.118404] NET: Registered protocol fam ly 10
[ 1.123762] Segment Roting with IPv6
[ 1.127539] NET: Registered protocol family 17
[ 1.132078] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 1.145515] 8021q: 802.1Q VLAN Support v1.8
[ 1.151720] Btrfs loaded, crc32c=crc32c-generic
[ 1.158678] d0012000.serial: ttyMV0 at MMIO 0xd0012000 (irq = 0, base_baud = 1562500) is a mvebu-uart
[ 1.168146] printk: console [ttyMV0] enabled
[ 1.168146] pink: co`sole [ttyMP0] enabled
[ 1.176889] printk: bootconsole Xar3700_uart0] disabled
[ 1.176889] printk: bootconsole [ar3700_uart0] disabled
[ 1.188986] pxa2xx-i2c d0011000.i2c: missing pinmux recovery information: -548717316480 -19
[ 1.196531] rtc-ds1307 0-006f: registered as rtc0
[ 1.199633] i2c i2c-0: PXA I2C adapter
[ 1.204242] mv88e6085 d0032004.mdio-mii:02: switch 0x3400 detected: Marvell 88A6141, revision 0
[ 1.224434] libphy: mdio: probed
[ 1.249382] mvneta d0040000.ethernet eth1: Using device tree mac address d8:58:d7:00:b5:c7
[ 61.275232] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[ 61.27848����� 1-...0: (1 GPs behind) idle=b1a/1/0x4000000000000000 softirq=199/200 fqs=3000
[ 61.287526] (detected by 0, t=6002 jiffies, g=-1027, q=304)
[ 61.293348] Task dump for CPU 1:
ա+��r����ʚ���Workqueue: events deferred_probe_work_func 22 2 0x0000000a
[ 61.309207] Call trace:
[ 61.311723] __switch_to+0x1c0/��48
[ 61.315390] 0xffffffc010bf0e78
[ 241.325226] rcu: INFO: rcu_sched detected stalls n CPUs/tasks:
[ 241.328465] rcu: 1-...0: (1 GPs behind) idle=b1a/1/0x4000000000000000 softirq=199/200 fqs=12001
[ 241.337601] (detecte by 0, t=24007 jiffies, g=-1027, q=304)
[ 241.343513] Task dump for CPU 1:
[ 241.346828] kworker/1:1 R running task 0 22 2 0x0000000a
[ 241.354090] Workqueue: events deferred_probe_work_func
[ 241.359371] Call trace:
[ 241.361882] __switch_to+0x1c0/0x248
[ 241.365555] 0xffffffc010bf0e78
[ 421.375226] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[ 421.378465] rcu: 1-...0: (1 GPs behind) idle=b1a/1/0x4000000000000000 softirq=199/200 fqs=21002
[ 421.387600] (detected by 0, t=42012 jiffies, g=-027, q=308)
[ 421.393513] Task dump for CPU 1:
[ 421.396828] kworker/1:1 R running task 0 22 2 0x0000000a
[ 421.404090] Workqueue: events deferred_probe_work_func
[ 421.409372] Call trace:
[ 421.411883\ __switch_to+0x1c0/0x248
[ 421.415555] 0xffffffc010bf0e78
[ 601.425226] rcu: INFO: rcu_sched detected stalls on CPUs/tXꁮ�.�Hh���r���¢���rcu: 1-...0: (1 GPs behind) idle=b1a/1/0x4000000000000000 softirq=199/200 fqs=30003
[ 60.437601] (detected by 0, t=60017 jiffies, g=-1027, q=308)
[ 601.443512] Task dump for CPU 1:
[ 601.446828] kworker/1:1 R ꁒ�չ�����task 0 22 2 0x0000000a
[ 601.454090] Workqueue: events deferred_probe_work_func
[ 601.459371] Call trace:
[ 601.461883] __switch_to+0x1c0/0x248
[ 601.465555] 0xffffffc010b`0e78
[ 781.475226] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[ 781.478466] rcu: 1-...0: (1 GPs behind) idlYO�
�1/0x4000000000000000 softirq=199/200 fqs=39004
[ 781.487600] (detected by 0, t=78022 jiffies :�-1027, q=308)
[ 781.493512] Task dump for CPU 1:
[ �r�����ʲ���kworker/1:1 R running task 0 22 2 0x0000000a
[ 781.504089] Workqueue: events deferred_probe_work_func
[ 781.509372] Call trace:
[ 7�r������� __switch_to+0x1c0/0x248
[ 781.515555] 0xffffffc010bf0e78
```
cc: @mbehun
If you need anything, please let me know.Turris OS 6.0https://gitlab.nic.cz/turris/os/build/-/issues/167Add options to hardening with option for common passwords inclusion2021-01-25T09:58:41+01:00Karel KociAdd options to hardening with option for common passwords inclusionWe have package with common passwords that should not be used for authentication. This is nice thing to include as option in hardening package list.We have package with common passwords that should not be used for authentication. This is nice thing to include as option in hardening package list.Turris OS 5.2.0https://gitlab.nic.cz/turris/os/build/-/issues/166collectd: Consider enabling signing/encryption support2020-08-01T18:57:35+02:00Elvenlord Elrondcollectd: Consider enabling signing/encryption supportcollectd's network plugin has the option to sign or encrypt the contents for data transfer to other collectd instances.
OpenWrt added this feature [here](https://github.com/openwrt/packages/commit/4ba4d8232d4431170faffadfa80fbb0ba76d20f...collectd's network plugin has the option to sign or encrypt the contents for data transfer to other collectd instances.
OpenWrt added this feature [here](https://github.com/openwrt/packages/commit/4ba4d8232d4431170faffadfa80fbb0ba76d20f1).
It is probably only a matter of adding `PACKAGE_COLLECTD_ENCRYPTED_NETWORK=y` to `configs/common/packages`?
Yes, this will introduce a new dependency on libgcrypt. On a small embedded platform this might be of concern. But for omnia and mox, it shouldn't be a big problem. And only people installing the network plugin will actually get that extra depeendencies. Which sounds acceptable to me.Turris OS 5.1https://gitlab.nic.cz/turris/os/build/-/issues/155[device tree compiler warnings] all benign?2023-08-16T11:01:43+02:00Ghost User[device tree compiler warnings] all benign?DTC prints several warnings:
Those for the SMB look benign
> Warning (simple_bus_reg): /soc/bootrom: simple-bus unit address format error, expected "11d000000000000"
> Warning (simple_bus_reg): /soc/devbus-bootcs: simple-bus unit ad...DTC prints several warnings:
Those for the SMB look benign
> Warning (simple_bus_reg): /soc/bootrom: simple-bus unit address format error, expected "11d000000000000"
> Warning (simple_bus_reg): /soc/devbus-bootcs: simple-bus unit address format error, expected "f001000000010400"
> Warning (simple_bus_reg): /soc/devbus-cs0: simple-bus unit address format error, expected "f001000000010408"
> Warning (simple_bus_reg): /soc/devbus-cs1: simple-bus unit address format error, expected "f001000000010410"
> Warning (simple_bus_reg): /soc/devbus-cs2: simple-bus unit address format error, expected "f001000000010418"
> Warning (simple_bus_reg): /soc/devbus-cs3: simple-bus unit address format error, expected "f001000000010420"
> Warning (simple_bus_reg): /soc/internal-regs: simple-bus unit address format error, expected "f001000000000000"
> Warning (simple_bus_reg): /soc/internal-regs/thermal@e8078: simple-bus unit address format error, expected "e4078"
> Warning (simple_bus_reg): /soc/sa-sram0: simple-bus unit address format error, expected "919000000000000"
> Warning (simple_bus_reg): /soc/sa-sram1: simple-bus unit address format error, expected "915000000000000"
> Warning (simple_bus_reg): /soc/bm-bppi: simple-bus unit address format error, expected "c04000000000000"
> Warning (simple_bus_reg): /soc/spi@10600: simple-bus unit address format error, expected "f001000000010600"
> Warning (simple_bus_reg): /soc/spi@10680: simple-bus unit address format error, expected "f001000000010680"
> Warning (simple_bus_reg): /soc/pcie: simple-bus unit address format error, expected "f001000000080000"
But I was wondering about those
> Warning (avoid_unnecessary_addr_size): /soc/internal-regs/mdio@72004/switch@10: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property
> Warning (avoid_unnecessary_addr_size): /soc/spi@10600/spi-nor@0: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property
> Warning (unique_unit_address): /soc/internal-regs/timer@20300: duplicate unit-address (also used in node /soc/internal-regs/watchdog@20300)Marek BehunMarek Behun