zanzibar

Members
  • Content Count

    10
  • Joined

  1. Hello, I am using up to date Armbian - Debian Buster with Armbian Linux 4.19.69-meson64 Linux version 4.19.69-meson64 (root@builder) (gcc version 7.4.1 20181213 [linaro-7.4-2019.02 revision 56ec6f6b99cc167ff0c2f8e1a2eed33b1edc85d4] (Linaro GCC 7.4-2019.02)) #5.95 SMP PREEMPT Mon Sep 2 01:21:39 CEST 2019. I have encountered Ethernet interface lockup on medium traffic (after 30s-120s when copying big files from external usb disk by sshfs - 240Mb/s). At high/medium Ethernet traffic the issue always occurs. It is most likely caused by some kernel update because I didn't have such problem before. Similar issue: https://github.com/rockchip-linux/kernel/issues/27 [ 1584.165514] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: discard [ 1689.827553] ------------[ cut here ]------------ [ 1689.827600] NETDEV WATCHDOG: eth0 (meson8b-dwmac): transmit queue 0 timed out [ 1689.827721] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:461 dev_watchdog+0x2b4/0x2c0 [ 1689.827736] Modules linked in: uas nf_log_ipv4 nf_log_common nft_limit xt_tcpudp xt_multiport xt_LOG xt_limit xt_conntrack nft_counter nft_chain_nat_ipv4 ipt_MASQUERADE nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nf_tables nfnetlink meson_rng rng_core scpi_hwmon meson_gxbb_wdt ip_tables x_tables realtek [ 1689.827866] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.19.69-meson64 #5.95 [ 1689.827871] Hardware name: Hardkernel ODROID-C2 (DT) [ 1689.827881] pstate: 20000005 (nzCv daif -PAN -UAO) [ 1689.827892] pc : dev_watchdog+0x2b4/0x2c0 [ 1689.827901] lr : dev_watchdog+0x2b4/0x2c0 [ 1689.827906] sp : ffff000008003da0 [ 1689.827912] x29: ffff000008003da0 x28: 0000000000000005 [ 1689.827926] x27: 0000000000000020 x26: 00000000ffffffff [ 1689.827939] x25: 0000000000000140 x24: ffff800071250480 [ 1689.827952] x23: ffff80007125045c x22: ffff800070ca5940 [ 1689.827965] x21: ffff000008e77000 x20: ffff800071250000 [ 1689.827978] x19: 0000000000000000 x18: ffffffffffffffff [ 1689.827991] x17: 0000000000000000 x16: 0000000000000000 [ 1689.828004] x15: ffff000008e93000 x14: 00000000fffffff0 [ 1689.828017] x13: ffff000008f2786a x12: ffff000008e93000 [ 1689.828030] x11: 0000000000000000 x10: ffff000008f26000 [ 1689.828043] x9 : 0000000000000000 x8 : 0000000000000001 [ 1689.828055] x7 : 0000000000000000 x6 : 0000000000000123 [ 1689.828068] x5 : 0000000000000000 x4 : 0000000000000001 [ 1689.828080] x3 : 0000000000000000 x2 : ffff000008e7c358 [ 1689.828093] x1 : 2481295eb9750900 x0 : 0000000000000000 [ 1689.828105] Call trace: [ 1689.828117] dev_watchdog+0x2b4/0x2c0 [ 1689.828131] call_timer_fn+0x20/0x78 [ 1689.828143] expire_timers+0xa4/0xb0 [ 1689.828154] run_timer_softirq+0xe4/0x1a0 [ 1689.828164] __do_softirq+0x10c/0x200 [ 1689.828174] irq_exit+0xac/0xc0 [ 1689.828186] __handle_domain_irq+0x60/0xb0 [ 1689.828194] gic_handle_irq+0x58/0xa8 [ 1689.828201] el1_irq+0xb0/0x128 [ 1689.828212] arch_cpu_idle+0x10/0x18 [ 1689.828220] do_idle+0x1d4/0x298 [ 1689.828229] cpu_startup_entry+0x20/0x28 [ 1689.828243] rest_init+0xcc/0xd8 [ 1689.828256] start_kernel+0x3d4/0x400 [ 1689.828269] ---[ end trace b79bbf67547ae10f ]--- [ 1689.828334] meson8b-dwmac c9410000.ethernet eth0: Reset adapter. [ 1689.909766] RTL8211F Gigabit Ethernet stmmac-0:00: attached PHY driver [RTL8211F Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:00, irq=37) [ 1689.922902] meson8b-dwmac c9410000.ethernet eth0: No Safety Features support found [ 1689.922925] meson8b-dwmac c9410000.ethernet eth0: PTP not supported by HW [ 1693.046757] meson8b-dwmac c9410000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 1737.955616] meson8b-dwmac c9410000.ethernet eth0: Reset adapter. [ 1738.037764] RTL8211F Gigabit Ethernet stmmac-0:00: attached PHY driver [RTL8211F Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:00, irq=37) [ 1738.050715] meson8b-dwmac c9410000.ethernet eth0: No Safety Features support found [ 1738.050737] meson8b-dwmac c9410000.ethernet eth0: PTP not supported by HW [ 1741.822114] meson8b-dwmac c9410000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
  2. Hello, Recently I have discovered bug in kernel or maybe iptables with using Huawei E3372h LTE Hi-Link USB dongle (or maybe other devices which exposes HTTP interfaces over cdc_ether). Odroid enters into kernel panic and reboot. I am using ARMBIAN 5.85 stable Debian GNU/Linux 9 (stretch) 4.19.42-meson64. kernel:[ 60.801868] Internal error: Oops: 96000004 [#1] PREEMPT SMP The steps to recreate the bug: 1) disable or remove NetworkManager, use only IPv4, 2) set network interfaces in /etc/network/interfaces source /etc/network/interfaces.d/* auto lo iface lo inet loopback auto eth0 allow-hotplug eth0 iface eth0 inet static address 10.0.0.1 netmask 255.255.255.0 allow-hotplug enxXXX iface enxXXX inet dhcp enxXXX - is example name of your E3372h (virtual?) ethernet interface. 3) check settings in /etc/sysctl.conf - you need have some routing capabilites on - mine is: kernel.printk = 3 4 1 3 net.ipv4.conf.default.rp_filter=1 net.ipv4.conf.all.rp_filter=1 net.ipv4.tcp_syncookies=1 net.ipv4.ip_forward=1 net.ipv4.conf.all.accept_redirects = 0 net.ipv6.conf.all.accept_redirects = 0 net.ipv4.conf.all.secure_redirects = 0 net.ipv4.conf.all.send_redirects = 0 net.ipv4.conf.all.accept_source_route = 0 net.ipv6.conf.all.accept_source_route = 0 net.ipv6.conf.all.disable_ipv6=1 net.ipv4.icmp_echo_ignore_broadcasts=1 net.ipv4.icmp_echo_ignore_all=1 vm.swappiness=100 4) set iptables rules to forward packets between local eth0 and usb dongle ethernet: *nat :PREROUTING ACCEPT [0:0] :INPUT ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :POSTROUTING ACCEPT [0:0] -A POSTROUTING -o enxXXX -j MASQUERADE COMMIT *filter :INPUT DROP [0:0] :FORWARD DROP [0:0] :OUTPUT DROP [0:0] :interfaces - [0:0] :open - [0:0] -A INPUT -m conntrack --ctstate ESTABLISHED -j ACCEPT -A INPUT -j interfaces -A INPUT -j open -A INPUT -j DROP -A FORWARD -i enxXXX -o eth0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -A FORWARD -i eth0 -o enxXXX -p tcp -m multiport --dports 80,443,9001,9111,3690 -j ACCEPT -A FORWARD -i eth0 -o enxXXX -p icmp -m icmp --icmp-type 8 -j ACCEPT -A FORWARD -j DROP -A OUTPUT -j ACCEPT -A interfaces -i lo -j ACCEPT COMMIT 5) connect to local eth0 other computer (set static IP to eg. 10.0.0.2, netmask 255.255.255.0 and gateway 10.0.0.1), 6) from other computer you should be able to ping E3372h eth interface: 192.168.8.1, 7) open web browser (I have Firefox) - enter address: http://192.168.8.1 8) after 5-10 seconds kernel panic occurs 9) after reboot there is a green background on screen via HDMI (need to hard power off and on to start without green screen). I have attached two fotos: 1 - kernel oops messages; 2 - green screen. Has anyone had a similar problem?
  3. Hello, I using up to date Armbian Stretch with kernel 4.19.41-meson64 #5.85 SMP PREEMPT Wed May 8 12:40:37 CEST 2019 aarch64 GNU/Linux. Today about 2 minutes after system boot I have found this warning in kernel log: May 12 07:51:48 xxx kernel: WARNING: CPU: 1 PID: 0 at kernel/time/hrtimer.c:917 hrtimer_forward+0x88/0xd0 May 12 07:51:48 xxx kernel: Modules linked in: cdc_ether usbnet uas xt_tcpudp nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_conntrack iptable_filter ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_connt May 12 07:51:48 xxx kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.19.41-meson64 #5.85 May 12 07:51:48 xxx kernel: Hardware name: Hardkernel ODROID-C2 (DT) May 12 07:51:48 xxx kernel: pstate: 20000085 (nzCv daIf -PAN -UAO) May 12 07:51:48 xxx kernel: pc : hrtimer_forward+0x88/0xd0 May 12 07:51:48 xxx kernel: lr : txdone_hrtimer+0xd0/0x108 May 12 07:51:48 xxx kernel: sp : ffff00000800be20 May 12 07:51:48 xxx kernel: x29: ffff00000800be20 x28: ffff80007ff8a580 May 12 07:51:48 xxx kernel: x27: ffff00000891a6d8 x26: 0000000000000001 May 12 07:51:48 xxx kernel: x25: 0000000000000000 x24: 0000000000000001 May 12 07:51:48 xxx kernel: x23: ffff8000710c4be8 x22: 00000000000000f8 May 12 07:51:48 xxx kernel: x21: ffff8000710c4bb8 x20: ffff8000710c4ac0 May 12 07:51:48 xxx kernel: x19: 00000000000f4240 x18: 0000000000000000 May 12 07:51:48 xxx kernel: x17: 0000000000000000 x16: 0000000000000000 May 12 07:51:48 xxx kernel: x15: 000000000000029a x14: 0000000000000400 May 12 07:51:48 xxx kernel: x13: 0000000000000001 x12: 0000000000000001 May 12 07:51:48 xxx kernel: x11: 0000000000ad3d80 x10: 0000000000000040 May 12 07:51:48 xxx kernel: x9 : ffff000008e93418 x8 : ffff800071400248 May 12 07:51:48 xxx kernel: x7 : ffff800071400288 x6 : 00000000d138f0b4 May 12 07:51:48 xxx kernel: x5 : 0000000000000001 x4 : ffff8000710c4be8 May 12 07:51:48 xxx kernel: x3 : 0000002116b3f554 x2 : 00000000000f4240 May 12 07:51:48 xxx kernel: x1 : 0000002116b3f76a x0 : 0000000000000216 May 12 07:51:48 xxx kernel: Call trace: May 12 07:51:48 xxx kernel: hrtimer_forward+0x88/0xd0 May 12 07:51:48 xxx kernel: __hrtimer_run_queues+0x120/0x1b8 May 12 07:51:48 xxx kernel: hrtimer_interrupt+0xd4/0x250 May 12 07:51:48 xxx kernel: arch_timer_handler_phys+0x28/0x40 May 12 07:51:48 xxx kernel: handle_percpu_devid_irq+0x80/0x138 May 12 07:51:48 xxx kernel: generic_handle_irq+0x24/0x38 May 12 07:51:48 xxx kernel: __handle_domain_irq+0x5c/0xb0 May 12 07:51:48 xxx kernel: gic_handle_irq+0x58/0xa8 May 12 07:51:48 xxx kernel: el1_irq+0xb0/0x128 May 12 07:51:48 xxx kernel: arch_cpu_idle+0x10/0x18 May 12 07:51:48 xxx kernel: do_idle+0x1d4/0x298 May 12 07:51:48 xxx kernel: cpu_startup_entry+0x20/0x28 May 12 07:51:48 xxx kernel: secondary_start_kernel+0x194/0x1d0 May 12 07:51:48 xxx kernel: ---[ end trace dcd1d1f08e0ad792 ]--- When it happened I had one USB device connected to ODROID - E3372h LTE modem (and it was online). But system working normally after that. I've never had such warning before (with previous kernel - 4.19.20). Maybe it has something to do with the last Armbian kernel update?
  4. This happened only once. I can't reproduce this bug since then. I have seen that raspberry had similar problems(long time ago): https://www.raspberrypi.org/forums/viewtopic.php?t=49840
  5. Hello, I using up to date Armbian Stretch with kernel 4.19.41-meson64 #5.85 SMP PREEMPT Wed May 8 12:40:37 CEST 2019 aarch64 GNU/Linux. I started using TP-Link TL-WN722N V1 USB WiFi dongle recently. Unfortunately Armbian has crashed and rebooted once during I using such USB dongle. I tried to reproduce this bug once more but I can't. I have installed firmware-atheros package for this USB dongle. Should I install armbian-firmware-full package instead of firmware-atheros? It could help? Log:
  6. @TonyMac32 Thanks armbianmonitor -U http://ix.io/1DAM
  7. @TonyMac32 I have exacly this module (orange): https://www.hardkernel.com/shop/16gb-emmc-module-c2-linux Reference chart (including performance tests): https://wiki.odroid.com/accessory/emmc/reference_chart Here is my dmesg about eMMC: [ 2.759256] mmc0: new HS200 MMC card at address 0001 [ 2.760146] mmcblk0: mmc0:0001 AJTD4R 14.6 GiB [ 2.760815] mmcblk0boot0: mmc0:0001 AJTD4R partition 1 4.00 MiB [ 2.761489] mmcblk0boot1: mmc0:0001 AJTD4R partition 2 4.00 MiB [ 2.761603] mmcblk0rpmb: mmc0:0001 AJTD4R partition 3 4.00 MiB, chardev (244:0) [ 2.762360] mmcblk0: p1 Extcsd data: root@odroidc2:~# mmc extcsd read /dev/mmcblk0 ============================================= Extended CSD rev 1.8 (MMC 5.1) ============================================= Card Supported Command sets [S_CMD_SET: 0x01] HPI Features [HPI_FEATURE: 0x01]: implementation based on CMD13 Background operations support [BKOPS_SUPPORT: 0x01] Max Packet Read Cmd [MAX_PACKED_READS: 0x3f] Max Packet Write Cmd [MAX_PACKED_WRITES: 0x3f] Data TAG support [DATA_TAG_SUPPORT: 0x01] Data TAG Unit Size [TAG_UNIT_SIZE: 0x02] Tag Resources Size [TAG_RES_SIZE: 0x00] Context Management Capabilities [CONTEXT_CAPABILITIES: 0x05] Large Unit Size [LARGE_UNIT_SIZE_M1: 0x07] Extended partition attribute support [EXT_SUPPORT: 0x03] Generic CMD6 Timer [GENERIC_CMD6_TIME: 0x0a] Power off notification [POWER_OFF_LONG_TIME: 0x3c] Cache Size [CACHE_SIZE] is 65536 KiB Background operations status [BKOPS_STATUS: 0x00] 1st Initialisation Time after programmed sector [INI_TIMEOUT_AP: 0x1e] Power class for 52MHz, DDR at 3.6V [PWR_CL_DDR_52_360: 0x00] Power class for 52MHz, DDR at 1.95V [PWR_CL_DDR_52_195: 0x00] Power class for 200MHz at 3.6V [PWR_CL_200_360: 0x00] Power class for 200MHz, at 1.95V [PWR_CL_200_195: 0x00] Minimum Performance for 8bit at 52MHz in DDR mode: [MIN_PERF_DDR_W_8_52: 0x00] [MIN_PERF_DDR_R_8_52: 0x00] TRIM Multiplier [TRIM_MULT: 0x02] Secure Feature support [SEC_FEATURE_SUPPORT: 0x55] Boot Information [BOOT_INFO: 0x07] Device supports alternative boot method Device supports dual data rate during boot Device supports high speed timing during boot Boot partition size [BOOT_SIZE_MULTI: 0x20] Access size [ACC_SIZE: 0x07] High-capacity erase unit size [HC_ERASE_GRP_SIZE: 0x01] i.e. 512 KiB High-capacity erase timeout [ERASE_TIMEOUT_MULT: 0x01] Reliable write sector count [REL_WR_SEC_C: 0x01] High-capacity W protect group size [HC_WP_GRP_SIZE: 0x10] i.e. 8192 KiB Sleep current (VCC) [S_C_VCC: 0x07] Sleep current (VCCQ) [S_C_VCCQ: 0x07] Sleep/awake timeout [S_A_TIMEOUT: 0x11] Sector Count [SEC_COUNT: 0x01d1f000] Device is block-addressed Minimum Write Performance for 8bit: [MIN_PERF_W_8_52: 0x00] [MIN_PERF_R_8_52: 0x00] [MIN_PERF_W_8_26_4_52: 0x00] [MIN_PERF_R_8_26_4_52: 0x00] Minimum Write Performance for 4bit: [MIN_PERF_W_4_26: 0x00] [MIN_PERF_R_4_26: 0x00] Power classes registers: [PWR_CL_26_360: 0x00] [PWR_CL_52_360: 0x00] [PWR_CL_26_195: 0x00] [PWR_CL_52_195: 0x00] Partition switching timing [PARTITION_SWITCH_TIME: 0x02] Out-of-interrupt busy timing [OUT_OF_INTERRUPT_TIME: 0x0a] I/O Driver Strength [DRIVER_STRENGTH: 0x1f] Card Type [CARD_TYPE: 0x57] HS200 Single Data Rate eMMC @200MHz 1.8VI/O HS Dual Data Rate eMMC @52MHz 1.8V or 3VI/O HS eMMC @52MHz - at rated device voltage(s) HS eMMC @26MHz - at rated device voltage(s) CSD structure version [CSD_STRUCTURE: 0x02] Command set [CMD_SET: 0x00] Command set revision [CMD_SET_REV: 0x00] Power class [POWER_CLASS: 0x00] High-speed interface timing [HS_TIMING: 0x02] Erased memory content [ERASED_MEM_CONT: 0x00] Boot configuration bytes [PARTITION_CONFIG: 0x48] Boot Partition 1 enabled No access to boot partition Boot config protection [BOOT_CONFIG_PROT: 0x00] Boot bus Conditions [BOOT_BUS_CONDITIONS: 0x01] High-density erase group definition [ERASE_GROUP_DEF: 0x01] Boot write protection status registers [BOOT_WP_STATUS]: 0x00 Boot Area Write protection [BOOT_WP]: 0x00 Power ro locking: possible Permanent ro locking: possible ro lock status: not locked User area write protection register [USER_WP]: 0x00 FW configuration [FW_CONFIG]: 0x00 RPMB Size [RPMB_SIZE_MULT]: 0x20 Write reliability setting register [WR_REL_SET]: 0x1f user area: the device protects existing data if a power failure occurs during a write operation partition 1: the device protects existing data if a power failure occurs during a write operation partition 2: the device protects existing data if a power failure occurs during a write operation partition 3: the device protects existing data if a power failure occurs during a write operation partition 4: the device protects existing data if a power failure occurs during a write operation Write reliability parameter register [WR_REL_PARAM]: 0x14 Device supports the enhanced def. of reliable write Enable background operations handshake [BKOPS_EN]: 0x00 H/W reset function [RST_N_FUNCTION]: 0x01 HPI management [HPI_MGMT]: 0x01 Partitioning Support [PARTITIONING_SUPPORT]: 0x07 Device support partitioning feature Device can have enhanced tech. Max Enhanced Area Size [MAX_ENH_SIZE_MULT]: 0x0003a3 i.e. 7626752 KiB Partitions attribute [PARTITIONS_ATTRIBUTE]: 0x00 Partitioning Setting [PARTITION_SETTING_COMPLETED]: 0x00 Device partition setting NOT complete General Purpose Partition Size [GP_SIZE_MULT_4]: 0x000000 [GP_SIZE_MULT_3]: 0x000000 [GP_SIZE_MULT_2]: 0x000000 [GP_SIZE_MULT_1]: 0x000000 Enhanced User Data Area Size [ENH_SIZE_MULT]: 0x000000 i.e. 0 KiB Enhanced User Data Start Address [ENH_START_ADDR]: 0x000000 i.e. 0 bytes offset Bad Block Management mode [SEC_BAD_BLK_MGMNT]: 0x00 Periodic Wake-up [PERIODIC_WAKEUP]: 0x00 Program CID/CSD in DDR mode support [PROGRAM_CID_CSD_DDR_SUPPORT]: 0x01 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[127]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[126]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[125]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[124]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[123]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[122]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[121]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[120]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[119]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[118]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[117]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[116]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[115]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[114]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[113]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[112]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[111]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[110]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[109]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[108]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[107]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[106]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[105]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[104]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[103]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[102]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[101]]: 0x05 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[100]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[99]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[98]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[97]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[96]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[95]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[94]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[93]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[92]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[91]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[90]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[89]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[88]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[87]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[86]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[85]]: 0x01 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[84]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[83]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[82]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[81]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[80]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[79]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[78]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[77]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[76]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[75]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[74]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[73]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[72]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[71]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[70]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[69]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[68]]: 0xc8 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[67]]: 0xc8 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[66]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[65]]: 0x00 Vendor Specific Fields [VENDOR_SPECIFIC_FIELD[64]]: 0x0f Native sector size [NATIVE_SECTOR_SIZE]: 0x00 Sector size emulation [USE_NATIVE_SECTOR]: 0x00 Sector size [DATA_SECTOR_SIZE]: 0x00 1st initialization after disabling sector size emulation [INI_TIMEOUT_EMU]: 0x00 Class 6 commands control [CLASS_6_CTRL]: 0x00 Number of addressed group to be Released[DYNCAP_NEEDED]: 0x00 Exception events control [EXCEPTION_EVENTS_CTRL]: 0x0000 Exception events status[EXCEPTION_EVENTS_STATUS]: 0x0000 Extended Partitions Attribute [EXT_PARTITIONS_ATTRIBUTE]: 0x0000 Context configuration [CONTEXT_CONF[51]]: 0x00 Context configuration [CONTEXT_CONF[50]]: 0x00 Context configuration [CONTEXT_CONF[49]]: 0x00 Context configuration [CONTEXT_CONF[48]]: 0x00 Context configuration [CONTEXT_CONF[47]]: 0x00 Context configuration [CONTEXT_CONF[46]]: 0x00 Context configuration [CONTEXT_CONF[45]]: 0x00 Context configuration [CONTEXT_CONF[44]]: 0x00 Context configuration [CONTEXT_CONF[43]]: 0x00 Context configuration [CONTEXT_CONF[42]]: 0x00 Context configuration [CONTEXT_CONF[41]]: 0x00 Context configuration [CONTEXT_CONF[40]]: 0x00 Context configuration [CONTEXT_CONF[39]]: 0x00 Context configuration [CONTEXT_CONF[38]]: 0x00 Context configuration [CONTEXT_CONF[37]]: 0x00 Packed command status [PACKED_COMMAND_STATUS]: 0x00 Packed command failure index [PACKED_FAILURE_INDEX]: 0x00 Power Off Notification [POWER_OFF_NOTIFICATION]: 0x01 Control to turn the Cache ON/OFF [CACHE_CTRL]: 0x01 eMMC Firmware Version: Command Queue Support [CMDQ_SUPPORT]: 0x01 Command Queue Depth [CMDQ_DEPTH]: 16 Command Enabled [CMDQ_MODE_EN]: 0x00 @Strykar So You have also too small read speeds on Armbian: https://wiki.odroid.com/accessory/emmc/reference_chart ("ODROID-C2 + Black eMMC Performance Test of File I/O").
  8. Hello, I have 16GB orange eMMC v0.4 module for Odroid C2. I have installed on it Armbian Debian Stretch Next (mainline kernel). When I run iozone I got read results that is slower than eMMC Hardkernel specs. root@odroidc2:~# iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2 Iozone: Performance Test of File I/O Version $Revision: 3.429 $ Compiled for 64 bit mode. Build: linux Contributors:William Norcott, Don Capps, Isom Crawford, Kirby Collins Al Slater, Scott Rhine, Mike Wisner, Ken Goss Steve Landherr, Brad Smith, Mark Kelly, Dr. Alain CYR, Randy Dunlap, Mark Montague, Dan Million, Gavin Brebner, Jean-Marc Zucconi, Jeff Blomberg, Benny Halevy, Dave Boone, Erik Habbinga, Kris Strecker, Walter Wong, Joshua Root, Fabrice Bacchella, Zhenghua Xue, Qin Li, Darren Sawyer, Vangel Bojaxhi, Ben England, Vikentsi Lapa. Run began: Sun Feb 10 03:49:18 2019 Include fsync in write timing O_DIRECT feature enabled Auto Mode File size set to 102400 kB Record Size 4 kB Record Size 16 kB Record Size 512 kB Record Size 1024 kB Record Size 16384 kB Command line used: iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2 Output is in kBytes/sec Time Resolution = 0.000001 seconds. Processor cache size set to 1024 kBytes. Processor cache line size set to 32 bytes. File stride size set to 17 * record size. random random bkwd record stride kB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread 102400 4 32953 36184 23772 23774 23679 25934 102400 16 39075 44064 42145 42258 41967 43945 102400 512 40897 41149 80160 80028 79930 41461 102400 1024 41512 41928 82305 82300 82167 42205 102400 16384 41108 43502 86202 86228 86214 43877 On Hardkernel Ubuntu when I run iozone I have max ~50 MB/s write and ~133MB/s read, but on Armbian only max ~86 MB/s read. Why is that?
  9. I found easy workaround. Add usbcore.autosuspend=-1 as kernel parameter by /boot/armbianEnv.txt file. Eg.: extraargs=usbcore.autosuspend=-1 Of course this workaround have cons: odroid c2 will take more power. @TonyMac32 Could you please give me more details where I should look for this issue in source files? Is it dwc2 usb driver?
  10. Hello, I have installed Armbian Debian Stretch Next (mainline kernel) on my Odroid C2 and updated to newest version(apt update & apt upgrade). Everything works fine except USB ports. I have USB LTE modem which is not recognized. I have tried "lsusb -v" but with this modem not works. But when I connect USB keyboard first then "lsusb -v" and next I connect LTE modem and type "lsusb -v" then it's works. I also tried connecting USB LTE modem before Odroid C2 boot but this workaround not working. Is there any workaround which not involving connecting more than one USB device? Maybe usb kernel modules (usbcore, ehci_hcd, ...) compiled as external modules will help find workaround?