Re: Im having issues with rebooting as well

FURRYe38 · ‎2024-03-19

Please post a screen capture of the RBRs debug page please.

JesseDiaz · ‎2024-03-19

me: 03/19/2024, 05:53:44 CPU %: 8.93% Memory Usage: 1122 MB/1743 MB Uptime: 3 days 08:02:49
Time: 03/19/2024, 05:58:42 CPU %: 8.93% Memory Usage: 1121 MB/1743 MB Uptime: 3 days 08:07:47
Time: 03/19/2024, 06:03:40 CPU %: 8.93% Memory Usage: 1123 MB/1743 MB Uptime: 3 days 08:12:46
Time: 03/19/2024, 06:08:39 CPU %: 8.93% Memory Usage: 1121 MB/1743 MB Uptime: 3 days 08:17:44
Time: 03/19/2024, 06:13:37 CPU %: 8.93% Memory Usage: 1122 MB/1743 MB Uptime: 3 days 08:22:42
Time: 03/19/2024, 06:18:35 CPU %: 8.93% Memory Usage: 1124 MB/1743 MB Uptime: 3 days 08:27:40
Time: 03/19/2024, 06:23:33 CPU %: 8.93% Memory Usage: 1124 MB/1743 MB Uptime: 3 days 08:32:39
Time: 03/19/2024, 06:28:32 CPU %: 8.93% Memory Usage: 1122 MB/1743 MB Uptime: 3 days 08:37:37
Time: 03/19/2024, 06:33:30 CPU %: 8.93% Memory Usage: 1124 MB/1743 MB Uptime: 3 days 08:42:35
Time: 03/19/2024, 06:38:28 CPU %: 8.93% Memory Usage: 1124 MB/1743 MB Uptime: 3 days 08:47:33
[31760:33092:0319/064257.120:ERROR:device_event_log_impl.cc(236)] [06:42:57.109] USB: usb_service_win.cc:105 SetupDiGetDeviceProperty({{A45C254E-DF1C-4EFD-8020-67D146A850E0}, 6}) failed: Element not found. (0x490)
[20864:30932:0319/064257.121:ERROR:device_event_log_impl.cc(236)] [06:42:57.110] USB: usb_service_win.cc:105 SetupDiGetDeviceProperty({{A45C254E-DF1C-4EFD-8020-67D146A850E0}, 6}) failed: Element not found. (0x490)
[31760:33092:0319/064258.585:ERROR:device_event_log_impl.cc(236)] [06:42:58.223] USB: usb_service_win.cc:105 SetupDiGetDeviceProperty({{A45C254E-DF1C-4EFD-8020-67D146A850E0}, 6}) failed: Element not found. (0x490)
[20864:30932:0319/064258.585:ERROR:device_event_log_impl.cc(236)] [06:42:58.227] USB: usb_service_win.cc:105 SetupDiGetDeviceProperty({{A45C254E-DF1C-4EFD-8020-67D146A850E0}, 6}) failed: Element not found. (0x490)
[31760:33092:0319/064258.872:ERROR:device_event_log_impl.cc(236)] [06:42:58.577] USB: usb_service_win.cc:105 SetupDiGetDeviceProperty({{A45C254E-DF1C-4EFD-8020-67D146A850E0}, 6}) failed: Element not found. (0x490)
[20864:30932:0319/064258.879:ERROR:device_event_log_impl.cc(236)] [06:42:58.581] USB: usb_service_win.cc:105 SetupDiGetDeviceProperty({{A45C254E-DF1C-4EFD-8020-67D146A850E0}, 6}) failed: Element not found. (0x490)
[20864:30932:0319/064326.066:ERROR:device_event_log_impl.cc(236)] [06:43:26.065] USB: usb_service_win.cc:105 SetupDiGetDeviceProperty({{A45C254E-DF1C-4EFD-8020-67D146A850E0}, 6}) failed: Element not found. (0x490)
[31760:33092:0319/064326.066:ERROR:device_event_log_impl.cc(236)] [06:43:26.065] USB: usb_service_win.cc:105 SetupDiGetDeviceProperty({{A45C254E-DF1C-4EFD-8020-67D146A850E0}, 6}) failed: Element not found. (0x490)
Time: 03/19/2024, 06:43:26 CPU %: 49.40% Memory Usage: 1182 MB/1743 MB Uptime: 0 days 00:01:02
Time: 03/19/2024, 06:48:25 CPU %: 21.93% Memory Usage: 1148 MB/1743 MB Uptime: 0 days 00:06:01
Time: 03/19/2024, 06:53:23 CPU %: 15.25% Memory Usage: 1149 MB/1743 MB Uptime: 0 days 00:10:59
Time: 03/19/2024, 06:58:21 CPU %: 12.65% Memory Usage: 1140 MB/1743 MB Uptime: 0 days 00:15:57
Time: 03/19/2024, 07:03:20 CPU %: 11.60% Memory Usage: 1138 MB/1743 MB Uptime: 0 days 00:20:56
Time: 03/19/2024, 07:08:18 CPU %: 10.86% Memory Usage: 1138 MB/1743 MB Uptime: 0 days 00:25:54
Time: 03/19/2024, 07:13:16 CPU %: 10.25% Memory Usage: 1136 MB/1743 MB Uptime: 0 days 00:30:52
Time: 03/19/2024, 07:18:15 CPU %: 9.81% Memory Usage: 1134 MB/1743 MB Uptime: 0 days 00:35:50
Time: 03/19/2024, 07:23:13 CPU %: 9.83% Memory Usage: 1136 MB/1743 MB Uptime: 0 days 00:40:49
Time: 03/19/2024, 07:28:11 CPU %: 9.49% Memory Usage: 1134 MB/1743 MB Uptime: 0 days 00:45:47
Time: 03/19/2024, 07:33:09 CPU %: 9.25% Memory Usage: 1134 MB/1743 MB Uptime: 0 days 00:50:45
Time: 03/19/2024, 07:38:08 CPU %: 9.22% Memory Usage: 1135 MB/1743 MB Uptime: 0 days 00:55:43
Time: 03/19/2024, 07:43:06 CPU %: 9.03% Memory Usage: 1134 MB/1743 MB Uptime: 0 days 01:00:42
Time: 03/19/2024, 07:48:04 CPU %: 8.89% Memory Usage: 1134 MB/1743 MB Uptime: 0 days 01:05:40

FURRYe38 · ‎2024-03-19

Ok so both WAN and Debug pages were reset.

Please continue to monitor and observe the CPU Usage and see if you notice any creeping for this value in a upwards direction or if it seems to crest at a certain value.

JesseDiaz · ‎2024-03-20

New beta firmware installed on RBR and 2 RBS. Monitoring tools executed for RBR and both RBS. Its been up for 17 hours since I installed the new beta firmware

FURRYe38 · ‎2024-03-21

👍

JesseDiaz · ‎2024-03-21

Reboot about 7:14 pm (pst ). But weird....the log doesnt show anything about that time.....but only the WAN and LAN went down

Time: 03/21/2024, 06:50:21 CPU %: 17.36% Memory Usage: 1126 MB/1743 MB Uptime: 0 days 00:32:09
Time: 03/21/2024, 06:55:20 CPU %: 16.48% Memory Usage: 1125 MB/1743 MB Uptime: 0 days 00:37:08
Time: 03/21/2024, 07:00:19 CPU %: 15.80% Memory Usage: 1126 MB/1743 MB Uptime: 0 days 00:42:07
Time: 03/21/2024, 07:05:18 CPU %: 15.19% Memory Usage: 1125 MB/1743 MB Uptime: 0 days 00:47:05
Time: 03/21/2024, 07:10:17 CPU %: 14.61% Memory Usage: 1125 MB/1743 MB Uptime: 0 days 00:52:04
Time: 03/21/2024, 07:15:15 CPU %: 14.13% Memory Usage: 1127 MB/1743 MB Uptime: 0 days 00:57:03
Time: 03/21/2024, 07:20:14 CPU %: 13.68% Memory Usage: 1121 MB/1743 MB Uptime: 0 days 01:02:01
Time: 03/21/2024, 07:25:12 CPU %: 13.28% Memory Usage: 1120 MB/1743 MB Uptime: 0 days 01:06:59
Time: 03/21/2024, 07:30:10 CPU %: 12.97% Memory Usage: 1126 MB/1743 MB Uptime: 0 days 01:11:58
Time: 03/21/2024, 07:35:09 CPU %: 12.66% Memory Usage: 1122 MB/1743 MB Uptime: 0 days 01:16:56
Time: 03/21/2024, 07:40:07 CPU %: 12.38% Memory Usage: 1124 MB/1743 MB Uptime: 0 days 01:21:54
Time: 03/21/2024, 07:45:05 CPU %: 12.11% Memory Usage: 1118 MB/1743 MB Uptime: 0 days 01:26:52
Time: 03/21/2024, 07:50:03 CPU %: 11.95% Memory Usage: 1126 MB/1743 MB Uptime: 0 days 01:31:51
Time: 03/21/2024, 07:55:02 CPU %: 11.79% Memory Usage: 1119 MB/1743 MB Uptime: 0 days 01:36:49
Time: 03/21/2024, 08:00:00 CPU %: 11.65% Memory Usage: 1125 MB/1743 MB Uptime: 0 days 01:41:47
Time: 03/21/2024, 08:04:58 CPU %: 11.55% Memory Usage: 1125 MB/1743 MB Uptime: 0 days 01:46:46
Time: 03/21/2024, 08:09:57 CPU %: 11.39% Memory Usage: 1125 MB/1743 MB Uptime: 0 days 01:51:44
Time: 03/21/2024, 08:14:55 CPU %: 11.28% Memory Usage: 1125 MB/1743 MB Uptime: 0 days 01:56:42
Time: 03/21/2024, 08:19:53 CPU %: 11.18% Memory Usage: 1124 MB/1743 MB Uptime: 0 days 02:01:40
Time: 03/21/2024, 08:24:52 CPU %: 11.08% Memory Usage: 1123 MB/1743 MB Uptime: 0 days 02:06:39
Time: 03/21/2024, 08:29:50 CPU %: 10.98% Memory Usage: 1125 MB/1743 MB Uptime: 0 days 02:11:37
Time: 03/21/2024, 08:34:48 CPU %: 10.88% Memory Usage: 1119 MB/1743 MB Uptime: 0 days 02:16:35
Time: 03/21/2024, 08:39:47 CPU %: 10.82% Memory Usage: 1122 MB/1743 MB Uptime: 0 days 02:21:34
Time: 03/21/2024, 08:44:45 CPU %: 10.74% Memory Usage: 1125 MB/1743 MB Uptime: 0 days 02:26:32
Time: 03/21/2024, 08:49:43 CPU %: 10.68% Memory Usage: 1123 MB/1743 MB Uptime: 0 days 02:31:30
Time: 03/21/2024, 08:54:42 CPU %: 10.62% Memory Usage: 1121 MB/1743 MB Uptime: 0 days 02:36:29

FURRYe38 · ‎2024-03-22

I recommend opening up a support ticket with NG support and lets start giving them more information and ask about RMA options. Only thing I can think of is that this RBR maybe faulty and no mater FW version, needs to be replaced.

JesseDiaz · ‎2024-03-22

Agreed. Now what would be the best way to do this as I know Fernando, one of the engineers at Netgear, is watchng this thread and is that has been helping me during this time including giving me all the beta firmwares.

FYI RBR just rebooted again

RBR Log

Time: 03/22/2024, 06:17:28 CPU %: 8.57% Memory Usage: 1131 MB/1743 MB Uptime: 0 days 01:02:20
Time: 03/22/2024, 06:22:26 CPU %: 8.50% Memory Usage: 1131 MB/1743 MB Uptime: 0 days 01:07:18
Time: 03/22/2024, 06:27:25 CPU %: 8.52% Memory Usage: 1131 MB/1743 MB Uptime: 0 days 01:12:17
Time: 03/22/2024, 06:32:23 CPU %: 8.45% Memory Usage: 1133 MB/1743 MB Uptime: 0 days 01:17:15
Time: 03/22/2024, 06:37:21 CPU %: 8.40% Memory Usage: 1132 MB/1743 MB Uptime: 0 days 01:22:13
Time: 03/22/2024, 06:42:19 CPU %: 8.39% Memory Usage: 1130 MB/1743 MB Uptime: 0 days 01:27:12
Time: 03/22/2024, 06:47:18 CPU %: 8.37% Memory Usage: 1129 MB/1743 MB Uptime: 0 days 01:32:10
Time: 03/22/2024, 06:52:16 CPU %: 8.31% Memory Usage: 1126 MB/1743 MB Uptime: 0 days 01:37:08
Time: 03/22/2024, 06:57:14 CPU %: 8.29% Memory Usage: 1131 MB/1743 MB Uptime: 0 days 01:42:06
Time: 03/22/2024, 07:02:13 CPU %: 8.33% Memory Usage: 1128 MB/1743 MB Uptime: 0 days 01:47:05
Time: 03/22/2024, 07:07:11 CPU %: 8.28% Memory Usage: 1131 MB/1743 MB Uptime: 0 days 01:52:03
Time: 03/22/2024, 07:12:09 CPU %: 8.26% Memory Usage: 1130 MB/1743 MB Uptime: 0 days 01:57:01
Time: 03/22/2024, 07:17:08 CPU %: 8.25% Memory Usage: 1130 MB/1743 MB Uptime: 0 days 02:02:00
Time: 03/22/2024, 07:22:06 CPU %: 8.27% Memory Usage: 1131 MB/1743 MB Uptime: 0 days 02:06:58
Time: 03/22/2024, 07:27:04 CPU %: 8.26% Memory Usage: 1128 MB/1743 MB Uptime: 0 days 02:11:56
Time: 03/22/2024, 07:32:02 0 0 0 Call to debug page timed out/did not fully populate

FURRYe38 · ‎2024-03-22

Ya I sent him this as well.

Just to confirm you had done a full on factory reset and setup from scratch with the beta FW?

I'd at least get a ticket open and get something started. I just had someone PM me from Feb and said was having bad issues with there 970 series, got an RMA and they are good now. So I'm wondering if yours maybe faulty out of the box like there's was. I told the user to ask about a cross shipping RMA where NG could send you a RMA unit while you hold on to the original unit, gives you some time to test out the new RMA unit. If all is good and the RMA works, then you have to send the original unit back to NG.

I think this would be worth getting that started while you and @Straq continue on this original unit.

JesseDiaz · ‎2024-03-22

Ive done a reset a few times....but not with this most recent beta firmware

FURRYe38 · ‎2024-03-22

That would be one last try I guess. Full on FR. If it still continues to reboot, let NG and @Straq know.

JesseDiaz · ‎2024-03-22

I will attempt to do this before I leave out of town. Ill be away for about 2 week.

FURRYe38 · ‎2024-03-22

👍

FURRYe38 · ‎2024-05-29

Any progress on this?

@JesseDiaz wrote:

I will attempt to do this before I leave out of town. Ill be away for about 2 week.

JesseDiaz · ‎2024-05-29

They sent me a new router....but still old issues. Its still rebooting.....at least based on the logs. Stability is a little worse too. Running the newrouterstat and newsatstats debug tools again

FURRYe38 · ‎2024-05-30

Have you been updating the support ticket on this?

What FW version is on the newer RBR?

JesseDiaz · ‎2024-05-30

I have...every move. I have the latest 9.11.1.1. or something like that. They wanted be on non-beta firmware

FURRYe38 · ‎2024-05-30

Ok, only other idea would be to put a Fan under or on top of the RBR. I see that a couple of other users posted about seeing connection issues at the RBR and after putting a fan on top, seemed to have stopped that. Have sent this to NG as well.

JesseDiaz · ‎2024-05-30

I can try that but if that resolves it then I’m gonna pass on keeping it.

FURRYe38 · ‎2024-05-31

Understandable. 👍

FURRYe38 · ‎2024-06-03

FYI, new FW available:

https://community.netgear.com/t5/Orbi-WiFi-7-BE-Mesh-Systems/New-RBE970-RBE971-Firmware-Version-9-12...

JesseDiaz · ‎2024-06-03

Damn I didnt see it this morning. Ill look for it when I get home. Is it manual or through the Orbi interface? Also I read the release notes, but do you know if this FW is supposed to directly correct the issue Im having?

FURRYe38 · ‎2024-06-03

I don't know for sure. I'm hoping it does for you.

I would personally recommend manually:

https://community.netgear.com/t5/Orbi-WiFi-7-BE-Mesh-Systems/Procedure-for-Factory-Reset-of-RBE970-s...

Download the files to a wired PC, bring RBS to same room or near RBR. Use MS Edge browser. Follow the PDF I linked.

Power cycle the system OFF and beck ON. Observe. If you continue to see behavior, FR and setup from scratch and check again. If still there, let NG know thru your support ticket.

JesseDiaz · ‎2024-06-03

So updated the firmware at 20:00:00 or somehere about there...and here is the log file right before and after. CPU Usuage just skyrocketed. I just now placed the fan on the router. Im not sure that this is due to syncing between the router and SAT but this is over an hours since I installed the new firmware. The highest its EVER been is 12% ( with the replacement router). It was always under 11% with the original router. And I did do the firmware manually and rebooted everything.

Time: 06/03/2024, 19:49:00 CPU %: 12.18% Memory Usage: 1038 MB/1743 MB Uptime: 7 days 13:25:29
Time: 06/03/2024, 19:53:58 CPU %: 12.18% Memory Usage: 1036 MB/1743 MB Uptime: 7 days 13:30:27
Time: 06/03/2024, 19:58:56 CPU %: 12.19% Memory Usage: 1031 MB/1743 MB Uptime: 7 days 13:35:25
Time: 06/03/2024, 20:03:55 CPU %: 44.48% Memory Usage: 1316 MB/1743 MB Uptime: 0 days 00:00:37
Time: 06/03/2024, 20:08:54 CPU %: 51.23% Memory Usage: 1098 MB/1743 MB Uptime: 0 days 00:05:36
[29644:15436:0603/201415.247:ERROR:fallback_task_provider.cc(127)] Every renderer should have at least one task provided by a primary task provider. If a "Renderer" fallback task is shown, it is a bug. If you have repro steps, please file a new bug and tag it as a dependency of crbug.com/739782.
Time: 06/03/2024, 20:13:53 0 0 0 Call to debug page timed out/did not fully populate
Time: 06/03/2024, 20:19:30 CPU %: 46.38% Memory Usage: 1111 MB/1743 MB Uptime: 0 days 00:03:08
Time: 06/03/2024, 20:24:28 CPU %: 30.18% Memory Usage: 1100 MB/1743 MB Uptime: 0 days 00:08:06
Time: 06/03/2024, 20:29:27 CPU %: 27.32% Memory Usage: 1090 MB/1743 MB Uptime: 0 days 00:13:07
Time: 06/03/2024, 20:34:27 CPU %: 26.83% Memory Usage: 1088 MB/1743 MB Uptime: 0 days 00:18:05
Time: 06/03/2024, 20:39:26 CPU %: 26.56% Memory Usage: 1089 MB/1743 MB Uptime: 0 days 00:23:11
Time: 06/03/2024, 20:44:31 CPU %: 26.09% Memory Usage: 1088 MB/1743 MB Uptime: 0 days 00:28:09
Time: 06/03/2024, 20:49:29 CPU %: 26.01% Memory Usage: 1087 MB/1743 MB Uptime: 0 days 00:33:07
Time: 06/03/2024, 20:54:34 CPU %: 26.10% Memory Usage: 1086 MB/1743 MB Uptime: 0 days 00:38:12
Time: 06/03/2024, 20:59:32 CPU %: 26.03% Memory Usage: 1086 MB/1743 MB Uptime: 0 days 00:43:10
Time: 06/03/2024, 21:04:30 CPU %: 25.96% Memory Usage: 1085 MB/1743 MB Uptime: 0 days 00:48:08
Time: 06/03/2024, 21:09:29 CPU %: 26.00% Memory Usage: 1083 MB/1743 MB Uptime: 0 days 00:53:07

FURRYe38 · ‎2024-06-04

Yes that would be expected to see higher than normal CPU usage while the system is settling in.

Be sure to power OFF the ISP modem, RBR and RBS for 1 minute then back ON in same order.

Give it about 10-30 minutes then check CPU usage. Should be low values by then I would presume.