[FS#682] WNR2000v3 bootloop after installing 17.01.0

[LEDE Bugs]

A new Flyspray task has been opened.  Details are below. 

User who did this - Aaron Z (aczlan) 

Attached to Project - LEDE Project
Summary - WNR2000v3 bootloop after installing 17.01.0
Task Type - Bug Report
Category - Base system
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - Low
Priority - Very Low
Reported Version - lede-17.01
Due in Version - Undecided
Due Date - Undecided
Details - My Netgear WNR2000v3 goes into a bootloop after installing 17.01.0 but is fine with the Trunk snapshot from 6 April 2017.
When it starts up, it gives me 4 pings, then it stops responding until it wakes back up. When it stops responding,m the network interface acts like it is disconnected (no link), then it comes back up just before it responds to pings again.
I had time tonight to plug a serial console into it and record what it does when you install 17.01.0
These were installed with TFTP from the recovery (hold reset for ~30 seconds when powering up, then tftp the image to 192.168.1.1)
Attached are two bootlogs:
  - Bootlog of the upgrade to 17.01 from recovery mode using the lede-17.01.0-r3205-59508e3-ar71xx-generic-wnr2000v3-squashfs-factory-NA.img image (goes into a bootloop after the install): WNR2000V3To17.01UpgradeBootlog.txt
  - Bootlog of the upgrade to the 6 April 2017 nightly (r3922-9613d97) using the lede-ar71xx-generic-wnr2000v3-squashfs-factory-NA.img image (works as expected): WNR2000V3To6April17SnapshotUpgradeBootlog.txt

I saw the same thing installing lede-17.01.0-r3205-59508e3-ar71xx-generic-wnr2000v3-squashfs-factory-NA.img from the factory web interface (Netgear wnr2000v3-V1.1.2.14) but I didnt save a bootlog of that

Let me know if more info is needed.

Aaron Z

 

One or more files have been attached.

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=682