R8000 - Kernel panic: Oops - BUG: 80000007 [#1] SMP ARM

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3  Next
Author Message
basofree
DD-WRT Novice


Joined: 12 Apr 2014
Posts: 14

PostPosted: Fri May 15, 2020 11:01    Post subject: Trying experimental build now Reply with quote
Hi there,

After some more dhd kernel panic reboots of the nETGEAR R8000 on r43078 and r43099 as well as r43136 (uptime ~ 2-3 days) I'm now shifting over to r43136-experimental_driver.

I haven't done a reset, yet - so currently both, the old settings for wl-interfaces and the new ath-interfaces, are stored in the nvram.

EDIT: I've deactivated the "Single User Beamforming" option - I guess it is the same as on the old driver - but unsure. Edit: The 5GHz interfaces won't come up.

Thumbs pressed

_________________
Qualcom/Atheros:
R9000 DD-WRT v3.0-r44251 std
WNDR3800 DD-WRT
Broadcom ARM:
R8000 DD-WRT v3.0-r44251 std (w/ experimental_driver)
R7000 DD-WRT v3.0-r44251 std
R6400 DD-WRT v3.0-r44251 std
Broadcom:
WRT610Nv1 DD-WRT mega
WRT160Nv1 DD-WRT vpn
WHR-G54S DD-WRT vpn

Using: OpenVPN,Wireguard,(VAP),DNSSEC,DDNS,JFFS2,QoS,NAT,DHCP client/server(multiple,static/dynamic),PPPoE,Telnet,SSH,WOL
Sponsor
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 7245
Location: Texas, USA

PostPosted: Fri May 15, 2020 13:39    Post subject: Reply with quote
Reset and configure from scratch.
_________________
Official Forum Rules, Guidelines, and Helpful InformationFirmware FAQInstallation WikiWhere Do I Download Firmware?
DON'T use Chromium-based browsersRTFM/STFW - TL;DR is NOT an excuse. • Why Should I Care What Color the Bikeshed Is?
Please DO NOT PM me with questions; Ask in the forum.

---------------------------------------------------------

Linux User #377467 counter.li.org / linuxcounter.net
basofree
DD-WRT Novice


Joined: 12 Apr 2014
Posts: 14

PostPosted: Tue May 19, 2020 12:00    Post subject: Reset - running on r43171 Reply with quote
Hi there,

Yes, I was going to reset anyway and configure from scratch anyway.

So, what I can say is...:

Before reset:
- ... that the 5 GHz² (ath 0 or 2) LED stays off - although it is up and I'm able to connect
- ... that the NETGEAR R8000 was running more than three days. Nevertheless, one of the 5 Ghz² interfaces went "away" > it wasn't present anymore.
- that the 5 GHz (ath2 !) network may not be properly bridged (wild guess) - devices like Google Chromecast aren't shown as available when connected to the 5 Ghz (ath2 !) network and the android device using the app is on the same network - I have to connect to the 2.4 Ghz network with another SSID to be able to manage the Chromecast devices (this problem is new - and wasn't present using dhd instead of brcmfmac[experimental driver])

After full reset and re-configuration (not enough time passed by to tell):
- ... that the 5 GHz² (ath 0 or 2) LED stays off - although it is up and I'm able to connect
- that the 5 GHz(ath2 !) network may not be properly bridged (wild guess) - devices like Google Chromecast aren't shown as available when connected to the 5 Ghz (ath2 !) network and the android device using the app is on the same network - I have to connect to the 2.4 Ghz network with another SSID to be able to manage the Chromecast devices (this problem is new - and wasn't present using dhd instead of brcmfmac[experimental driver])

_________________
Qualcom/Atheros:
R9000 DD-WRT v3.0-r44251 std
WNDR3800 DD-WRT
Broadcom ARM:
R8000 DD-WRT v3.0-r44251 std (w/ experimental_driver)
R7000 DD-WRT v3.0-r44251 std
R6400 DD-WRT v3.0-r44251 std
Broadcom:
WRT610Nv1 DD-WRT mega
WRT160Nv1 DD-WRT vpn
WHR-G54S DD-WRT vpn

Using: OpenVPN,Wireguard,(VAP),DNSSEC,DDNS,JFFS2,QoS,NAT,DHCP client/server(multiple,static/dynamic),PPPoE,Telnet,SSH,WOL
zigzap
DD-WRT Novice


Joined: 12 May 2020
Posts: 2

PostPosted: Sun May 24, 2020 9:08    Post subject: Re: Reset - running on r43171 Reply with quote
basofree wrote:
Hi there,

Yes, I was going to reset anyway and configure from scratch anyway.

So, what I can say is...:

Before reset:
- ... that the 5 GHz² (ath 0 or 2) LED stays off - although it is up and I'm able to connect
- ... that the NETGEAR R8000 was running more than three days. Nevertheless, one of the 5 Ghz² interfaces went "away" > it wasn't present anymore.
- that the 5 GHz (ath2 !) network may not be properly bridged (wild guess) - devices like Google Chromecast aren't shown as available when connected to the 5 Ghz (ath2 !) network and the android device using the app is on the same network - I have to connect to the 2.4 Ghz network with another SSID to be able to manage the Chromecast devices (this problem is new - and wasn't present using dhd instead of brcmfmac[experimental driver])

After full reset and re-configuration (not enough time passed by to tell):
- ... that the 5 GHz² (ath 0 or 2) LED stays off - although it is up and I'm able to connect
- that the 5 GHz(ath2 !) network may not be properly bridged (wild guess) - devices like Google Chromecast aren't shown as available when connected to the 5 Ghz (ath2 !) network and the android device using the app is on the same network - I have to connect to the 2.4 Ghz network with another SSID to be able to manage the Chromecast devices (this problem is new - and wasn't present using dhd instead of brcmfmac[experimental driver])


Did you find a new frimware that solves the problem and works well with r8000? My version r43136 dhd does not work well and I had alott of different issues with WiFi when using the experemental driver same build.
basofree
DD-WRT Novice


Joined: 12 Apr 2014
Posts: 14

PostPosted: Sun May 24, 2020 10:56    Post subject: Re: Reset - running on r43171 Reply with quote
zigzap wrote:

Did you find a new frimware that solves the problem and works well with r8000? My version r43136 dhd does not work well and I had alott of different issues with WiFi when using the experemental driver same build.

Hi zigzap,
I'm currently in a similar situation.
On my R8000 the dhd-versions leads to crashes.
Try the new experimental beta: /05-22-2020-r43217/netgear-r8000/experimental_driver/. But please reset and reconfigure completely.

Nevertheless, these are the problems I'm experiencing with r43217-experimental_driver on the NETGEAR R8000 right now:

    - WiFi 5GHz² LED not working
    - WLAN devices won't properly come up after WiFi on/off button pressed, to disable/enable it
    - [Edit] WLAN devices crash after some time
    - Problems in discovering network services (like Google Chromecast - it seems like the networks are "mixed up" (wild guess) - Maybe [43219] by brainslayer - to fix allocation bug in nand driver will help [waiting for new build]
    - JFFS size display bug [as mentioned in the build thread]

_________________
Qualcom/Atheros:
R9000 DD-WRT v3.0-r44251 std
WNDR3800 DD-WRT
Broadcom ARM:
R8000 DD-WRT v3.0-r44251 std (w/ experimental_driver)
R7000 DD-WRT v3.0-r44251 std
R6400 DD-WRT v3.0-r44251 std
Broadcom:
WRT610Nv1 DD-WRT mega
WRT160Nv1 DD-WRT vpn
WHR-G54S DD-WRT vpn

Using: OpenVPN,Wireguard,(VAP),DNSSEC,DDNS,JFFS2,QoS,NAT,DHCP client/server(multiple,static/dynamic),PPPoE,Telnet,SSH,WOL


Last edited by basofree on Sun May 24, 2020 13:22; edited 1 time in total
buffpatel
DD-WRT User


Joined: 22 Feb 2011
Posts: 100

PostPosted: Sun May 24, 2020 11:23    Post subject: Reply with quote
Hi, quick update.

I'm running newest build r43217 (5/22/20) with experimental driver on my R8000.
The reboots are about the same maybe every 2-3 days.

One new thing that has popped up is that after ~24 hours of up time my wireless radios will simply stop working and become disabled. This happens on both R8000's after ~1 day of uptime. When this happens, if I click on the wireless status it'll only act as if ath0 is the only radio I have and the channel will be blank and I can't choose a channel. On the Wireless Status page it just says my radio is unknown. (I attached screen shots).

ath1 despite not being able to be managed in the GUI, never actually gets disabled. I can still connect to it. I don't have any error messages for it in my logs.

For ath0: My log says "Firmware has Crashed" and a few seconds later says that ath0 has entered disabled state. I also get an error code that says: BUG: Bad page state in process modprobe pfn:069cf. I pasted the log at the bottom in this message.

For ath2: it usually enters disabled state first before the firmware crashed error message. I see lots of error messages with some accounting sessions and devices associating and disassociatin and eventually ath2 enters disabled state. Interestingly the 2 mac addresses that have those error messages are my two android devices. That log is attached as a file.

May 24 06:56:55 R8000 kernel 0001:01:00.0: CONSOLE: 118218.693 wl0: wlc_bmac_processpmq: skip entry with mc/bc address 9b:aa:7d:31:4b:be
May 24 06:56:55 R8000 kernel 0001:01:00.0: CONSOLE: 118218.731 wl0: wlc_bmac_processpmq: skip entry with mc/bc address 9b:aa:7d:31:4b:be
May 24 06:56:55 R8000 kernel 0001:01:00.0: CONSOLE: 118218.769 wl0: wlc_bmac_processpmq: skip entry with mc/bc address 9b:aa:7d:31:4b:be
May 24 06:56:55 R8000 kernel 0001:01:00.0: CONSOLE: 118218.799 wl0: wlc_bmac_processpmq: skip entry with mc/bc address 9b:aa:7d:31:4b:be
May 24 06:56:57 R8000 kernel ieee80211 phy0: brcmf_fw_crashed: Firmware has halted or crashed
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE: 118220.192
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE: FWID 01-de3d698f
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE: flags 110005
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE: 118220.193
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE: TRAP 7(26fea8): pc 1871b8, lr 1867e9, sp 26ff00, cpsr 600001df, spsr 600001bf
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE: 118220.193 r0 1000000, r1 40000000, r2 40, r3 25f2f8, r4 1fca98, r5 26af20, r6 25f2f0
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE: 118220.193 r7 25eaa4, r8 25f2f8, r9 0, r10 fee747d1, r11 9445a005, r12 5a60090
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE: 118220.193
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE: sp+0 00000000 0026af20 00000000 0018861d
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE: 118220.193 sp+10 00000000 0025f3c0 00000000 0018078c
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE:
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE: 118220.193 sp+c 0018861d
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE: 118220.193 sp+2c 00006fc7
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE: 118220.193 sp+30 00006f9d
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE: 118220.193 sp+3c 00007005
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE: 118220.193 sp+4c 00007243
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE: 118220.193 sp+5c 00183825
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE: 118220.193 sp+70 001837f9
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE: 118220.193 sp+8c 001823d7
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE: 118220.193 sp+98 000001df
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE: 118220.193 sp+d8 000071df
May 24 06:56:57 R8000 kernel 0001:01:00.0: CONSOLE: 118220.193 sp+e8 00188e59
May 24 06:56:57 R8000 kernel ieee80211 phy0: brcmf_netdev_start_xmit: xmit rejected state=0
May 24 06:56:58 R8000 kernel ieee80211 phy0: brcmf_fil_cmd_data: bus is down. we have nothing to do.
May 24 06:56:58 R8000 kernel ieee80211 phy0: brcmf_fil_cmd_data: bus is down. we have nothing to do.
May 24 06:56:58 R8000 kernel ieee80211 phy0: brcmf_cfg80211_stop_ap: SET SSID error (-5)
May 24 06:56:58 R8000 kernel ieee80211 phy0: brcmf_fil_cmd_data: bus is down. we have nothing to do.
May 24 06:56:58 R8000 kernel ieee80211 phy0: brcmf_cfg80211_stop_ap: BRCMF_C_DOWN error -5
May 24 06:56:58 R8000 kernel ieee80211 phy0: brcmf_fil_cmd_data: bus is down. we have nothing to do.
May 24 06:56:58 R8000 kernel ieee80211 phy0: brcmf_cfg80211_stop_ap: setting AP mode failed -5
May 24 06:56:58 R8000 kernel ieee80211 phy0: brcmf_fil_cmd_data: bus is down. we have nothing to do.
May 24 06:56:58 R8000 kernel br0: port 2(ath0) entered disabled state
May 24 06:56:58 R8000 kernel device ath0 left promiscuous mode
May 24 06:56:58 R8000 kernel br0: port 2(ath0) entered disabled state
May 24 06:56:58 R8000 kernel brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43602-pcie for chip BCM43602/1
May 24 06:56:58 R8000 kernel brcmfmac 0001:01:00.0: Direct firmware load for M failed with error -2
May 24 06:56:58 R8000 kernel brcmfmac 0001:01:00.0: Direct firmware load for brcm/brcmfmac43602-pcie.txt failed with error -2
May 24 06:57:01 R8000 httpd httpd : Request Error Code 404: File favicon.ico not found.
May 24 06:57:01 R8000 kernel BUG: Bad page state in process modprobe pfn:069cf
May 24 06:57:01 R8000 kernel page:86ecb9e0 count:-1 mapcount:0 mapping: (null) index:0x0
May 24 06:57:01 R8000 kernel flags: 0x0()
May 24 06:57:01 R8000 kernel page dumped because: nonzero _count
May 24 06:57:01 R8000 kernel Modules linked in: xt_IMQ imq ebtable_nat ebtables ksmbd ext4 jbd2 mbcache fuse crc16 tun usb_storage sr_mod cdrom sd_mod scsi_mod xhci_plat_hcd xhci_pci xhci_hcd ohci_pci ohci_hcd ehci_pci ehci_hcd usbcore usb_common xt_physdev
May 24 06:57:01 R8000 kernel CPU: 0 PID: 18165 Comm: modprobe Tainted: P 4.4.224 #199
May 24 06:57:01 R8000 kernel Hardware name: Northstar Prototype
May 24 06:57:01 R8000 kernel Backtrace:
May 24 06:57:01 R8000 kernel [<8001b2f8>] (dump_backtrace) from [<8001b9b8>] (show_stack+0x18/0x1c)
May 24 06:57:01 R8000 kernel r7:86ecb9e0 r6:60000013 r5:00000000 r4:80537060
May 24 06:57:01 R8000 kernel [<8001b9a0>] (show_stack) from [<8016d4f8>] (dump_stack+0x94/0xa8)
May 24 06:57:01 R8000 kernel [<8016d464>] (dump_stack) from [<800a0a54>] (bad_page+0x114/0x12c)
May 24 06:57:01 R8000 kernel r7:86ecb9e0 r6:80524100 r5:80596ae4 r4:ffffffff
May 24 06:57:01 R8000 kernel [<800a0940>] (bad_page) from [<800a4008>] (get_page_from_freelist+0x9a8/0xc64)
May 24 06:57:01 R8000 kernel r10:86ecb9e0 r9:00000200 r8:8045cf9c r7:8045cf88 r6:00000001 r5:00000000
May 24 06:57:01 R8000 kernel r4:ffffffff r3:00000000
May 24 06:57:01 R8000 kernel [<800a3660>] (get_page_from_freelist) from [<800a438c>] (__alloc_pages_nodemask+0xc8/0x78c)
May 24 06:57:01 R8000 kernel r10:02000200 r9:80525954 r8:86808df0 r7:00000000 r6:76f22000 r5:02000200
May 24 06:57:01 R8000 kernel r4:00000000
May 24 06:57:01 R8000 kernel [<800a42c4>] (__alloc_pages_nodemask) from [<800a4a68>] (__get_free_pages+0x18/0x34)
May 24 06:57:01 R8000 kernel r10:76f24000 r9:85a7de00 r8:86808df0 r7:86808fa8 r6:76f22000 r5:86808f50
May 24 06:57:01 R8000 kernel r4:870de3c0
May 24 06:57:01 R8000 kernel [<800a4a50>] (__get_free_pages) from [<800baf9c>] (unmap_region+0x78/0x174)
May 24 06:57:01 R8000 kernel [<800baf24>] (unmap_region) from [<800bd4dc>] (do_munmap+0x29c/0x3dc)
May 24 06:57:01 R8000 kernel r10:870de3c4 r9:86808f50 r8:76f22000 r7:76f24000 r6:870de3c0 r5:86808fa8
May 24 06:57:01 R8000 kernel r4:00000000
May 24 06:57:01 R8000 kernel [<800bd240>] (do_munmap) from [<800bdcc4>] (mmap_region+0x170/0x638)
May 24 06:57:01 R8000 kernel r10:870de3c0 r9:870de3c4 r8:76f24000 r7:86808670 r6:00002000 r5:76f22000
May 24 06:57:01 R8000 kernel r4:86808f68
May 24 06:57:01 R8000 kernel [<800bdb54>] (mmap_region) from [<800be548>] (do_mmap+0x3bc/0x46c)
May 24 06:57:01 R8000 kernel r10:870de3c0 r9:805259e4 r8:00000002 r7:76f22000 r6:8601a700 r5:00000073
May 24 06:57:01 R8000 kernel r4:00002000
May 24 06:57:01 R8000 kernel [<800be18c>] (do_mmap) from [<800ae368>] (vm_mmap_pgoff+0x74/0xa4)
May 24 06:57:01 R8000 kernel r10:000000c0 r9:00000003 r8:00002000 r7:76f22000 r6:00000000 r5:870de3fc
May 24 06:57:01 R8000 kernel r4:85a7df38
May 24 06:57:01 R8000 kernel [<800ae2f4>] (vm_mmap_pgoff) from [<800bc984>] (SyS_mmap_pgoff+0x8c/0xc0)
May 24 06:57:01 R8000 kernel r9:85a7c000 r8:8601a700 r7:76f22000 r6:00002000 r5:00000003 r4:00000012
May 24 06:57:01 R8000 kernel [<800bc8f8>] (SyS_mmap_pgoff) from [<80009560>] (ret_fast_syscall+0x0/0x40)
May 24 06:57:01 R8000 kernel r8:80009744 r7:000000c0 r6:00000012 r5:00000005 r4:00000000
May 24 06:57:05 R8000 kernel BUG: Bad page state in process kworker/u4:0 pfn:069d0
May 24 06:57:05 R8000 kernel page:86ecba00 count:-1 mapcount:0 mapping: (null) index:0x0
May 24 06:57:05 R8000 kernel flags: 0x0()
May 24 06:57:05 R8000 kernel page dumped because: nonzero _count
May 24 06:57:05 R8000 kernel Modules linked in: xt_IMQ imq ebtable_nat ebtables ksmbd ext4 jbd2 mbcache fuse crc16 tun usb_storage sr_mod cdrom sd_mod scsi_mod xhci_plat_hcd xhci_pci xhci_hcd ohci_pci ohci_hcd ehci_pci ehci_hcd usbcore usb_common xt_physdev
May 24 06:57:05 R8000 kernel CPU: 0 PID: 18072 Comm: kworker/u4:0 Tainted: P B 4.4.224 #199
May 24 06:57:05 R8000 kernel Hardware name: Northstar Prototype
May 24 06:57:05 R8000 kernel Workqueue: events_unbound call_usermodehelper_exec_work
May 24 06:57:05 R8000 kernel Backtrace:
May 24 06:57:05 R8000 kernel [<8001b2f8>] (dump_backtrace) from [<8001b9b8>] (show_stack+0x18/0x1c)
May 24 06:57:05 R8000 kernel r7:86ecba00 r6:60000013 r5:00000000 r4:80537060
May 24 06:57:05 R8000 kernel [<8001b9a0>] (show_stack) from [<8016d4f8>] (dump_stack+0x94/0xa8)
May 24 06:57:05 R8000 kernel [<8016d464>] (dump_stack) from [<800a0a54>] (bad_page+0x114/0x12c)
May 24 06:57:05 R8000 kernel r7:86ecba00 r6:00000002 r5:00000000 r4:ffffffff
May 24 06:57:05 R8000 kernel [<800a0940>] (bad_page) from [<800a4008>] (get_page_from_freelist+0x9a8/0xc64)
May 24 06:57:05 R8000 kernel r10:86ecba00 r9:00000000 r8:8045cf9c r7:8045cf88 r6:00000002 r5:00000000
May 24 06:57:05 R8000 kernel r4:ffffffff r3:00000000
May 24 06:57:05 R8000 kernel [<800a3660>] (get_page_from_freelist) from [<800a438c>] (__alloc_pages_nodemask+0xc8/0x78c)
May 24 06:57:05 R8000 kernel r10:026080c0 r9:80525954 r8:00000000 r7:00000001 r6:00000000 r5:026080c0
May 24 06:57:05 R8000 kernel r4:00000000
May 24 06:57:05 R8000 kernel [<800a42c4>] (__alloc_pages_nodemask) from [<800a4c18>] (alloc_kmem_pages_node+0x20/0x28)
May 24 06:57:05 R8000 kernel r10:87979800 r9:8058de60 r8:00000000 r7:ffffffff r6:00000000 r5:00800111
May 24 06:57:05 R8000 kernel r4:8611c400
May 24 06:57:05 R8000 kernel [<800a4bf8>] (alloc_kmem_pages_node) from [<80038f14>] (copy_process.part.0+0xfc/0x1294)
May 24 06:57:05 R8000 kernel [<80038e18>] (copy_process.part.0) from [<8003a228>] (_do_fork+0xc4/0x2dc)
May 24 06:57:05 R8000 kernel r10:80531d3c r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:858a5780
May 24 06:57:05 R8000 kernel r4:00800111
May 24 06:57:05 R8000 kernel [<8003a164>] (_do_fork) from [<8003a474>] (kernel_thread+0x34/0x3c)
May 24 06:57:05 R8000 kernel r10:80531d3c r9:00000000 r8:00000000 r7:8783af00 r6:87802800 r5:858a5780
May 24 06:57:05 R8000 kernel r4:871b9d80
May 24 06:57:05 R8000 kernel [<8003a440>] (kernel_thread) from [<8004c500>] (call_usermodehelper_exec_work+0x40/0xb8)
May 24 06:57:05 R8000 kernel [<8004c4c0>] (call_usermodehelper_exec_work) from [<80050314>] (process_one_work+0x1b8/0x2e4)
May 24 06:57:05 R8000 kernel r4:871b9d80
May 24 06:57:05 R8000 kernel [<8005015c>] (process_one_work) from [<80050b3c>] (worker_thread+0x298/0x460)
May 24 06:57:05 R8000 kernel r9:00000000 r8:87802814 r7:858a5798 r6:87802800 r5:87802800 r4:858a5780
May 24 06:57:05 R8000 kernel [<800508a4>] (worker_thread) from [<80054378>] (kthread+0xf8/0x100)
May 24 06:57:05 R8000 kernel r10:00000000 r9:00000000 r8:00000000 r7:800508a4 r6:858a5780 r5:00000000
May 24 06:57:05 R8000 kernel r4:86adb380
May 24 06:57:05 R8000 kernel [<80054280>] (kthread) from [<80009620>] (ret_from_fork+0x14/0x34)
May 24 06:57:05 R8000 kernel r7:00000000 r6:00000000 r5:80054280 r4:86adb380



Screen Shot 2020-05-24 at 6.59.39 AM.png
 Description:
 Filesize:  173.56 KB
 Viewed:  1034 Time(s)

Screen Shot 2020-05-24 at 6.59.39 AM.png



Screen Shot 2020-05-24 at 7.01.05 AM.png
 Description:
 Filesize:  208.36 KB
 Viewed:  1034 Time(s)

Screen Shot 2020-05-24 at 7.01.05 AM.png



ath2_log.txt
 Description:

Download
 Filename:  ath2_log.txt
 Filesize:  4.09 KB
 Downloaded:  22 Time(s)

zigzap
DD-WRT Novice


Joined: 12 May 2020
Posts: 2

PostPosted: Sun May 24, 2020 11:33    Post subject: Re: Reset - running on r43171 Reply with quote
basofree wrote:

Hi zigzap,
I'm currently in a similar situation.
On my R8000 the dhd-versions leads to crashes.
Try the new experimental beta: /05-22-2020-r43217/netgear-r8000/experimental_driver/. But please reset and reconfigure completely.

Nevertheless, these are the problems I'm experiencing with r43217-experimental_driver on the NETGEAR R8000 right now:

    - WiFi 5GHz² LED not working
    - WLAN devices won't properly come up after WiFi on/off button pressed, to disable/enable it
    - Problems in discovering network services (like Google Chromecast - it seems like the networks are "mixed up" (wild guess) - Maybe [43219] by brainslayer - to fix allocation bug in nand driver will help [waiting for new build]
    - JFFS size display bug [as mentioned in the build thread]

Thanks, for the recommendation. Looks like waiting for a new build might be my best option, as I use Nvidia Shields Chromecast funksjonality alot. I will post in this thread if I find a build that works well.
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 7245
Location: Texas, USA

PostPosted: Sun May 24, 2020 11:39    Post subject: Reply with quote
Report in the corresponding build thread(s), please.

@buffpatel: I sent a copy of your report to the developer for review.

_________________
Official Forum Rules, Guidelines, and Helpful InformationFirmware FAQInstallation WikiWhere Do I Download Firmware?
DON'T use Chromium-based browsersRTFM/STFW - TL;DR is NOT an excuse. • Why Should I Care What Color the Bikeshed Is?
Please DO NOT PM me with questions; Ask in the forum.

---------------------------------------------------------

Linux User #377467 counter.li.org / linuxcounter.net
RageX
DD-WRT Novice


Joined: 01 Jan 2020
Posts: 36

PostPosted: Sat Sep 12, 2020 4:33    Post subject: Reply with quote
Hi buffpatel, did you manage to fix this issue?

I'm getting the exact same issue on my DIR-890L, and as I understand they share similar hardware.

I've tied the occurrences to when an Oppo R17 phone is connected to the router. I've a suspicion that it was caused by a firmware update on the phone.

Present on an old version of DD-WRT (r41811), and its also present on the latest version (r44340).

Edit: Looks like a mod removed the post quote. The post quote is important because it highlights the exact issue I'm facing. See direct link to post https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1203554#1203554
Opposable
DD-WRT Novice


Joined: 26 Dec 2019
Posts: 4

PostPosted: Sun Sep 13, 2020 14:43    Post subject: Reply with quote
RageX wrote:
Hi buffpatel, did you manage to fix this issue?

I'm getting the exact same issue on my DIR-890L, and as I understand they share similar hardware.

I've tied the occurrences to when an Oppo R17 phone is connected to the router. I've a suspicion that it was caused by a firmware update on the phone.

Present on an old version of DD-WRT (r41811), and its also present on the latest version (r44340).

Edit: Looks like a mod removed the post quote. The post quote is important because it highlights the exact issue I'm facing. See direct link to post https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1203554#1203554


Have you tried the experimental drivers? I was having this issue on my 890l until I moved over to them. Since then, the BS builds have been just as stable as my old Kong builds.
RageX
DD-WRT Novice


Joined: 01 Jan 2020
Posts: 36

PostPosted: Sun Sep 13, 2020 15:10    Post subject: Reply with quote
Opposable wrote:
RageX wrote:
Hi buffpatel, did you manage to fix this issue?

I'm getting the exact same issue on my DIR-890L, and as I understand they share similar hardware.

I've tied the occurrences to when an Oppo R17 phone is connected to the router. I've a suspicion that it was caused by a firmware update on the phone.

Present on an old version of DD-WRT (r41811), and its also present on the latest version (r44340).

Edit: Looks like a mod removed the post quote. The post quote is important because it highlights the exact issue I'm facing. See direct link to post https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1203554#1203554


Have you tried the experimental drivers? I was having this issue on my 890l until I moved over to them. Since then, the BS builds have been just as stable as my old Kong builds.


So you also had the following error message spam in your syslogs?

Code:
 May 08 12:13:27 R8000 kernel CONSOLE: 014404.140 wl2: wlc_bmac_processpmq: skip entry with mc/bc address 05:b4:29:fe:f9:37
 May 08 12:13:27 R8000 kernel CONSOLE: 014404.155 wl2: wlc_bmac_processpmq: skip entry with mc/bc address 05:b4:29:fe:f9:37
 May 08 12:13:27 R8000 kernel CONSOLE: 014404.349 wl2: wlc_bmac_processpmq: skip entry with mc/bc address 05:b4:29:fe:f9:37
 May 08 12:13:27 R8000 kernel CONSOLE: 014404.407 wl2: wlc_bmac_processpmq: skip entry with mc/bc address 05:b4:29:fe:f9:37
 May 08 12:13:27 R8000 kernel CONSOLE: 014404.435 wl2: wlc_bmac_processpmq: skip entry with mc/bc address 05:b4:29:fe:f9:37
 May 08 12:13:27 R8000 kernel CONSOLE: 014404.439 wl2: wlc_bmac_processpmq: skip entry with mc/bc address 05:b4:29:fe:f9:37
 May 08 12:13:27 R8000 kernel CONSOLE: 014404.553 wl2: wlc_bmac_processpmq: skip entry with mc/bc address 05:b4:29:fe:f9:37
 May 08 12:13:27 R8000 kernel CONSOLE: 014404.756 wl2: wlc_bmac_processpmq: skip entry with mc/bc address 05:b4:29:fe:f9:37
 May 08 12:13:27 R8000 kernel CONSOLE: 014404.882 wl2: wlc_bmac_processpmq: skip entry with mc/bc address 05:b4:29:fe:f9:37
 May 08 12:13:27 R8000 kernel CONSOLE: 014404.968 wl2: wlc_bmac_processpmq: skip entry with mc/bc address 05:b4:29:fe:f9:37


And the experimental drivers fixed it?
Opposable
DD-WRT Novice


Joined: 26 Dec 2019
Posts: 4

PostPosted: Mon Sep 14, 2020 16:53    Post subject: Reply with quote
Hundreds and hundreds of them, and they would be one digit removed from the MAC address of my Pixel phone.

Additionally, I would crash every couple of hours on the standard BS builds. Moving to experimental has fixed both issues.
RageX
DD-WRT Novice


Joined: 01 Jan 2020
Posts: 36

PostPosted: Tue Sep 15, 2020 3:43    Post subject: Reply with quote
Opposable wrote:
Hundreds and hundreds of them, and they would be one digit removed from the MAC address of my Pixel phone.

Additionally, I would crash every couple of hours on the standard BS builds. Moving to experimental has fixed both issues.


Thanks for that tip, very helpful.

I noticed in one of the build threads you posted that the experimental build does not allow the disabling of wireless SSID broadcast? This means that all 3 wireless radios will have to be switched on?
buffpatel
DD-WRT User


Joined: 22 Feb 2011
Posts: 100

PostPosted: Wed Sep 16, 2020 12:13    Post subject: Reply with quote
RageX wrote:
Hi buffpatel, did you manage to fix this issue?

I'm getting the exact same issue on my DIR-890L, and as I understand they share similar hardware.



Hi, and sorry for the delay in reply. Unfortunately, I never found a solution for this problem (of having "skip entry" errors in my logs). After tons of google searches it appears to me that this has been an issue with numerous routers for years without anyone ever finding a solution.

My "solution" was to move to the experimental driver builds for the R8000 which improved my routers stability and then I simply turned off the logging function on my router. Out of sight out of mind, right? I know it's not a perfect solution, but with the experimental build my router often gets uptimes of 3-4 weeks now.

I know that you're not using the R8000, so I'm not sure if your DIR-890L has an experimental driver or not. If I were you, I'd just focus on the routers stability - if it's working for 10-12 days without issues, well I'd just take that and be happy regardless of what's in the logs. Sorry I couldn't be much more help, but I'm not sure if anyone knows why these messages occur in the logs, much less has a way to fix them.
RageX
DD-WRT Novice


Joined: 01 Jan 2020
Posts: 36

PostPosted: Wed Sep 16, 2020 12:59    Post subject: Reply with quote
buffpatel wrote:
RageX wrote:
Hi buffpatel, did you manage to fix this issue?

I'm getting the exact same issue on my DIR-890L, and as I understand they share similar hardware.



Hi, and sorry for the delay in reply. Unfortunately, I never found a solution for this problem (of having "skip entry" errors in my logs). After tons of google searches it appears to me that this has been an issue with numerous routers for years without anyone ever finding a solution.

My "solution" was to move to the experimental driver builds for the R8000 which improved my routers stability and then I simply turned off the logging function on my router. Out of sight out of mind, right? I know it's not a perfect solution, but with the experimental build my router often gets uptimes of 3-4 weeks now.

I know that you're not using the R8000, so I'm not sure if your DIR-890L has an experimental driver or not. If I were you, I'd just focus on the routers stability - if it's working for 10-12 days without issues, well I'd just take that and be happy regardless of what's in the logs. Sorry I couldn't be much more help, but I'm not sure if anyone knows why these messages occur in the logs, much less has a way to fix them.


Thanks buffpatel. I thought it was an issue with a cheapo branded smartphone, but Opposable got the same issue with his Pixel as well. Google is not very helpful with this particular log entry.

The logs are practically unreadable as there's so much spam, the error comes out every second or every few seconds. I had to put a log filter on papertrail to remove those entries automatically otherwise the log would be unreadable.

I'm considering trying the experimental driver (890L has an experimental driver), but it appears that for the 890L the 3rd wifi band can't be switched off with that experimental driver (not sure if that's still the case with the latest build).

Also my current non-experimental driver build has been up for the last 4-5 days straight and its reasonably stable. Some minor hiccups, like an instant d/c and reconnect on one smartphone once, and dropping some 2.4GHz wifi devices for like 1min before reconnecting by itself (once), but other than that no biggie.

The hardware of the R8000 is virtually the same as the 890L, which I why I posted a question on this thread. Kong's R8000 firmware works almost perfectly on the 890L.

I'll continue monitoring and thanks again for your response.
Goto page Previous  1, 2, 3  Next Display posts from previous:    Page 2 of 3
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum