OpenWrt SNAPSHOT r22302 on MR8300

You mean the bug REPORT :wink:
I even read that you quoted me.
Tomorrow, I'll install a 22.03 snapshot and log the boot, to compare with the master snapshot one.

try both:

https://downloads.openwrt.org/releases/22.03-SNAPSHOT/targets/ipq40xx/generic/openwrt-22.03-snapshot-r20119-50d707e344-ipq40xx-generic-linksys_mr8300-squashfs-factory.bin

and EKO1 build with LuCi

https://dl.eko.one.pl/luci/openwrt-22.03/ipq40xx/generic/luci-22.03-snapshot-r20090-c2331038b2-ipq40xx-generic-linksys_mr8300-squashfs-factory.bin

1 Like

Hi.
I have just installed both 22.03 snapshots and ran into the very same issue than with master snapshots. I have published the serial logs on the Github thread.

I am having the same problem on EA8300 and MR8300, I see the bug report has no acknowledgment yet.

Are the developers looking at this bug?

1 Like

I would like to know if other devices have the same kind of issue (same/other target), or if it's only related to EA/MR8300. I assume that other users would have post a question in the forum.

I trust them on this, even if it takes a long time.

Hi.
22.03.4 file was released a few minutes ago. It also fails to boot with the very same error.
Here is the boot log.

EDIT : I installed official factory image using Linksys OEM.


Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset),  D - Delta,  S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.1.1-00108
S - IMAGE_VARIANT_STRING=DAACANAZA
S - OEM_IMAGE_VERSION_STRING=CRM
S - Boot Config, 0x00000025
S - Reset status Config, 0x00000010
S - Core 0 Frequency, 0 MHz
B -       262 - PBL, Start
B -      1341 - bootable_media_detect_entry, Start
B -      2618 - bootable_media_detect_success, Start
B -      2633 - elf_loader_entry, Start
B -      4047 - auth_hash_seg_entry, Start
B -      6215 - auth_hash_seg_exit, Start
B -     71409 - elf_segs_hash_verify_entry, Start
B -    194195 - PBL, End
B -    194219 - SBL1, Start
B -    286403 - pm_device_init, Start
D -         7 - pm_device_init, Delta
B -    287901 - boot_flash_init, Start
D -     87530 - boot_flash_init, Delta
B -    379742 - boot_config_data_table_init, Start
D -     14026 - boot_config_data_table_init, Delta - (419 Bytes)
B -    396462 - clock_init, Start
D -      7561 - clock_init, Delta
B -    407463 - CDT version:2,Platform ID:8,Major ID:1,Minor ID:0,Subtype:6
B -    410877 - sbl1_ddr_set_params, Start
B -    415971 - cpr_init, Start
D -         2 - cpr_init, Delta
B -    420354 - Pre_DDR_clock_init, Start
D -         4 - Pre_DDR_clock_init, Delta
D -     13172 - sbl1_ddr_set_params, Delta
B -    433660 - pm_driver_init, Start
D -         2 - pm_driver_init, Delta
B -    504354 - sbl1_wait_for_ddr_training, Start
D -        28 - sbl1_wait_for_ddr_training, Delta
B -    520448 - Image Load, Start
D -    144007 - QSEE Image Loaded, Delta - (269176 Bytes)
B -    664881 - Image Load, Start
D -      2123 - SEC Image Loaded, Delta - (2048 Bytes)
B -    675063 - Image Load, Start
D -    187335 - APPSBL Image Loaded, Delta - (444135 Bytes)
B -    862796 - QSEE Execution, Start
D -        56 - QSEE Execution, Delta
B -    869023 - SBL1, End
D -    676806 - SBL1, Delta
S - Flash Throughput, 2085 KB/s  (715778 Bytes,  343206 us)
S - DDR Frequency, 672 MHz


U-Boot 2012.07 [Chaos Calmer 15.05.1,r35193] (Sep 27 2018 - 09:37:31)

CBT U-Boot ver: 1.3.3

smem ram ptable found: ver: 1 len: 3
DRAM:  512 MiB
machid : 0x8010006
NAND:  ID = 9590dac2
Vendor = c2
Device = da
ONFI device found
SF NAND unsupported id:ff:ff:ff:ffSF: Unsupported manufacturer ff
ipq_spi: SPI Flash not found (bus/cs/speed/mode) = (0/0/48000000/0)
256 MiB
MMC:   qca_mmc: 0
PCI0 Link Intialized
In:    serial
Out:   serial
Err:   serial
machid: 8010006
flash_type: 2
Net:   MAC0 addr:0:3:7f:ba:db:ad
PHY ID1: 0x4d
PHY ID2: 0xd0b1
ipq40xx_ess_sw_init done
eth0

Updating boot_count ... done

Hit any key to stop autoboot:  0

Memory test start,  banksize=0x2000000, data size=0x8000, test count per bank=64
Memory test end, lapsed time = 3 seconds

The test result is success


NAND read: device 0 offset 0x780000, size 0x500000
 5242880 bytes read: OK
## Booting kernel from FIT Image at 84000000 ...
   Using 'config@1' configuration
   Trying 'kernel-1' kernel subimage
     Description:  ARM OpenWrt Linux-5.10.176
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x840000e4
     Data Size:    2833136 Bytes = 2.7 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x80208000
     Entry Point:  0x80208000
     Hash algo:    crc32
     Hash value:   71ec1298
     Hash algo:    sha1
     Hash value:   491a3927d1f20acec9885f76c219fbc2e8ef15ee
   Verifying Hash Integrity ... crc32+ sha1+ OK
## Flattened Device Tree from FIT Image at 84000000
   Using 'config@1' configuration
   Trying 'fdt-1' FDT blob subimage
     Description:  ARM OpenWrt linksys_mr8300 device tree blob
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x842b3d0c
     Data Size:    17795 Bytes = 17.4 KiB
     Architecture: ARM
     Hash algo:    crc32
     Hash value:   4104046e
     Hash algo:    sha1
     Hash value:   0b9d034fe92159a6280be86aefd57a8514a5522a
   Verifying Hash Integrity ... crc32+ sha1+ OK
   Booting using the fdt blob at 0x842b3d0c
   Loading Kernel Image ... OK
OK
   Loading Device Tree to 871e8000, end 871ef582 ... OK
Device nand2 not found!
eth0 MAC Address from ART is not valid
eth1 MAC Address from ART is not valid
Using machid 0x8010006 from environment

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 5.10.176 (builder@buildhost) (arm-openwrt-linux-muslgnueabi-gcc (OpenWrt GCC 11.2.0 r20123-38ccc47687) 11.2.0, GNU ld (GNU Binutils) 2.37) #0 SMP Sun Apr 9 12:27:46 2023
[    0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Linksys MR8300 (Dallas)
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000080000000-0x000000009fffffff]
[    0.000000]   HighMem  empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000080000000-0x0000000087dfffff]
[    0.000000]   node   0: [mem 0x0000000087e00000-0x0000000087ffffff]
[    0.000000]   node   0: [mem 0x0000000088000000-0x000000009fffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x000000009fffffff]
[    0.000000] percpu: Embedded 15 pages/cpu s31116 r8192 d22132 u61440
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 129920
[    0.000000] Kernel command line: init=/sbin/init rootfstype=ubifs ubi.mtd=11,2048 root=ubi0:ubifs rootwait rw root=/dev/ubiblock0_0 rootfstype=squashfs ro
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 506816K/524288K available (6479K kernel code, 608K rwdata, 956K rodata, 1024K init, 246K bss, 17472K reserved, 0K cma-reserved, 0K highmem)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, 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: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] arch_timer: cp15 timer(s) running at 48.00MHz (virt).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xb11fd3bfb, max_idle_ns: 440795203732 ns
[    0.000009] sched_clock: 56 bits at 48MHz, resolution 20ns, wraps every 4398046511096ns
[    0.000025] Switching to timer-based delay loop, resolution 20ns
[    0.000334] Calibrating delay loop (skipped), value calculated using timer frequency.. 96.00 BogoMIPS (lpj=480000)
[    0.000361] pid_max: default: 32768 minimum: 301
[    0.000546] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.000568] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.001578] CPU: Testing write buffer coherency: ok
[    0.001960] qcom_scm: convention: smc legacy
[    0.002948] Setting up static identity map for 0x80300000 - 0x8030003c
[    0.003117] rcu: Hierarchical SRCU implementation.
[    0.003401] dyndbg: Ignore empty _ddebug table in a CONFIG_DYNAMIC_DEBUG_CORE build
[    0.003779] smp: Bringing up secondary CPUs ...
[    0.007320] smp: Brought up 1 node, 4 CPUs
[    0.007346] SMP: Total of 4 processors activated (384.00 BogoMIPS).
[    0.007357] CPU: All CPU(s) started in SVC mode.
[    0.012962] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5
[    0.013142] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.013169] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.013433] pinctrl core: initialized pinctrl subsystem
[    0.015265] NET: Registered protocol family 16
[    0.015689] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.016895] thermal_sys: Registered thermal governor 'step_wise'
[    0.017327] cpuidle: using governor ladder
[    0.017386] cpuidle: using governor menu
[    0.044684] cryptd: max_cpu_qlen set to 1000
[    0.049569] usbcore: registered new interface driver usbfs
[    0.049644] usbcore: registered new interface driver hub
[    0.049716] usbcore: registered new device driver usb
[    0.049771] pps_core: LinuxPPS API ver. 1 registered
[    0.049785] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.049814] PTP clock support registered
[    0.051890] clocksource: Switched to clocksource arch_sys_counter
[    0.052896] NET: Registered protocol family 2
[    0.053156] IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.054303] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear)
[    0.054372] TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
[    0.054436] TCP bind hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.054528] TCP: Hash tables configured (established 4096 bind 4096)
[    0.054658] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[    0.054700] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[    0.054983] NET: Registered protocol family 1
[    0.055054] PCI: CLS 0 bytes, default 64
[    0.057429] workingset: timestamp_bits=14 max_order=17 bucket_order=3
[    0.062421] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.062449] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.194945] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 248)
[    0.197252] qcom-pcie 40000000.pci: host bridge /soc/pci@40000000 ranges:
[    0.197313] qcom-pcie 40000000.pci:       IO 0x0040200000..0x00402fffff -> 0x0040200000
[    0.197347] qcom-pcie 40000000.pci:      MEM 0x0040300000..0x0040ffffff -> 0x0040300000
[    0.473455] qcom-pcie 40000000.pci: Link up
[    0.473617] qcom-pcie 40000000.pci: PCI host bridge to bus 0000:00
[    0.473642] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.473664] pci_bus 0000:00: root bus resource [io  0x0000-0xfffff] (bus address [0x40200000-0x402fffff])
[    0.473680] pci_bus 0000:00: root bus resource [mem 0x40300000-0x40ffffff]
[    0.473731] pci 0000:00:00.0: [17cb:1001] type 01 class 0x060400
[    0.473763] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x00000fff]
[    0.473834] pci 0000:00:00.0: PME# supported from D0 D3hot
[    0.475358] PCI: bus0: Fast back to back transfers disabled
[    0.475682] pci 0000:01:00.0: [168c:0056] type 00 class 0x028000
[    0.475859] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x001fffff 64bit]
[    0.476690] pci 0000:01:00.0: PME# supported from D0 D3hot
[    0.478433] PCI: bus1: Fast back to back transfers disabled
[    0.478489] pci 0000:00:00.0: BAR 8: assigned [mem 0x40400000-0x405fffff]
[    0.478508] pci 0000:00:00.0: BAR 0: assigned [mem 0x40300000-0x40300fff]
[    0.478532] pci 0000:01:00.0: BAR 0: assigned [mem 0x40400000-0x405fffff 64bit]
[    0.478623] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[    0.478640] pci 0000:00:00.0:   bridge window [mem 0x40400000-0x405fffff]
[    0.481637] pcieport 0000:00:00.0: AER: enabled with IRQ 102
[    0.483826] bam-dma-engine 8e04000.dma: num-channels unspecified in dt
[    0.483851] bam-dma-engine 8e04000.dma: num-ees unspecified in dt
[    0.485260] tcsr 1949000.tcsr: setting wifi_glb_cfg = 41000000
[    0.485362] tcsr 194b000.tcsr: setting usb hs phy mode select = e700e7
[    0.485454] tcsr 1953000.ess_tcsr: setting ess interface select = 0
[    0.485549] tcsr 1957000.tcsr: setting wifi_noc_memtype_m0_m2 = 2222222
[    0.485884] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.487790] msm_serial 78af000.serial: msm_serial: detected port #0
[    0.487839] msm_serial 78af000.serial: uartclk = 1843200
[    0.487899] 78af000.serial: ttyMSM0 at MMIO 0x78af000 (irq = 32, base_baud = 115200) is a MSM
[    0.487930] msm_serial: console setup on port #0
[    1.180398] printk: console [ttyMSM0] enabled
[    1.185619] msm_serial: driver initialized
[    1.194843] loop: module loaded
[    1.196397] nand: device found, Manufacturer ID: 0xc2, Chip ID: 0xda
[    1.196800] nand: Macronix MX30LF2G18AC
[    1.203447] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    1.206963] Block protection check failed
[    1.214706] 16 fixed-partitions partitions found on MTD device qcom_nand.0
[    1.218686] Creating 16 MTD partitions on "qcom_nand.0":
[    1.225472] 0x000000000000-0x000000100000 : "sbl1"
[    1.232522] 0x000000100000-0x000000200000 : "mibib"
[    1.237075] 0x000000200000-0x000000300000 : "qsee"
[    1.241798] 0x000000300000-0x000000380000 : "cdt"
[    1.246244] 0x000000380000-0x000000400000 : "appsblenv"
[    1.250998] 0x000000400000-0x000000480000 : "ART"
[    1.256033] 0x000000480000-0x000000680000 : "appsbl"
[    1.262291] 0x000000680000-0x000000700000 : "u_env"
[    1.265896] 0x000000700000-0x000000740000 : "s_env"
[    1.270230] 0x000000740000-0x000000780000 : "devinfo"
[    1.275210] 0x000000780000-0x000005f80000 : "kernel"
[    1.363373] 0x000000a80000-0x000005f80000 : "rootfs"
[    1.444299] mtd: setting mtd11 (rootfs) as root device
[    1.444641] mtdsplit: no squashfs found in "rootfs"
[    1.448358] 0x000005f80000-0x00000b780000 : "alt_kernel"
[    1.537228] 0x000006280000-0x00000b780000 : "alt_rootfs"
[    1.618101] 0x00000b780000-0x00000b880000 : "sysdiag"
[    1.619582] 0x00000b880000-0x00000ff00000 : "syscfg"
[    1.729759] ESS reset ok!
[    1.803983] ESS reset ok!
[    2.480995] EDMA using MAC@ - using
[    2.481011] c2:1c:27:0d:05:47
[    2.567108] i2c /dev entries driver
[    2.569046] sdhci: Secure Digital Host Controller Interface driver
[    2.569411] sdhci: Copyright(c) Pierre Ossman
[    2.575743] sdhci-pltfm: SDHCI platform and OF driver helper
[    2.584329] NET: Registered protocol family 10
[    2.587447] Segment Routing with IPv6
[    2.590159] NET: Registered protocol family 17
[    2.593929] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    2.598156] 8021q: 802.1Q VLAN Support v1.8
[    2.611431] Registering SWP/SWPB emulation handler
[    2.626668] ubi0: attaching mtd11
[    2.626718] ubi0 error: 0xc06f4048: VID header offset 2048 too large.
[  ▒[    2.636874] Waiting for root device /dev/ubiblock0_0...

1 Like

If you look at the differences to the 'build.c' code in the MTD device driver in the linux sources between version 5.10.172 and 5.10.176 you will see the offending component causing the EA8300 and MR8300 devices to fail to start. This modification may also impact other 'generic' builds in the ipq40xx branch, just have not confirmed them all since most users stick with the last stable release and will be duped when they attempt to 'upgrade' to the 22.03.4 faulty release.

Does it only happen when kernsize 500000 is set? did you check?

Kernel size is not the issue, the MTD code change is. Already tested previously with kernel size 600000 as already set in the ip40xx builds for the Linksys Velop routers using the same dual partition configuration.

1 Like

I have an EA6350 which also doesn't start with master snapshots (don't have serial logs) but assuming it's related. It reboots back into the other partition eventually.

2 Likes

If the stable 22.03.3 build for the EA6350 starts up and the latest unannounced posting of stable 22.03.4 does not, since it is using kernel 5.10.176 instead, it most likely is affected, but the snapshots were affected since kernels 5.10.172/5.15.99.

I can confirm that the "v3 patch" from here works and the MR8300 snapshot boots again. Pull request seems to be on its way.

1 Like

I was indeed wondering if other ipq40xx devices had the same issue.

Just tried the EA6350 with 22.03.4 and it does not boot (22.03.3 does). I just got this router around the time of the start of this thread and the newer kernels have never worked so I've been assuming it's affected by same issue.

1 Like

Just fetched the MR8300 snapshot r22549 and confirm that it still does not boot, if your build snapshot is different then can you confirm if this is the case and that some future cut will be integrating the patch as mentioned. The kernel sources for 5.15.106 are still showing as unpatched so I am assuming that an OpenWRT roll-out fix is being applied.

1 Like

My bad, I was talking of building the snapshot on your own, since you have to apply the patch for yourself. The pull request hasn't followed yet.

Hi.
Well at least it works with the patch. Let us know when the PR had been merged.
Any link to share ?

So, for me to summarize, is commit:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/mtd/ubi?h=next-20230412&id=1e020e1b96afdecd20680b5b5be2a6ffc3d27628

Fixing the issue or?
Cause if it is, then it should be backported to OpenWrt to fix those devices booting

1 Like

Does the following address this issue or is it something else that we are waiting for?

ANSWERING MYSELF:
I have now tried the latest r20125.
Same problem, router fails to boot.

The PR targets the next linux kernel, so the fix will not be applied to any of the existing broken branches. It should have been submitted as a general PR to correct all LTS streams, so there should not be a resolution from the mainline kernel tree anytime soon nor has it been integrated into the OpenWRT trees since a localized patch has not been created for all UBI based targets using MTD devices. Will need to scan for all impacted equipment using this driver as is currently being released into the 22.03.4 builds.

2 Likes