NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
[SRX5308] ERROR: miiSwitchRegisterRead: Timeout
I have the following in the logs of my SRX5308 [latest FW 4.3.3-6]. The messy alignment is verbatim.
Sat Oct 31 17:21:17 2015((GMT+0100)) [SRX5308][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x1 addr 0x0
0
00041e431380
Sat Oct 31 17:21:11 2015((GMT+0100)) [SRX5308][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x1 addr 0x0
Sat Oct 31 17:19:31 2015((GMT+0100)) [SRX5308][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x1 addr 0x0
00041e431380
Sat Oct 31 17:14:47 2015((GMT+0100)) [SRX5308][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x20 addr 0x10
Sat Oct 31 17:12:44 2015((GMT+0100)) [SRX5308][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x1 addr 0x0
0000041e431380
Sat Oct 31 17:12:22 2015((GMT+0100)) [SRX5308][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x1 addr 0x0
Fri Oct 30 10:03:26 2015((GMT+0100)) [SRX5308][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x1 addr 0x0
0000041e431380
Fri Oct 30 10:03:26 2015((GMT+0100)) [SRX5308][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x1 addr 0x0
This seems to happen mostly under heavy load, in particular with >4 large files downloading under http, over 2 or 3 WANs each with effective download bandwith approaching 70 Mbit/s. These messages correspond to observed failures of the downloads.
Rebooting the SRX5308 does not cure the problem.
Any idea?
3 Replies
Just guessing: that miiSwitchRegisterRead seems to refer to the Media Independent Interface (a standardized interface between an Ethernet logic IC and a PHYsical interface IC connected to the Ethernet magnetics), and suggests that a switch-related register can't be read.
Also: I notice that when the high traffic coinciding with these errors is underway, log-on to the SRX5308's web interface is extremely slow. This all points to the SRX5308 being maxed out by the heavy traffic.
I have the same issue on my FVS336GV3 latest FW. I have all the error messages below after reboot, without any traffic.
[FVS336GV3]Wed Jan 13 12:30:21 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x1 addr 0x0 tcindex_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980 [FVS336GV3]Wed Jan 13 13:06:27 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] xt_TCPMSS: bad length (320 bytes) out at page 0x1 addr 0x0 tcindex_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980 [FVS336GV3]Wed Jan 13 13:27:24 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x1 addr 0x0 tcindex_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980 [FVS336GV3]Wed Jan 13 14:45:13 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x21 addr 0x18 index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980 [FVS336GV3]Wed Jan 13 15:30:12 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x22 addr 0x0 index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980 [FVS336GV3]Wed Jan 13 15:32:29 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x20 addr 0x98 index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980 [FVS336GV3]Wed Jan 13 15:47:24 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x1 addr 0x0 8 index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980 [FVS336GV3]Wed Jan 13 15:52:29 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x24 addr 0xc0 index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980 [FVS336GV3]Wed Jan 13 16:07:31 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x24 addr 0x50 index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980 [FVS336GV3]Wed Jan 13 17:32:31 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x22 addr 0x14 index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980 [FVS336GV3]Wed Jan 13 18:07:35 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x22 addr 0x14 index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980 [FVS336GV3]Wed Jan 13 20:12:34 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x1 addr 0x4 4 index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980 [FVS336GV3]Wed Jan 13 20:57:19 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x20 addr 0x94 index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980 [FVS336GV3]Wed Jan 13 21:02:23 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x20 addr 0x10 index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980 [FVS336GV3]Wed Jan 13 21:37:41 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] xt_TCPMSS: bad length (320 bytes) out at page 0x20 addr 0x10 index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980 [FVS336GV3]Wed Jan 13 22:15:21 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x22 addr 0x14 index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980 [FVS336GV3]Wed Jan 13 22:27:22 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x1 addr 0x4 4 index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980 [FVS336GV3]Wed Jan 13 22:52:34 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x24 addr 0x98 index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980 [FVS336GV3]Wed Jan 13 22:57:31 2016((GMT+0100)) [FVS336GV3][Kernel][KERNEL] ERROR: miiSwitchRegisterRead: Timeout at page 0x23 addr 0x10 index_walk(tp a800000004a35f00,walker a8000000038f3900),p a8000000039c9980
Hi thomaskrampe,
I believe you have created a new post regarding your concern. Kindly check my response on this link below:
Regards,
DaneA
NETGEAR Community Team
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
