Date: Thu, 27 Oct 2016 21:52:38 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: YongHyeon PYUN <pyunyh@gmail.com> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: CURRENT: re(4) crashing system Message-ID: <20161027215238.49c1a037.ohartman@zedat.fu-berlin.de> In-Reply-To: <20161027010004.GA1215@michelle.fasterthan.co.kr> References: <20161023132538.6bf55fb2@hermann> <20161024051359.GA1185@michelle.fasterthan.co.kr> <20161024140337.47af924e@freyja.zeit4.iv.bundesimmobilien.de> <20161025020538.GA1238@michelle.fasterthan.co.kr> <20161025070338.76ad6711@hermann> <20161027010004.GA1215@michelle.fasterthan.co.kr>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/NTHGmNAIAXvTVoCf1yM/1El Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Am Thu, 27 Oct 2016 10:00:04 +0900 YongHyeon PYUN <pyunyh@gmail.com> schrieb: > On Tue, Oct 25, 2016 at 07:03:38AM +0200, Hartmann, O. wrote: > > On Tue, 25 Oct 2016 11:05:38 +0900 > > YongHyeon PYUN <pyunyh@gmail.com> wrote: > > =20 >=20 > [...] >=20 > > > I'm not sure but it's likely the issue is related with EEE/Green > > > Ethernet handling. EEE is negotiated feature with link partner. If > > > you directly connect your laptop to non-EEE capable link partner > > > like other re(4) box without switches you may be able to tell > > > whether the issue is EEE/Green Ethernet related one or not. =20 > >=20 > > Me either since when I discovered a problem the first time with > > CURRENT, that was the Friday before last week's Friday, there was a > > unlucky coicidence: I got the new switch, FreeBSD introduced a serious > > bug and I changed the NICs. > >=20 > > The laptop, the last in the row of re(4) equipted systems on which I > > use the Realtek NIC, does well now with Green IT technology, but > > crashes on plugging/unplugging - not on each event, but at least in one > > of ten. =20 >=20 > Hmm, it seems you know how to trigger the issue. When you unplug > UTP cable was there active network traffic on re(4) device? > It would be helpful to know which event triggers the crash(e.g. > unplugging or plugging). And would you show me backtrace of panic? Yes, as I wrote, plugging and unplugging. Usually, there is no traffic I'm = aware of, simply the - a hunch - attempt to renegotiate the connection triggers the c= rash. As I can force by bringing up and down the port on the switch. Of course you can get a panic/backtrace, but I need the weekend. I complai= ned in another thread about the inability of getting a core - I use ELI encrypt= ed swap, so I shot myself at that point. >=20 > > I guess the Green IT issue is more a unlucky guess of mine and went > > hand in hand with the problem I face with CURRENT right now on some > > older, Non UEFI machines. > > =20 >=20 > Ok. >=20 > [...] > >=20 > > As requested the informations about re0 and rgephy0 on the laptop > > (Lenovo E540)=20 > >=20 > > [...] > >=20 > > rgephy0: <RTL8251 1000BASE-T media interface> PHY 1 on miibus0 > > rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, > > 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT-FDX, 1000baseT-FDX-master, > > 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow > >=20 > > re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port > > 0x3000-0x30ff mem 0xf0d04000-0xf0d04fff,0xf0d00000-0xf0d03fff at device > > 0.0 on pci2 re0: Using 1 MSI-X message re0: ASPM disabled > > re0: Chip rev. 0x50800000 > > re0: MAC rev. 0x00100000 =20 >=20 > This looks like 8168GU controller. >=20 > [...] >=20 > > I use options netmap in kernel config, but the problem is also present > > without this option - just for the record. > > =20 >=20 > Yup, netmap(4) has nothing to do with the crash. >=20 > Thanks. > _______________________________________________ > 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" --Sig_/NTHGmNAIAXvTVoCf1yM/1El Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJYElsGAAoJEOgBcD7A/5N8pw8H/1uNdTn79FsV8THnUXoP2llw dzJtY4klCOsrYZW1dZceLWebJ6TYmOfeOwWxsEq1jq8287VAWan9TqJLdGBoDmhT hMzdI95RYIqkKr9bcRN+9CDB8I+/x0KcfZla+8LXG2doIBrgp6F92fI8wnwqivCC bNTTEqAhAOGfsE4ajFHNaw3yfHFyUrYBR2M2TxeCMt/afLj259KvFeYt2AxWD/iA RA9a17ctjcW1SaCu8lkg/aakWxmZ4upUoxf8MxL8ojMJxGagec3Au2/NQLuUcrnz 62nhLQEujabnV9vxaOVX160yggTsI0l3BJ49LjfAFptsRaWFgdxKZRcW7kA4M0E= =dl83 -----END PGP SIGNATURE----- --Sig_/NTHGmNAIAXvTVoCf1yM/1El--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161027215238.49c1a037.ohartman>