[LEDE-DEV] [PATCH] [17.01] Kernel: bump to 4.4.51

[davidea]

i know it's an old message,
i have another router with mediatek processor and it has similar 
behavior when i enable smart queue management , disabling it the problem 
is solved

Il 25/02/2017 21:02, Stijn Segers ha scritto:
> So...
>
>
> I have been running on 4.4.51 on a few days now but it looks like 
> there's some weird stuff going on on my DIR-860L... I don't know if 
> this is merely a timeline coincidence or if it's something linked to 
> .51 (or .50).
>
> I checked its uptime and it reported < 2h (flashed it two days ago), 
> wifi connection periodically craps out, when I check if my desktop 
> still has a wired connection, it shows the router doesn't respond to 
> DHCP requests anymore either... DNS is broken as well. Restarting both 
> dnsmasq (DHCP) and Unbound (DNS) services doesn't work, they keep 
> hanging for some reason.
>
> I have a few traces like these in logread:
>
> Sat Feb 25 20:10:09 2017 kern.err kernel: [ 3040.980000] INFO: 
> rcu_sched detected stalls on CPUs/tasks:
> Sat Feb 25 20:10:09 2017 kern.err kernel: [ 3040.990000] 3-...: (0 
> ticks this GP) idle=4b8/0/0 softirq=1265/1265 fqs=0
> Sat Feb 25 20:10:09 2017 kern.err kernel: [ 3041.000000] (detected by 
> 1, t=6004 jiffies, g=4116, c=4115, q=2999)
> Sat Feb 25 20:10:09 2017 kern.info kernel: [ 3041.010000] Task dump 
> for CPU 3:
> Sat Feb 25 20:10:09 2017 kern.info kernel: [ 3041.020000] 
> swapper/3      R running      0     0      1 0x00100000
> Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.030000] Stack : 
> 00000000 00000001 7fabc3c8 00000000 00000000 780022c0 804572a4 80400000
> Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.030000] 8040675c 
> 00000001 00000001 80406680 80406724 80400000 00000000 8001346c
> Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.030000] 1100fc03 
> 00000003 87c74000 87c75ec0 80400000 8005dbf8 1100fc03 00000003
> Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.030000] 00000000 
> 80400000 804572a4 8005dbf0 80400000 8001abd8 1100fc03 00000000
> Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.030000] 00000004 
> 804064a0 000000a0 8001abe0 a0080040 50204041 0353017a 04405c16
> Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.030000] ...
> Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.100000] Call 
> Trace:[<8001346c>] 0x8001346c
> Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.110000] [<8005dbf8>] 
> 0x8005dbf8
> Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.120000] [<8005dbf0>] 
> 0x8005dbf0
> Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.120000] [<8001abd8>] 
> 0x8001abd8
> Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.130000] [<8001abe0>] 
> 0x8001abe0
> Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.140000] [<80214444>] 
> 0x80214444
> Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.150000]
> Sat Feb 25 20:10:09 2017 kern.err kernel: [ 3041.150000] rcu_sched 
> kthread starved for 6019 jiffies! g4116 c4115 f0x0 s3 ->state=0x1
>
> Any ideas what I should be looking for?
>
> Other stuff (ar71xx and x86/64 namely) are still up (uninterrupted 
> since their last flash to a firmware with a 4.4.51 kernel) and I 
> haven't gotten any complaints from their users.
>
> Stijn
>
>
> _______________________________________________
> Lede-dev mailing list
> Lede-dev at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev