From owner-freebsd-hardware@FreeBSD.ORG Thu Jun 7 05:45:50 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 10D3F106564A for ; Thu, 7 Jun 2012 05:45:50 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id BB9D88FC08 for ; Thu, 7 Jun 2012 05:45:49 +0000 (UTC) Received: by dadv36 with SMTP id v36so373458dad.13 for ; Wed, 06 Jun 2012 22:45:49 -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=uVw7DO3Nm+P+WoguGoJ2MhRFvyY+Kxpc0UC8ogIO56E=; b=CQJT6gfLGQPVN5DlGxKv4WRzaXoDwfeTIRksYQif1nz6JfnDrfJ4Ii5tV4XM5TnDo7 5S55tl8y/lQ7PtJuoiUqwybG/VZ1biKx4KL7pq1/bB4WlRqc2+rbNtko8zutC+nObMgz FdACnibqfPvaufMpI0t3fQBIm/sZu/uPL65wzH4hkTFBK5dsBC6bAafL5ZvLsD7kkCmU wHK3KFJWfQsfMlKhfNCyBd+pHqEjK42J3zn+5dVGo65i+r1WjtNEBlYcaiV2NElWLI5N uYr7cUh26lHQEgsdBVqVR3o/ZISawEGcXMUh/eekheqGgRFtOfPjpNU8BZM5gKxBvLnb u8HA== Received: by 10.68.204.227 with SMTP id lb3mr4852847pbc.92.1339047949246; Wed, 06 Jun 2012 22:45:49 -0700 (PDT) Received: from pyunyh@gmail.com ([114.111.62.249]) by mx.google.com with ESMTPS id kt1sm2911581pbc.32.2012.06.06.22.45.45 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 06 Jun 2012 22:45:47 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Thu, 07 Jun 2012 14:45:42 -0700 From: YongHyeon PYUN Date: Thu, 7 Jun 2012 14:45:42 -0700 To: Mike Tancsa Message-ID: <20120607214542.GE3834@michelle.cdnetworks.com> References: <4FC03C83.4030109@sentex.net> <20120601200942.GD10661@michelle.cdnetworks.com> <4FC8A903.6060203@sentex.net> <201206011030.52753.jhb@freebsd.org> <4FCA223F.5080009@sentex.net> <20120605004720.GB4010@michelle.cdnetworks.com> <4FCF9B42.4090100@sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4FCF9B42.4090100@sentex.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-hardware@freebsd.org Subject: Re: pcie realtek issue (re driver) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2012 05:45:50 -0000 On Wed, Jun 06, 2012 at 02:02:42PM -0400, Mike Tancsa wrote: > On 6/4/2012 8:47 PM, YongHyeon PYUN wrote: > > Hmm, Target abort/parity error looks serious to me. Could you > > remove re(4) driver in kernel and perform cold boot and check the > > AER errors again? > > (I assume your controller is not a stand-alone PCIe controller so > > I excluded resitting the controller). > > > Hi, > This is a stand alone card actually. Here it is after a power cycle. > Perhaps just a bad card ? Probably yes. For parity errors there is nothing can be done in driver side. It would be interesting to know how other operating systems handle this. > > none2@pci0:4:0:0: class=0x020000 card=0xffffffff chip=0x816810ec > rev=0x03 hdr=0x00 > vendor = 'Realtek Semiconductor Co., Ltd.' > device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller' > class = network > subclass = ethernet > bar [10] = type I/O Port, range 32, base 0, size 256, disabled > bar [18] = type Memory, range 64, base 0, size 4096, disabled > bar [20] = type Prefetchable Memory, range 64, base 0, size 16384, > disabled > cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0 > cap 05[50] = MSI supports 1 message, 64 bit > cap 10[70] = PCI-Express 2 endpoint IRQ 2 max data 128(128) link x1(x1) > cap 11[ac] = MSI-X supports 4 messages in maps 0x20 and 0x2c > PCI errors = Master Data Parity Error > Sent Target-Abort > Received Target-Abort > Received Master-Abort > Signalled System Error > Detected Parity Error