randomuser931583
Occasional Visitor
I got the router a few months ago and was hoping 386.1 would resolve this issue but it seems to persist.
These crashes are not full crashes, only what I as a layperson could describe as a module failing and being reloaded. There is no full reinitialization of the system and downtime is about 10 seconds.
https://www.snbforums.com/threads/a...ta-is-now-available.68205/page-10#post-639072 is almost identical to errors I'm experiencing so I'm not sure if this is a possible issue.
Most recent crash on 386.1.2:
May 5 00:05:02 crashlog: <1>Unable to handle kernel NULL pointer dereference at virtual address 00000151
May 5 00:05:02 crashlog: <1>pgd = c0014000
May 5 00:05:02 crashlog: <1>[00000151] *pgd=00000000
May 5 00:05:02 crashlog: <0>Internal error: Oops: 17 [#1] PREEMPT SMP ARM
May 5 00:05:02 crashlog: <4>CPU: 0 PID: 239 Comm: bcmsw_rx Tainted: P O 4.1.52 #1
May 5 00:05:02 crashlog: <4>Hardware name: Generic DT based system
Previous errors identical to the one in the link:
May 5 00:05:02 crashlog: <1>Unable to handle kernel NULL pointer dereference at virtual address 0000000c
May 5 00:05:02 crashlog: <1>pgd = c0014000
May 5 00:05:02 crashlog: <1>[0000000c] *pgd=00000000
May 5 00:05:02 crashlog: <0>Internal error: Oops: 17 [#1] PREEMPT SMP ARM
May 5 00:05:02 crashlog: <4>CPU: 1 PID: 529 Comm: wl0-kthrd Tainted: P O 4.1.52 #1
Furthermore it appears the commonality of the crashes is they end within the bcm 675x blob.
I've also experimented with enabling/disabling QoS and other router features to turn acceleration on/off and haven't seen any success. In fact, even after reboots the status of "Archer" and "Flow Cache" remain enabled.
There does not appear to be any pattern with the router events immediately prior to the crash and therefore is, as far as I can tell, not reproduceable by any of my actions.
Full stacktrace is attached of a crash.
These crashes are not full crashes, only what I as a layperson could describe as a module failing and being reloaded. There is no full reinitialization of the system and downtime is about 10 seconds.
https://www.snbforums.com/threads/a...ta-is-now-available.68205/page-10#post-639072 is almost identical to errors I'm experiencing so I'm not sure if this is a possible issue.
Most recent crash on 386.1.2:
May 5 00:05:02 crashlog: <1>Unable to handle kernel NULL pointer dereference at virtual address 00000151
May 5 00:05:02 crashlog: <1>pgd = c0014000
May 5 00:05:02 crashlog: <1>[00000151] *pgd=00000000
May 5 00:05:02 crashlog: <0>Internal error: Oops: 17 [#1] PREEMPT SMP ARM
May 5 00:05:02 crashlog: <4>CPU: 0 PID: 239 Comm: bcmsw_rx Tainted: P O 4.1.52 #1
May 5 00:05:02 crashlog: <4>Hardware name: Generic DT based system
Previous errors identical to the one in the link:
May 5 00:05:02 crashlog: <1>Unable to handle kernel NULL pointer dereference at virtual address 0000000c
May 5 00:05:02 crashlog: <1>pgd = c0014000
May 5 00:05:02 crashlog: <1>[0000000c] *pgd=00000000
May 5 00:05:02 crashlog: <0>Internal error: Oops: 17 [#1] PREEMPT SMP ARM
May 5 00:05:02 crashlog: <4>CPU: 1 PID: 529 Comm: wl0-kthrd Tainted: P O 4.1.52 #1
Furthermore it appears the commonality of the crashes is they end within the bcm 675x blob.
I've also experimented with enabling/disabling QoS and other router features to turn acceleration on/off and haven't seen any success. In fact, even after reboots the status of "Archer" and "Flow Cache" remain enabled.
There does not appear to be any pattern with the router events immediately prior to the crash and therefore is, as far as I can tell, not reproduceable by any of my actions.
Full stacktrace is attached of a crash.
Attachments
Last edited: