Re: [LEDE-DEV] [PATCH] [17.01] Kernel: bump to 4.4.51
On 23 February 2017 at 22:35, Stijn Segers wrote: > Updates the 17.01 kernel to .51. > > Compile-tested on: > * ar71xx > * ramips/mt7621 > * x86/64 > > Run-tested on: > * ar71xx > * ramips/mt7621 > > Signed-off-by: Stijn Segers Why not the common way? Update kernel in master & cherry-pick to lede-17.01 branch? What makes this 17.01 specific? ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] [17.01] Kernel: bump to 4.4.51
Hi Rafal, I talked this through with jow, a lot of targets have already dropped 4.4 support in trunk, which makes backporting 4.4 updates to 17.01 non-trivial. He was OK with me sending in a patch just for 17.01. Cheers Stijn Op do, 23 feb 2017 om 10:44 , schreef Rafał Miłecki : On 23 February 2017 at 22:35, Stijn Segers wrote: Updates the 17.01 kernel to .51. Compile-tested on: * ar71xx * ramips/mt7621 * x86/64 Run-tested on: * ar71xx * ramips/mt7621 Signed-off-by: Stijn Segers Why not the common way? Update kernel in master & cherry-pick to lede-17.01 branch? What makes this 17.01 specific? ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] [17.01] Kernel: bump to 4.4.51
please also prepare a separate patch for trunk, so we canmerge both, even if they are different patches John On 24/02/2017 08:27, Stijn Segers wrote: > Hi Rafal, > > I talked this through with jow, a lot of targets have already dropped > 4.4 support in trunk, which makes backporting 4.4 updates to 17.01 > non-trivial. > > He was OK with me sending in a patch just for 17.01. > > Cheers > > Stijn > > Op do, 23 feb 2017 om 10:44 , schreef Rafał Miłecki : >> On 23 February 2017 at 22:35, Stijn Segers >> wrote: >>> Updates the 17.01 kernel to .51. >>> >>> Compile-tested on: >>> * ar71xx >>> * ramips/mt7621 >>> * x86/64 >>> >>> Run-tested on: >>> * ar71xx >>> * ramips/mt7621 >>> >>> Signed-off-by: Stijn Segers >> >> Why not the common way? Update kernel in master & cherry-pick to >> lede-17.01 branch? What makes this 17.01 specific? > > > ___ > Lede-dev mailing list > Lede-dev@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/lede-dev ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] [17.01] Kernel: bump to 4.4.51
please also prepare a separate patch for trunk, so we canmerge both, even if they are different patches John Hi John, Will do so this evening (CET), no access to my system from work. Cheers Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] [17.01] Kernel: bump to 4.4.51
This should be suitable: https://github.com/lede-project/source/pull/874 Kevin On 24/02/17 08:24, Stijn Segers wrote: please also prepare a separate patch for trunk, so we canmerge both, even if they are different patches John Hi John, Will do so this evening (CET), no access to my system from work. Cheers Stijn ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] [17.01] Kernel: bump to 4.4.51
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.98] INFO: rcu_sched detected stalls on CPUs/tasks: Sat Feb 25 20:10:09 2017 kern.err kernel: [ 3040.99] 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.00] (detected by 1, t=6004 jiffies, g=4116, c=4115, q=2999) Sat Feb 25 20:10:09 2017 kern.info kernel: [ 3041.01] Task dump for CPU 3: Sat Feb 25 20:10:09 2017 kern.info kernel: [ 3041.02] swapper/3 R running 0 0 1 0x0010 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] Stack : 0001 7fabc3c8 780022c0 804572a4 8040 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] 8040675c 0001 0001 80406680 80406724 8040 8001346c Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] 1100fc03 0003 87c74000 87c75ec0 8040 8005dbf8 1100fc03 0003 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] 8040 804572a4 8005dbf0 8040 8001abd8 1100fc03 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] 0004 804064a0 00a0 8001abe0 a0080040 50204041 0353017a 04405c16 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] ... Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.10] Call Trace:[<8001346c>] 0x8001346c Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.11] [<8005dbf8>] 0x8005dbf8 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.12] [<8005dbf0>] 0x8005dbf0 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.12] [<8001abd8>] 0x8001abd8 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.13] [<8001abe0>] 0x8001abe0 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.14] [<8021>] 0x8021 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.15] Sat Feb 25 20:10:09 2017 kern.err kernel: [ 3041.15] 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@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
Re: [LEDE-DEV] [PATCH] [17.01] Kernel: bump to 4.4.51
Op za, 25 feb 2017 om 9:02 , schreef Stijn Segers : 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.98] INFO: rcu_sched detected stalls on CPUs/tasks: Sat Feb 25 20:10:09 2017 kern.err kernel: [ 3040.99] 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.00] (detected by 1, t=6004 jiffies, g=4116, c=4115, q=2999) Sat Feb 25 20:10:09 2017 kern.info kernel: [ 3041.01] Task dump for CPU 3: Sat Feb 25 20:10:09 2017 kern.info kernel: [ 3041.02] swapper/3 R running 0 0 1 0x0010 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] Stack : 0001 7fabc3c8 780022c0 804572a4 8040 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] 8040675c 0001 0001 80406680 80406724 8040 8001346c Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] 1100fc03 0003 87c74000 87c75ec0 8040 8005dbf8 1100fc03 0003 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] 8040 804572a4 8005dbf0 8040 8001abd8 1100fc03 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] 0004 804064a0 00a0 8001abe0 a0080040 50204041 0353017a 04405c16 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] ... Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.10] Call Trace:[<8001346c>] 0x8001346c Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.11] [<8005dbf8>] 0x8005dbf8 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.12] [<8005dbf0>] 0x8005dbf0 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.12] [<8001abd8>] 0x8001abd8 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.13] [<8001abe0>] 0x8001abe0 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.14] [<8021>] 0x8021 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.15] Sat Feb 25 20:10:09 2017 kern.err kernel: [ 3041.15] 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 As a follow-up, I reverted to a .49 build and that exhibits similar symptoms... Sun Feb 26 10:46:18 2017 kern.err kernel: [ 1292.42] INFO: rcu_sched detected stalls on CPUs/tasks: Sun Feb 26 10:46:18 2017 kern.err kernel: [ 1292.43] 1-...: (0 ticks this GP) idle=0be/0/0 softirq=101979/101979 fqs=0 Sun Feb 26 10:46:18 2017 kern.err kernel: [ 1292.44] (detected by 2, t=6004 jiffies, g=4716, c=4715, q=758) Sun Feb 26 10:46:18 2017 kern.info kernel: [ 1292.45] Task dump for CPU 1: Sun Feb 26 10:46:18 2017 kern.info kernel: [ 1292.46] swapper/1 R running 0 0 1 0x0010 Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.47] Stack : 1400 0005 804572a4 8040 Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.47] 8040675c 0001 0001 80406540 80406724 8040 8001346c Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.47] 0001 87c7 87c71ec0 8040 8005dbf8 1100fc03 0001 Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.47] 8040 804572a4 8005dbf0 8040 8001abd8 1100fc03 Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.47] 0004 804064a0 00a0 8001abe0 a0080240 50205861 03530172 04405c16 Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.47] ... Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.54] Call Trace:[<8001346c>] 0x8001346c Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.55] [<8005dbf8>] 0x8005dbf8 Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.56] [<8005dbf0>] 0x8005dbf0 Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.57] [<8001abd8>] 0x8001abd8 Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.57] [<8001abe0>] 0x8001abe0 Sun Feb 26 10:46:18 2017 kern.warn kernel: [ 1292.58] Sun Feb 26 10:46:18 2017 kern.err kernel: [ 1292.58] rcu_sched kthread starved for 6018 jiffies! g4716 c4715 f0x0 s3 ->state=0x1 So it's not the .50/.51 bumps at least. Wondering if SQM (Cake) has something to do with it. ___
Re: [LEDE-DEV] [PATCH] [17.01] Kernel: bump to 4.4.51
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.98] INFO: rcu_sched detected stalls on CPUs/tasks: Sat Feb 25 20:10:09 2017 kern.err kernel: [ 3040.99] 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.00] (detected by 1, t=6004 jiffies, g=4116, c=4115, q=2999) Sat Feb 25 20:10:09 2017 kern.info kernel: [ 3041.01] Task dump for CPU 3: Sat Feb 25 20:10:09 2017 kern.info kernel: [ 3041.02] swapper/3 R running 0 0 1 0x0010 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] Stack : 0001 7fabc3c8 780022c0 804572a4 8040 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] 8040675c 0001 0001 80406680 80406724 8040 8001346c Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] 1100fc03 0003 87c74000 87c75ec0 8040 8005dbf8 1100fc03 0003 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] 8040 804572a4 8005dbf0 8040 8001abd8 1100fc03 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] 0004 804064a0 00a0 8001abe0 a0080040 50204041 0353017a 04405c16 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.03] ... Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.10] Call Trace:[<8001346c>] 0x8001346c Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.11] [<8005dbf8>] 0x8005dbf8 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.12] [<8005dbf0>] 0x8005dbf0 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.12] [<8001abd8>] 0x8001abd8 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.13] [<8001abe0>] 0x8001abe0 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.14] [<8021>] 0x8021 Sat Feb 25 20:10:09 2017 kern.warn kernel: [ 3041.15] Sat Feb 25 20:10:09 2017 kern.err kernel: [ 3041.15] 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@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev ___ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
