Unfortunately, for my BE92U, I still got a kernel crash with the time issue on the latest pre-release with the newest GPL. Here is the latest crash:
```
Mar 15 10:22:57 et12 hostapd: wl2.2: STA 00:00:00:00:00:00 IEEE 802.11: disassociated
Aug 24 04:56:16 router kernel: rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
Aug 24 04:56:16 router kernel: rcu: 0-...!: (2 ticks this GP) idle=dc6/1/0x4000000000000000 softirq=7290684/7290684 fqs=0
Aug 24 04:56:16 router kernel: rcu: 1-...!: (222 ticks this GP) idle=2ba/1/0x4000000000000000 softirq=5063391/5064327 fqs=0
Aug 24 04:56:16 router kernel: rcu: (detected by 2, t=900726557960 jiffies, g=3071113, q=45)
Aug 24 04:56:16 router kernel: tdts_core_ioctl_udb_op_prog_ctrl() fail!
Aug 24 04:56:16 router kernel: rcu: rcu_sched kthread starved for 900726557960 jiffies! g3071113 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x200 ->cpu=2
Aug 24 04:56:16 router kernel: rcu: RCU grace-period kthread stack dump:
Sep 29 11:24:32 router chronyd[12818]: Forward time jump detected!
Aug 24 04:56:16 router kernel: [BLOCKED - INBOUND] IN=vlan4094 OUT= MAC=60:cf:84:3a:a9:a0:40:48:6e:bc:b6:31:08:00:45:00:00:2c SRC=193.163.125.7 DST=172.1.136.40 LEN=44 TOS=0x00 PREC=0x00 TTL=242 ID=40195 PROTO=TCP SPT=33207 DPT=2762 SEQ=1412969829 ACK=0 WINDOW=14600 RES=0x00 SYN URGP=0 OPT (020405B4)
Aug 24 04:56:16 router kernel: rcu_sched R 0 11 2 0x00000008
Aug 24 04:56:16 router kernel: Call trace:
Aug 24 04:56:16 router kernel: __switch_to+0x148/0x170
Aug 24 04:56:16 router kernel: [BLOCKED - INBOUND] IN=vlan4094 OUT= MAC=60:cf:84:3a:a9:a0:40:48:6e:bc:b6:31:08:00:45:00:00:34 SRC=85.217.149.69 DST=172.1.136.40 LEN=52 TOS=0x00 PREC=0x00 TTL=46 ID=44471 PROTO=TCP SPT=41441 DPT=5858 SEQ=4017440342 ACK=0 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B40103030801010402)
Aug 24 04:56:16 router kernel: __schedule+0x214/0x5a0
Aug 24 04:56:16 router kernel: schedule+0x38/0xa0
Aug 24 04:56:16 router kernel: schedule_timeout+0x15c/0x2a0
Aug 24 04:56:16 router kernel: rcu_gp_kthread+0x488/0x900
Aug 24 04:56:16 router kernel: [BLOCKED - INBOUND] IN=vlan4094 OUT= MAC=60:cf:84:3a:a9:a0:40:48:6e:bc:b6:31:08:00:45:00:00:28 SRC=185.224.128.16 DST=172.1.136.40 LEN=40 TOS=0x00 PREC=0x00 TTL=242 ID=54321 PROTO=TCP SPT=33144 DPT=9000 SEQ=101545099 ACK=0 WINDOW=65535 RES=0x00 SYN URGP=0
Aug 24 04:56:16 router kernel: kthread+0x118/0x150
Aug 24 04:56:16 router kernel: ret_from_fork+0x10/0x24
Aug 24 04:56:16 router crond[4808]: time disparity of 15012122 minutes detected
```
It still seems more stable than 102.7_beta2 but unfortunately, the crash is still there at least for me (note the et12 line is coming from the et12 mesh node since all logs seem re-routed to my external log server; it's just to give a sense of the time jump).
Thanks,
Romain
```
Mar 15 10:22:57 et12 hostapd: wl2.2: STA 00:00:00:00:00:00 IEEE 802.11: disassociated
Aug 24 04:56:16 router kernel: rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
Aug 24 04:56:16 router kernel: rcu: 0-...!: (2 ticks this GP) idle=dc6/1/0x4000000000000000 softirq=7290684/7290684 fqs=0
Aug 24 04:56:16 router kernel: rcu: 1-...!: (222 ticks this GP) idle=2ba/1/0x4000000000000000 softirq=5063391/5064327 fqs=0
Aug 24 04:56:16 router kernel: rcu: (detected by 2, t=900726557960 jiffies, g=3071113, q=45)
Aug 24 04:56:16 router kernel: tdts_core_ioctl_udb_op_prog_ctrl() fail!
Aug 24 04:56:16 router kernel: rcu: rcu_sched kthread starved for 900726557960 jiffies! g3071113 f0x2 RCU_GP_WAIT_FQS(5) ->state=0x200 ->cpu=2
Aug 24 04:56:16 router kernel: rcu: RCU grace-period kthread stack dump:
Sep 29 11:24:32 router chronyd[12818]: Forward time jump detected!
Aug 24 04:56:16 router kernel: [BLOCKED - INBOUND] IN=vlan4094 OUT= MAC=60:cf:84:3a:a9:a0:40:48:6e:bc:b6:31:08:00:45:00:00:2c SRC=193.163.125.7 DST=172.1.136.40 LEN=44 TOS=0x00 PREC=0x00 TTL=242 ID=40195 PROTO=TCP SPT=33207 DPT=2762 SEQ=1412969829 ACK=0 WINDOW=14600 RES=0x00 SYN URGP=0 OPT (020405B4)
Aug 24 04:56:16 router kernel: rcu_sched R 0 11 2 0x00000008
Aug 24 04:56:16 router kernel: Call trace:
Aug 24 04:56:16 router kernel: __switch_to+0x148/0x170
Aug 24 04:56:16 router kernel: [BLOCKED - INBOUND] IN=vlan4094 OUT= MAC=60:cf:84:3a:a9:a0:40:48:6e:bc:b6:31:08:00:45:00:00:34 SRC=85.217.149.69 DST=172.1.136.40 LEN=52 TOS=0x00 PREC=0x00 TTL=46 ID=44471 PROTO=TCP SPT=41441 DPT=5858 SEQ=4017440342 ACK=0 WINDOW=65535 RES=0x00 SYN URGP=0 OPT (020405B40103030801010402)
Aug 24 04:56:16 router kernel: __schedule+0x214/0x5a0
Aug 24 04:56:16 router kernel: schedule+0x38/0xa0
Aug 24 04:56:16 router kernel: schedule_timeout+0x15c/0x2a0
Aug 24 04:56:16 router kernel: rcu_gp_kthread+0x488/0x900
Aug 24 04:56:16 router kernel: [BLOCKED - INBOUND] IN=vlan4094 OUT= MAC=60:cf:84:3a:a9:a0:40:48:6e:bc:b6:31:08:00:45:00:00:28 SRC=185.224.128.16 DST=172.1.136.40 LEN=40 TOS=0x00 PREC=0x00 TTL=242 ID=54321 PROTO=TCP SPT=33144 DPT=9000 SEQ=101545099 ACK=0 WINDOW=65535 RES=0x00 SYN URGP=0
Aug 24 04:56:16 router kernel: kthread+0x118/0x150
Aug 24 04:56:16 router kernel: ret_from_fork+0x10/0x24
Aug 24 04:56:16 router crond[4808]: time disparity of 15012122 minutes detected
```
It still seems more stable than 102.7_beta2 but unfortunately, the crash is still there at least for me (note the et12 line is coming from the et12 mesh node since all logs seem re-routed to my external log server; it's just to give a sense of the time jump).
Thanks,
Romain