On Sun, May 21, 2017 at 09:29:42AM +0000, Thomas Mueller wrote:
> 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?
> 

https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html

> 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 guess you have two issues. No connection with static IPv4 address
and kernel crash.  Couldn't you obtain a kernel crash dump when you
encounter kernel panic? If this is no crash dump you probably have
some missing kernel configuration.

> I can still connect on that computer with Hiro H50191 USB wireless adapter, 
> driver rsu.
> 
> Tom
> 
_______________________________________________
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to