From owner-freebsd-current@freebsd.org Mon Nov 7 02:25:51 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 E2D73C2D556 for ; Mon, 7 Nov 2016 02:25:51 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::231]) (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 A9D746A8; Mon, 7 Nov 2016 02:25:51 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by mail-pf0-x231.google.com with SMTP id d2so83091784pfd.0; Sun, 06 Nov 2016 18:25:51 -0800 (PST) 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=cdbvLpB5cFK4pof11K/kRnq/H9RkvLcwLwPqbZuQaaE=; b=BcuxImOBfRKB+l/pTaBUIbkN+Ok0sCm5SNG2Xc357vyplHutvQZ2SyW8EhU3o6MMo9 JhUSHx82TWZWYsFq9sozbaUKLQbgIoF9JjI4TkXYzrABonP7Ww1g36P+DMugCTTq6FMW Lps0fXvSfgQdXk+b+hRkX5ZHyHlvLPdBj7TPpO6H/Fnc2Xpx9PKEwBvEUniEiy23oxHq itQ6xF8ehkYJwDGeUJiJL8mKj3CR9AvPBEXjMe6Ywhk6f+tmHF/JIUc9IWUUYymzfMvA WEa4uv54dLSDmZP4uUUzPLc8v8fmJW5FCwDhz+8SdwO/JhCxPpehi9pp1GaElJpoSG7L cKkA== 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=cdbvLpB5cFK4pof11K/kRnq/H9RkvLcwLwPqbZuQaaE=; b=hQbsan1kiPonMIXCv8zGZYKvGKV/2DdHLgv/q0T7LhgyqXpMVjQyfT6QPxu8KHdNVb /3Wny0eE9iGYbGnf045o96po1aJ+iydp/M5Z/8bWnmliln6SN5SMEOEUsx5N5NxRZOgB lbQVVtqj46fP5Rktd0S6zqzwxalEhYExS5gbcUIvtXSdYy1+n7vUKwnthplMBvcSv6Qb ef5mrTteEhrOrjtgh3uwj3lOWOvbvoUBq6GEvaBKfupNITiGnlgmKNPgLHnluXi0PqTg /Q3sKQs/kUJvsbOe/LampUThUAybjLMvKjY+ZSlLS8rbfA2cnTz7zUMiLFf7WHwacDsi OTyg== X-Gm-Message-State: ABUngvfW0mof4KdA4NIkb4sEMo5DD2wASd+4Mn4uAcEcUP0Tl/F8z1c3eZt+r6HaIN8uwg== X-Received: by 10.98.152.212 with SMTP id d81mr9317486pfk.12.1478484989822; Sun, 06 Nov 2016 18:16:29 -0800 (PST) Received: from localhost ([61.74.222.244]) by smtp.gmail.com with ESMTPSA id wg1sm695721pab.46.2016.11.06.18.16.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 06 Nov 2016 18:16:29 -0800 (PST) From: YongHyeon PYUN X-Google-Original-From: "YongHyeon PYUN" Received: by localhost (sSMTP sendmail emulation); Mon, 07 Nov 2016 11:16:23 +0900 Date: Mon, 7 Nov 2016 11:16:23 +0900 To: "Hartmann, O." Cc: FreeBSD CURRENT , gnn@FreeBSD.org Subject: Re: CURRENT: re(4) crashing system Message-ID: <20161107021623.GA1557@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> <20161031021222.GA1252@michelle.fasterthan.co.kr> <20161106132036.06add6ca@hermann> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161106132036.06add6ca@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, 07 Nov 2016 02:25:52 -0000 On Sun, Nov 06, 2016 at 01:20:36PM +0100, Hartmann, O. wrote: > On Mon, 31 Oct 2016 11:12:22 +0900 > YongHyeon PYUN wrote: > > > 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. > > This time I hope I got it right! > > Attached you'll find the latest CURRENT's backtrace on the provoked > crash (plug and unplug). > > I also saved the kernel and coredump, so if you need me to do further > investigations,please let me know. > Thanks a lot for the backtrace. This backtrace is not the one I expected and I guess the issue is related with cached route removal on interface down. Quick looking over the code didn't reveal the cause of crash(I'm not familiar with that part code). Probably gnn@ may have better idea what's going on here(CCed). Thanks.