From owner-freebsd-current@freebsd.org Mon May 22 04:49:44 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F3BEED78B7C for ; Mon, 22 May 2017 04:49:43 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 705E41CA0 for ; Mon, 22 May 2017 04:49:42 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LdLw5-1ddRKV0xqT-00iRfB; Mon, 22 May 2017 06:49:30 +0200 Date: Mon, 22 May 2017 06:49:22 +0200 From: "O. Hartmann" To: Thomas Mueller Cc: YongHyeon PYUN , freebsd-current@freebsd.org Subject: Re: Problem with re(4) Ethernet driver has resurfaced in 11-STABLE and HEAD Message-ID: <20170522064922.762ec941@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <20170522015546.GB1091@michelle.fasterthan.co.kr> References: <63.BF.09002.3974D195@dnvrco-omsmta01> <20170521054152.GA1091@michelle.fasterthan.co.kr> <5B.41.25473.11E51295@dnvrco-omsmta03> <20170522015546.GB1091@michelle.fasterthan.co.kr> Organization: Walstatt X-Mailer: Claws Mail 3.15.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:YEiFehpJ/doLVIgvhLxt+5IurTEn1CZdU/Aif2M+5aOw6ksBb3S zy0CtK8A2P+cDcMuCtCZAKVK7bET86Nrt6fV/XL8THP9ggWLrx2Rx8ckQ5j1TIlf9sjmYM8 fwapRH3C0JHvYMl5MJMh/15zEiXaIXJz5lAtiXSMssf6w0Vpe5b+k/SHWXM+zzg/0bIDSnF NDTLFRb4Ult/emwiTnhMw== X-UI-Out-Filterresults: notjunk:1;V01:K0:V9SMnFgMct4=:PZhwE7hCgC1+zIVxzw+iUl F2PJqwOhjqNpCl5j45GS1Oocevd0nnNnFTvAtjF5RnWsg4Cc6TIy61OaDTkdIyIwqod+RwdrR iCELDYjDdl3PzerDPwpORnllmruN+KFjtiRUQNqdQlwqt1t8RR/k0WPwPZqBEB6pR2SDC6AdV r7eBB5RkxOM03BoJtYIhW1OFHlITYzfM05/ncbizqeyq/gN7XmuBNFYUmo5rBj1jatjCru9Gr KTeyaK2pE10Dtzg6Ui61XkTIi2QKleW4eoqGg0fbc2FOL/BMSPAiELwLnc812Xjfw5XEkkH3l a+fBFTSrcwCZivBioJYT/APmZsNWq745Fd97g8bNFBFRMM3J1JM9o0RqEqRRPPpGKLGvlv+Jj N26bus5YOcFw02Ms1e8l4WcNm2fNyZ5Fz2Ph0Twjs6RSl6Rcm1Opk2B20kJIjBIIuzhVhlqXq j1UZA9hKxqkvJ4uoslHxe+sVE0WyiwBgj71oE3cpxYAY0lZ+k35yLaRUNoYBNxbeeyuWKCtlb I9bqfEro4uR0pxadJybgQKgHRoEW2Tlo4BgQGBe6q8kD2u03vB/Ri5zrZYjpUkXaHwth7bqux U3lUEAhnAt2EDbBeX6WJnYoZfZYm5SId8NJz3rkpFj+KMz24OPI5A7XXY56G3UyB/NTidnQjv c3xiRoSkLTSKtcoIDg0Xe3CWK995hiTFFGk9mkW+CA2JFZC2LWZf39khbNKQi6u1pdDHoPCpf 5TFw/SYb73JD/A8bKtU4iqBzLBsMkGi6onPdhiQkdq2AeZjJbCbjH4n1Ag7Soa8MN3BHZwjbS 4NkVnlE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2017 04:49:44 -0000 On Mon, 22 May 2017 10:55:46 +0900 YongHyeon PYUN wrote: Just for my curiosity: do you have "options FLOWTABLE" defined in your kernel config? > 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-unsubscribe@freebsd.org"