B5 Rebooting "ethernet link emac rx dma stuck"


#1

Upgraded this link to 1.5.1 a few days ago. There was a power last night and when the power came back this B5 rebooted every three minutes for three hours with the following in the log file over and over again.

BTW: Startup reason says ‘user reboot’ but we didn’t touch it until this AM when I logged in and saw the alarms.

2018-08-06 09:27:40 (UTC +0000) root: MIMO_EVENT binaryversion=90afb59714e83b80041e9bf58c3ba9765029cc29 build_time=2018-06-06 23:01:55 (UTC +0000) bamboo_build_time_stamp=2018-06-06T23:02:19.832Z bamboo_build_number=19 project=FWREL-REL5 branch=release/1.5.1
2018-08-06 09:27:47 (UTC +0000) root: MIMO_EVENT ethernet vendor id: 0x243d91.
2018-08-06 09:27:47 (UTC +0000) root: MIMO_EVENT Shutdown reason: Reboot by a SW User Process - Ethernet inactivity
2018-08-06 09:27:49 (UTC +0000) root: MIMO_EVENT Startup reason: User Reboot
2018-08-06 09:28:41 (UTC +0000) root: MIMO_EVENT ethernet link emac rx dma stuck
2017-01-01 00:00:02 (UTC +0000) root: MIMO_EVENT no GPS signal for 3 seconds
2018-08-06 09:29:34 (UTC +0000) root: MIMO_EVENT GPS signal recovered
2018-08-06 09:29:46 (UTC +0000) root: MIMO_EVENT Wireless associated
2018-08-06 09:30:01 (UTC +0000) root: MIMO_EVENT ethernet link becomes ready
2018-08-06 09:30:04 (UTC +0000) root: MIMO_EVENT ethernet link down
2018-08-06 09:30:06 (UTC +0000) root: MIMO_EVENT ethernet link up (100/Full)
2018-08-06 09:30:09 (UTC +0000) root: MIMO_EVENT binaryversion=90afb59714e83b80041e9bf58c3ba9765029cc29 build_time=2018-06-06 23:01:55 (UTC +0000) bamboo_build_time_stamp=2018-06-06T23:02:19.832Z bamboo_build_number=19 project=FWREL-REL5 branch=release/1.5.1
2018-08-06 09:30:17 (UTC +0000) root: MIMO_EVENT ethernet vendor id: 0x243d91.
2018-08-06 09:30:17 (UTC +0000) root: MIMO_EVENT Shutdown reason: Reboot by a SW User Process - Ethernet inactivity
2018-08-06 09:30:19 (UTC +0000) root: MIMO_EVENT Startup reason: User Reboot
2018-08-06 09:30:58 (UTC +0000) root: MIMO_EVENT ethernet link emac rx dma stuck
2017-01-01 00:00:03 (UTC +0000) root: MIMO_EVENT no GPS signal for 3 seconds
2018-08-06 09:31:51 (UTC +0000) root: MIMO_EVENT GPS signal recovered
2018-08-06 09:32:04 (UTC +0000) root: MIMO_EVENT Wireless associated
2018-08-06 09:32:17 (UTC +0000) root: MIMO_EVENT ethernet link is not ready
2018-08-06 09:32:20 (UTC +0000) root: MIMO_EVENT ethernet link up (100/Full)
2018-08-06 09:32:23 (UTC +0000) root: MIMO_EVENT ethernet link down
2018-08-06 09:32:23 (UTC +0000) root: MIMO_EVENT binaryversion=90afb59714e83b80041e9bf58c3ba9765029cc29 build_time=2018-06-06 23:01:55 (UTC +0000) bamboo_build_time_stamp=2018-06-06T23:02:19.832Z bamboo_build_number=19 project=FWREL-REL5 branch=release/1.5.1
2018-08-06 09:32:25 (UTC +0000) root: MIMO_EVENT ethernet link up (100/Full)
2018-08-06 09:32:30 (UTC +0000) root: MIMO_EVENT ethernet vendor id: 0x243d91.
2018-08-06 09:32:30 (UTC +0000) root: MIMO_EVENT Shutdown reason: Reboot by a SW User Process - Ethernet inactivity
2018-08-06 09:32:32 (UTC +0000) root: MIMO_EVENT Startup reason: User Reboot
2018-08-06 09:33:21 (UTC +0000) root: MIMO_EVENT ethernet link emac rx dma stuck
2017-01-01 00:00:01 (UTC +0000) root: MIMO_EVENT no GPS signal for 3 seconds
2018-08-06 09:34:14 (UTC +0000) root: MIMO_EVENT GPS signal recovered
2018-08-06 09:34:38 (UTC +0000) root: MIMO_EVENT ethernet link is not ready
2018-08-06 09:34:42 (UTC +0000) root: MIMO_EVENT Wireless associated
2018-08-06 09:34:46 (UTC +0000) root: MIMO_EVENT ethernet link up (100/Full)
2018-08-06 09:34:49 (UTC +0000) root: MIMO_EVENT binaryversion=90afb59714e83b80041e9bf58c3ba9765029cc29 build_time=2018-06-06 23:01:55 (UTC +0000) bamboo_build_time_stamp=2018-06-06T23:02:19.832Z bamboo_build_number=19 project=FWREL-REL5 branch=release/1.5.1


#2

Ouch, can’t say I remember seeing something like this. Have you contacted Mimosa Support? If they find the issue, please let the rest of us know what the solution is!


#3

Hi @ian1,

This is very interesting and also very bad. I haven’t seen anything like this, but I am creating you a case right now. Hang tight and I’ll send you an email with more info!


#4

Thanks Dustin - sent the info in email as requested.

Ian


#5

Please do let the rest of us know what you all find.


#6

I do know they are looking at it. I’m behind on this and a few other things because I’m out on a customer site. :frowning: Will let you guys know more soon.