From owner-freebsd-current@freebsd.org Thu Feb 4 00:51:45 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 1E352A9BC03 for ; Thu, 4 Feb 2016 00:51:45 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::234]) (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 E313F158B for ; Thu, 4 Feb 2016 00:51:44 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by mail-pf0-x234.google.com with SMTP id n128so24396170pfn.3 for ; Wed, 03 Feb 2016 16:51:44 -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-type:content-disposition:in-reply-to:user-agent; bh=6VeRUMfg1yQZ8H7d2p9KBza8fPXaUOS15axmlsiLVJY=; b=wMfk1RisugpV7FfqwNX0H43PRaySnOJrGpCcXc5PeTSs5tdQ/f8bsbnAn754oU6FPU 4BSqG8x7ITFiDKUsuV5pHVGozafWW0SD5a2xYZUb9j6SvpzCaNXOVWzJOT3juaAs6BLV FxY4cWBnTJqzeSvlv+VVSX+awGGz71qHZVByuSX8n88EY1JfjxppaiwPVxmjxrbdJ922 5R2HLSWstuVi4T5Q34bm7UzYJ44w8dM8k/rOF2TbIYkaX++lnD19Y2V8aun5M70xWCU/ UOG6Efxjlo0Ifqgu9SZJK0Rv8KNsQpaghbRUx/IURrrXj9KVpaPoVVo1pUrCLABCSwhn qlXw== 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-type:content-disposition :in-reply-to:user-agent; bh=6VeRUMfg1yQZ8H7d2p9KBza8fPXaUOS15axmlsiLVJY=; b=A4o86CJN1MaFAutyEwTG6DqgTepQTTE93/7c1oMfhPX5lyhdWqJmnSDZBAFrDo+Q87 yIcRnvMihVYW9KqjbdYl2aipJKMIU8RlairLlr+EQZlBaaHJyL5475CAb2d95EI9eKEX Df+trPRv7qy0zHZ6J7nMRam1xu/VQZTL9ZnH7o/YPmsr3/FqzdNZ0+voJvaafFM1pqx4 k8SBsSetun+dJ4AuvObQ2mMm/9EPxpI7jJF6OxpbF8751Gy6Id8KhSsGOHYPhJlFQt5E 9a88Kh2INssFuUQgk7vNnH+T+CzzK741UvUH43IzEmt0UAbE5OljJIaKpALQHzNg4L0+ vgoA== X-Gm-Message-State: AG10YOSXIJsy7dYTzSqC8OzYWhrtQASDDYuIaOcxUH7NyGE0GcSCZ3EdLsMXzLwCqwfhtw== X-Received: by 10.66.100.228 with SMTP id fb4mr6882772pab.84.1454547104566; Wed, 03 Feb 2016 16:51:44 -0800 (PST) Received: from localhost ([106.247.248.2]) by smtp.gmail.com with ESMTPSA id dg1sm12472464pad.18.2016.02.03.16.51.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Feb 2016 16:51:43 -0800 (PST) From: YongHyeon PYUN X-Google-Original-From: "YongHyeon PYUN" Received: by localhost (sSMTP sendmail emulation); Thu, 04 Feb 2016 09:51:32 +0900 Date: Thu, 4 Feb 2016 09:51:32 +0900 To: s.o.k@web.de Cc: freebsd-current@freebsd.org Subject: Re: Realtek 8168/8111 if_re not working in current r295091 Message-ID: <20160204005132.GA1181@michelle.fasterthan.co.kr> Reply-To: pyunyh@gmail.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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: Thu, 04 Feb 2016 00:51:45 -0000 On Wed, Feb 03, 2016 at 08:57:01PM +0100, s.o.k@web.de wrote: > After updating -current at Jan, 31st (r295091) the Realtek ethernet device driver of my Zotac ZBox RI323 mini pc seems to be broken: I can neither connect to the host even though the interface is shown as active, nor can I initiate connection from the host through re0. > Reverting the kernel to my previous build -current r290151 (install date Nov 1st, 2015) the re0 interface is working OK. > > Looking through the svn logs regarding /head/sys/dev/re/if_re.c I supect, that Revision 290566 might have someting to do with this and that I have to include my Realtek Chipset to the exclusion list for "enabling RX/TX after initial configuration (or viceversa; I am really confused here), but I havent got a clue how; as I do not know how to find the right RL_HWREV_XXX flag for my device. > You can get Chip/MAC revision information from dmesg output. (dmesg | grep re0 would do).