Date: Mon, 22 May 2017 10:55:46 +0900 From: YongHyeon PYUN <pyunyh@gmail.com> To: Thomas Mueller <mueller6722@twc.com> Cc: freebsd-current@freebsd.org Subject: Re: Problem with re(4) Ethernet driver has resurfaced in 11-STABLE and HEAD Message-ID: <20170522015546.GB1091@michelle.fasterthan.co.kr> In-Reply-To: <5B.41.25473.11E51295@dnvrco-omsmta03> References: <63.BF.09002.3974D195@dnvrco-omsmta01> <20170521054152.GA1091@michelle.fasterthan.co.kr> <5B.41.25473.11E51295@dnvrco-omsmta03>
next in thread | previous in thread | raw e-mail | index | archive | help
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 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170522015546.GB1091>