bbursley Posted June 19 Share Posted June 19 Hello, R3 user here updated to the latest OS, experiencing odd issues with wifi just suddenly stalling or just dropping the device off wireless. This just seems to happen randomly and for no real reason at all. I do not have IPv6 or anything else odd enabled either. My second issue I have had so far, is the UI not loading from the web, at one point it told me "hold on, this could take up to four minutes", another time it just simply would not load at all, with some sort of emoji looking face and asked if I wanted to continue/try again. A reboot of the router usually clears things up for a bit. It does not seem to stop data from passing or anything else, but it can be kind of more annoying than not. Both issues kind of seem concerning on the reliability front. Its definitely not enjoyable hearing your wife complain about the buffering of the TV, as well as the fact that sometimes even when I would get dropped, the wireless password wouldn't be accepted at some moments, so odd. My last biggest gripe (its not game breaking as the ui access lag), is that settings don't seem to stick from one device to the next, and that makes me feel like they are not always super reliable. For instance, from my work mac to my pc, I could sometimes log into the device and find that ping stabilizer is active, even when I deactivated it on another device, hmmmm. Another issue I see frequently is the speed test bypass just enabling itself all over again, even when I chose to leave it off. All in all, the router seems to do as its advertised when its not going through these weird fits, and as I type this, I cannot even load other websites, call of duty has not disconnected me though, wtf.... Link to comment Share on other sites More sharing options...
Chup Posted June 19 Share Posted June 19 (edited) Seconded. I'm having the exact same issues and the system logs seem to show errors too. kern.warn kernel: r7 : bee70a2c r6 : bee70ae0 r5 : 00000008 r4 : 00000000kern.warn kernel: r3 : 00000000 r2 : 00000008 r1 : 00000001 r0 : bee70ae4kern.warn kernel: Flags: nzCv IRQs on FIQs on Mode USER_32 ISA ARM Segment userkern.warn kernel: Control: 10c5387d Table: 0262804a DAC: 00000055kern.warn kernel: CPU: 0 PID: 4309 Comm: datahistory Tainted: P W O 4.19.183 #16kern.warn kernel: Hardware name: Generic DT based systemkern.warn kernel: [<c0210a14>] (unwind_backtrace) from [<c020b9a8>] (show_stack+0x10/0x14)kern.warn kernel: [<c020b9a8>] (show_stack) from [<c088a634>] (dump_stack+0x90/0xa4)kern.warn kernel: [<c088a634>] (dump_stack) from [<c022d8e0>] (get_signal+0x658/0x680)kern.warn kernel: [<c022d8e0>] (get_signal) from [<c020b094>] (do_signal+0xcc/0x538)kern.warn kernel: [<c020b094>] (do_signal) from [<c020b6c4>] (do_work_pending+0xb4/0xd0)kern.warn kernel: [<c020b6c4>] (do_work_pending) from [<c0201070>] (slow_work_pending+0xc/0x20)kern.warn kernel: Exception stack(0xc2751fb0 to 0xc2751ff8)kern.warn kernel: 1fa0: bee70ae4 00000001 00000008 00000000kern.warn kernel: 1fc0: 00000000 00000008 bee70ae0 bee70a2c bee70a2c 00013738 bee709a0 bee709afkern.warn kernel: 1fe0: 00028f0c bee70940 00013718 b6d61b10 200f0010 ffffffff daemon.err odhcp6c[9019]: Failed to send SOLICIT message to ff02::1:2 (Cannot assign requested address) Edited June 19 by Chup Something else in system log bbursley 1 Link to comment Share on other sites More sharing options...
bbursley Posted June 19 Author Share Posted June 19 3 hours ago, Chup said: Seconded. I'm having the exact same issues and the system logs seem to show errors too. kern.warn kernel: r7 : bee70a2c r6 : bee70ae0 r5 : 00000008 r4 : 00000000kern.warn kernel: r3 : 00000000 r2 : 00000008 r1 : 00000001 r0 : bee70ae4kern.warn kernel: Flags: nzCv IRQs on FIQs on Mode USER_32 ISA ARM Segment userkern.warn kernel: Control: 10c5387d Table: 0262804a DAC: 00000055kern.warn kernel: CPU: 0 PID: 4309 Comm: datahistory Tainted: P W O 4.19.183 #16kern.warn kernel: Hardware name: Generic DT based systemkern.warn kernel: [<c0210a14>] (unwind_backtrace) from [<c020b9a8>] (show_stack+0x10/0x14)kern.warn kernel: [<c020b9a8>] (show_stack) from [<c088a634>] (dump_stack+0x90/0xa4)kern.warn kernel: [<c088a634>] (dump_stack) from [<c022d8e0>] (get_signal+0x658/0x680)kern.warn kernel: [<c022d8e0>] (get_signal) from [<c020b094>] (do_signal+0xcc/0x538)kern.warn kernel: [<c020b094>] (do_signal) from [<c020b6c4>] (do_work_pending+0xb4/0xd0)kern.warn kernel: [<c020b6c4>] (do_work_pending) from [<c0201070>] (slow_work_pending+0xc/0x20)kern.warn kernel: Exception stack(0xc2751fb0 to 0xc2751ff8)kern.warn kernel: 1fa0: bee70ae4 00000001 00000008 00000000kern.warn kernel: 1fc0: 00000000 00000008 bee70ae0 bee70a2c bee70a2c 00013738 bee709a0 bee709afkern.warn kernel: 1fe0: 00028f0c bee70940 00013718 b6d61b10 200f0010 ffffffff daemon.err odhcp6c[9019]: Failed to send SOLICIT message to ff02::1:2 (Cannot assign requested address) Yeah, nothing that really breaks anything, but it is kind of annoying Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted June 20 Administrators Share Posted June 20 Could you grab the logs from http://192.168.77.1/cgi-bin/logs.txt when this happens please - it should work without access and so should give us a good overall picture of what is happening Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now