Modify

Opened 3 years ago

Closed 2 years ago

#19579 closed defect (fixed)

Ubiquiti Bullet 5M / ar71xx / ethernet sometimes not working / r45583

Reported by: bittorf@… Owned by: developers
Priority: normal Milestone:
Component: packages Version: Trunk
Keywords: Cc:

Description

after upgrading a bullet from r41522 to r45583
i detected a "missing ethernet phy":

root@box:~ mii-tool eth0
  No MII transceiver present!.

this happens sometimes and goes away with a reboot...
this never happend before with the old firmware.

Attachments (0)

Change History (4)

comment:1 Changed 3 years ago by bittorf@…

if this happens, dmesg show something like this:

[  122.050000] eth0: tx timeout
[  122.050000] eth0: link down
[  123.220000] eth0: link up (1000Mbps/Full duplex)
[  133.050000] eth0: tx timeout
[  133.050000] eth0: link down
[  133.520000] eth0: link up (1000Mbps/Full duplex)
[  139.060000] eth0: tx timeout
[  139.060000] eth0: link down
[  139.700000] eth0: link up (1000Mbps/Full duplex)
[  145.060000] eth0: tx timeout
[  145.060000] eth0: link down
[  145.880000] eth0: link up (1000Mbps/Full duplex)

comment:2 Changed 3 years ago by ufo@…

we also have that behaviour with cc-trunk since a while. downgrading some devices to bb-trunk (20150220, r44441) makes the ethernet-port more stable, but doesnt solve that problem.
the behaviour seems not that often than on cc-trunk, and most of the times we dont need a reboot (only a few times per week), because device is "repairing" it by itself after a second.

with bb-trunk:
[39696.300000] eth0: link down
[39697.300000] eth0: link up (100Mbps/Full duplex)
[40993.300000] eth0: link down
[40995.300000] eth0: link up (100Mbps/Full duplex)
[42575.300000] eth0: link down
[42576.300000] eth0: link up (100Mbps/Full duplex)

especially with xw-devices from ubnt we have more problems. is there another ticket for that?

here with cc-trunk, mostly ethernet is running in a proper way only some minutes/hours. wondering, why there is 1000MBit/s speed, we have PoE-Stuff and only 100MBit/s on the cables.. maybe its some powermanagement?
[ 253.880000] eth0: link up (10Mbps/Half duplex)
[ 255.880000] eth0: link up (100Mbps/Full duplex)
[ 299.880000] eth0: link up (100Mbps/Half duplex)
[ 301.880000] eth0: link up (100Mbps/Full duplex)
[ 317.880000] eth0: link down
[ 318.880000] eth0: link up (100Mbps/Full duplex)
[ 356.880000] eth0: link up (10Mbps/Half duplex)
[ 358.880000] eth0: link up (100Mbps/Full duplex)
[ 468.880000] eth0: link up (100Mbps/Half duplex)
[ 470.880000] eth0: link up (100Mbps/Full duplex)
[ 524.880000] eth0: link down
[ 525.880000] eth0: link up (100Mbps/Full duplex)
[ 737.880000] eth0: link up (100Mbps/Half duplex)
[ 739.880000] eth0: link up (100Mbps/Full duplex)
[ 773.880000] eth0: link up (100Mbps/Half duplex)
[ 775.880000] eth0: link up (100Mbps/Full duplex)
[ 1011.880000] eth0: link up (1000Mbps/Full duplex)

comment:3 Changed 3 years ago by ufo@…

another ticket within this context: /ticket/19085.html
ticket:19085

comment:4 Changed 2 years ago by nbd

  • Resolution set to fixed
  • Status changed from new to closed

fixed in r47892, r47895

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.