Hi,
On Fri, May 25, 2018 at 7:06 PM, Kristian Evensen
<kristian.even...@gmail.com> wrote:
>> I know how to fix the issue by recovery, however, from the responses
>> in the topic on the Lede forum it seems more people are running into
>> this issue. This definitely needs to be fixed before a 18.06 release.
>> Is there someone with a mt7621 device that can reproduce the problem,
>> and that has serial access? We might be able to figure out what is
>> going wrong.
I kept looking into this and instrumented /lib/upgrade/stage2. I added
some output showing which processes were left for each iteration of
the loop, as well as when "Failed to kill ..." hits. It seems that
hostapd, for some time, takes unexpectedly long to close:
Sending TERM to remaining processes ... loop limit 10
logd
rpcd
netifd
odhcpd
crond
ntpd
nginx
nginx
ubusd
dnsmasq
sh
sh
sh
sshd
sleep
sh
hostapd
hostapd
rsync
ssh
sleep
[ 115.583843] device wlan0 left promiscuous mode
[ 115.588436] br-lan: port 3(wlan0) entered disabled state
[ 115.594261] device wlan1 left promiscuous mode
[ 115.598798] br-lan: port 2(wlan1) entered disabled state
Sending KILL to remaining processes ... loop limit 10
hostapd
loop limit 9
hostapd
loop limit 8
hostapd
loop limit 7
hostapd
loop limit 6
hostapd
loop limit 5
hostapd
loop limit 4
hostapd
loop limit 3
hostapd
loop limit 2
hostapd
loop limit 1
Failed to kill all processes.
PID USER VSZ STAT COMMAND
1 root 992 S /sbin/upgraded /tmp/firmware.bin . /lib/functions.sh
2 root 0 SW [kthreadd]
3 root 0 IW [kworker/0:0]
4 root 0 IW< [kworker/0:0H]
5 root 0 IW [kworker/u8:0]
6 root 0 IW< [mm_percpu_wq]
7 root 0 SW [ksoftirqd/0]
8 root 0 IW [rcu_sched]
9 root 0 IW [rcu_bh]
10 root 0 SW [migration/0]
11 root 0 SW [cpuhp/0]
12 root 0 SW [cpuhp/1]
13 root 0 SW [migration/1]
14 root 0 SW [ksoftirqd/1]
15 root 0 IW [kworker/1:0]
16 root 0 IW< [kworker/1:0H]
17 root 0 SW [cpuhp/2]
18 root 0 SW [migration/2]
19 root 0 SW [ksoftirqd/2]
20 root 0 IW [kworker/2:0]
21 root 0 IW< [kworker/2:0H]
22 root 0 SW [cpuhp/3]
23 root 0 SW [migration/3]
24 root 0 SW [ksoftirqd/3]
25 root 0 IW [kworker/3:0]
26 root 0 IW< [kworker/3:0H]
27 root 0 IW [kworker/u8:1]
34 root 0 IW [kworker/u8:2]
65 root 0 IW [kworker/0:1]
66 root 0 IW [kworker/3:1]
67 root 0 IW [kworker/2:1]
136 root 0 IW [kworker/1:1]
137 root 0 SW [oom_reaper]
138 root 0 IW< [writeback]
140 root 0 IW< [crypto]
142 root 0 IW< [kblockd]
157 root 0 IW [kworker/u8:3]
177 root 0 IW< [watchdogd]
201 root 0 SW [kswapd0]
233 root 0 IW< [pencrypt]
262 root 0 IW< [pdecrypt]
295 root 0 SW [spi0]
353 root 0 IW< [ipv6_addrconf]
362 root 0 IW< [kworker/1:1H]
363 root 0 IW< [kworker/0:1H]
365 root 0 IW< [kworker/3:1H]
366 root 0 IW< [kworker/2:1H]
416 root 0 IW [kworker/1:2]
417 root 0 IW [kworker/0:2]
457 root 0 SWN [jffs2_gcd_mtd6]
575 root 0 IW [kworker/2:2]
869 root 0 IW< [cfg80211]
1842 root 0 IW [kworker/3:2]
7535 root 1328 S /bin/sh /lib/upgrade/stage2 /tmp/firmware.bin . /lib
7547 root 1184 R /bin/ps
sysupgrade abort[ 124.152193] reboot: Restarting system
ed with return code: 256
With a working update, KILL usually looks like this:
BR,
Kristian
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.infradead.org/mailman/listinfo/openwrt-devel
