From owner-freebsd-stable@FreeBSD.ORG Mon Sep 22 01:59:38 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 30152106564A for ; Mon, 22 Sep 2008 01:59:38 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.191]) by mx1.freebsd.org (Postfix) with ESMTP id F180B8FC0C for ; Mon, 22 Sep 2008 01:59:31 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by ti-out-0910.google.com with SMTP id d27so668422tid.3 for ; Sun, 21 Sep 2008 18:59:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=VjXGrJiYUfARH+4I4T1fUqqmh+uiK7eFG4xn40kXcpg=; b=GI1G6xuRpcgZLRE3Byn2VQxmZGmc4eAzjEjCUViHf1GHmXFflvmiYPc3S/7d5OBKTY 5pWJHi4o40zZwV7dGlMXxT3vRWZZ5Kvdh/UG4GkWkYH+txe5Z/XmsazKE0aWei/mBMg+ ogc09bEggbekeMMkmj99UoS1gtEqEK4Oat+Us= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=GgncVgEy0BjRPxghRqR+mYRZZWS1BSLUEkM7o/pBT3Tpl6KmSoY8Fs8DzQgn7qdMXs eatF2/rlNqq96SMrNrJRvyWmweOuep2C0DzFC71Ck4sAAofC4VyHADtQmIynVevNQwKN 131jpdQ5fQG2SVJ2Sg1EvUyo84zUq4mRYo570= Received: by 10.110.70.17 with SMTP id s17mr4596877tia.18.1222048762025; Sun, 21 Sep 2008 18:59:22 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id a14sm11188603tia.0.2008.09.21.18.59.19 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 21 Sep 2008 18:59:20 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m8M1vMc8026898 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Sep 2008 10:57:22 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m8M1vJQO026897; Mon, 22 Sep 2008 10:57:19 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 22 Sep 2008 10:57:19 +0900 From: PYUN Yong-Hyeon To: Bob Willcox Message-ID: <20080922015718.GB26294@cdnetworks.co.kr> References: <20080920042418.GB1322@rancor.immure.com> <20080920123914.GA72833@icarus.home.lan> <20080920132429.GA15275@rancor.immure.com> <20080920140456.GA74663@icarus.home.lan> <20080920144510.GB15275@rancor.immure.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080920144510.GB15275@rancor.immure.com> User-Agent: Mutt/1.4.2.1i Cc: Jeremy Chadwick , freebsd-stable@FreeBSD.org Subject: Re: RELENG_7 hangs on boot w/Gigabyte MA78GM-S2H MB X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 22 Sep 2008 01:59:38 -0000 On Sat, Sep 20, 2008 at 09:45:10AM -0500, Bob Willcox wrote: > On Sat, Sep 20, 2008 at 07:04:56AM -0700, Jeremy Chadwick wrote: > > On Sat, Sep 20, 2008 at 08:24:29AM -0500, Bob Willcox wrote: [...] > > > none3@pci0:2:0:0: class=0x020000 card=0xe0001458 chip=0x816810ec rev=0x02 hdr=0x00 > > > vendor = 'Realtek Semiconductor' > > > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > > > class = network > > > subclass = ethernet > > > > Regarding the Realtek issue: I've CC'd PYUN Yong-Hyeon (surname in > > caps), who maintains the re(4) driver for FreeBSD. He might have a > > patch available for you to try, or help determine how to get this NIC > > working on FreeBSD. He'll probably need more than just pciconf -lv > > output, but should be able to work with you. > > Ok, that'd be great. I must say that I'm close to simply returning this > MB and going with something not quite so new that is more likely to > work. I was hoping to get this system up and running this weekend. :( > There is one unresolved issue in re(4), some newer controllers does not respond to PHY access so re(4) fails to attach driver. If you can see a message like 'PHY write failed' in boot it indicates you're suffering from the issue. I have a local patch for this but it needs more testing as I don't have that hardware that exhibits the issue. Did you see the message? If you can't see 'PHY write failed' message during boot you might have a newer controller. Please post dmesg output for the case to add your device id to re(4). -- Regards, Pyun YongHyeon