Here is a test build for V1 owners who want to run kernel 4.9. Keep in mind that I don't have a V1 to test with, so you are downloading this at your own risk. Essentially, I just used the patch as was posted previously. Please report back if this works or not. Also, keep an eye on CPU thermals and you might tweak the fan setting to run more often.
Topic: davidc502 1900ac 3200acm builds
The content of this topic has been archived between 26 Feb 2018 and 7 May 2018. Unfortunately there are posts – most likely complete pages – missing.
Page 174 of 229
The Linux Kernel has 4.14 out for a while... And it is an LTS version... @davidc502 when you will start to compile with 4.14 on the WRT3200ACM?
WWTK wrote:
@makedir I don't find it obvious at all, my 1900acs and 3200acm have never rebooted, not once.
I feel there are multiple issues at play.
Nope. The reason why you dont experience it that often (never so far), is connected with two reasons as I see it. First, there is already a CPUIDLE disable patch included for the three models of 1900acs, 3200 and 1200, because they have all the same CPU (a different one than the 1900v1). Just look into your dmesg boot messages and you will find two lines for this (found armada bla bla is bugged bla cpuidle disabled bla). And you mostly dont do much with your routers triggering high cpu/ram usage. For the first, I guess this patch might not work properly, and still leads to random but rare reboots.
Latest bug:
[190298.776912] swap_free: Bad swap file entry 00000c00
[190298.781933] BUG: Bad page map in process sleep pte:00060000 pmd:1cba5831
[190298.788840] addr:00021000 vm_flags:00000875 anon_vma: (null) mapping:df0ab614 index:11
[190298.796988] file:busybox fault:filemap_fault mmap:generic_file_readonly_mmap readpage:squashfs_readpage
[190298.806632] CPU: 1 PID: 20131 Comm: sleep Not tainted 4.9.65 #0
[190298.812664] Hardware name: Marvell Armada 380/385 (Device Tree)
[190298.818712] [<c0016010>] (unwind_backtrace) from [<c0012220>] (show_stack+0x10/0x14)
[190298.826584] [<c0012220>] (show_stack) from [<c0218580>] (dump_stack+0x7c/0x9c)
[190298.833932] [<c0218580>] (dump_stack) from [<c00b5140>] (print_bad_pte+0x154/0x18c)
[190298.841713] [<c00b5140>] (print_bad_pte) from [<c00b718c>] (unmap_page_range+0x2f4/0x554)
[190298.850015] [<c00b718c>] (unmap_page_range) from [<c00b773c>] (unmap_vmas+0x44/0x54)
[190298.857881] [<c00b773c>] (unmap_vmas) from [<c00bc0fc>] (exit_mmap+0xc0/0x1bc)
[190298.865223] [<c00bc0fc>] (exit_mmap) from [<c0026ee8>] (mmput+0x38/0xf4)
[190298.872043] [<c0026ee8>] (mmput) from [<c002b650>] (do_exit+0x354/0x838)
[190298.878862] [<c002b650>] (do_exit) from [<c002cc64>] (do_group_exit+0x48/0xd0)
[190298.886204] [<c002cc64>] (do_group_exit) from [<c002ccfc>] (__wake_up_parent+0x0/0x18)
[190298.894261] Disabling lock debugging due to kernel taint
[190298.899977] BUG: Bad rss-counter state mm:db2e7c00 idx:2 val:-1root@wrtarm:~# sensors
tmp421-i2c-0-4c
Adapter: mv64xxx_i2c adapter
temp1: +40.3°C
temp2: +41.8°C
armada_thermal-virtual-0
Adapter: Virtual device
temp1: +68.5°CWhat are the three thermals? Is armada_thermal-virtual-0 the cpu core? This is actually under idle for some hours.
@davidc502 please compile a image for wrt1200 too with the patch config and I will test it and tell thermals too.
(Last edited by makedir on 18 Dec 2017, 13:57)
davidc502 wrote:
Here is a test build for V1 owners who want to run kernel 4.9. Keep in mind that I don't have a V1 to test with, so you are downloading this at your own risk. Essentially, I just used the patch as was posted previously. Please report back if this works or not. Also, keep an eye on CPU thermals and you might tweak the fan setting to run more often.
I just installed it... I'll let you know what happens. Thank you!
//Brew
S Pimenta wrote:
The Linux Kernel has 4.14 out for a while... And it is an LTS version... @davidc502 when you will start to compile with 4.14 on the WRT3200ACM?
It's going to all depend on when the developers will push the change to trunk. As soon as that is complete then we can start to include them in our builds.
makedir wrote:
WWTK wrote:@makedir I don't find it obvious at all, my 1900acs and 3200acm have never rebooted, not once.
I feel there are multiple issues at play.
Nope. The reason why you dont experience it that often (never so far), is connected with two reasons as I see it. First, there is already a CPUIDLE disable patch included for the three models of 1900acs, 3200 and 1200, because they have all the same CPU (a different one than the 1900v1). Just look into your dmesg boot messages and you will find two lines for this (found armada bla bla is bugged bla cpuidle disabled bla). And you mostly dont do much with your routers triggering high cpu/ram usage. For the first, I guess this patch might not work properly, and still leads to random but rare reboots.
Latest bug:
[190298.776912] swap_free: Bad swap file entry 00000c00 [190298.781933] BUG: Bad page map in process sleep pte:00060000 pmd:1cba5831 [190298.788840] addr:00021000 vm_flags:00000875 anon_vma: (null) mapping:df0ab614 index:11 [190298.796988] file:busybox fault:filemap_fault mmap:generic_file_readonly_mmap readpage:squashfs_readpage [190298.806632] CPU: 1 PID: 20131 Comm: sleep Not tainted 4.9.65 #0 [190298.812664] Hardware name: Marvell Armada 380/385 (Device Tree) [190298.818712] [<c0016010>] (unwind_backtrace) from [<c0012220>] (show_stack+0x10/0x14) [190298.826584] [<c0012220>] (show_stack) from [<c0218580>] (dump_stack+0x7c/0x9c) [190298.833932] [<c0218580>] (dump_stack) from [<c00b5140>] (print_bad_pte+0x154/0x18c) [190298.841713] [<c00b5140>] (print_bad_pte) from [<c00b718c>] (unmap_page_range+0x2f4/0x554) [190298.850015] [<c00b718c>] (unmap_page_range) from [<c00b773c>] (unmap_vmas+0x44/0x54) [190298.857881] [<c00b773c>] (unmap_vmas) from [<c00bc0fc>] (exit_mmap+0xc0/0x1bc) [190298.865223] [<c00bc0fc>] (exit_mmap) from [<c0026ee8>] (mmput+0x38/0xf4) [190298.872043] [<c0026ee8>] (mmput) from [<c002b650>] (do_exit+0x354/0x838) [190298.878862] [<c002b650>] (do_exit) from [<c002cc64>] (do_group_exit+0x48/0xd0) [190298.886204] [<c002cc64>] (do_group_exit) from [<c002ccfc>] (__wake_up_parent+0x0/0x18) [190298.894261] Disabling lock debugging due to kernel taint [190298.899977] BUG: Bad rss-counter state mm:db2e7c00 idx:2 val:-1root@wrtarm:~# sensors tmp421-i2c-0-4c Adapter: mv64xxx_i2c adapter temp1: +40.3°C temp2: +41.8°C armada_thermal-virtual-0 Adapter: Virtual device temp1: +68.5°CWhat are the three thermals? Is armada_thermal-virtual-0 the cpu core? This is actually under idle for some hours.
@davidc502 please compile a image for wrt1200 too with the patch config and I will test it and tell thermals too.
I have the 1200 built from this patch as well, so I'll upload it for you to try tonight.
Brewder wrote:
davidc502 wrote:Here is a test build for V1 owners who want to run kernel 4.9. Keep in mind that I don't have a V1 to test with, so you are downloading this at your own risk. Essentially, I just used the patch as was posted previously. Please report back if this works or not. Also, keep an eye on CPU thermals and you might tweak the fan setting to run more often.
I just installed it... I'll let you know what happens. Thank you!
//Brew
Unfortunately that didn't take long... my 1900ACv1 rebooted after about 17 minutes... So I rolled back to your rock solid r5113 build with Kernel 4.4.93.
//Brew
@makedir
when I had these routers as the main router in the house, first the 1900 then the 3200 they were both running postgresql and bandwidthd and use in excess of 1tb of data per month. I had plenty of issues with the wifi drivers right now my 3200 is throwing tons of these:
[148339.165699] ieee80211 phy1: staid 1 deleted
[148947.254482] ieee80211 phy1: staid 1 deleted
[148949.172862] ieee80211 phy1: staid 1 deleted
[149576.215154] ieee80211 phy1: staid 1 deleted
[150209.150338] ieee80211 phy1: staid 1 deleted
[150848.362196] ieee80211 phy1: staid 1 deleted
[151490.298940] ieee80211 phy1: staid 1 deleted
[152116.218991] ieee80211 phy1: staid 1 deleted
[152759.378607] ieee80211 phy1: staid 1 deleted
[152761.391892] ieee80211 phy1: staid 1 deleted
[153398.413521] ieee80211 phy1: staid 1 deleted
[154334.389553] ieee80211 phy1: staid 1 deleted
[154945.336513] ieee80211 phy1: staid 1 deleted
[155575.319188] ieee80211 phy1: staid 1 deleted
[156208.171174] ieee80211 phy1: staid 1 deleted
[156831.136569] ieee80211 phy1: staid 1 deleted
[157468.029929] ieee80211 phy1: staid 1 deleted
[158097.058509] ieee80211 phy1: staid 1 deleted
[158729.191922] ieee80211 phy1: staid 1 deletedso i'll have to reboot but It is still working as i'm connected through it right now typing this there are currently 144 of these in my dmesg output.
currently my core router is a netgear r8000.
after reboot i see in my dmesg
[ 0.090053] cpuidle: using governor ladder
[ 0.090182] mvebu-pmsu: CPU hotplug support is currently broken on Armada 38x: disabling
[ 0.090188] mvebu-pmsu: CPU idle is currently broken on Armada 38x: disablingI have run them both without an ipv6 and with one just as fyi. I seem to run into routing issues when ipv6 is active with some hardware in the house.
(Last edited by WWTK on 18 Dec 2017, 15:04)
mkdir wrote:
Just look into your dmesg boot messages and you will find two lines for this (found armada bla bla is bugged bla cpuidle disabled bla)
3200acm@r5422:
[ 0.000000] Selected CPU frequency (16) unsupported
[ 0.090045] cpuidle: using governor ladder
[ 0.090174] mvebu-pmsu: CPU hotplug support is currently broken on Armada 38x: disabling
[ 0.090180] mvebu-pmsu: CPU idle is currently broken on Armada 38x: disablingSensors output:
tmp421-i2c-0-4c
Adapter: mv64xxx_i2c adapter
temp1: +48.7°C
temp2: +51.6°C
armada_thermal-virtual-0
Adapter: Virtual device
temp1: +78.9°CIs 78.9°C too high @~90% idle ?
WWTK wrote:
I had plenty of issues with the wifi drivers right now my 3200 is throwing tons of these:
[148339.165699] ieee80211 phy1: staid 1 deleted
[148947.254482] ieee80211 phy1: staid 1 deleted
...............................................................................
For me 11 in ~10hours, but so far wifi seems to be ok:
(btw, what does this log entry mean?)
[ 159.856278] ieee80211 phy1: staid 2 deleted
[ 252.652569] ieee80211 phy0: staid 2 deleted
[ 615.838610] ieee80211 phy1: staid 2 deleted
[ 737.571285] ieee80211 phy1: staid 2 deleted
[ 915.556298] ieee80211 phy0: staid 2 deleted
[ 951.337844] ieee80211 phy1: staid 2 deleted
[ 1419.733830] ieee80211 phy1: staid 2 deleted
[ 1459.533682] ieee80211 phy1: staid 2 deleted
[ 1508.295383] ieee80211 phy1: staid 2 deleted
[10805.043972] ieee80211 phy1: staid 1 deleted
[24821.992634] ieee80211 phy1: staid 1 deletedand a lot of those:
...........................................
[ 35.991549] ieee80211 phy1: change: 0x40
[ 36.031548] ieee80211 phy0: change: 0x60
[ 36.181579] ieee80211 phy1: change: 0x40
[ 36.251561] ieee80211 phy0: change: 0x40
[ 36.381556] ieee80211 phy1: change: 0x40
[ 36.471552] ieee80211 phy0: change: 0x40
[ 36.571551] ieee80211 phy1: change: 0x40
[ 36.691554] ieee80211 phy0: change: 0x40
[ 36.771566] ieee80211 phy1: change: 0x40
[ 36.850586] ieee80211 phy1: change: 0x100
[ 36.911575] ieee80211 phy0: change: 0x40
[ 36.934164] ieee80211 phy1: change: 0x100
...........................................I will wait for a build with kernel 4.14 
(Last edited by Zorr0x on 18 Dec 2017, 19:36)
davidc502 wrote:
Here is a test build for V1 owners who want to run kernel 4.9. Keep in mind that I don't have a V1 to test with, so you are downloading this at your own risk. Essentially, I just used the patch as was posted previously. Please report back if this works or not. Also, keep an eye on CPU thermals and you might tweak the fan setting to run more often.
@davidc502
I also tested this firmware version the router unfortunately rebooted after about 45 minutes.
I monitored the temperature which oddly enough were not getting higher compared to the builds from the LEDE thread.
Router: WRT1900ac v1
Firmware: @davidc502 test build OpenWrt (Linux 4.9.67)
Status: REBOOTING bug not resolved
(Last edited by racef@ce on 18 Dec 2017, 20:20)
racef@ce wrote:
davidc502 wrote:Here is a test build for V1 owners who want to run kernel 4.9. Keep in mind that I don't have a V1 to test with, so you are downloading this at your own risk. Essentially, I just used the patch as was posted previously. Please report back if this works or not. Also, keep an eye on CPU thermals and you might tweak the fan setting to run more often.
@davidc502
I also tested this firmware version the router unfortunately rebooted after about 45 minutes.
I monitored the temperature which oddly enough were not getting higher compared to the builds from the LEDE thread.Router: WRT1900ac v1
Firmware: @davidc502 test build OpenWrt (Linux 4.9.67)
Status: REBOOTING bug not resolved
Thanks for testing though.
Just flashed the latest version. Seems 160Mhz doesn't work on it. No biggie.
[ 164.555694] ------------[ cut here ]------------
[ 164.560394] WARNING: CPU: 0 PID: 7056 at backports-2017-11-01/net/mac80211/ieee80211_i.h:1412 sta_info_alloc+0x2f4/0x3dc [mac80211]
[ 164.572285] Modules linked in: pppoe ppp_async pppox ppp_generic nf_nat_pptp nf_conntrack_pptp nf_conntrack_ipv6 iptable_nat ipt_REJECT ipt_MASQUERADE xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_policy xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_esp xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY ums_usbat ums_sddr55 ums_sddr09 ums_karma ums_jumpshot ums_isd200 ums_freecom ums_datafab ums_cypress ums_alauda ts_fsm ts_bm slhc rfcomm nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_conntrack_ipv4 nf_nat_ipv4 nf_nat_h323 nf_nat_amanda nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp
[ 164.644835] nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_irc nf_conntrack_h323 nf_conntrack_broadcast ts_kmp nf_conntrack_amanda iptable_mangle iptable_filter ipt_ah ipt_ECN ip_tables hidp hci_uart crc_ccitt btusb btmrvl_sdio btmrvl btintel bnep bluetooth fuse sch_cake em_nbyte cls_basic sch_dsmark sch_pie sch_gred sch_teql act_ipt em_text em_meta sch_codel sch_sfq sch_fq act_police sch_prio em_cmp sch_red act_connmark nf_conntrack act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_tbf sch_htb sch_hfsc sch_ingress hid evdev input_core mwlwifi mac80211 cfg80211 compat cryptodev xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport ip_set_hash_netnet ip_set_hash_net ip_set_hash_netportnet ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip<7>[ 164.722265] ieee80211 phy0: change: 0x40
[ 164.726546] ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables msdos bonding ifb tun vfat fat ntfs nls_utf8 nls_iso8859_1 nls_cp437 regmap_mmio sha512_generic sha256_generic md5 hmac ecb cmac authenc ohci_pci uhci_hcd ohci_platform ohci_hcd gpio_button_hotplug
[ 164.761270] CPU: 0 PID: 7056 Comm: hostapd Not tainted 4.9.67 #0
[ 164.762264] ieee80211 phy1: change: 0x40
[ 164.771234] Hardware name: Marvell Armada 380/385 (Device Tree)
[ 164.777190] [<c0016010>] (unwind_backtrace) from [<c0012220>] (show_stack+0x10/0x14)
[ 164.784971] [<c0012220>] (show_stack) from [<c0218520>] (dump_stack+0x7c/0x9c)
[ 164.792224] [<c0218520>] (dump_stack) from [<c00292c8>] (__warn+0xbc/0xec)
[ 164.799128] [<c00292c8>] (__warn) from [<c002939c>] (warn_slowpath_null+0x1c/0x24)
[ 164.806758] [<c002939c>] (warn_slowpath_null) from [<bf19b33c>] (sta_info_alloc+0x2f4/0x3dc [mac80211])
[ 164.816245] [<bf19b33c>] (sta_info_alloc [mac80211]) from [<bf1afc90>] (ieee80211_add_station+0x7c/0x124 [mac80211])
[ 164.826861] [<bf1afc90>] (ieee80211_add_station [mac80211]) from [<bf173860>] (nl80211_new_station+0x330/0x4b8 [cfg80211])
[ 164.837974] [<bf173860>] (nl80211_new_station [cfg80211]) from [<bf1586e8>] (extack_doit+0x2c/0x70 [compat])
[ 164.847853] [<bf1586e8>] (extack_doit [compat]) from [<c03d5548>] (genl_rcv_msg+0x288/0x310)
[ 164.856327] [<c03d5548>] (genl_rcv_msg) from [<c03d48e4>] (netlink_rcv_skb+0x58/0xb4)
[ 164.864189] [<c03d48e4>] (netlink_rcv_skb) from [<c03d52ac>] (genl_rcv+0x20/0x34)
[ 164.871702] [<c03d52ac>] (genl_rcv) from [<c03d42e8>] (netlink_unicast+0x138/0x1fc)
[ 164.879390] [<c03d42e8>] (netlink_unicast) from [<c03d4754>] (netlink_sendmsg+0x2f0/0x310)
[ 164.887692] [<c03d4754>] (netlink_sendmsg) from [<c038f4b4>] (sock_sendmsg+0x14/0x24)
[ 164.895555] [<c038f4b4>] (sock_sendmsg) from [<c038fa44>] (___sys_sendmsg+0x184/0x228)
[ 164.903506] [<c038fa44>] (___sys_sendmsg) from [<c03907e0>] (__sys_sendmsg+0x40/0x64)
[ 164.911371] [<c03907e0>] (__sys_sendmsg) from [<c000ed40>] (ret_fast_syscall+0x0/0x3c)
[ 164.919336] ---[ end trace 2a38521a485fba1d ]---
[ 164.922278] ieee80211 phy1: change: 0x40
[ 164.922286] ieee80211 phy0: change: 0x40
[ 164.932161] ------------[ cut here ]------------
[ 164.936852] WARNING: CPU: 1 PID: 7056 at backports-2017-11-01/net/mac80211/ieee80211_i.h:1412 sta_info_alloc+0x2f4/0x3dc [mac80211]
[ 164.948735] Modules linked in: pppoe ppp_async pppox ppp_generic nf_nat_pptp nf_conntrack_pptp nf_conntrack_ipv6 iptable_nat ipt_REJECT ipt_MASQUERADE xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_policy xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_esp xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY ums_usbat ums_sddr55 ums_sddr09 ums_karma ums_jumpshot ums_isd200 ums_freecom ums_datafab ums_cypress ums_alauda ts_fsm ts_bm slhc rfcomm nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_conntrack_ipv4 nf_nat_ipv4 nf_nat_h323 nf_nat_amanda nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp
[ 165.021176] nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_irc nf_conntrack_h323 nf_conntrack_broadcast ts_kmp nf_conntrack_amanda iptable_mangle iptable_filter ipt_ah ipt_ECN ip_tables hidp hci_uart crc_ccitt btusb btmrvl_sdio btmrvl btintel bnep bluetooth fuse sch_cake em_nbyte cls_basic sch_dsmark sch_pie sch_gred sch_teql act_ipt em_text em_meta sch_codel sch_sfq sch_fq act_police sch_prio em_cmp sch_red act_connmark nf_conntrack act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_tbf sch_htb sch_hfsc sch_ingress hid evdev input_core mwlwifi mac80211 cfg80211 compat cryptodev xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport ip_set_hash_netnet ip_set_hash_net ip_set_hash_netportnet ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables msdos bonding ifb tun vfat fat ntfs nls_utf8 nls_iso8859_1 nls_cp437 regmap_mmio sha512_generic<7>[ 165.122257] ieee80211 phy1: change: 0x40
[ 165.126987] sha256_generic md5 hmac ecb cmac authenc ohci_pci uhci_hcd ohci_platform ohci_hcd gpio_button_hotplug
[ 165.137499] CPU: 1 PID: 7056 Comm: hostapd Tainted: G W 4.9.67 #0
[ 165.142261] ieee80211 phy0: change: 0x60
[ 165.148683] Hardware name: Marvell Armada 380/385 (Device Tree)
[ 165.154635] [<c0016010>] (unwind_backtrace) from [<c0012220>] (show_stack+0x10/0x14)
[ 165.162415] [<c0012220>] (show_stack) from [<c0218520>] (dump_stack+0x7c/0x9c)
[ 165.169668] [<c0218520>] (dump_stack) from [<c00292c8>] (__warn+0xbc/0xec)
[ 165.176571] [<c00292c8>] (__warn) from [<c002939c>] (warn_slowpath_null+0x1c/0x24)
[ 165.184203] [<c002939c>] (warn_slowpath_null) from [<bf19b33c>] (sta_info_alloc+0x2f4/0x3dc [mac80211])
[ 165.193679] [<bf19b33c>] (sta_info_alloc [mac80211]) from [<bf1afc90>] (ieee80211_add_station+0x7c/0x124 [mac80211])
[ 165.204284] [<bf1afc90>] (ieee80211_add_station [mac80211]) from [<bf173860>] (nl80211_new_station+0x330/0x4b8 [cfg80211])
[ 165.215392] [<bf173860>] (nl80211_new_station [cfg80211]) from [<bf1586e8>] (extack_doit+0x2c/0x70 [compat])
[ 165.225268] [<bf1586e8>] (extack_doit [compat]) from [<c03d5548>] (genl_rcv_msg+0x288/0x310)
[ 165.233741] [<c03d5548>] (genl_rcv_msg) from [<c03d48e4>] (netlink_rcv_skb+0x58/0xb4)
[ 165.241603] [<c03d48e4>] (netlink_rcv_skb) from [<c03d52ac>] (genl_rcv+0x20/0x34)
[ 165.248266] ieee80211 phy0: change: 0x100
[ 165.253138] [<c03d52ac>] (genl_rcv) from [<c03d42e8>] (netlink_unicast+0x138/0x1fc)
[ 165.260825] [<c03d42e8>] (netlink_unicast) from [<c03d4754>] (netlink_sendmsg+0x2f0/0x310)
[ 165.269126] [<c03d4754>] (netlink_sendmsg) from [<c038f4b4>] (sock_sendmsg+0x14/0x24)
[ 165.276990] [<c038f4b4>] (sock_sendmsg) from [<c038fa44>] (___sys_sendmsg+0x184/0x228)
[ 165.284941] [<c038fa44>] (___sys_sendmsg) from [<c03907e0>] (__sys_sendmsg+0x40/0x64)
[ 165.292804] [<c03907e0>] (__sys_sendmsg) from [<c000ed40>] (ret_fast_syscall+0x0/0x3c)
[ 165.300832] ---[ end trace 2a38521a485fba1e ]---
[ 165.305638] ------------[ cut here ]------------
[ 165.310316] WARNING: CPU: 1 PID: 7056 at backports-2017-11-01/net/mac80211/ieee80211_i.h:1412 sta_info_alloc+0x2f4/0x3dc [mac80211]
[ 165.322200] Modules linked in:
[ 165.322288] ieee80211 phy1: change: 0x40
[ 165.329035] pppoe ppp_async pppox ppp_generic nf_nat_pptp nf_conntrack_pptp nf_conntrack_ipv6 iptable_nat ipt_REJECT ipt_MASQUERADE xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_policy xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_esp xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_HL xt_DSCP xt_CT xt_CLASSIFY ums_usbat ums_sddr55 ums_sddr09 ums_karma ums_jumpshot ums_isd200 ums_freecom ums_datafab ums_cypress ums_alauda ts_fsm ts_bm slhc rfcomm nf_reject_ipv4 nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_redirect nf_nat_proto_gre nf_nat_masquerade_ipv4 nf_nat_irc nf_conntrack_ipv4 nf_nat_ipv4 nf_nat_h323 nf_nat_amanda nf_nat nf_log_ipv4 nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_tftp nf_conntrack_snmp nf_conntrack_sip nf_conntrack_rtcache nf_conntrack_proto_gre nf_conntrack_irc nf_conntrack_h323 nf_conntrack_broadcast ts_kmp nf_conntrack_amanda iptable_mangle iptable_filter ipt_ah ipt_ECN ip_tables hidp hci_uart crc_ccitt btusb btmrvl_sdio btmrvl btintel bnep bluetooth fuse sch_cake em_nbyte cls_basic sch_dsmark sch_pie sch_gred sch_teql act_ipt em_text em_meta sch_codel sch_sfq sch_fq act_police sch_prio em_cmp sch_red act_connmark nf_conntrack act_skbedit act_mirred em_u32 cls_u32 cls_tcindex cls_flow cls_route cls_fw sch_tbf sch_htb sch_hfsc sch_ingress hid evdev input_core mwlwifi mac80211 cfg80211 compat cryptodev xt_set ip_set_list_set ip_set_hash_netiface ip_set_hash_netport ip_set_hash_netnet ip_set_hash_net ip_set_hash_netportnet ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables x_tables msdos bonding ifb tun vfat fat ntfs nls_utf8 nls_iso8859_1 nls_cp437 regmap_mmio sha512_generic sha256_generic md5 hmac ecb cmac authenc ohci_pci uhci_hcd ohci_platform ohci_hcd gpio_button_hotplug
[ 165.510998] CPU: 1 PID: 7056 Comm: hostapd Tainted: G W 4.9.67 #0
[ 165.512243] ieee80211 phy1: change: 0x40
[ 165.522183] Hardware name: Marvell Armada 380/385 (Device Tree)
[ 165.528136] [<c0016010>] (unwind_backtrace) from [<c0012220>] (show_stack+0x10/0x14)
[ 165.535915] [<c0012220>] (show_stack) from [<c0218520>] (dump_stack+0x7c/0x9c)
[ 165.543169] [<c0218520>] (dump_stack) from [<c00292c8>] (__warn+0xbc/0xec)
[ 165.550073] [<c00292c8>] (__warn) from [<c002939c>] (warn_slowpath_null+0x1c/0x24)
[ 165.557704] [<c002939c>] (warn_slowpath_null) from [<bf19b33c>] (sta_info_alloc+0x2f4/0x3dc [mac80211])
[ 165.567179] [<bf19b33c>] (sta_info_alloc [mac80211]) from [<bf1afc90>] (ieee80211_add_station+0x7c/0x124 [mac80211])
[ 165.577784] [<bf1afc90>] (ieee80211_add_station [mac80211]) from [<bf173860>] (nl80211_new_station+0x330/0x4b8 [cfg80211])
[ 165.588893] [<bf173860>] (nl80211_new_station [cfg80211]) from [<bf1586e8>] (extack_doit+0x2c/0x70 [compat])
[ 165.598769] [<bf1586e8>] (extack_doit [compat]) from [<c03d5548>] (genl_rcv_msg+0x288/0x310)
[ 165.607242] [<c03d5548>] (genl_rcv_msg) from [<c03d48e4>] (netlink_rcv_skb+0x58/0xb4)
[ 165.615104] [<c03d48e4>] (netlink_rcv_skb) from [<c03d52ac>] (genl_rcv+0x20/0x34)
[ 165.622617] [<c03d52ac>] (genl_rcv) from [<c03d42e8>] (netlink_unicast+0x138/0x1fc)
[ 165.630304] [<c03d42e8>] (netlink_unicast) from [<c03d4754>] (netlink_sendmsg+0x2f0/0x310)
[ 165.638604] [<c03d4754>] (netlink_sendmsg) from [<c038f4b4>] (sock_sendmsg+0x14/0x24)
[ 165.646469] [<c038f4b4>] (sock_sendmsg) from [<c038fa44>] (___sys_sendmsg+0x184/0x228)
[ 165.654419] [<c038fa44>] (___sys_sendmsg) from [<c03907e0>] (__sys_sendmsg+0x40/0x64)
[ 165.662283] [<c03907e0>] (__sys_sendmsg) from [<c000ed40>] (ret_fast_syscall+0x0/0x3c)
[ 165.670260] ---[ end trace 2a38521a485fba1f ]---EDIT: That's on the 3200ACM. Forgot to mention it.
EDIT #2: Actually I think it might just not like to change wifi settings on the fly.... odd
(Last edited by farchord on 18 Dec 2017, 22:34)
I just had again another reboot. Of course there is nothing in the logs stored on the usb flash, how would it. I just used a 'logread -f >> /mnt/share/logging.log &' though, so that would never log dmesg outputs I guess, is there a way to write those too to file? Was just switching to my tablet via Synergy and puff, reboot. Weird how it always happens in situations where I do something. Last time it happened the instant where I was opening Luci in web browser. I am still somehow thinking the reboots just began happening after I updated the wifi driver / switched from build r5297. If I google about "Bad page map in process " people tell in other forums this may be related to bad RAM, heat problems, and/or CPU frequency issues.
Is there a way to check if those patches are working / cpuidle is really off (not compiled)? @racef@ce maybe the patch wasnt included in the rom by accident?
How would I properly disable ipv6 too btw, so just to test this theory? I doubt it would do anything about the bad page maps do I also have, which mostly trigger a reboot then once in a while, if it happens to a critical process.
Also the patch for disabling cpuidle and cpufreq wont rise temps really in my understanding because of how a (arm) cmos works. If its idling it doesnt matter much if its clocked 2ghz, 1ghz or 500mhz. It has no influence on the temps because no currents flow.
(Last edited by makedir on 18 Dec 2017, 23:33)
davidc502 wrote:
makedir wrote:WWTK wrote:@makedir I don't find it obvious at all, my 1900acs and 3200acm have never rebooted, not once.
I feel there are multiple issues at play.
Nope. The reason why you dont experience it that often (never so far), is connected with two reasons as I see it. First, there is already a CPUIDLE disable patch included for the three models of 1900acs, 3200 and 1200, because they have all the same CPU (a different one than the 1900v1). Just look into your dmesg boot messages and you will find two lines for this (found armada bla bla is bugged bla cpuidle disabled bla). And you mostly dont do much with your routers triggering high cpu/ram usage. For the first, I guess this patch might not work properly, and still leads to random but rare reboots.
Latest bug:
[190298.776912] swap_free: Bad swap file entry 00000c00 [190298.781933] BUG: Bad page map in process sleep pte:00060000 pmd:1cba5831 [190298.788840] addr:00021000 vm_flags:00000875 anon_vma: (null) mapping:df0ab614 index:11 [190298.796988] file:busybox fault:filemap_fault mmap:generic_file_readonly_mmap readpage:squashfs_readpage [190298.806632] CPU: 1 PID: 20131 Comm: sleep Not tainted 4.9.65 #0 [190298.812664] Hardware name: Marvell Armada 380/385 (Device Tree) [190298.818712] [<c0016010>] (unwind_backtrace) from [<c0012220>] (show_stack+0x10/0x14) [190298.826584] [<c0012220>] (show_stack) from [<c0218580>] (dump_stack+0x7c/0x9c) [190298.833932] [<c0218580>] (dump_stack) from [<c00b5140>] (print_bad_pte+0x154/0x18c) [190298.841713] [<c00b5140>] (print_bad_pte) from [<c00b718c>] (unmap_page_range+0x2f4/0x554) [190298.850015] [<c00b718c>] (unmap_page_range) from [<c00b773c>] (unmap_vmas+0x44/0x54) [190298.857881] [<c00b773c>] (unmap_vmas) from [<c00bc0fc>] (exit_mmap+0xc0/0x1bc) [190298.865223] [<c00bc0fc>] (exit_mmap) from [<c0026ee8>] (mmput+0x38/0xf4) [190298.872043] [<c0026ee8>] (mmput) from [<c002b650>] (do_exit+0x354/0x838) [190298.878862] [<c002b650>] (do_exit) from [<c002cc64>] (do_group_exit+0x48/0xd0) [190298.886204] [<c002cc64>] (do_group_exit) from [<c002ccfc>] (__wake_up_parent+0x0/0x18) [190298.894261] Disabling lock debugging due to kernel taint [190298.899977] BUG: Bad rss-counter state mm:db2e7c00 idx:2 val:-1root@wrtarm:~# sensors tmp421-i2c-0-4c Adapter: mv64xxx_i2c adapter temp1: +40.3°C temp2: +41.8°C armada_thermal-virtual-0 Adapter: Virtual device temp1: +68.5°CWhat are the three thermals? Is armada_thermal-virtual-0 the cpu core? This is actually under idle for some hours.
@davidc502 please compile a image for wrt1200 too with the patch config and I will test it and tell thermals too.
I have the 1200 built from this patch as well, so I'll upload it for you to try tonight.
The patch didn't appear to work, so I don't know if you even want to try the 1200 build?
@davidc502 There seem to be more people saying it works (in the lede thread), than just one person here that is is not. This isnt meant in a mean way, just rational thinking. Are you sure you put the correct file in the zip for him, are you sure you attached the patch correctly? Thats why I asked, if there is a way maybe to verify it, if cpuidle and cpufreq are disabled via the patch.
(Last edited by makedir on 19 Dec 2017, 12:48)
Hey guys,
My wireless clients get disconnected very frequently, don't know what i causing this. Sick and tired of searching in Google..
I have r5501 snapshot from David.
System Log
Tue Dec 19 20:47:43 2017 daemon.info dnsmasq-dhcp[3200]: DHCPDISCOVER(br-lan) 64:bc:0c:82:56:2c
Tue Dec 19 20:47:43 2017 daemon.info dnsmasq-dhcp[3200]: DHCPOFFER(br-lan) 10.0.0.168 64:bc:0c:82:56:2c
Tue Dec 19 20:47:43 2017 daemon.info dnsmasq-dhcp[3200]: DHCPREQUEST(br-lan) 10.0.0.168 64:bc:0c:82:56:2c
Tue Dec 19 20:47:43 2017 daemon.info dnsmasq-dhcp[3200]: DHCPACK(br-lan) 10.0.0.168 64:bc:0c:82:56:2c
Tue Dec 19 20:47:44 2017 daemon.info hostapd: wlan0: STA 64:bc:0c:82:56:2c IEEE 802.11: authenticated
Tue Dec 19 21:05:14 2017 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED ac:fd:ce:68:62:71Kernel log
[ 715.373083] ieee80211 phy1: staid 4 deleted
[ 1018.375560] ieee80211 phy1: staid 2 deleted
[ 1733.565729] ieee80211 phy0: staid 1 deleted
[ 1951.439204] ieee80211 phy0: staid 1 deleted
[ 1977.669814] ieee80211 phy0: staid 1 deleted
[ 2014.172222] ieee80211 phy0: staid 1 deleted
[ 2233.142886] ieee80211 phy1: staid 3 deleted
[ 2467.986306] ieee80211 phy1: staid 3 deleted
[ 3368.004484] ieee80211 phy1: staid 3 deleted
[ 3413.044021] ieee80211 phy1: staid 3 deleted
[ 3457.069403] ieee80211 phy1: staid 3 deleted
[ 3465.344312] ieee80211 phy1: staid 3 deleted
[ 3477.519148] ieee80211 phy1: staid 3 deleted
[ 3499.275725] ieee80211 phy1: staid 3 deleted
[ 3515.565832] ieee80211 phy1: staid 3 deleted
[ 3542.668437] ieee80211 phy1: staid 3 deleted
[ 4662.182224] ieee80211 phy1: staid 3 deleted
[ 5623.253322] ieee80211 phy1: staid 4 deleted
[ 5712.395938] ieee80211 phy1: staid 3 deleted
[ 5949.133870] ieee80211 phy1: staid 2 deleted
[ 6134.429592] ieee80211 phy1: staid 3 deleted
[ 6261.546953] ieee80211 phy1: staid 2 deleted
[ 6623.586844] ieee80211 phy1: staid 2 deleted
[ 7126.227137] ieee80211 phy1: staid 2 deleted
[ 7294.155539] ieee80211 phy1: staid 1 deleted
[ 7955.823344] ieee80211 phy1: staid 2 deleted
[ 8090.344810] ieee80211 phy1: staid 3 deleted
[ 9118.388395] ieee80211 phy1: staid 2 deleted
[ 9153.208856] ieee80211 phy1: staid 2 deleted
[ 9156.828817] ieee80211 phy1: staid 2 deleted
[ 9409.586370] ieee80211 phy1: staid 2 deleted
[ 9446.710827] ieee80211 phy1: staid 2 deleted
[12372.113966] ieee80211 phy1: staid 2 deleted
[12529.267802] ieee80211 phy1: staid 4 deleted
[12583.480166] ieee80211 phy1: staid 2 deleted
[12897.520569] ieee80211 phy1: staid 2 deleted
[13344.288762] ieee80211 phy1: staid 1 deleted
[13413.506611] ieee80211 phy0: staid 1 deleted
[13428.842346] ieee80211 phy1: staid 4 deleted
[14993.716641] ieee80211 phy1: staid 1 deleted
[16044.612990] ieee80211 phy0: staid 1 deletedLinux, Android, Windows..doesn't matter the OS, when I get a system log like the one I posted, that device will lost connectivity..
I'm really losing the hope on getting this device stable..
Best regards and I hope someone can help me
(Last edited by Icipher on 19 Dec 2017, 22:25)
Icipher wrote:
Hey guys,
My wireless clients get disconnected very frequently, don't know what i causing this. Sick and tired of searching in Google..I have r5501 snapshot from David.
System Log
Tue Dec 19 20:47:43 2017 daemon.info dnsmasq-dhcp[3200]: DHCPDISCOVER(br-lan) 64:bc:0c:82:56:2c Tue Dec 19 20:47:43 2017 daemon.info dnsmasq-dhcp[3200]: DHCPOFFER(br-lan) 10.0.0.168 64:bc:0c:82:56:2c Tue Dec 19 20:47:43 2017 daemon.info dnsmasq-dhcp[3200]: DHCPREQUEST(br-lan) 10.0.0.168 64:bc:0c:82:56:2c Tue Dec 19 20:47:43 2017 daemon.info dnsmasq-dhcp[3200]: DHCPACK(br-lan) 10.0.0.168 64:bc:0c:82:56:2c Tue Dec 19 20:47:44 2017 daemon.info hostapd: wlan0: STA 64:bc:0c:82:56:2c IEEE 802.11: authenticated Tue Dec 19 21:05:14 2017 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED ac:fd:ce:68:62:71Kernel log
[ 715.373083] ieee80211 phy1: staid 4 deleted [ 1018.375560] ieee80211 phy1: staid 2 deleted [ 1733.565729] ieee80211 phy0: staid 1 deleted [ 1951.439204] ieee80211 phy0: staid 1 deleted [ 1977.669814] ieee80211 phy0: staid 1 deleted [ 2014.172222] ieee80211 phy0: staid 1 deleted [ 2233.142886] ieee80211 phy1: staid 3 deleted [ 2467.986306] ieee80211 phy1: staid 3 deleted [ 3368.004484] ieee80211 phy1: staid 3 deleted [ 3413.044021] ieee80211 phy1: staid 3 deleted [ 3457.069403] ieee80211 phy1: staid 3 deleted [ 3465.344312] ieee80211 phy1: staid 3 deleted [ 3477.519148] ieee80211 phy1: staid 3 deleted [ 3499.275725] ieee80211 phy1: staid 3 deleted [ 3515.565832] ieee80211 phy1: staid 3 deleted [ 3542.668437] ieee80211 phy1: staid 3 deleted [ 4662.182224] ieee80211 phy1: staid 3 deleted [ 5623.253322] ieee80211 phy1: staid 4 deleted [ 5712.395938] ieee80211 phy1: staid 3 deleted [ 5949.133870] ieee80211 phy1: staid 2 deleted [ 6134.429592] ieee80211 phy1: staid 3 deleted [ 6261.546953] ieee80211 phy1: staid 2 deleted [ 6623.586844] ieee80211 phy1: staid 2 deleted [ 7126.227137] ieee80211 phy1: staid 2 deleted [ 7294.155539] ieee80211 phy1: staid 1 deleted [ 7955.823344] ieee80211 phy1: staid 2 deleted [ 8090.344810] ieee80211 phy1: staid 3 deleted [ 9118.388395] ieee80211 phy1: staid 2 deleted [ 9153.208856] ieee80211 phy1: staid 2 deleted [ 9156.828817] ieee80211 phy1: staid 2 deleted [ 9409.586370] ieee80211 phy1: staid 2 deleted [ 9446.710827] ieee80211 phy1: staid 2 deleted [12372.113966] ieee80211 phy1: staid 2 deleted [12529.267802] ieee80211 phy1: staid 4 deleted [12583.480166] ieee80211 phy1: staid 2 deleted [12897.520569] ieee80211 phy1: staid 2 deleted [13344.288762] ieee80211 phy1: staid 1 deleted [13413.506611] ieee80211 phy0: staid 1 deleted [13428.842346] ieee80211 phy1: staid 4 deleted [14993.716641] ieee80211 phy1: staid 1 deleted [16044.612990] ieee80211 phy0: staid 1 deletedLinux, Android, Windows..doesn't matter the OS, when I get a system log like the one I posted, that device will lost connectivity..
I'm really losing the hope on getting this device stable..Best regards and I hope someone can help me
Those are all normal logs. Have you tried the standard lede build or DD-WRT and see if the same is happening?
makedir wrote:
@davidc502 There seem to be more people saying it works (in the lede thread), than just one person here that is is not. This isnt meant in a mean way, just rational thinking. Are you sure you put the correct file in the zip for him, are you sure you attached the patch correctly? Thats why I asked, if there is a way maybe to verify it, if cpuidle and cpufreq are disabled via the patch.
I'll look through the thread and see if there's anything I'm missing.
Hey David,
I though that those logs were something related with disconnections (things found in git issues and openwrt forum)
I only tried this device with your builds (a lot of them), I will try with standard lede and report back then
Am I the only one reporting something like this?
Regards
Icipher wrote:
Hey David,
I though that those logs were something related with disconnections (things found in git issues and openwrt forum)
I only tried this device with your builds (a lot of them), I will try with standard lede and report back then
Am I the only one reporting something like this?
Regards
As far as I know there are no disconnect issues going on right now... However, that doesn't mean that you are not having a problem.
Just to make sure we are on the same page... So, you can be logged into your phone and watching a video (for example) and are getting disconnects? These are happening while you are active on your phones, and not when the screen goes dark after the phone or device has been set down for a few minutes?
davidc502 wrote:
makedir wrote:@davidc502 There seem to be more people saying it works (in the lede thread), than just one person here that is is not. This isnt meant in a mean way, just rational thinking. Are you sure you put the correct file in the zip for him, are you sure you attached the patch correctly? Thats why I asked, if there is a way maybe to verify it, if cpuidle and cpufreq are disabled via the patch.
I'll look through the thread and see if there's anything I'm missing.
I see there is a revision in NainKult's patch. It was probably out there the other day and I just didn't notice it. Will give that patch a try.
*EDIT*
I believe the revision was already out there because I'm getting the same message from the patcher that I got the first time.
(Last edited by davidc502 on 20 Dec 2017, 02:09)
Just been the one I think, reworked for the updated config-4.9 posted since the patch was put in the thread. Not convinced as to the wisdom of this on other members of the wrtpac than the mamba, but...
Edit: I'm at r5578-f704b64
Edit2: I just built with that patch and no questions, so I think it's good, but let me know if not.
(Last edited by Villeneuve on 20 Dec 2017, 02:56)
Villeneuve wrote:
Just been the one I think, reworked for the updated config-4.9 posted since the patch was put in the thread. Not convinced as to the wisdom of this on other members of the wrtpac than the mamba, but...
Edit: I'm at r5578-f704b64
Thanks Villeneuve
Just posted out on lede, and didn't know how I should answer some of the questions during the initial startup of the new config after patching.
Icipher wrote:
Hey David,
I though that those logs were something related with disconnections (things found in git issues and openwrt forum)
I only tried this device with your builds (a lot of them), I will try with standard lede and report back then
Am I the only one reporting something like this?
Regards
There are known issues with stock firmware for the 3200acm per the stickied Linksys thread at http://community.linksys.com/t5/Wireles … -p/1246764. Essentially devices are saying they are connected to wifi, but aren't actually getting an internet connection.
I don't know how much of the stock code makes it into the open source builds, but I know I had major issues with more recent builds using firmware from this Nov/Dec which mimicked my issues with stock firmware. So far I have had decent luck running LEDE stable or an older build from David from around October, but newer builds caused wifi instability with me.
Just my experience - i know others are having great luck with the most recent builds.
(Last edited by AjkayAlan on 20 Dec 2017, 05:23)
davidc502 wrote:
Here is a test build for V1 owners who want to run kernel 4.9. Keep in mind that I don't have a V1 to test with, so you are downloading this at your own risk. Essentially, I just used the patch as was posted previously. Please report back if this works or not. Also, keep an eye on CPU thermals and you might tweak the fan setting to run more often.
2nd attempt at patching the V1 for the 4.9 kernel. Please let me know if the results change.
Sorry, posts 4351 to 4350 are missing from our archive.
Page 174 of 229