Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FS#3686 - Belkin F9K1115 v2 - boot loop with 21.02 snapshot #8763

Closed
openwrt-bot opened this issue Mar 16, 2021 · 11 comments
Closed

FS#3686 - Belkin F9K1115 v2 - boot loop with 21.02 snapshot #8763

openwrt-bot opened this issue Mar 16, 2021 · 11 comments
Labels
bug flyspray release/21.02 target/ath79

Comments

@openwrt-bot
Copy link

@openwrt-bot openwrt-bot commented Mar 16, 2021

siturf:

Boot loop, no communication with the router after upgrade to 21.02 snapshot (tested r15866).

Upgrade from Belkin web UI (factory image) is not working.

Probably migration to the new ath79 architecture is not correct:

@openwrt-bot
Copy link
Author

@openwrt-bot openwrt-bot commented Oct 15, 2021

nerzakt:

Mine does the same thing I have a f9k1109v1, I am stuck on 19.0.7

@aparcar aparcar added the release/21.02 label Feb 22, 2022
@mrtnmtth
Copy link

@mrtnmtth mrtnmtth commented Mar 10, 2022

Same problem here with 21.02.2 on F9K1115 V2 after upgrade from 19.07.9

Kernel log:

OK$
No initrd$
## Transferring control to Linux (at address 80060000) ...$
## Giving linux memsize in bytes, 134217728$
Starting kernel ...$
[    0.000000] Linux version 4.14.267 (builder@buildhost) (gcc version 7.5.0 (OpenWrt GCC 7.5.0 r11405-2a3558b0de)) #0 Wed Feb 16 20:47:59 2022$
[    0.000000] bootconsole [early0] enabled$
[    0.000000] CPU0 revision is: 00019750 (MIPS 74Kc)$
[    0.000000] SoC: Qualcomm Atheros QCA9558 ver 1 rev 0$
[    0.000000] Determined physical RAM map:$
[    0.000000]  memory: 08000000 @ 00000000 (usable)$
[    0.000000] Initrd not found or empty - disabling initrd$
[    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.$
[    0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes$
[    0.000000] Zone ranges:$
[    0.000000]   Normal   [mem 0x0000000000000000-0x0000000007ffffff]$
[    0.000000] Movable zone start for each node$
[    0.000000] Early memory node ranges$
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000007ffffff]$
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000007ffffff]$
[    0.000000] random: get_random_bytes called from 0x804656ec with crng_init=0$
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 32512$
[    0.000000] Kernel command line:  board=F9K1115V2 console=ttyS0,115200 mtdparts=spi0.0:256k(u-boot)ro,64k(u-boot-env),14464k(rootfs),1408k(kernel),64k(nvram)ro,64k(envram)ro,64k(art)ro,15872k@0x50000(firmware) rootfstype=squashfs noinitrd$
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)$
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)$
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)$
[    0.000000] Writing ErrCtl register=00000000$
[    0.000000] Readback ErrCtl register=00000000$
[    0.000000] Memory: 124940K/131072K available (3470K kernel code, 172K rwdata, 464K rodata, 236K init, 207K bss, 6132K reserved, 0K cma-reserved)$
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1$
[    0.000000] NR_IRQS: 51$
[    0.000000] Clocks: CPU:720.000MHz, DDR:600.000MHz, AHB:200.000MHz, Ref:40.000MHz$
[    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 5309056796 ns$
[    0.000007] sched_clock: 32 bits at 360MHz, resolution 2ns, wraps every 5965232126ns$
[    0.008302] Calibrating delay loop... 358.80 BogoMIPS (lpj=1794048)$
[    0.074984] pid_max: default: 32768 minimum: 301$
[    0.080081] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)$
[    0.087122] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)$
[    0.096482] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns$
[    0.106979] futex hash table entries: 256 (order: -1, 3072 bytes)$
[    0.114450] NET: Registered protocol family 16$
[    0.120328] MIPS: machine is Belkin AC1750DB$
[    0.599619] registering PCI controller with io_map_base unset$
[    0.605847] registering PCI controller with io_map_base unset$
[    0.622627] PCI host bridge to bus 0000:00$
[    0.626993] pci_bus 0000:00: root bus resource [mem 0x10000000-0x11ffffff]$
[    0.634338] pci_bus 0000:00: root bus resource [io  0x0000]$
[    0.640267] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0]$
[    0.647491] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]$
[    0.656361] pci 0000:00:00.0: BAR 0: assigned [mem 0x10000000-0x101fffff 64bit]$
[    0.664188] pci 0000:00:00.0: BAR 6: assigned [mem 0x10200000-0x1020ffff pref]$
[    0.671973] PCI host bridge to bus 0000:01$
[    0.676355] pci_bus 0000:01: root bus resource [mem 0x12000000-0x13ffffff]$
[    0.683669] pci_bus 0000:01: root bus resource [io  0x0001]$
[    0.689601] pci_bus 0000:01: root bus resource [??? 0x00000000 flags 0x0]$
[    0.696824] pci_bus 0000:01: No busn resource found for root bus, will use [bus 01-ff]$
[    0.705423] pci 0000:01:00.0: enabling Extended Tags$
[    0.710987] pci 0000:01:00.0: BAR 0: assigned [mem 0x12000000-0x12007fff 64bit]$
[    0.721674] clocksource: Switched to clocksource MIPS$
[    0.727918] NET: Registered protocol family 2$
[    0.732763] IP idents hash table entries: 2048 (order: 2, 16384 bytes)$
[    0.740341] TCP established hash table entries: 1024 (order: 0, 4096 bytes)$
[    0.747806] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)$
[    0.754588] TCP: Hash tables configured (established 1024 bind 1024)$
[    0.761461] UDP hash table entries: 256 (order: 0, 4096 bytes)$
[    0.767718] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)$
[    0.774570] NET: Registered protocol family 1$
[    0.781773] Crashlog allocated RAM at address 0x3f00000$
[    0.788540] workingset: timestamp_bits=30 max_order=15 bucket_order=0$
[    0.799757] squashfs: version 4.0 (2009/01/31) Phillip Lougher$
[    0.805997] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.$
[    0.824622] io scheduler noop registered$
[    0.828792] io scheduler deadline registered (default)$
[    0.834657] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled$
[    0.843215] console [ttyS0] disabled$
[    0.867094] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11, base_baud = 2500000) is a 16550A
[    0.876280] console [ttyS0] enabled$
[    0.876280] console [ttyS0] enabled$
[    0.883706] bootconsole [early0] disabled$
[    0.883706] bootconsole [early0] disabled$
[    0.897918] m25p80 spi0.0: found w25q128, expected m25p80$
[    0.914465] m25p80 spi0.0: w25q128 (16384 Kbytes)$
[    0.919272] 8 cmdlinepart partitions found on MTD device spi0.0$
[    0.925298] Creating 8 MTD partitions on "spi0.0":$
[    0.930166] 0x000000000000-0x000000040000 : "u-boot"$
[    0.936678] 0x000000040000-0x000000050000 : "u-boot-env"$
[    0.943209] 0x000000050000-0x000000e70000 : "rootfs"$
[    0.948881] mtd: device 2 (rootfs) set to be root filesystem$
[    0.954718] mtdsplit: no squashfs found in "rootfs"$
[    0.960750] 0x000000e70000-0x000000fd0000 : "kernel"$
[    0.966932] 0x000000fd0000-0x000000fe0000 : "nvram"$
[    0.973622] 0x000000fe0000-0x000000ff0000 : "envram"$
[    0.979766] 0x000000ff0000-0x000001000000 : "art"$
[    0.986261] 0x000000050000-0x000000fd0000 : "firmware"$
[    1.005990] switch0: Atheros AR8337 rev. 2 switch registered on ag71xx-mdio.0$
[    2.333213] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd036, driver=Atheros AR8216/AR8236/AR8316]$
[    2.344507] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode: rgmii$
[    2.601672] random: fast init done$
[    2.973266] eth1: Atheros AG71xx at 0xba000000, irq 5, mode: sgmii$
[    2.981144] NET: Registered protocol family 10$
[    2.989622] Segment Routing with IPv6$
[    2.993473] NET: Registered protocol family 17$
[    2.998026] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.$
[    3.011618] 8021q: 802.1Q VLAN Support v1.8$
[    3.018816] List of all partitions:$
[    3.022407] 1f00             256 mtdblock0$
[    3.022411]  (driver?)$
[    3.029042] 1f01              64 mtdblock1$
[    3.029046]  (driver?)$
[    3.035694] 1f02           14464 mtdblock2$
[    3.035697]  (driver?)$
[    3.042341] 1f03            1408 mtdblock3$
[    3.042344]  (driver?)$
[    3.048973] 1f04              64 mtdblock4$
[    3.048976]  (driver?)$
[    3.055609] 1f05              64 mtdblock5$
[    3.055613]  (driver?)$
[    3.062254] 1f06              64 mtdblock6$
[    3.062258]  (driver?)$
[    3.068887] 1f07           15872 mtdblock7$
[    3.068890]  (driver?)$
[    3.075518] No filesystem could mount root, tried:$
[    3.075522]  squashfs$
[    3.080462]$
[    3.084280] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)$
[    3.093720] Rebooting in 1 seconds..

@ynezz
Copy link
Member

@ynezz ynezz commented Mar 11, 2022

Seems like sysupgrade issue to me:

[    0.948881] mtd: device 2 (rootfs) set to be root filesystem$
[    0.954718] mtdsplit: no squashfs found in "rootfs"$

So in order to find out what is going on, we would need to see the console output during sysupgrade process from 19.07. Maybe @xdarklight would have some clue?

@mrtnmtth Can you please try flashing openwrt-21.02.2-ath79-generic-belkin_f9k1115-v2-squashfs-factory.bin via the U-Boot HTTP upgrade page (which is by default listening on 192.168.2.1) and report back?

@ynezz ynezz added the bug label Mar 11, 2022
@xdarklight
Copy link
Contributor

@xdarklight xdarklight commented Mar 13, 2022

So in order to find out what is going on, we would need to see the console output during sysupgrade process from 19.07. > Maybe @xdarklight would have some clue?

I think I did test sysupgrade from ar71xx to ath79 back then but it's been a while.
sysupgrade from one ath79 image to another does work, I just recently did this on my device.

@mrtnmtth Can you please try flashing openwrt-21.02.2-ath79-generic-belkin_f9k1115-v2-squashfs-factory.bin via the U-Boot HTTP upgrade page (which is by default listening on 192.168.2.1) and report back?

I am sure that I tried this approach as I found some issue with the image generation process and had to tackle that.
So I'm interested in hearing whether this works for @mrtnmtth

@mrtnmtth
Copy link

@mrtnmtth mrtnmtth commented Mar 13, 2022

Flashing openwrt-21.02.2-ath79-generic-belkin_f9k1115-v2-squashfs-factory.bin via the recovery web-if does indeed work.

For other devices, sysupgrades from ar71xx to ath79 also worked without any problems back on 19.07, when I applied them a year or two ago.

I guess there might be something missing from the sysupgrade image for this device. Old images used to be around 16MB whereas the 21.02 ath79 ones are only 6MB.

Image comparison using binwalk:

$ binwalk openwrt-21.02.2-ath79-generic-belkin_f9k1115-v2-squashfs-sysupgrade.bin 

DECIMAL       HEXADECIMAL     DESCRIPTION
--------------------------------------------------------------------------------
64            0x40            LZMA compressed data, properties: 0x6D, dictionary size: 8388608 bytes, uncompressed size: 6467078 bytes
2097152       0x200000        Squashfs filesystem, little endian, version 4.0, compression:xz, size: 3692310 bytes, 1246 inodes, blocksize: 262144 bytes, created: 2022-02-16 20:29:10

$ binwalk openwrt-19.07.9-ar71xx-tiny-f9k1115v2-squashfs-sysupgrade.bin 

DECIMAL       HEXADECIMAL     DESCRIPTION
--------------------------------------------------------------------------------
0             0x0             Squashfs filesystem, little endian, version 4.0, compression:xz, size: 2727450 bytes, 1173 inodes, blocksize: 1048576 bytes, created: 2022-02-16 20:47:59
14811136      0xE20000        uImage header, header size: 64 bytes, header CRC: 0xD240BA07, created: 2022-02-16 20:47:59, image size: 1402346 bytes, Data Address: 0x80060000, Entry Point: 0x80060000, data CRC: 0x7ED248F5, OS: Linux, CPU: MIPS, image type: OS Kernel Image, compression type: lzma, image name: "MIPS OpenWrt Linux-4.14.267"
14811200      0xE20040        LZMA compressed data, properties: 0x6D, dictionary size: 8388608 bytes, uncompressed size: 4405652 bytes

@xdarklight
Copy link
Contributor

@xdarklight xdarklight commented Mar 13, 2022

Flashing openwrt-21.02.2-ath79-generic-belkin_f9k1115-v2-squashfs-factory.bin via the recovery web-if does indeed work.

great, thanks for reporting back!

For other devices, sysupgrades from ar71xx to ath79 also worked without any problems back on 19.07, when I applied them a year or two ago.

I guess there might be something missing from the sysupgrade image for this device. Old images used to be around 16MB whereas the 21.02 ath79 ones are only 6MB.

On my own device I run master. The image size there is similar to 21.02. sysupgrade (from one ath79 image to another) works fine for me.

I suspect that the ar71xx -> ath79 sysupgrade problem comes from the LZMA loader because original u-boot has some kernel size restrictions (which I think is why in ar71xx the device was moved to the tiny sub-target, while there's plenty of space in flash). I have been re-using this part from F9J1108v2 which was added by @dmascord
If my suspicion is correct then F9J1108v2 also cannot be sysupgrade'd from ar71xx to ath79. That said, I am not sure how to tell the image (or image building code) that flashing from ar71xx is unsupported.

@mrtnmtth
Copy link

@mrtnmtth mrtnmtth commented Mar 14, 2022

To be fair, I needed to force the sysupgrade from 19.07.

Device f9k1115v2 not supported by this image
Supported devices: belkin,f9k1115-v2
Invalid image type.
Image check failed but --force given - will update anyway!

But I anyway assumed this to be a valid upgrade path and proceeded. Maybe it should just be documented somewhere that the sysupgrade 19.07 -> 21.02 is not supported for this device (and maybe other affected Belkin devices too).

Another issue I noticed is that the eth interfaces are now enumerated the other way around. Therefore, my network config needed some manual fixing as well.

@xdarklight
Copy link
Contributor

@xdarklight xdarklight commented Mar 14, 2022

To be fair, I needed to force the sysupgrade from 19.07.

Device f9k1115v2 not supported by this image
Supported devices: belkin,f9k1115-v2
Invalid image type.
Image check failed but --force given - will update anyway!

But I anyway assumed this to be a valid upgrade path and proceeded. Maybe it should just be documented somewhere that the sysupgrade 19.07 -> 21.02 is not supported for this device (and maybe other affected Belkin devices too).

I found this documentation in the wiki: https://openwrt.org/docs/guide-user/installation/ar71xx.to.ath79
It mentions that forcing sysupgrade is only supported at your own risk.

The release notes for 21.02.0 are linking to above wiki page as well: https://openwrt.org/releases/21.02/notes-21.02.0#dropped_hardware_targets
That section also mentions that "it is recommended to reinstall OpenWrt 21.02 from scratch".

Another issue I noticed is that the eth interfaces are now enumerated the other way around. Therefore, my network config needed some manual fixing as well.

Above mentioned wiki page even has a section with "incompatible changes". It states that there are changes to Ethernet interfaces, LEDs and wifi device paths.

@mrtnmtth
Copy link

@mrtnmtth mrtnmtth commented Mar 14, 2022

Oh well... 😅. Shame on me for not rtfm.

Sorry for bothering you then. But thanks very much for the support anyway.

@xdarklight
Copy link
Contributor

@xdarklight xdarklight commented Mar 14, 2022

Oh well... sweat_smile. Shame on me for not rtfm.

Sorry for bothering you then. But thanks very much for the support anyway.

It's not that this was the first thing on my mind - so don't worry!

In this ticket there's now three different reports:

  1. the original reporter states that installing a 21.02 snapshot factory image on F9K1115v2 results in a bootloop
  2. the first commenter reports the "same" problem (I read this as: 21.02 snapshot bootloops) on a F9K1109v1 which is a Ralink RT3883 based device
  3. @mrtnmtth reports that a 21.02 snapshot factory image works fine on F9K1115v2

I suggest closing this issue for two reasons:

  • there's now a very recent report by @mrtnmtth that the 21.02 factory image works on F9K1115v2
  • F9K1109v1 is a completely different device and has nothing to do with the original report or any discussion in this ticket. If the reporter reads this: please create a separate issue

I am not an OpenWrt developer so I don't have permission to close this issue myself.

@ynezz
Copy link
Member

@ynezz ynezz commented Mar 14, 2022

@xdarklight Thanks!

@ynezz ynezz closed this as completed Mar 14, 2022
@ynezz ynezz added the target/ath79 label Mar 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug flyspray release/21.02 target/ath79
Projects
None yet
Development

No branches or pull requests

5 participants