Problem with re(4) Ethernet driver has resurfaced in 11-STABLE and HEAD
Thomas Mueller
mueller6722 at twc.com
Sun May 21 09:29:55 UTC 2017
from YongHyeon PYUN:
> [removed stable@ from CC]
> > I recently updated my 10.1-STABLE to 11.0-STABLE and find I can no longer connect with the Ethernet.
> > dhclient re0 produces
> > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 4
> > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 11
> > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 19
> > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 7
> > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 14
> > DHCPDISCOVER on re0 to 255.255.255.255 port 67 interval 5
> > No DHCPOFFERS received.
> > No working leases in persistent database - sleeping.
> If you assign an static IPv4 address to re(4) are you able to use
> the network interface?
> AFAIK there was no significant re(4) changes for a long time. Could
> you show us back trace information?
Problem with re(4) reappeared in both 11.0-STABLE and HEAD, but OK to trim stable@ since changes/fixes would go to HEAD first.
No connection with static IPv4 address.
Where do I get back trace information?
Problem was more severe with HEAD in that OS immediately crashed into debugger, while in 11.0-STABLE, only the connection failed but may have left memory unstable.
I can still connect on that computer with Hiro H50191 USB wireless adapter, driver rsu.
Tom
More information about the freebsd-current
mailing list