NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RS80
Oct 20, 2026Aspirant
GS752TPv2 Ports down, aborted boot sequence
I have a GS752TPv2 that powers on. But no connectivity on any port.
I connected a TTL-USB and Link up with TeraTerm into the serial console see logging attached.
I have send FW V6.0.6.2 binary over ymodem to flash and wrote them to RUNTIME1 and RUNTIME2 after reboot same sh... than before.
How can i fix the Problem? Whats goes wrong?
BOOT Loader Version 1.0.0.5 (2017-12-28 09:35:22 UTC)
CPU : 700 MHz
RAM : 128 MB
FLASH: 32 MB
Model: GS752TPv2
MAC : 80:CC:9C:**:**:**
Hit Esc key to stop autoboot: 0
## Booting image from partition ... 0
## Booting kernel from Legacy Image at 81000000 ...
Version: 6.0.6.2
Created: 2021-02-04 17:31:48 UTC
Data Size: 11009456 Bytes = 10.5 MB
Checksum ... OK
Uncompressing ... OK
Starting kernel ...
dal_cypress_construct_phyConfig_init,1039: 0.0 phy enable fail.
dal_cypress_construct_phyConfig_init,1039: 0.1 phy enable fail.
dal_cypress_construct_phyConfig_init,1039: 0.2 phy enable fail.
dal_cypress_construct_phyConfig_init,1039: 0.3 phy enable fail.
dal_cypress_construct_phyConfig_init,1039: 0.4 phy enable fail.
dal_cypress_construct_phyConfig_init,1039: 0.5 phy enable fail.
dal_cypress_construct_phyConfig_init,1039: 0.6 phy enable fail.
dal_cypress_construct_phyConfig_init,1039: 0.7 phy enable fail.
dal_cypress_construct_phyConfig_init,1055: 0.0 phy enable fail.
dal_cypress_construct_phyConfig_init,1055: 0.1 phy enable fail.
dal_cypress_construct_phyConfig_init,1055: 0.2 phy enable fail.
dal_cypress_construct_phyConfig_init,1055: 0.3 phy enable fail.
dal_cypress_construct_phyConfig_init,1055: 0.4 phy enable fail.
dal_cypress_construct_phyConfig_init,1055: 0.5 phy enable fail.
dal_cypress_construct_phyConfig_init,1055: 0.6 phy enable fail.
dal_cypress_construct_phyConfig_init,1055: 0.7 phy enable fail.
unknown rt error code f030
<3><!-RTK_INIT_FAILURE-!>Init SKI Core Driver Module....FAILED
CPU 0 Unable to handle kernel paging request at virtual address 00000000, epc == 8003de18, ra == c00ebf84
Oops[#1]:
CPU: 0 PID: 128 Comm: insmod Tainted: P O 3.18.24 #3
task: 8090c5a8 ti: 8093c000 task.ti: 8093c000
$ 0 : 00000000 00000000 00000000 0000007d
$ 4 : 00000000 ffffffff 00000000 00000000
$ 8 : 0000003c 80152134 ffffffff 803fba40
$12 : 810b6014 803120ac 00000000 00000000
$16 : 00000001 00000000 00000000 00040000
$20 : 00000001 c1a50000 c1a50000 00000000
$24 : 8003de00 c00ebe90
$28 : 8093c000 8093d9a8 803e0000 c00ebf84
Hi : 00000004
Lo : d39ab280
epc : 8003de18 down_interruptible+0x18/0x60
ra : c00ebf84 osal_sem_take+0xf4/0x158 [rtcore]
Status: 1000ff02 KERNEL EXL
Cause : 08800008
BadVA : 00000000
PrId : 00019555 (MIPS 34Kc)
Modules linked in: l2g_igmp(PO+) l2g_lacp(PO) l2g_authmgr(PO) l2g_stp(PO) l2g_gvrp(PO) ski(PO) osal(O) ksi(PO) net(PO) board_conf(O) max3421_hcd rtdrv rtk rtcore
Process insmod (pid: 128, threadinfo=8093c000, task=8090c5a8, tls=77b0a460)
Stack : 00000000 00000141 803fb940 00000000 ffffffff c00ebf84 00000000 000c0000
00000001 00000000 c15afe60 c1310000 c00ebfe8 8093da28 00040000 00000001
c1a50000 c07a7620 ffffffff ffffffff 00000000 803fb940 80152080 c1a50000
803e0000 c15a1318 00000000 87c01640 00000020 810b6000 87c02380 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
...
Call Trace:
[<8003de18>] down_interruptible+0x18/0x60
[<c00ebf84>] osal_sem_take+0xf4/0x158 [rtcore]
[<c07a7620>] rsd_l3_adminIntfMgmt_get+0x34/0xa0 [ski]
[<c15a1318>] mcast_querier_init+0xf4/0x19c [l2g_igmp]
[<c158dda8>] mcast_init+0x84/0x1a4 [l2g_igmp]
[<c1a61038>] init_module+0x38/0x90 [l2g_igmp]
[<8000058c>] do_one_initcall+0xf8/0x25c
[<80061608>] load_module+0x1ecc/0x22a8
[<80061a84>] SyS_init_module+0xa0/0x104
[<8000a81c>] handle_sys+0x11c/0x140
Code: 41706000 32100001 000000c0 <8c820000> 1040000c 00000000 2442ffff ac820000 00001021
---[ end trace ec21f9d5a702edb1 ]---
Segmentation fault
Segmentation fault
~ #
Thx a lot
Regards Sascha
1 Reply
- schumakuGuru - Experienced User
Hello Sascha
What hit my eyes is that it's says Booting kernel from Legacy Image, then it appears that some PHY could not be initialized or found.
I tend to suggest to open a support ticket via HTTPS://my.netgear.com/ as these switches come with a limited lifetime warranty, at least to the original buyer.
Where is the idea coming from using such an old firmware image? At some point (have not looked into the FW history yet), downgrading was depreciated.
Regards
-Kurt
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!