Bug #3373
closed
Sun Quad fast Ethernet ports constantly resetting
0%
Description
Using the hme driver in version 2.1 with part# 501-5406-07 Sun Quad Fast Ethernet PCI card. Once configured, the ports operate normally until link is lost due to cable unplugged. Upon reconnecting the cable, the port begins an endless loop of constantly resetting at an irregular rate of a few seconds interval. If the port is configured statically, pinging the gateway will alternate between normal return when link light is on to "no route to host" when link light is off. This condition is usually accompanied by console error "arprequest: cannot find matching address." Following is System Log sample after cable for hme0 configured as WAN DHCP is reconnected:
Dec 21 17:12:03 pfSense kernel: hme0: link state changed to UP
Dec 21 17:12:03 pfSense kernel: hme0: link state changed to DOWN
Dec 21 17:12:03 pfSense check_reload_status: Linkup starting hme0
Dec 21 17:12:03 pfSense check_reload_status: Linkup starting hme0
Dec 21 17:12:04 pfSense php: rc.linkup: The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf hme0 > /tmp/hme0_output 2> /tmp/hme0_error_output' returned exit code '1', the output was ''
Dec 21 17:12:04 pfSense php: rc.linkup: Accept router advertisements on interface hme0
Dec 21 17:12:05 pfSense php: rc.linkup: ROUTING: setting default route to 192.168.0.1
Dec 21 17:12:05 pfSense php: rc.linkup: DEVD Ethernet detached event for wan
Dec 21 17:12:05 pfSense php: rc.linkup: The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf hme0 > /tmp/hme0_output 2> /tmp/hme0_error_output' returned exit code '15', the output was ''
Dec 21 17:12:05 pfSense php: rc.linkup: The command '/sbin/route change -inet default '192.168.0.1'' returned exit code '1', the output was 'route: writing to routing socket: No such process route: writing to routing socket: Network is unreachable change net default: gateway 192.168.0.1: Network is unreachable'
Dec 21 17:12:05 pfSense php: rc.linkup: Accept router advertisements on interface hme0
Dec 21 17:12:06 pfSense php: rc.linkup: ROUTING: setting default route to 192.168.0.1
Dec 21 17:12:06 pfSense php: rc.linkup: The command '/sbin/route change -inet default '192.168.0.1'' returned exit code '1', the output was 'route: writing to routing socket: No such process route: writing to routing socket: Network is unreachable change net default: gateway 192.168.0.1: Network is unreachable'
Updated by Chris Buechler over 10 years ago
- Status changed from New to Rejected
we don't control or develop drivers.
https://doc.pfsense.org/index.php/Policy_on_FreeBSD_issues
Updated by Charlie Singleton over 10 years ago
This driver has worked in all previous versions. There are hundreds of units in operations now with this hardware in them. This is similar to the issue with msk and other drivers that was fixed here https://github.com/pfsense/pfsense/commit/f3a4601c85c4de78caa4f12fefd64067fd83dbe8
But this does not fix this issue. Do I go to the author of the driver for a fix? Or if I fix this myself, can It be made an official fix? My concern is all the units in operation now. If they boot up and run there will be no problems until the link state changes to down (cable unplugged) and then link back up. At that point the port will never stabilize until reboot.
Updated by Chris Buechler over 10 years ago
I'm guessing it may be fixed already in FreeBSD 10, in which case there isn't anything that needs to be done for 2.2. That's where I would recommend starting though, test it on the latest 10.0 RC and see what happens. A backported patch to 8.3 via pull request to our tools github repo would be acceptable if you can confirm it works first.