Newcomer

Losing connection a lot in one day

Been losing connection mostly wifi a lot in one day. Bought a new modem (Surfboard 6190) and a router (asus rt-ac3100) and have 300/20 Spectrum internet Smiley Sad really stressful as i have done everything i could ( factory reset on my router, left my modem and router off for 3 hours, power cycle both, and etc.) 

 

Oct 25 17:53:22 kernel: dhd_prot_ioctl: status ret value is -110
Oct 25 17:53:24 kernel: dhd_msgbuf_wait_ioctl_cmplt: resumed on timeout rxcnt_timeout 46
Oct 25 17:53:24 kernel: dhd_msgbuf_wait_ioctl_cmplt: timeout > MAX_CNTL_TX_TIMEOUT
Oct 25 17:53:24 kernel: dhd_prot_ioctl: status ret value is -110
Oct 25 17:53:48 watchdog: restart httpd
Oct 25 17:53:48 rc_service: watchdog 301:notify_rc stop_httpd
Oct 25 17:53:48 rc_service: watchdog 301:notify_rc start_httpd
Oct 25 17:53:48 RT-AC3100: start httpd - SSL
Oct 25 17:53:48 RT-AC3100: start httpd
Oct 25 17:53:51 kernel: dhd_msgbuf_wait_ioctl_cmplt: resumed on timeout rxcnt_timeout 47
Oct 25 17:53:51 kernel: dhd_msgbuf_wait_ioctl_cmplt: timeout > MAX_CNTL_TX_TIMEOUT
Oct 25 17:53:51 kernel: dhd_prot_ioctl: status ret value is -110
Oct 25 17:53:53 kernel: dhd_msgbuf_wait_ioctl_cmplt: resumed on timeout rxcnt_timeout 48
Oct 25 17:53:53 kernel: dhd_msgbuf_wait_ioctl_cmplt: timeout > MAX_CNTL_TX_TIMEOUT
Oct 25 17:53:53 kernel: dhd_prot_ioctl: status ret value is -110
Oct 25 17:54:18 watchdog: restart httpd
Oct 25 17:54:18 rc_service: watchdog 301:notify_rc stop_httpd
Oct 25 17:54:18 rc_service: watchdog 301:notify_rc start_httpd
Oct 25 17:54:18 rc_service: waitting "stop_httpd" via watchdog ...
Oct 25 17:54:19 RT-AC3100: start httpd - SSL
Oct 25 17:54:19 RT-AC3100: start httpd
Oct 25 17:54:22 kernel: dhd_msgbuf_wait_ioctl_cmplt: resumed on timeout rxcnt_timeout 49
Oct 25 17:54:22 kernel: dhd_msgbuf_wait_ioctl_cmplt: timeout > MAX_CNTL_TX_TIMEOUT
Oct 25 17:54:22 kernel: dhd_prot_ioctl: status ret value is -110
Oct 25 17:54:24 kernel: dhd_msgbuf_wait_ioctl_cmplt: resumed on timeout rxcnt_timeout 50
Oct 25 17:54:24 kernel: dhd_msgbuf_wait_ioctl_cmplt: timeout > MAX_CNTL_TX_TIMEOUT
Oct 25 17:54:24 kernel: dhd_prot_ioctl: status ret value is -110
Oct 25 17:54:48 watchdog: restart httpd
Oct 25 17:54:48 rc_service: watchdog 301:notify_rc stop_httpd
Oct 25 17:54:48 rc_service: watchdog 301:notify_rc start_httpd
Oct 25 17:54:48 rc_service: waitting "stop_httpd" via watchdog ...
Oct 25 17:54:49 RT-AC3100: start httpd - SSL
Oct 25 17:54:49 RT-AC3100: start httpd
Oct 25 17:54:52 kernel: dhd_msgbuf_wait_ioctl_cmplt: resumed on timeout rxcnt_timeout 51
Oct 25 17:54:52 kernel: dhd_msgbuf_wait_ioctl_cmplt: timeout > MAX_CNTL_TX_TIMEOUT
Oct 25 17:54:52 kernel: dhd_prot_ioctl: status ret value is -110
Oct 25 17:54:54 kernel: dhd_msgbuf_wait_ioctl_cmplt: resumed on timeout rxcnt_timeout 52
Oct 25 17:54:54 kernel: dhd_msgbuf_wait_ioctl_cmplt: timeout > MAX_CNTL_TX_TIMEOUT
Oct 25 17:54:54 kernel: dhd_prot_ioctl: status ret value is -110
Oct 25 17:55:18 watchdog: restart httpd
Oct 25 17:55:18 rc_service: watchdog 301:notify_rc stop_httpd
Oct 25 17:55:18 rc_service: watchdog 301:notify_rc start_httpd
Oct 25 17:55:18 RT-AC3100: start httpd - SSL
Oct 25 17:55:18 RT-AC3100: start httpd
Oct 25 17:55:21 kernel: dhd_msgbuf_wait_ioctl_cmplt: resumed on timeout rxcnt_timeout 53
Oct 25 17:55:21 kernel: dhd_msgbuf_wait_ioctl_cmplt: timeout > MAX_CNTL_TX_TIMEOUT
Oct 25 17:55:21 kernel: dhd_prot_ioctl: status ret value is -110
Oct 25 17:55:23 kernel: dhd_msgbuf_wait_ioctl_cmplt: resumed on timeout rxcnt_timeout 54
Oct 25 17:55:23 kernel: dhd_msgbuf_wait_ioctl_cmplt: timeout > MAX_CNTL_TX_TIMEOUT
Oct 25 17:55:23 kernel: dhd_prot_ioctl: status ret value is -110
Oct 25 17:55:48 watchdog: restart httpd
Oct 25 17:55:48 rc_service: watchdog 301:notify_rc stop_httpd
Oct 25 17:55:48 rc_service: watchdog 301:notify_rc start_httpd
Oct 25 17:55:48 RT-AC3100: start httpd - SSL
Oct 25 17:55:48 RT-AC3100: start httpd
Oct 25 17:55:51 kernel: dhd_msgbuf_wait_ioctl_cmplt: resumed on timeout rxcnt_timeout 55
Oct 25 17:55:51 kernel: dhd_msgbuf_wait_ioctl_cmplt: timeout > MAX_CNTL_TX_TIMEOUT
Oct 25 17:55:51 kernel: dhd_prot_ioctl: status ret value is -110
Oct 25 17:55:54 kernel: dhd_msgbuf_wait_ioctl_cmplt: resumed on timeout rxcnt_timeout 56
Oct 25 17:55:54 kernel: dhd_msgbuf_wait_ioctl_cmplt: timeout > MAX_CNTL_TX_TIMEOUT
Oct 25 17:55:54 kernel: dhd_prot_ioctl: status ret value is -110
Oct 25 17:56:18 watchdog: restart httpd
Oct 25 17:56:18 rc_service: watchdog 301:notify_rc stop_httpd
Oct 25 17:56:18 rc_service: watchdog 301:notify_rc start_httpd
Oct 25 17:56:18 rc_service: waitting "stop_httpd" via watchdog ...
Oct 25 17:56:19 RT-AC3100: start httpd - SSL
Oct 25 17:56:19 RT-AC3100: start httpd
Oct 25 17:56:22 kernel: dhd_msgbuf_wait_ioctl_cmplt: resumed on timeout rxcnt_timeout 57
Oct 25 17:56:22 kernel: dhd_msgbuf_wait_ioctl_cmplt: timeout > MAX_CNTL_TX_TIMEOUT
Oct 25 17:56:22 kernel: dhd_prot_ioctl: status ret value is -110
Oct 25 17:56:24 kernel: dhd_msgbuf_wait_ioctl_cmplt: resumed on timeout rxcnt_timeout 58
Oct 25 17:56:24 kernel: dhd_msgbuf_wait_ioctl_cmplt: timeout > MAX_CNTL_TX_TIMEOUT
Oct 25 17:56:24 kernel: dhd_prot_ioctl: status ret value is -110
Oct 25 17:56:48 watchdog: restart httpd
Oct 25 17:56:48 rc_service: watchdog 301:notify_rc stop_httpd
Oct 25 17:56:48 rc_service: watchdog 301:notify_rc start_httpd
Oct 25 17:56:48 rc_service: waitting "stop_httpd" via watchdog ...
Oct 25 17:56:49 RT-AC3100: start httpd - SSL
Oct 25 17:56:49 RT-AC3100: start httpd
Oct 25 17:56:52 kernel: dhd_msgbuf_wait_ioctl_cmplt: resumed on timeout rxcnt_timeout 59
Oct 25 17:56:52 kernel: dhd_msgbuf_wait_ioctl_cmplt: timeout > MAX_CNTL_TX_TIMEOUT
Oct 25 17:56:52 kernel: dhd_prot_ioctl: status ret value is -110
Oct 25 17:56:54 kernel: dhd_msgbuf_wait_ioctl_cmplt: resumed on timeout rxcnt_timeout 60
Oct 25 17:56:54 kernel: dhd_msgbuf_wait_ioctl_cmplt: timeout > MAX_CNTL_TX_TIMEOUT
Oct 25 17:56:54 kernel: dhd_prot_ioctl: status ret value is -110
Oct 25 17:57:18 watchdog: restart httpd
Oct 25 17:57:18 rc_service: watchdog 301:notify_rc stop_httpd
Oct 25 17:57:18 rc_service: watchdog 301:notify_rc start_httpd
Oct 25 17:57:18 rc_service: waitting "stop_httpd" via watchdog ...
Oct 25 17:57:19 RT-AC3100: start httpd - SSL
Oct 25 17:57:19 RT-AC3100: start httpd
Oct 25 17:57:22 kernel: dhd_msgbuf_wait_ioctl_cmplt: resumed on timeout rxcnt_timeout 61
Oct 25 17:57:22 kernel: dhd_msgbuf_wait_ioctl_cmplt: timeout > MAX_CNTL_TX_TIMEOUT
Oct 25 17:57:22 kernel: dhd_prot_ioctl: status ret value is -110
Oct 25 17:57:24 kernel: dhd_msgbuf_wait_ioctl_cmplt: resumed on timeout rxcnt_timeout 62
Oct 25 17:57:24 kernel: dhd_msgbuf_wait_ioctl_cmplt: timeout > MAX_CNTL_TX_TIMEOUT
Oct 25 17:57:24 kernel: dhd_prot_ioctl: status ret value is -110
Oct 25 17:57:48 watchdog: restart httpd
Oct 25 17:57:48 rc_service: watchdog 301:notify_rc stop_httpd
Oct 25 17:57:48 rc_service: watchdog 301:notify_rc start_httpd
Oct 25 17:57:48 rc_service: waitting "stop_httpd" via watchdog ...
Oct 25 17:57:49 RT-AC3100: start httpd - SSL
Oct 25 17:57:49 RT-AC3100: start httpd
Oct 25 17:57:50 kernel: dhd_prot_rxbufpost_ctrl:3207: Ctrl submit Msgbuf Not available to post buffer
Oct 25 17:57:52 kernel: dhd_msgbuf_wait_ioctl_cmplt: resumed on timeout rxcnt_timeout 63
Oct 25 17:57:52 kernel: dhd_msgbuf_wait_ioctl_cmplt: timeout > MAX_CNTL_TX_TIMEOUT
Oct 25 17:57:52 kernel: dhd_prot_ioctl: status ret value is -110
Oct 25 17:57:52 kernel: dhd_prot_rxbufpost_ctrl:3207: Ctrl submit Msgbuf Not available to post buffer
Oct 25 17:57:54 kernel: dhd_msgbuf_wait_ioctl_cmplt: resumed on timeout rxcnt_timeout 64
Oct 25 17:57:54 kernel: dhd_msgbuf_wait_ioctl_cmplt: timeout > MAX_CNTL_TX_TIMEOUT
Oct 25 17:57:54 kernel: dhd_prot_ioctl: status ret value is -110
Oct 25 17:58:18 watchdog: restart httpd
Oct 25 17:58:18 rc_service: watchdog 301:notify_rc stop_httpd
Oct 25 17:58:18 rc_service: watchdog 301:notify_rc start_httpd
Oct 25 17:58:18 rc_service: waitting "stop_httpd" via watchdog ...
Oct 25 17:58:19 RT-AC3100: start httpd - SSL
Oct 25 17:58:19 RT-AC3100: start httpd

 

Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectedUncorrectables
1Locked256QAM24645.00 MHz1.30 dBmV40.37 dB90
2Locked256QAM1507.00 MHz3.20 dBmV40.95 dB70
3Locked256QAM2513.00 MHz2.90 dBmV40.95 dB10
4Locked256QAM3519.00 MHz2.90 dBmV40.95 dB10
5Locked256QAM4525.00 MHz2.50 dBmV40.37 dB00
6Locked256QAM5531.00 MHz3.30 dBmV40.95 dB00
7Locked256QAM6537.00 MHz3.00 dBmV40.95 dB00
8Locked256QAM7543.00 MHz2.80 dBmV40.37 dB00
9Locked256QAM8549.00 MHz2.70 dBmV40.95 dB00
10Locked256QAM9555.00 MHz2.30 dBmV40.37 dB00
11Locked256QAM10561.00 MHz2.40 dBmV40.37 dB00
12Locked256QAM11567.00 MHz1.80 dBmV40.37 dB00
13Locked256QAM12573.00 MHz1.80 dBmV40.37 dB00
14Locked256QAM13579.00 MHz2.20 dBmV40.37 dB00
15Locked256QAM14585.00 MHz2.40 dBmV40.95 dB00
16Locked256QAM15591.00 MHz2.20 dBmV40.37 dB00
17Locked256QAM16597.00 MHz2.20 dBmV40.37 dB00
18Locked256QAM17603.00 MHz1.40 dBmV40.37 dB00
19Locked256QAM18609.00 MHz1.40 dBmV40.95 dB00
20Locked256QAM19615.00 MHz0.30 dBmV40.37 dB50
21Locked256QAM20621.00 MHz0.10 dBmV38.98 dB50
22Locked256QAM21627.00 MHz1.30 dBmV40.37 dB110
23Locked256QAM22633.00 MHz1.60 dBmV40.37 dB00
24Locked256QAM23639.00 MHz1.70 dBmV40.37 dB00

 
Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA605120 kSym/s37.00 MHz37.00 dBmV
2LockedATDMA595120 kSym/s30.60 MHz36.25 dBmV
3LockedATDMA585120 kSym/s23.30 MHz35.50 dBmV
4LockedTDMA572560 kSym/s18.50 MHz35.00 dBmV
8 REPLIES 8
Newcomer

Re: Losing connection a lot in one day

Oct 25 22:28:50 rc_service: ntp 523:notify_rc restart_upnpOct 25 22:28:50 rc_service: ntp 523:notify_rc restart_diskmonOct 25 22:28:50 disk_monitor: FinishOct 25 22:28:50 dhcp client: bound 70.95.138.5 via 70.95.128.1 during 47395 seconds.Oct 25 22:28:51 disk monitor: be idleOct 25 22:28:52 kernel: dhd_prot_flow_ring_create: Send Flow Create Req flow ID 263 for peer a0:32:99:ab:c6:84 prio 0 ifindex 0Oct 25 22:28:53 kernel: dhd_prot_flow_ring_create_response_process: Flow Create Response status = 0 Flow 263Oct 25 22:28:53 kernel: CONSOLE: 026760.420 flow_create : bitmap_size=512  maxitems=512Oct 25 22:28:53 kernel: CONSOLE: 026760.429 wl0.0: wlc_send_bar: seq 0x1 tid 0Oct 25 22:29:21 crond[313]: time disparity of 366089 minutes detectedOct 25 22:30:36 kernel: dhd_prot_flow_ring_create: Send Flow Create Req flow ID 264 for peer 9c:2a:83:f7:f7:e0 prio 0 ifindex 0Oct 25 22:30:36 kernel: dhd_prot_flow_ring_create_response_process: Flow Create Response status = 0 Flow 264Oct 25 22:30:36 kernel: CONSOLE: 026862.220 flow_create : bitmap_size=512  maxitems=512Oct 25 22:30:36 kernel: CONSOLE: 026862.571 wl1.0: wlc_send_bar: seq 0x2 tid 0Oct 25 22:30:38 kernel: CONSOLE: 026864.317 wl1.0: wlc_send_bar: seq 0x1 tid 3Oct 25 22:31:55 kernel: dhd_prot_flow_ring_create: Send Flow Create Req flow ID 262 for peer 68:37:e9:e2:d5:14 prio 0 ifindex 0Oct 25 22:31:55 kernel: dhd_prot_flow_ring_create_response_process: Flow Create Response status = 0 Flow 262Oct 25 22:31:55 kernel: CONSOLE: 026942.353 flow_create : bitmap_size=512  maxitems=512Oct 25 22:31:55 kernel: CONSOLE: 026942.364 wl0.0: wlc_send_bar: seq 0x1 tid 0Oct 25 23:00:51 disk_monitor: Got SIGALRM...Oct 25 23:04:25 rc_service: httpd 315:notify_rc restart_wirelessOct 25 23:04:26 kernel: dhd_flow_rings_delete_for_peer: ifindex 0Oct 25 23:04:26 kernel: dhd_prot_flow_ring_delete: Send Flow Delete Req RING ID 262 for peer 68:37:e9:e2:d5:14 prio 0 ifindex 0Oct 25 23:04:26 kernel: dhd_flow_rings_delete_for_peer: ifindex 0Oct 25 23:04:26 kernel: dhd_prot_flow_ring_delete: Send Flow Delete Req RING ID 263 for peer a0:32:99:ab:c6:84 prio 0 ifindex 0Oct 25 23:04:26 kernel: dhd_flow_rings_delete_for_peer: ifindex 0Oct 25 23:04:26 kernel: dhd_prot_flow_ring_delete: Send Flow Delete Req RING ID 264 for peer 90:60:f1:89:df:e8 prio 0 ifindex 0Oct 25 23:04:26 kernel: dhd_flow_rings_delete_for_peer: ifindex 0Oct 25 23:04:26 kernel: dhd_bus_flow_ring_delete_request Smiley Very Happyelete PendingOct 25 23:04:26 kernel: dhd_bus_flow_ring_delete_request Smiley Very Happyelete PendingOct 25 23:04:26 kernel: dhd_bus_flow_ring_delete_request Smiley Very Happyelete PendingOct 25 23:04:26 kernel: dhd_prot_flow_ring_delete: Send Flow Delete Req RING ID 265 for peer 01:00:5e:00:00:01 prio 3 ifindex 0Oct 25 23:04:26 kernel: dhd_prot_flow_ring_delete_response_process: Flow Delete Response status = 0 Oct 25 23:04:26 kernel: dhd_prot_flow_ring_delete_response_process: Flow Delete Response status = 0 Oct 25 23:04:26 kernel: dhd_prot_flow_ring_delete_response_process: Flow Delete Response status = 0 Oct 25 23:04:26 kernel: dhd_prot_flow_ring_delete_response_process: Flow Delete Response status = 0 Oct 25 23:04:26 kernel: dhd_prot_ioctl: status ret value is -29 Oct 25 23:04:26 kernel: CONSOLE: 028888.782 wl0: link down (wl0)Oct 25 23:04:26 kernel: dhd_flow_rings_delete_for_peer: ifindex 0Oct 25 23:04:26 kernel: dhd_prot_flow_ring_delete: Send Flow Delete Req RING ID 264 for peer 9c:2a:83:f7:f7:e0 prio 0 ifindex 0Oct 25 23:04:26 kernel: dhd_flow_rings_delete_for_peer: ifindex 0Oct 25 23:04:26 kernel: dhd_bus_flow_ring_delete_request Smiley Very Happyelete PendingOct 25 23:04:26 kernel: dhd_prot_flow_ring_delete: Send Flow Delete Req RING ID 265 for peer 01:00:5e:00:00:01 prio 3 ifindex 0Oct 25 23:04:26 kernel: dhd_prot_flow_ring_delete_response_process: Flow Delete Response status = 0 Oct 25 23:04:26 kernel: dhd_prot_flow_ring_delete_response_process: Flow Delete Response status = 0 Oct 25 23:04:26 kernel: dhd_prot_ioctl: status ret value is -29 Oct 25 23:04:26 kernel: CONSOLE: 028889.255 wl1: link down (wl1)Oct 25 23:04:31 kernel: dhd_prot_ioctl: status ret value is -9 Oct 25 23:04:31 kernel: dhd_prot_ioctl: status ret value is -29 Oct 25 23:04:31 kernel: dhd_prot_ioctl: status ret value is -23 Oct 25 23:04:31 kernel: dhd_prot_ioctl: status ret value is -23 Oct 25 23:04:31 kernel: dhd_prot_ioctl: status ret value is -23 Oct 25 23:04:31 kernel: dhd_prot_ioctl: status ret value is -23 Oct 25 23:04:31 kernel: dhd_prot_ioctl: status ret value is -23 Oct 25 23:04:31 kernel: dhd_prot_ioctl: status ret value is -23 Oct 25 23:04:31 kernel: CONSOLE: 028894.272 wl0: wl_openOct 25 23:04:31 kernel: CONSOLE: 028894.305 wl0: wlc_ampdu_tx_set: AGG Mode = MAC+AQM txmaxpkts 512Oct 25 23:04:31 kernel: CONSOLE: 028894.327 wl0: wl_openOct 25 23:04:31 kernel: CONSOLE: 028894.328 wlc_ucode_download: wl0: Loading non-MU ucodeOct 25 23:04:31 kernel: dhd_prot_ioctl: status ret value is -9 Oct 25 23:04:31 kernel: dhd_prot_ioctl: status ret value is -29 Oct 25 23:04:31 kernel: dhd_prot_ioctl: status ret value is -23 Oct 25 23:04:31 kernel: dhd_prot_ioctl: status ret value is -23 Oct 25 23:04:31 kernel: dhd_prot_ioctl: status ret value is -20 Oct 25 23:04:31 kernel: CONSOLE: 028894.342 wl0: CORE INIT : nfifo 6 mu_tx_enab 0Oct 25 23:04:31 kernel: CONSOLE: 028894.342 wl0: CORE INIT : mode 2 pktclassify 1 rxsplit 0  hdr conve 0 DMA_CT DisabledOct 25 23:04:31 kernel: CONSOLE: 028894.353 wl0: wlc_enable_probe_req: state down, deferring setting of host flagsOct 25 23:04:31 kernel: CONSOLE: 028894.353 enable 1: q0 frmcnt 0, wrdcnt 0, q1 frmcnt 0, wrdcnt 0Oct 25 23:04:31 kernel: dhd_prot_ioctl: status ret value is -23 Oct 25 23:04:31 kernel: dhd_prot_ioctl: status ret value is -23 Oct 25 23:04:32 kernel: dhd_prot_ioctl: status ret value is -23 Oct 25 23:04:32 kernel: dhd_prot_ioctl: status ret value is -23

Expert

Re: Losing connection a lot in one day

Looks like a coaxial issue from broadcast TV ingress if that modem signal page was pulled up right after a reset...

Something is corroded, loose or chewed up outside.

 Next issue is the routers logs.... Do a factory reset on it.

 

Newcomer

Re: Losing connection a lot in one day

I dont have any tv subscription anymore and i have been doing factory reset on the router and still having issues and also routers rebot itself. I remove the splitter from before so now modem is only connected directly so i dont know maybe ill wait and hope the tech guy fix my problem 😐
Trusted Helper

Re: Losing connection a lot in one day


@Johnyboi wrote:
I dont have any tv subscription anymore and i have been doing factory reset on the router and still having issues and also routers rebot itself. I remove the splitter from before so now modem is only connected directly so i dont know maybe ill wait and hope the tech guy fix my problem 😐

Hello,

 

You need to contact Spectrum for a signal and drop line test.  As well as a check of the main tap on your street.  Avoid resetting any modems, routers, or cable boxes for at least six hours prior to the appointment so that the error codes can be read by the tech.  Resetting the equipment resets the error codes.  If your signals and line drop are good, you might want to consider at that point replacing the modem, or renting one from Spectrum to insure capability with their network.  The signal and drop line check should be done first.

 

Satch

Newcomer

Re: Losing connection a lot in one day

Thank you called spectrum and they will be here today to check
Newcomer

Re: Losing connection a lot in one day

So guy from spectrum didnt find anything except he told me my router is bad so im trying out their modem router and see what happens
Proven Sharer

Re: Losing connection a lot in one day

It never surprises me to hear about a home service tech saying that "Your customer-owned modem is bad, try renting one of ours.."   Then when you complain a month later that their WiFi gateway doesn't work any better, they will spend hours fixing things that weren't considered bad during their first trip.  

Expert

Re: Losing connection a lot in one day

What router were you using with the 6190?

Post the new combo units signal and error log pages.

What model # is it?