True, but what if someone lives in those specified countries? That's why I think that any advice other than "set it to the country you're in" is a bad idea. Sure, OpenWrt, this forum, and its members are not responsible for users setting a different country and possibly running into issues with the regulating body (or the military!), but in my opinion we should strive to recommend the best possible option within legal limits.
While you are right, it is not our direct legal responsibility, actions of our users do have consequences for the project as a whole. The most recent iteration of the Radio Emissions Directive (RED) of the European Union, for example, does mention users circumventing power limits or band usage requirements (DFS and such) by flashing alternative firmware. And it suggests vendors to take measures against that. The paragraph in the law (Article 3(3)(i)) making that a hard requirement has not been activated at this point, as industry was pushing for self-regulation (as usual). But we are just one inch away from law-markers banning custom firmware if they feel that the self-imposed measures taken by the industry are not sufficient.
So if the idea "flash OpenWrt to gain more TX power and annoy all radar operators around" becomes popular (supposedly among people who have little to zero knowledge of electronics or how RF works), this will most certainly have consequences such as making it extremely hard to flash OpenWrt on future devices as they will be required to use secure boot or similar mechanism preventing the user from doing that.
And btw: there is of course documentation telling users to set the country code.
12 Likes
Orange light with Linksys e8450 after update OpenWrt Snapshot
Guys, Could you please help me on it.
Thanks in advanced.!
Is it normal to see a the link state in flux as frequently as I am seeing? This RT3200 is configured as a dumb AP and port 1 is the uplink to my router.
I have these lines repeated 37 times in 5 days of uptime:
...
[47774.101531] mt7530 mdio-bus:00 lan1: Link is Down
[47774.106526] br-lan: port 1(lan1) entered disabled state
[47777.223662] mt7530 mdio-bus:00 lan1: Link is Up - 1Gbps/Full - flow control off
[47777.231036] br-lan: port 1(lan1) entered blocking state
[47777.236264] br-lan: port 1(lan1) entered forwarding state
...
Output of `dmesg` for the first 2 days (I had to limit it to 2 days in order to keep the post under the forum's 32,000 character limit).
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 5.10.93 (facade@quadruple) (aarch64-openwrt-linux-musl-gcc (OpenWrt GCC 11.2.0 r0+18538-8cdc356f8c) 11.2.0, GNU ld (GNU Binutils) 2.37) #0 SMP Thu Jan 20 20:06:44 2022
[ 0.000000] Machine model: Linksys E8450 (UBI)
[ 0.000000] earlycon: uart8250 at MMIO32 0x0000000011002000 (options '')
[ 0.000000] printk: bootconsole [uart8250] enabled
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000040000000-0x000000005fffffff]
[ 0.000000] DMA32 empty
[ 0.000000] Normal empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000040000000-0x0000000042ffffff]
[ 0.000000] node 0: [mem 0x0000000043000000-0x000000004302ffff]
[ 0.000000] node 0: [mem 0x0000000043030000-0x000000005fffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x000000005fffffff]
[ 0.000000] On node 0 totalpages: 131072
[ 0.000000] DMA zone: 2048 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 131072 pages, LIFO batch:31
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: PSCIv1.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.2
[ 0.000000] percpu: Embedded 20 pages/cpu s43800 r8192 d29928 u81920
[ 0.000000] pcpu-alloc: s43800 r8192 d29928 u81920 alloc=20*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1
[ 0.000000] Detected VIPT I-cache on CPU0
[ 0.000000] CPU features: detected: ARM erratum 845719
[ 0.000000] CPU features: kernel page table isolation disabled by kernel configuration
[ 0.000000] CPU features: detected: ARM erratum 843419
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 129024
[ 0.000000] Kernel command line: earlycon=uart8250,mmio32,0x11002000 console=ttyS0,115200n1 swiotlb=512
[ 0.000000] Dentry cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] Memory: 493672K/524288K available (7934K kernel code, 864K rwdata, 2160K rodata, 448K init, 289K bss, 30616K 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] Tracing variant of Tasks RCU enabled.
[ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[ 0.000000] GIC: GICv2 detected, but range too small and irqchip.gicv2_force_probe not set
[ 0.000000] random: get_random_bytes called from start_kernel+0x340/0x484 with crng_init=0
[ 0.000000] arch_timer: cp15 timer(s) running at 12.50MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x2e2049cda, max_idle_ns: 440795202628 ns
[ 0.000003] sched_clock: 56 bits at 12MHz, resolution 80ns, wraps every 4398046511080ns
[ 0.008485] Calibrating delay loop (skipped), value calculated using timer frequency.. 25.00 BogoMIPS (lpj=125000)
[ 0.019216] pid_max: default: 32768 minimum: 301
[ 0.024072] Mount-cache hash table entries: 1024 (order: 1, 8192 bytes, linear)
[ 0.031651] Mountpoint-cache hash table entries: 1024 (order: 1, 8192 bytes, linear)
[ 0.040650] rcu: Hierarchical SRCU implementation.
[ 0.045745] dyndbg: Ignore empty _ddebug table in a CONFIG_DYNAMIC_DEBUG_CORE build
[ 0.053976] smp: Bringing up secondary CPUs ...
[ 0.058994] Detected VIPT I-cache on CPU1
[ 0.059002] CPU features: SANITY CHECK: Unexpected variation in SYS_CNTFRQ_EL0. Boot CPU: 0x00000000bebc20, CPU1: 0x00000000000000
[ 0.059017] CPU features: Unsupported CPU feature variation detected.
[ 0.059049] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[ 0.059115] smp: Brought up 1 node, 2 CPUs
[ 0.093096] SMP: Total of 2 processors activated.
[ 0.097964] CPU features: detected: 32-bit EL0 Support
[ 0.103285] CPU features: detected: CRC32 instructions
[ 0.108704] CPU: All CPU(s) started at EL2
[ 0.112947] alternatives: patching kernel code
[ 0.120998] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.131216] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[ 0.138331] pinctrl core: initialized pinctrl subsystem
[ 0.144212] NET: Registered protocol family 16
[ 0.149530] DMA: preallocated 128 KiB GFP_KERNEL pool for atomic allocations
[ 0.156976] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[ 0.165034] DMA: preallocated 128 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[ 0.173614] thermal_sys: Registered thermal governor 'fair_share'
[ 0.173623] thermal_sys: Registered thermal governor 'bang_bang'
[ 0.179936] thermal_sys: Registered thermal governor 'step_wise'
[ 0.186199] thermal_sys: Registered thermal governor 'user_space'
[ 0.192709] ASID allocator initialised with 65536 entries
[ 0.205147] pstore: Registered ramoops as persistent store backend
[ 0.211574] ramoops: using 0x10000@0x42ff0000, ecc: 0
[ 0.248049] SCSI subsystem initialized
[ 0.252184] libata version 3.00 loaded.
[ 0.256305] usbcore: registered new interface driver usbfs
[ 0.262110] usbcore: registered new interface driver hub
[ 0.267655] usbcore: registered new device driver usb
[ 0.275004] clocksource: Switched to clocksource arch_sys_counter
[ 0.281978] NET: Registered protocol family 2
[ 0.286660] IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.294531] tcp_listen_portaddr_hash hash table entries: 256 (order: 0, 4096 bytes, linear)
[ 0.303207] TCP established hash table entries: 4096 (order: 3, 32768 bytes, linear)
[ 0.311262] TCP bind hash table entries: 4096 (order: 4, 65536 bytes, linear)
[ 0.318711] TCP: Hash tables configured (established 4096 bind 4096)
[ 0.325377] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 0.332148] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 0.339453] NET: Registered protocol family 1
[ 0.343978] PCI: CLS 0 bytes, default 64
[ 0.349149] workingset: timestamp_bits=46 max_order=17 bucket_order=0
[ 0.358517] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.364565] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 0.407631] mtk-tphy 1a0c4000.usb-phy: failed to get ref_clk(id-1)
[ 0.419520] mt-pmic-pwrap 10001000.pwrap: unexpected interrupt int=0x1
[ 0.434432] Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
[ 0.441892] printk: console [ttyS0] disabled
[ 0.446412] 11002000.serial: ttyS0 at MMIO 0x11002000 (irq = 22, base_baud = 1562500) is a 16550A
[ 0.455635] printk: console [ttyS0] enabled
[ 0.463998] printk: bootconsole [uart8250] disabled
[ 0.474402] 11004000.serial: ttyS1 at MMIO 0x11004000 (irq = 23, base_baud = 1562500) is a 16550A
[ 0.484131] 1100c000.serial: ttyS2 at MMIO 0x1100c000 (irq = 27, base_baud = 17499995) is a MediaTek BTIF
[ 0.493864] serial serial0: tty port ttyS2 registered
[ 0.499646] mtk_rng 1020f000.rng: registered RNG driver
[ 0.499661] hwrng: no data available
[ 0.508618] cacheinfo: Unable to detect cache hierarchy for CPU 0
[ 0.517840] loop: module loaded
[ 0.521872] mtk-snand 1100d000.snfi: chip is FM35Q1GA, size 128MB, page size 2048, oob size 64
[ 0.530792] 4 fixed-partitions partitions found on MTD device 1100d000.snfi
[ 0.537780] Creating 4 MTD partitions on "1100d000.snfi":
[ 0.543174] 0x000000000000-0x000000080000 : "bl2"
[ 0.548779] 0x000000080000-0x0000001c0000 : "fip"
[ 0.555120] 0x0000001c0000-0x0000002c0000 : "factory"
[ 0.561580] 0x000000300000-0x000008000000 : "ubi"
[ 0.595188] random: fast init done
[ 0.702780] libphy: Fixed MDIO Bus: probed
[ 0.730883] libphy: mdio: probed
[ 0.735418] mtk_soc_eth 1b100000.ethernet eth0: mediatek frame engine at 0xffffffc011a20000, irq 35
[ 0.746162] i2c /dev entries driver
[ 0.750906] mtk-wdt 10212000.watchdog: Watchdog enabled (timeout=31 sec, nowayout=0)
[ 0.762250] NET: Registered protocol family 10
[ 0.767539] Segment Routing with IPv6
[ 0.771240] NET: Registered protocol family 17
[ 0.775869] 8021q: 802.1Q VLAN Support v1.8
[ 0.781202] pstore: Using crash dump compression: deflate
[ 0.796185] mtk-pcie 1a143000.pcie: host bridge /pcie@1a143000 ranges:
[ 0.802724] mtk-pcie 1a143000.pcie: Parsing ranges property...
[ 0.808578] mtk-pcie 1a143000.pcie: MEM 0x0020000000..0x0027ffffff -> 0x0020000000
[ 0.843156] mtk-pcie 1a143000.pcie: PCI host bridge to bus 0000:00
[ 0.849361] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.854841] pci_bus 0000:00: root bus resource [mem 0x20000000-0x27ffffff]
[ 0.861715] pci_bus 0000:00: scanning bus
[ 0.865772] pci 0000:00:00.0: [14c3:3258] type 01 class 0x060400
[ 0.871798] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x1ffffffff 64bit pref]
[ 0.880734] pci_bus 0000:00: fixups for bus
[ 0.884923] pci 0000:00:00.0: scanning [bus 00-00] behind bridge, pass 0
[ 0.891626] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.899643] pci 0000:00:00.0: scanning [bus 00-00] behind bridge, pass 1
[ 0.906475] pci_bus 0000:01: scanning bus
[ 0.910699] pci 0000:01:00.0: [14c3:7915] type 00 class 0x000280
[ 0.916887] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x000fffff 64bit pref]
[ 0.924206] pci 0000:01:00.0: reg 0x18: [mem 0x00000000-0x00003fff 64bit pref]
[ 0.931530] pci 0000:01:00.0: reg 0x20: [mem 0x00000000-0x00000fff 64bit pref]
[ 0.939492] pci 0000:01:00.0: supports D1 D2
[ 0.943753] pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.950386] pci 0000:01:00.0: PME# disabled
[ 0.954868] pci 0000:01:00.0: 2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x1 link at 0000:00:00.0 (capable of 4.000 Gb/s with 5.0 GT/s PCIe x1 link)
[ 0.996367] pci_bus 0000:01: fixups for bus
[ 1.000554] pci_bus 0000:01: bus scan returning with max=01
[ 1.006140] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 1.012752] pci_bus 0000:00: bus scan returning with max=01
[ 1.018338] pci 0000:00:00.0: BAR 0: no space for [mem size 0x200000000 64bit pref]
[ 1.025989] pci 0000:00:00.0: BAR 0: failed to assign [mem size 0x200000000 64bit pref]
[ 1.033984] pci 0000:00:00.0: BAR 8: assigned [mem 0x20000000-0x201fffff]
[ 1.040772] pci 0000:01:00.0: BAR 0: assigned [mem 0x20000000-0x200fffff 64bit pref]
[ 1.048594] pci 0000:01:00.0: BAR 2: assigned [mem 0x20100000-0x20103fff 64bit pref]
[ 1.056419] pci 0000:01:00.0: BAR 4: assigned [mem 0x20104000-0x20104fff 64bit pref]
[ 1.064237] pci 0000:00:00.0: PCI bridge to [bus 01]
[ 1.069203] pci 0000:00:00.0: bridge window [mem 0x20000000-0x201fffff]
[ 1.076085] pcieport 0000:00:00.0: of_irq_parse_pci: failed with rc=-22
[ 1.082690] pcieport 0000:00:00.0: assign IRQ: got 0
[ 1.087663] pcieport 0000:00:00.0: enabling device (0000 -> 0002)
[ 1.093767] pcieport 0000:00:00.0: enabling bus mastering
[ 1.099710] mtk-pcie 1a145000.pcie: host bridge /pcie@1a145000 ranges:
[ 1.106258] mtk-pcie 1a145000.pcie: Parsing ranges property...
[ 1.112092] mtk-pcie 1a145000.pcie: MEM 0x0028000000..0x002fffffff -> 0x0028000000
[ 1.220296] mtk-pcie 1a145000.pcie: Port1 link down
[ 1.225312] mtk-pcie 1a145000.pcie: PCI host bridge to bus 0001:00
[ 1.231489] pci_bus 0001:00: root bus resource [bus 00-ff]
[ 1.236980] pci_bus 0001:00: root bus resource [mem 0x28000000-0x2fffffff]
[ 1.243846] pci_bus 0001:00: scanning bus
[ 1.249046] pci_bus 0001:00: fixups for bus
[ 1.253222] pci_bus 0001:00: bus scan returning with max=00
[ 1.259145] mtk_hsdma 1b007000.dma-controller: Using 3 as missing dma-requests property
[ 1.267420] mtk_hsdma 1b007000.dma-controller: MediaTek HSDMA driver registered
[ 1.310959] libphy: dsa slave smi: probed
[ 1.315918] mt7530 mdio-bus:00 lan1 (uninitialized): PHY [dsa-0.0:00] driver [Generic PHY] (irq=POLL)
[ 1.326565] mt7530 mdio-bus:00 lan2 (uninitialized): PHY [dsa-0.0:01] driver [Generic PHY] (irq=POLL)
[ 1.337196] mt7530 mdio-bus:00 lan3 (uninitialized): PHY [dsa-0.0:02] driver [Generic PHY] (irq=POLL)
[ 1.347844] mt7530 mdio-bus:00 lan4 (uninitialized): PHY [dsa-0.0:03] driver [Generic PHY] (irq=POLL)
[ 1.358660] mt7530 mdio-bus:00 wan (uninitialized): PHY [dsa-0.0:04] driver [Generic PHY] (irq=POLL)
[ 1.369569] mt7530 mdio-bus:00: configuring for fixed/2500base-x link mode
[ 1.376701] DSA: tree 0 setup
[ 1.376840] mt7530 mdio-bus:00: Link is Up - 2.5Gbps/Full - flow control rx/tx
[ 1.380459] xhci-mtk 1a0c0000.usb: xHCI Host Controller
[ 1.392164] xhci-mtk 1a0c0000.usb: new USB bus registered, assigned bus number 1
[ 1.401274] xhci-mtk 1a0c0000.usb: hcc params 0x01403198 hci version 0x96 quirks 0x0000000000210010
[ 1.410366] xhci-mtk 1a0c0000.usb: irq 31, io mem 0x1a0c0000
[ 1.416507] hub 1-0:1.0: USB hub found
[ 1.420283] hub 1-0:1.0: 2 ports detected
[ 1.424563] xhci-mtk 1a0c0000.usb: xHCI Host Controller
[ 1.429816] xhci-mtk 1a0c0000.usb: new USB bus registered, assigned bus number 2
[ 1.437223] xhci-mtk 1a0c0000.usb: Host supports USB 3.0 SuperSpeed
[ 1.443533] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[ 1.451941] hub 2-0:1.0: USB hub found
[ 1.455728] hub 2-0:1.0: 1 port detected
[ 1.460738] UBI: auto-attach mtd3
[ 1.464066] ubi0: attaching mtd3
[ 1.852103] ubi0: scanning is finished
[ 1.860200] ubi0: attached mtd3 (name "ubi", size 125 MiB)
[ 1.865044] usb 1-1: new high-speed USB device number 2 using xhci-mtk
[ 1.865705] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 1.879073] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 1.885855] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 1.892807] ubi0: good PEBs: 999, bad PEBs: 1, corrupted PEBs: 0
[ 1.898807] ubi0: user volume: 6, internal volumes: 1, max. volumes count: 128
[ 1.906023] ubi0: max/mean erase counter: 3/1, WL threshold: 4096, image sequence number: 610487392
[ 1.915061] ubi0: available PEBs: 0, total reserved PEBs: 999, PEBs reserved for bad PEB handling: 19
[ 1.924333] ubi0: background thread "ubi_bgt0d" started, PID 760
[ 1.931246] FIT: Default configuration: "config-1" (OpenWrt linksys_e8450-ubi)
[ 1.938514] FIT: kernel sub-image 0x00001000..0x004ebf71 "kernel-1" (ARM64 OpenWrt Linux-5.10.93)
[ 1.948347] FIT: flat_dt sub-image 0x004ec000..0x004f3328 "fdt-1" (ARM64 OpenWrt linksys_e8450-ubi device tree blob)
[ 1.959742] FIT: filesystem sub-image 0x004f4000..0x00ff3fff "rootfs-1" (ARM64 OpenWrt linksys_e8450-ubi rootfs)
[ 1.970519] FIT: selecting configured loadable "rootfs-1" to be root filesystem
[ 1.977824] ubiblock0_4: p1(rootfs-1)
[ 1.978126] block ubiblock0_4: created from ubi0:4(fit)
[ 1.990864] VFS: Mounted root (squashfs filesystem) readonly on device 259:1.
[ 1.998212] Freeing unused kernel memory: 448K
[ 2.025071] Run /sbin/init as init process
[ 2.029159] with arguments:
[ 2.032116] /sbin/init
[ 2.034813] with environment:
[ 2.037953] HOME=/
[ 2.040303] TERM=linux
[ 2.211780] init: Console is alive
[ 2.215390] init: - watchdog -
[ 2.535110] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[ 2.557608] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 2.564083] scsi host0: usb-storage 1-1:1.0
[ 2.568604] usbcore: registered new interface driver usb-storage
[ 2.575579] usbcore: registered new interface driver uas
[ 2.581128] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[ 2.591896] init: - preinit -
[ 2.868620] mtk_soc_eth 1b100000.ethernet eth0: configuring for fixed/2500base-x link mode
[ 2.877171] mtk_soc_eth 1b100000.ethernet eth0: Link is Up - 2.5Gbps/Full - flow control rx/tx
[ 2.886204] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 2.893138] mt7530 mdio-bus:00 lan1: configuring for phy/gmii link mode
[ 2.900335] 8021q: adding VLAN 0 to HW filter on device lan1
[ 2.914175] random: procd: uninitialized urandom read (4 bytes read)
[ 3.645618] scsi 0:0:0:0: Direct-Access Ut165 USB Flash Disk 0.00 PQ: 0 ANSI: 2
[ 3.655251] sd 0:0:0:0: [sda] 3947016 512-byte logical blocks: (2.02 GB/1.88 GiB)
[ 3.662888] sd 0:0:0:0: [sda] Write Protect is off
[ 3.667692] sd 0:0:0:0: [sda] Mode Sense: 00 00 00 00
[ 3.672881] sd 0:0:0:0: [sda] Asking for cache data failed
[ 3.678369] sd 0:0:0:0: [sda] Assuming drive cache: write through
[ 3.821298] sda: sda1
[ 3.825265] sd 0:0:0:0: [sda] Attached SCSI removable disk
[ 5.018379] mt7530 mdio-bus:00 lan1: Link is Up - 1Gbps/Full - flow control rx/tx
[ 5.025899] IPv6: ADDRCONF(NETDEV_CHANGE): lan1: link becomes ready
[ 6.979726] mount_root: loading kmods from internal overlay
[ 6.995206] kmodloader: loading kernel modules from //etc/modules-boot.d/*
[ 7.002814] kmodloader: done loading kernel modules from //etc/modules-boot.d/*
[ 7.164533] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 7.175600] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 7.186136] Buffer I/O error on dev mtdblock2, logical block 32, async page read
[ 7.352667] UBIFS (ubi0:5): Mounting in unauthenticated mode
[ 7.358482] UBIFS (ubi0:5): background thread "ubifs_bgt0_5" started, PID 865
[ 7.374928] UBIFS (ubi0:5): recovery needed
[ 7.446519] UBIFS (ubi0:5): recovery completed
[ 7.451039] UBIFS (ubi0:5): UBIFS: mounted UBI device 0, volume 5, name "rootfs_data"
[ 7.458876] UBIFS (ubi0:5): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 7.468787] UBIFS (ubi0:5): FS size: 85835776 bytes (81 MiB, 676 LEBs), journal size 4317184 bytes (4 MiB, 34 LEBs)
[ 7.479216] UBIFS (ubi0:5): reserved for root: 4054235 bytes (3959 KiB)
[ 7.485832] UBIFS (ubi0:5): media format: w5/r0 (latest is w5/r0), UUID 16212358-5126-4A13-AAE2-413789C8BAE7, small LPT model
[ 7.498145] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
[ 7.507905] block: extroot: not configured
[ 7.512129] UBIFS (ubi0:5): un-mount UBI device 0
[ 7.516884] UBIFS (ubi0:5): background thread "ubifs_bgt0_5" stops
[ 7.525550] UBIFS (ubi0:5): Mounting in unauthenticated mode
[ 7.531343] UBIFS (ubi0:5): background thread "ubifs_bgt0_5" started, PID 868
[ 7.568787] UBIFS (ubi0:5): UBIFS: mounted UBI device 0, volume 5, name "rootfs_data"
[ 7.576648] UBIFS (ubi0:5): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 7.586558] UBIFS (ubi0:5): FS size: 85835776 bytes (81 MiB, 676 LEBs), journal size 4317184 bytes (4 MiB, 34 LEBs)
[ 7.596985] UBIFS (ubi0:5): reserved for root: 4054235 bytes (3959 KiB)
[ 7.603592] UBIFS (ubi0:5): media format: w5/r0 (latest is w5/r0), UUID 16212358-5126-4A13-AAE2-413789C8BAE7, small LPT model
[ 7.695968] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 7.707001] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 7.717526] Buffer I/O error on dev mtdblock2, logical block 32, async page read
[ 7.842215] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
[ 7.851642] block: extroot: not configured
[ 7.857274] mount_root: switching to ubifs overlay
[ 7.865218] overlayfs: "xino" feature enabled using 2 upper inode bits.
[ 7.874743] urandom-seed: Seeding with /etc/urandom.seed
[ 7.920529] mt7530 mdio-bus:00 lan1: Link is Down
[ 7.929778] procd: - early -
[ 7.932739] procd: - watchdog -
[ 8.088350] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 8.099382] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 8.109908] Buffer I/O error on dev mtdblock2, logical block 32, async page read
[ 8.321885] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 8.332938] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 8.343462] Buffer I/O error on dev mtdblock2, logical block 32, async page read
[ 8.405687] random: crng init done
[ 8.478280] procd: - watchdog -
[ 8.482619] procd: - ubus -
[ 8.541274] procd: - init -
[ 8.598743] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 8.609860] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 8.620420] Buffer I/O error on dev mtdblock2, logical block 32, async page read
[ 8.876086] urngd: v1.0.2 started.
[ 8.876104] Buffer I/O error on dev mtdblock2, logical block 32, async page read
[ 8.952916] kmodloader: loading kernel modules from /etc/modules.d/*
[ 8.990065] GACT probability on
[ 8.994451] Mirror/redirect action on
[ 9.004428] u32 classifier
[ 9.007162] input device check on
[ 9.010822] Actions configured
[ 9.020766] Loading modules backported from Linux version v5.15.8-0-g43e577d7a2cb
[ 9.028298] Backport generated by backports.git v5.15.8-1-0-g83f664bb
[ 9.047752] usbcore: registered new interface driver ums-alauda
[ 9.054760] usbcore: registered new interface driver ums-cypress
[ 9.061876] usbcore: registered new interface driver ums-datafab
[ 9.069134] usbcore: registered new interface driver ums-freecom
[ 9.076246] usbcore: registered new interface driver ums-isd200
[ 9.083165] usbcore: registered new interface driver ums-jumpshot
[ 9.090235] usbcore: registered new interface driver ums-karma
[ 9.097173] usbcore: registered new interface driver ums-sddr09
[ 9.104086] usbcore: registered new interface driver ums-sddr55
[ 9.111069] usbcore: registered new interface driver ums-usbat
[ 9.129578] xt_time: kernel timezone is -0000
[ 9.199138] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 9.210560] mt7915e 0000:01:00.0: assign IRQ: got 143
[ 9.215748] pci 0000:00:00.0: enabling bus mastering
[ 9.220730] mt7915e 0000:01:00.0: enabling device (0000 -> 0002)
[ 9.226830] mt7915e 0000:01:00.0: enabling bus mastering
[ 9.260124] mt7622-wmac 18000000.wmac: HW/SW Version: 0x8a108a10, Build Time: 20190801210006a
[ 9.260124]
[ 9.294271] mt7915e 0000:01:00.0: HW/SW Version: 0x8a108a10, Build Time: 20201105222230a
[ 9.294271]
[ 9.349181] mt7622-wmac 18000000.wmac: N9 Firmware Version: 2.0, Build Time: 20200131180931
[ 9.406414] Buffer I/O error on dev mtdblock2, logical block 32, async page read
[ 9.430205] mt7915e 0000:01:00.0: WM Firmware Version: ____000000, Build Time: 20201105222304
[ 9.454563] mt7915e 0000:01:00.0: WA Firmware Version: DEV_000000, Build Time: 20201105222323
[ 9.579361] PPP generic driver version 2.4.2
[ 9.584866] NET: Registered protocol family 24
[ 9.602086] kmodloader: done loading kernel modules from /etc/modules.d/*
[ 9.679809] Buffer I/O error on dev mtdblock2, logical block 32, async page read
[ 9.991234] Buffer I/O error on dev mtdblock2, logical block 32, async page read
[ 10.052963] Buffer I/O error on dev mtdblock2, logical block 32, async page read
[ 10.196632] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts:
[ 12.177247] print_req_error: 20 callbacks suppressed
[ 12.177256] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 12.194158] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 12.204809] buffer_io_error: 5 callbacks suppressed
[ 12.204846] Buffer I/O error on dev mtdblock2, logical block 32, async page read
[ 12.354012] mtk_soc_eth 1b100000.ethernet eth0: Link is Down
[ 12.398880] mtk_soc_eth 1b100000.ethernet eth0: configuring for fixed/2500base-x link mode
[ 12.407331] mtk_soc_eth 1b100000.ethernet eth0: Link is Up - 2.5Gbps/Full - flow control rx/tx
[ 12.411655] mt7530 mdio-bus:00 lan1: configuring for phy/gmii link mode
[ 12.425141] 8021q: adding VLAN 0 to HW filter on device lan1
[ 12.441239] br-lan: port 1(lan1) entered blocking state
[ 12.446520] br-lan: port 1(lan1) entered disabled state
[ 12.455676] device lan1 entered promiscuous mode
[ 12.460303] device eth0 entered promiscuous mode
[ 12.499183] mt7530 mdio-bus:00 lan2: configuring for phy/gmii link mode
[ 12.513232] 8021q: adding VLAN 0 to HW filter on device lan2
[ 12.524672] mt7530 mdio-bus:00 lan2: Link is Up - 1Gbps/Full - flow control rx/tx
[ 12.531218] br-lan: port 2(lan2) entered blocking state
[ 12.537483] br-lan: port 2(lan2) entered disabled state
[ 12.544706] device lan2 entered promiscuous mode
[ 12.580614] mt7530 mdio-bus:00 lan3: configuring for phy/gmii link mode
[ 12.588039] 8021q: adding VLAN 0 to HW filter on device lan3
[ 12.601338] br-lan: port 3(lan3) entered blocking state
[ 12.606647] br-lan: port 3(lan3) entered disabled state
[ 12.613399] device lan3 entered promiscuous mode
[ 12.626074] mt7530 mdio-bus:00 lan4: configuring for phy/gmii link mode
[ 12.633329] 8021q: adding VLAN 0 to HW filter on device lan4
[ 12.637662] mt7530 mdio-bus:00 lan4: Link is Up - 1Gbps/Full - flow control rx/tx
[ 12.641435] br-lan: port 4(lan4) entered blocking state
[ 12.651712] br-lan: port 4(lan4) entered disabled state
[ 12.658210] device lan4 entered promiscuous mode
[ 12.674197] br-lan: port 2(lan2) entered blocking state
[ 12.679472] br-lan: port 2(lan2) entered forwarding state
[ 12.685088] br-lan: port 4(lan4) entered blocking state
[ 12.690319] br-lan: port 4(lan4) entered forwarding state
[ 12.702898] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 12.730242] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 12.740843] Buffer I/O error on dev mtdblock2, logical block 32, async page read
[ 13.147663] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 13.162076] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 13.172751] Buffer I/O error on dev mtdblock2, logical block 32, async page read
[ 13.425438] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 13.445804] blk_update_request: I/O error, dev mtdblock2, sector 256 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 13.456396] Buffer I/O error on dev mtdblock2, logical block 32, async page read
[ 15.294899] br-lan: port 5(wlan1) entered blocking state
[ 15.300306] br-lan: port 5(wlan1) entered disabled state
[ 15.305868] device wlan1 entered promiscuous mode
[ 15.310685] br-lan: port 5(wlan1) entered blocking state
[ 15.316059] br-lan: port 5(wlan1) entered forwarding state
[ 15.322030] br-lan: port 5(wlan1) entered disabled state
[ 15.568401] mt7530 mdio-bus:00 lan1: Link is Up - 1Gbps/Full - flow control rx/tx
[ 15.575956] br-lan: port 1(lan1) entered blocking state
[ 15.581176] br-lan: port 1(lan1) entered forwarding state
[ 16.050744] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[ 16.057258] br-lan: port 5(wlan1) entered blocking state
[ 16.062574] br-lan: port 5(wlan1) entered forwarding state
[ 16.187412] br-lan: port 6(wlan1-1) entered blocking state
[ 16.192930] br-lan: port 6(wlan1-1) entered disabled state
[ 16.198776] device wlan1-1 entered promiscuous mode
[ 16.206509] br-lan: port 6(wlan1-1) entered blocking state
[ 16.212024] br-lan: port 6(wlan1-1) entered forwarding state
[ 16.238046] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1-1: link becomes ready
[47774.101531] mt7530 mdio-bus:00 lan1: Link is Down
[47774.106526] br-lan: port 1(lan1) entered disabled state
[47777.223662] mt7530 mdio-bus:00 lan1: Link is Up - 1Gbps/Full - flow control off
[47777.231036] br-lan: port 1(lan1) entered blocking state
[47777.236264] br-lan: port 1(lan1) entered forwarding state
[47784.501510] br-lan: port 1(lan1) entered disabled state
[47784.507143] mt7530 mdio-bus:00 lan1: Link is Down
[47787.623588] mt7530 mdio-bus:00 lan1: Link is Up - 1Gbps/Full - flow control rx/tx
[47787.631124] br-lan: port 1(lan1) entered blocking state
[47787.636349] br-lan: port 1(lan1) entered forwarding state
[132172.563898] mt7530 mdio-bus:00 lan1: Link is Down
[132172.569100] br-lan: port 1(lan1) entered disabled state
[132175.685880] mt7530 mdio-bus:00 lan1: Link is Up - 1Gbps/Full - flow control off
[132175.693335] br-lan: port 1(lan1) entered blocking state
[132175.698644] br-lan: port 1(lan1) entered forwarding state
[132181.923688] mt7530 mdio-bus:00 lan1: Link is Down
[132181.928657] br-lan: port 1(lan1) entered disabled state
[132185.045974] mt7530 mdio-bus:00 lan1: Link is Up - 1Gbps/Full - flow control rx/tx
[132185.053733] br-lan: port 1(lan1) entered blocking state
[132185.059068] br-lan: port 1(lan1) entered forwarding state
[153060.799262] br-lan: port 1(lan1) entered disabled state
[153060.804932] mt7530 mdio-bus:00 lan1: Link is Down
[153093.041171] mt7530 mdio-bus:00 lan1: Link is Up - 1Gbps/Full - flow control rx/tx
[153093.048796] br-lan: port 1(lan1) entered blocking state
[153093.054110] br-lan: port 1(lan1) entered forwarding state
[169083.954337] br-lan: port 1(lan1) entered disabled state
[169083.960386] mt7530 mdio-bus:00 lan1: Link is Down
[169124.516153] mt7530 mdio-bus:00 lan1: Link is Up - 1Gbps/Full - flow control rx/tx
[169124.523783] br-lan: port 1(lan1) entered blocking state
[169124.529100] br-lan: port 1(lan1) entered forwarding state
[169126.674045] br-lan: port 2(lan2) entered disabled state
[169126.680237] mt7530 mdio-bus:00 lan2: Link is Down
[169129.796239] mt7530 mdio-bus:00 lan2: Link is Up - 1Gbps/Full - flow control rx/tx
[169129.803899] br-lan: port 2(lan2) entered blocking state
[169129.809212] br-lan: port 2(lan2) entered forwarding state
[170388.185112] mt7530 mdio-bus:00 lan2: Link is Down
[170388.190294] br-lan: port 2(lan2) entered disabled state
[170419.387004] mt7530 mdio-bus:00 lan2: Link is Up - 1Gbps/Full - flow control rx/tx
[170419.394655] br-lan: port 2(lan2) entered blocking state
[170419.399968] br-lan: port 2(lan2) entered forwarding state
I'm not seeing this on any of my devices. All links stay up reliably for weeks. Maybe the link partner has some troubles? Or the wiring is not really perfect?
1 Like
Thanks for the reply. I found some similar reports on other devices (example) where some found the patch cable to blame. I just switched it out for another one and will see.
1 Like
Is there any concensus yet as to whether the hardware offloading thing is a universal problem?
It seems universal and old, also applies to other mt7622 platforms, as discussed here: https://forum.banana-pi.org/t/banana-pi-bpi-r64-mainline-openwrt-image/11415/129. A bug was filled (https://bugs.openwrt.org/index.php?do=details&task_id=3561) but it seems nobody worked to test, confirm or trace the problem...
Has anyone successfully flashed and booted into a recent nightly snapshot (ie last night's)? I just built from master with two modifications
- Applying PR#4975 bumping the kernel to 5.10.94
- Reverting 08d9f6e302 to keep fw4 be getting defaulted
I flashed the resulting image but neither the network nor the wifi radio came up. I had to recover reverting to a build from a week or so ago. Since I changed too many variables, I don't know if the kernel bump broke it or if something in master since the last time I build an image broke it. Or perhaps it was my reverting the firewall bump.
I guess the next experiment is to build master without reverting the firewall change or without applying the kernel bump to see if that boots/works. I am reluctant to do it not wanting to potentially brick the RT3200.
1 Like
You will not manage to brick it, don't worry. Holding reset button on power-on to boot into recovery firmware will always work (unless you overwrite the bootloader, and for that you'd need to insmod kmod-mtd-rw i_want_a_brick=1...)
2 Likes
that's unfortunate. I wonder why the bug was marked as Very Low priority, seems like a pretty big issue.
Is there any way I can help debug this issue?
The bug FS#3561 is also related to MTK hardware offloading, but it's a different issue which has already been resolved, we never saw that on Linux 5.10. Doesn't mean that it's unrelated, but it's definitely a different place in the code where things go wrong.
<1>[1375173.739141] [dead000000000110] address between user and kernel address ranges
...
<7>[1375173.979700] Call trace:
<7>[1375173.982316] nf_flow_offload_ip_hook+0x778/0x1340 [nf_flow_table]
<7>[1375173.988575] nf_flow_table_offload_setup+0x334/0x660 [nf_flow_table]
...
vs.
[ 1148.631719] Unable to handle kernel paging request at virtual address ffffff883e35ffa0
...
[ 1149.188834] Call trace:
[ 1149.191272] mtk_flow_offload_add+0xd0/0x180
[ 1149.195531] mtk_flow_offload+0x4c/0x60
...
The old bug on 5.4 was also very easy to trigger, it happened quite immediately once there was traffic being routed.
2 Likes
@daniel - I posted my findings in the 5.10.94 PR but probably ok for me to echo them in this thread: I believe that upstream kernel 5.10.94 breaks networking (both wired and wifi) on this device. I say that compiling the latest commit from master + that PR. The RT3200 boots, but networking is dead. The only course of action is entering recovery mode and reflashing/restoring settings.
1 Like
hey, graysky2, fancy seeing you here. I use your rpi4 archlinuxarm port 
@daniel on the subject of connecting to the router (for example if the network is down), the info on the wiki is pretty sparse, is the serial connection 5V? I can help to try to debug the kernel oops issue with flow offloading, I have an jtag arm debugger and a nice usb ft232rl dongle. All I need is some pointers (specifically how to trigger it reliably)
I found some great pics of the PCB here https://min.news/zh-cn/digital/0537bfbf3db8d55a4367d46a7a38dc4e.html (I haven't opened mine yet). It looks like the jtag interface is exposed as just pads, is there enough vertical space to solder a connector onto that?
Serial signal level is 3.3V.
If you have the device at hand, please go ahead and build from https://github.com/openwrt/openwrt/pull/4975 and let us know what you see on the serial console, as for some reason neither wired nor wireless network comes up according to @darksky .
JTAG pads are 1.27mm pitch, so it's a bit challenging to solder, but manageable (also because you only need to few of those pins)
To be prepared for eventual bricks which require JTAG to be brought back to live I've bought myself one of those:
1 Like
netfilter folks got back to me and it looks like this could be caused by a race-condition in our (rather hacky) integration of flow-offloading into old-school iptables. Hence, using the more recent nftables firewall mechanisms in the kernel would avoid using that hack and thus most likely also work-around that bug.
As OpenWrt has anyway switched to use the newly written, nftables-based firewall4 for the upcoming release, I've also generated new installer and sysupgrade images which are now based on that.
I didn't yet have a chance to test this myself yet, hence marked it as a pre-release.
4 Likes
Dear Guys, Can anybody help me to restore stock firmware, i am on Linksys - E8450 and don't have any backup files to achieve this. Please do the needful.
Thanks
interesting, so maybe this bug is a thing of the past then. I haven't worked with the openwrt build system before, have you got any pointers how to get specifically the e8450 build set up as fast as possible, eager to try the kernel bump PR and get at the serial port as I've just opened my belkin (it's nice that it's reachable without detaching the pcb from the plastic. it should also be possible to solder an angled connector to get the jtag exposed on the side of the board, it looks like there is just enough vertical space in the case; will be tricky tho)
1 Like
There are some backup archives from other routers in this topic: https://github.com/dangowrt/linksys-e8450-openwrt-installer/issues/14, for example "0.6.0 boot_backup MTD". But do NOT restore the factory partition from other router, normally your router is still having the original in place. You will also need to edit the "foreign" mtd3 partition with your router specific information before restoring (this is used by the factory firmware). The restore procedure may depend on which bootchain you have currently running, better see the "Restoring the vendor/official firmware" chapter from here: https://github.com/dangowrt/linksys-e8450-openwrt-installer
Will be nice to share your results. I recently tried some home-cooked builds using firewall4 but I wasn't able to make it work properly. For example, miniupnpd did not work properly - even if upnp tables and chains are created, the invoking client UPnP/NAT test fails. With another build the whole firewall/NAT did not work at all. So I am waiting to see some good results before trying again the migration to firewall4. Thanks.
Just started the build. Had to set up the LLVM toolchain path manually in the menuconfig for the eBPF thing. Fingers crossed