From owner-freebsd-stable@FreeBSD.ORG Thu Sep 26 02:32:38 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 11741EFA for ; Thu, 26 Sep 2013 02:32:38 +0000 (UTC) (envelope-from mueller6721@twc.com) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.225]) by mx1.freebsd.org (Postfix) with ESMTP id C5A8F2652 for ; Thu, 26 Sep 2013 02:32:37 +0000 (UTC) Received: from [74.130.200.176] ([74.130.200.176:52950] helo=localhost) by cdptpa-oedge03 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 36/52-26070-28C93425; Thu, 26 Sep 2013 02:31:30 +0000 Date: Thu, 26 Sep 2013 02:31:30 +0000 Message-ID: <36.52.26070.28C93425@cdptpa-oedge03> From: "Thomas Mueller" To: freebsd-stable@freebsd.org Subject: Re: dhclient failure with Realtek 8111E Etnernet on new MSI motherboard References: <20130925063610.GA1507@michelle.cdnetworks.com> X-RR-Connecting-IP: 107.14.168.142:25 X-Cloudmark-Score: 0 Cc: Yonghyeon PYUN X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Sep 2013 02:32:38 -0000 > It looks like 8168E-VL. > Could you try attached patch and show me the dmesg output(re(4) and > rgephy(4) only)? The patch was generated to support 8106E but it > will correctly show MAC revision number. I assume I go to /usr/src and run patch < /home/arlene/computer/re.8106.diff Then rebuild the kernel with -DNO_MODULES and install under a different name, like kernelre? I would install this on USB-stick installation, could do this for i386 USB-stick installation as well. > > Somewhat later I got > > Memory modified after free 0xfffffe0011546800(2048) val=977e3dd > 4 @ 0xfffffe0011546800 > > Memory modified after free 0xfffffe001153b800(2048) val=ffffffff @ 0xfffffe00115 > 3b800 > > Memory modified after free 0xfffffe0011524800(2048) val=977e3dd4 @ 0xfffffe00115 > 24800 > > VESA: set_mode(): 24(18) -> 24(18) > > Memory modified after free 0xfffffe0011594000(2048) val=977e3dd4 @ 0xfffffe00115 > 94000 > The size(2048) indicates mbuf cluster which in turn means bad > things happened in re(4). I have no idea how this can happen > though. > If you assign static IP addressi to re(4), does the driver works as > expected? I can try assigning a static address to re4, not really sure how to set up manually, though I did it long ago in Slackware Linux. I wouldn't have known size 2048 indicated something bad, though the message's presence and system crash indicated that something was fouled up in memory. Tom