From owner-freebsd-stable@FreeBSD.ORG Thu Sep 26 05:00:45 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 23232587 for ; Thu, 26 Sep 2013 05:00:45 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pd0-x22d.google.com (mail-pd0-x22d.google.com [IPv6:2607:f8b0:400e:c02::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EEF1E2B22 for ; Thu, 26 Sep 2013 05:00:44 +0000 (UTC) Received: by mail-pd0-f173.google.com with SMTP id p10so630125pdj.4 for ; Wed, 25 Sep 2013 22:00:44 -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-type:content-disposition:in-reply-to:user-agent; bh=yhOMCjRqDJG9wCTL4r8z57B+qoInRN8SSQcV0Trf/PY=; b=AD4r1ssPG+MZi13GzRjOBEUKuA9D4WumM3g2o3sSlJJQyWJnFhMioLHYnUsz4knAD3 dFBi7p4x1NmuKJfZ5gIFgu7pFtHdJcHffUXjEv7ow0H2fro//ziw9ijhtNjrur22NBnF obF+mIpAjbq5jjzjK+d5SnU6hCjYo/pGqUmRslUqcDmWO3TUfUXeiObTW+Sq28cJGmIm K3H8LtnMsTR8UhGV715oMme6ig98z7TCfjtOORH2xoBxG4FlhfW00ThVXGYu3LlhqwlB gGgRMjW5iKkAti73dEW5DJw+cYhGTn4d/e9PGRdvcJ30HhVUwpCiTkrcZoFWkrlgOvr2 0SMw== X-Received: by 10.66.161.229 with SMTP id xv5mr3014313pab.87.1380171644564; Wed, 25 Sep 2013 22:00:44 -0700 (PDT) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPSA id ve9sm51539632pbc.19.1969.12.31.16.00.00 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 25 Sep 2013 22:00:43 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Thu, 26 Sep 2013 14:00:39 +0900 From: Yonghyeon PYUN Date: Thu, 26 Sep 2013 14:00:39 +0900 To: Thomas Mueller Subject: Re: dhclient failure with Realtek 8111E Etnernet on new MSI motherboard Message-ID: <20130926050038.GA1494@michelle.cdnetworks.com> References: <20130925063610.GA1507@michelle.cdnetworks.com> <36.52.26070.28C93425@cdptpa-oedge03> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <36.52.26070.28C93425@cdptpa-oedge03> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: pyunyh@gmail.com 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 05:00:45 -0000 On Thu, Sep 26, 2013 at 02:31:30AM +0000, Thomas Mueller wrote: > > 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 > Yes. > Then rebuild the kernel with -DNO_MODULES and install under a different name, like kernelre? > Rebuilding kernel should be enough. See http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html for more information. > 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 >