From owner-freebsd-current@freebsd.org Mon Oct 31 02:12:29 2016 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 27F6CC27217 for ; Mon, 31 Oct 2016 02:12:29 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pf0-x233.google.com (mail-pf0-x233.google.com [IPv6:2607:f8b0:400e:c00::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E9A791C3B for ; Mon, 31 Oct 2016 02:12:28 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by mail-pf0-x233.google.com with SMTP id 189so15108835pfz.3 for ; Sun, 30 Oct 2016 19:12:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-disposition:in-reply-to:user-agent; bh=6v/oNpjzJacVlJDd2DEEko1IvC8J2oxBPCWKrFMhlhM=; b=jeLfFV0sTNSHsTCof48AIrPTQa4V8rPIJQCiCWxDkuCSVxHxH3sk1hBq7lnCQq9CZo 915FCb6W6EJdAs7XAVXWFVVrNotm8dknq6+a42eVfmbcwQwj8Rk/Gn8k0IadzSRNqmS8 cpcO5D1aAyrvaxnL/b4VME4fsbeMWxS/IdXV5a4g/VDL74t12XPyBEDQZJoxlIyjePBI LgAAu5AzMCYEurPIYKBzMSRcwDrvEt/Fyr2i2HEuT74FCb/Lmg7u3GW4I1cCe/Tze5dc BJ/SHT1owGKysHp8MvzQxGtZ0z5sjrdYNDP9+XhzrWSCb2p221HcpxcncoSPwqU2JEoH p9kw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:date:to:cc:subject:message-id:reply-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=6v/oNpjzJacVlJDd2DEEko1IvC8J2oxBPCWKrFMhlhM=; b=YHKwGSh6Q7ETnWNGGbvGMIALm74z79WHhqR9GI8xyIv2+w1O2+X/KCRh3AJJJB+x/9 LF1JSue3BKRdrgJbaRNPHm37e25VvGZwkR//RkcFW6vQnwLjVZr0T9WgXCLHTS/1aTCy 0SdnPpJhPo+LuWBToJCt5xheXXQ0wc02gzur2F8OXtqjCmZiwkqDRxIGFxhxBViJFkNT TRFL4JZQ9Pi4ZmLnEyk1JqrTdf9zYOvCx1zEFIBQ4v0PY25UEbxIAEcCqCh62sDeAh6l /1nqQlommTdhY3FXdv4hlZAZ0u3z3+EJ8N9vY69DytS/N41mzSk+X2IPE+3CzQnHdhcO l9nA== X-Gm-Message-State: ABUngvejCyPwm6iBQMx+G74J1Gadqxr13lduwNxywK08zYSwJ02GCQh+GvTtsaWWt22wRw== X-Received: by 10.98.35.140 with SMTP id q12mr44849648pfj.180.1477879948481; Sun, 30 Oct 2016 19:12:28 -0700 (PDT) Received: from localhost ([61.74.222.244]) by smtp.gmail.com with ESMTPSA id xg4sm32307903pac.39.2016.10.30.19.12.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 30 Oct 2016 19:12:27 -0700 (PDT) From: YongHyeon PYUN X-Google-Original-From: "YongHyeon PYUN" Received: by localhost (sSMTP sendmail emulation); Mon, 31 Oct 2016 11:12:22 +0900 Date: Mon, 31 Oct 2016 11:12:22 +0900 To: "Hartmann, O." Cc: FreeBSD CURRENT Subject: Re: CURRENT: re(4) crashing system Message-ID: <20161031021222.GA1252@michelle.fasterthan.co.kr> Reply-To: pyunyh@gmail.com 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> <20161028212113.5c4a2ca2@hermann> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161028212113.5c4a2ca2@hermann> User-Agent: Mutt/1.4.2.3i 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, 31 Oct 2016 02:12:29 -0000 On Fri, Oct 28, 2016 at 09:21:13PM +0200, Hartmann, O. wrote: > On Thu, 27 Oct 2016 10:00:04 +0900 > YongHyeon PYUN wrote: > > > On Tue, Oct 25, 2016 at 07:03:38AM +0200, Hartmann, O. wrote: > > > On Tue, 25 Oct 2016 11:05:38 +0900 > > > YongHyeon PYUN wrote: > > > > > > > [...] > > > > > > 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. > > > > > > 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. > > > > > > 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. > > > > 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? > > > > > 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. > > > > > > > Ok. > > > > [...] > > > > > > As requested the informations about re0 and rgephy0 on the laptop > > > (Lenovo E540) > > > > > > [...] > > > > > > rgephy0: 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 > > > > > > re0: > > > 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 > > > > This looks like 8168GU controller. > > > > [...] > > > > > I use options netmap in kernel config, but the problem is also > > > present without this option - just for the record. > > > > > > > Yup, netmap(4) has nothing to do with the crash. > > > > Thanks. > > Attached, you'll find the backtrace of the crash. This time it was > really easy - just one pull of the LAN cabling - and we are happy :-/ > > Please let me know if you need something else. I will return to normal > operations (disabling debugging) due to CURRENT is very unstable at the > moment on other hosts beyond r307157. > It seems the attachment was stripped.